• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 667 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS 5.1.0.08012 Linux - Xdctools Default Permissions.

zborgerd
Prodigy 90 points

CCS 5.1.0.08012 Linux - Default permissions on a clean install of CCS result in the following while building the "Hello World" DSP/BIOS example for an F28069 Piccolo controlStick.

**** Build of configuration Debug for project DSPBIOS Hello ****

/usr/local/CCSv5/ccsv5/utils/bin/gmake -k all
Building file: ../hello.tcf
Invoking: TConf Script Compiler
"/usr/local/CCSv5/xdctools_3_22_02_27/tconf" -b -Dconfig.importPath="/usr/local/CCSv5/bios_5_41_10_36/packages;" "../hello.tcf"
/bin/sh: /usr/local/CCSv5/xdctools_3_22_02_27/tconf: Permission denied
gmake: *** [hellocfg.cmd] Error 126
gmake: Target `all' not remade because of errors.

**** Build Finished ****

 

I worked around this by making tconf and tconf.x86U executable (chmod +x).

Should this be made executable by default?  If so, then this may be a bug, albeit a trivial one.  There are several other tools in the folder that are not executable by default after install.  CCS was installed as root with the method described in the installation instructions, and was only ever run as a user.

 

After:

**** Build of configuration Debug for project DSPBIOS Hello ****

/usr/local/CCSv5/ccsv5/utils/bin/gmake -k all
Building file: ../hello.tcf
Invoking: TConf Script Compiler
"/usr/local/CCSv5/xdctools_3_22_02_27/tconf" -b -Dconfig.importPath="/usr/local/CCSv5/bios_5_41_10_36/packages;" "../hello.tcf"
Finished building: ../hello.tcf
 
Building file: ../hello.c
Invoking: C2000 Compiler
"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -mt -ml -g --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/c2000/include" --include_path="/home/zborgerd/workspace_v5_1/DSPBIOS Hello/Debug" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/bios/include" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/rtdx/include/c2000" --diag_warning=225 --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 --preproc_with_compile --preproc_dependency="hello.pp"  "../hello.c"
Finished building: ../hello.c
 
Building file: hellocfg.s??
Invoking: C2000 Compiler
"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -mt -ml -g --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/c2000/include" --include_path="/home/zborgerd/workspace_v5_1/DSPBIOS Hello/Debug" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/bios/include" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/rtdx/include/c2000" --diag_warning=225 --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 --preproc_with_compile --preproc_dependency="hellocfg.pp"  "hellocfg.s28"
Finished building: hellocfg.s??
 
Building file: hellocfg_c.c
Invoking: C2000 Compiler
"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -mt -ml -g --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/c2000/include" --include_path="/home/zborgerd/workspace_v5_1/DSPBIOS Hello/Debug" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/bios/include" --include_path="/usr/local/CCSv5/bios_5_41_10_36/packages/ti/rtdx/include/c2000" --diag_warning=225 --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 --preproc_with_compile --preproc_dependency="hellocfg_c.pp"  "hellocfg_c.c"
Finished building: hellocfg_c.c
 
Building target: DSPBIOS Hello.out
Invoking: C2000 Linker
"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -mt -ml -g --diag_warning=225 --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 -z -m"DSPBIOS Hello.map" --stack_size=0x300 --warn_sections -i"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/lib" -i"/usr/local/CCSv5/ccsv5/tools/compiler/c2000/include" -i"/usr/local/CCSv5/bios_5_41_10_36/packages/ti/rtdx/lib/c2000" -i"/usr/local/CCSv5/bios_5_41_10_36/packages/ti/bios/lib" --reread_libs --rom_model -o "DSPBIOS Hello.out" -l"./hellocfg.cmd"  "./hellocfg_c.obj" "./hellocfg.obj" "./hello.obj" -l"libc.a"
<Linking>
Finished building target: DSPBIOS Hello.out
 

**** Build Finished ****

  • 0
    TI__Guru**** 173310 points

    The version of BIOS and xdctools you are using are the ones packaged with CCS 5.1.0.07001, and yes, this is a known bug in the Linux version of that build. The permissions of all the executables in the xdctools folder are missing the execute permissions. You can workaround it temporarily, as you noted, by adding execute permission to the executables in the xdctools folder.

    This bug is fixed in the 5.1.0.08012 build for Linux, however, there is now a new problem with that version in starting up CCS. Please see this post for details: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/137678.aspx.

    We hope to get these issues resolved as soon as possible, and we appreciate your patience and understanding while we work through them.

  • 0 in reply to AartiG
    Prodigy 90 points

    Thanks for the info.

     

    Weird.  I must have some residual files from the upgrade process (I thought that I uninstalled everything).  So now I guess I have a hybrid version between the two.

     

    What's the recommended method for updating to a new beta release?  Should I uninstall any old versions before installing a new version, or is it generally acceptable to upgrade an existing version?  Is there anything that's installed anywhere aside from /usr/local/CCSv5 ?  I think that I did see some udev rules in the typical location in /etc, but didn't poke around too much to see what else was installed.  Is the uninstall process generally deemed to be reliable at this point?

     

    Thanks.

  • 0 in reply to zborgerd
    TI__Guru**** 173310 points

    zborgerd said:
    What's the recommended method for updating to a new beta release?  Should I uninstall any old versions before installing a new version, or is it generally acceptable to upgrade an existing version? 

    For the beta releases, there isn't an update path. You need to uninstall and reinstall if you want to install to the same folder, or you can keep more than two versions installed at the same time in different folders. For uninstalling, I usually run uninstall_CCSv5 from within the /ccsv5 folder. This works quite nicely and reliably. If any files/folders happen to be left behind you can just delete them.