• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 379 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.

LP-AM243: CCS: How to Debug dependency libraries

Tony Josi
Prodigy 30 points
Part Number: LP-AM243


Hi,

Code Composer Studio - Version: 12.3.0.00005

I have a main project that uses another CCS static library project as a dependency [ Main Project -> Properties -> CCS Build -> Dependencies], the main project links the library and works fine on the target device, however if I try to set a breakpoint anywhere in the dependency static library I get the following error popup:

Following image shows the full project in the IDE:

Is it possible to debug dependency libraries like that? Is there any other way to do it?

Thanks 

  • 0
    TI__Guru 55485 points

    Hi Tony,

    You can debug the library, but you may need to tell CCS where the source files are located, by default, CCS assumes the library source is in the same place as the application code (in CCS workspace), but the library source is in the SDK install location. You only need to do it once though.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Prodigy 30 points

    Hi Ming, 

    Thanks for the response. The library that I have created is not taking source files from the SDK install location instead I have local copy of the source files in the static library project folder itself. Those local copies are what I use to build the library. If the files are local copies I believe the IDE won't have any trouble identifying the files in the library. But I think the problem is for the main project that finally build the executable (.out) using the dependency to identify were those debug symbols are when I keep a breakpoint in the library source files.

    Thanks

    Tony

  • 0 in reply to Tony Josi
    TI__Guru 55485 points

    Hi Tony, 

    What is the content of the line 604 of tcpip.c? It must be calling some other functions which are not defined in your local copy.

    It is better to keep the source code for all the libraries in the SDK install location.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Prodigy 30 points

    Hi Ming,

    The line 604 in tcpip.c is calling an internal function defined in the library itself (lwip_init()). I have verified that its defined in the static library sources.

    I'm trying to create a local copy of the library as a dependency project locally because I wanted to modify one of the libraries, and didn't want those changes to affect the files in the SDK install path.

    Thanks

  • 0 in reply to Tony Josi
    TI__Guru 55485 points

    Hi Tony,

    There are two things I can think of right now:

    1. Where the library path in your CCS Linker option points to? The workspace or the SDK install location?

    2. Can you set the break point at 604 of tcpip.c and single step (F5) into the lwip_init? Hopefully CCS will ask you to input the source path again.

    Best regards,

    Ming