• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 653 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/AM3358: Unresolved symbols in CCS editor

Braden Hines
Intellectual 370 points

Part Number: AM3358

Tool/software: Code Composer Studio

I have configured CCS to do remote debugging on a Beaglebone host, using gdb.  It all works fine - I can build, run, set breakpoints.

But in the CCS editor, I see all these bug icons saying that system calls and #defines cannot be resolved:

This is not fatal, just distracting in amongst all the other information one tries to parse when running the code.  Any idea what's up?  This is happening with both functions like printf and symbols like O_RDWR which are defined in the #includes just a few lines above.

There is one other oddity which may or may not be related - I am only able to debug using "manual debug", using the Debug Configuration that I have created for working with my Beaglebone.  I haven't been able to figure out how to get a Remote Debugging session to work when I just click the Bug icon.  I've tried copying it into the appropriate folder using the instructions here, but it doesn't help.  I get the idea that Automatic Debugging sessions always need to be associated with a debug probe?  And since there isn't one for my GDB Remote Debug session, I can't figure out how to do Automatic debugging.

(FYI in case it matters, I am doing remote debugging and building from a Windows host.  It was challenging to get set up, but it works quite well now.  The trick was that I had to discover that the Linaro compiler is no longer the way to do it - you need to download the latest directly from ARM.  I then use the mingw-w64-i686-arm-none-linux-gnueabihf version of GDB.)

Thanks,
Brad

  • 0
    TI__Guru**** 483701 points

    Hi Brad,

    Braden Hines said:

    But in the CCS editor, I see all these bug icons saying that system calls and #defines cannot be resolved:

    Can you repost your screenshot? The link to it is broken. Please see the below FAQ if you still have troubles:

    https://e2e.ti.com/support/tools/ccs/f/81/t/821597

    Braden Hines said:
    There is one other oddity which may or may not be related - I am only able to debug using "manual debug", using the Debug Configuration that I have created for working with my Beaglebone.

    This is typically how I have done it in the past also. But this is because I have built the linux application outside CCS and only used CCS for debug purposes. I believe you should be able to somehow link that debug configuration with the project so that it will use it to launch the debug when you press the "Debug" button. I'll need to investigate this further.

    Thanks

    ki 

  • 0 in reply to Ki
    Intellectual 370 points

    Hi Ki,

    Here's the screen grab:

    Regarding the manual debug, I can report one other interesting thing.  When I copy the .launch file from the .metadata\.plugins\org.eclipse.debug.core\.launches folder to the project's .launches folder and then click the Bug icon, the newly copied .launch file actually gets *deleted* by CCS.  Then it throws an error about a ccxml file, that has nothing to do with this particular project, being missing.

  • 0 in reply to Braden Hines
    TI__Guru**** 483701 points

    Thanks. Those looks like CODAN errors (Eclipse/CDT static CODe ANalysis tool). They can generate many false positives, hence we typically disable it for CCS projects:

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

    What type of project are you working with? I assume it is not a CCS project. Is it a standard Eclipse CDT managed make project? 

  • 0 in reply to Ki
    Intellectual 370 points

    Thanks, Ki, that was helpful.  I unchecked and applied the setting.  It didn't fix it at first, but exiting and restarting CCS did the trick.

    Yeah, I used CCS to create the project, but the project type was "C++ project", I believe, approximately following the instructions here.

    Thanks,

    Brad