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.

after i clone the drive, CCS works weird

Other Parts Discussed in Thread: CCSTUDIO

My TM4C1294 project on HDD was working perfectly until I clone the drive.

After I clone my drive from HDD to SSD, everything works fine except CCS

In my project, I have many .C files and .H files, all the global #define are in .H files, such as 

mydef.h:

#define myoption

...

myproject.c:

#include "mydef.h" 

#ifdef myoption

mycodes..

#endif

After cloning, the project's .C files can still see the .H files, but it won't include any of the #define statements. In the above example, I can even click on mydef.h in the #include statement and open the file properly and see #define myoption, but in myproject.c, mycodes is always grayed out, as if myoption was never defined.

I've never seen such thing, and I tried multiple actions, such as renaming mydef.h, adding full file path to #include, nothing works

Could anyone give me some pointers? Thanks!

  • Hi David,

    If the project builds fine, but just an issue with code highlighting in the editor, can you try rebuilding the index for the project?

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#rebuild-index

    Thanks

    ki

  • I rebuild and refresh the index, same result.

    It may have built properly, but since the highliigh is a big mess, there is no way I can prove all the #if and #ifdef are processed properly. Both active block and non-active block defined conditionally by #if and #ifdef are highlighted, making it impossible to figure out which section of code is active

  • My CCS is 6.2.0.00050

  • My CCS is 6.2.0.00050

    This is a very old and unsupported version of CCS. I would try updating to a version more current.

    You can also try cleaning your workspace folder.

    ki

  • I have bad experience with upgrading CCS before, that's why i hardly upgrade

    i wonder if i can just upgrade CCS and leave the compiler, toolchain, etc alone

    if i take this path, where do i find the latest ccs without touching my compiler/library/toolchain/etc?

  • I have bad experience with upgrading CCS before, that's why i hardly upgrade

    Understood. Try cleaning the workspace folder first. Perhaps that will resolve the issue

    i wonder if i can just upgrade CCS and leave the compiler, toolchain, etc alone

    if i take this path, where do i find the latest ccs without touching my compiler/library/toolchain/etc?

    You can use older versions of the toolchain with a newer CCS IDE. What I recommend is to leave your 6.2 installation alone and then install CCS 10.3 in a different directory. Then you can point your CCS 10.3 installation to use the compiler from 6.2 by specifying the discovery path to the compiler that comes in 6.2:

    https://software-dl.ti.com/ccs/esd/documents/ccs_compiler-installation-selection.html#compiler-discovery

  • I would like to try your suggestion to install 10.3

    After specifying the compiler, how do i specify 10.3 to use the original library toolchain source?

  • Installed 10.3 and imported the project and switched to CCSV6/tools/compiler

    When I build the project, got the following errors, any chance for you to give me some pointers?

    gmake: Target 'all' not remade because of errors.
    unresolved symbol __aeabi_ldivmod, first referenced in ./a2d.obj
    unresolved symbol __TI_decompress_none
    unresolved symbol __TI_decompress_rle24
    unresolved symbol __TI_zero_init
    unresolved symbol memcmp, first referenced in ./utils/lwiplib.obj
    unresolved symbol memcpy, first referenced in ./enet_fs.obj
    unresolved symbol memset, first referenced in ./pga.obj
    unresolved symbol strcpy, first referenced in ./eepr.obj
    unresolved symbol strlen, first referenced in ./atoi.obj

    <Linking>
    error #16004-D: file "./usb_dev_bulk.obj" has a Tag_ABI_VFP_args attribute value of "3" that is different than one previously seen ("1"); combining incompatible files
    error #16004-D: file "./ushell_task.obj" has a Tag_ABI_VFP_args attribute value of "3" that is different than one previously seen ("1"); combining incompatible files
    error #16004-D: file "./utilities.obj" has a Tag_ABI_VFP_args attribute value of "3" that is different than one previously seen ("1"); combining incompatible files
    error #16004-D: file "./xusb_host_msc.obj" has a Tag_ABI_VFP_args attribute value of "3" that is different than one previously seen ("1"); combining incompatible files
    error #16004-D: file "./utils/ustdlib.obj" has a Tag_ABI_VFP_args attribute value of "3" that is different than one previously seen ("1"); combining incompatible files
    warning #10204-D: automatic RTS selection: could not resolve index library "libc.a" to a compatible library
    error #10234-D: unresolved symbols remain
    "../enet_lwip_ccs.cmd", line 74: error #10104: undefined symbol "__stack" used in expression

  • Can you provide your full build output. I would like to see everything in the build console. You can copy&paste to a text file and attach the file to this thread.

    Thanks

    ki

  • Hi David,

    Let's work on one thing at a time in this thread. Can you provide the build output for the other project? I split other post to a new thread

  • After a clean rebuild, these errors disappeared. it may actually work (maybe the .obj files built by ccs 6 is not compatible with 10), I need to check 

    To check it, I need to build the full project in a batch file

    Here is what I do with CCS6 (one line in a long batch file)

    C:\ti\ccsv6\eclipse\eclipsec -noSplash -data "C:\Users\chen window 10\workspace_v6_2" -application com.ti.ccstudio.apps.projectBuild -ccs.projects usb_udp_thumb_tryout_214 -ccs.configuration x4108

    Do I simply change ccsv6 to ccs10?

    C:\ti\ccs1031\ccs\eclipse\eclipsec -noSplash -data "C:\Users\chen window 10\workspace_v10" -application com.ti.ccstudio.apps.projectBuild -ccs.projects usb_udp_thumb_tryout_214 -ccs.configuration x4108

    Do I need any extra switch?

  • The command-line build system should work the same between the versions. 

    One suggestion. I noticed that your username has spaces in it. This sometimes can cause issues:

    https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/740719/faq-ccs-why-do-i-need-to-avoid-non-alphanumeric-unicode-characters-in-my-paths?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

    Thanks

    ki