• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1212 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.

CCSv5 library debugging

Thomas S
Intellectual 600 points
Other Parts Discussed in Thread: TEST2

I have a project (Test2) which uses another library (driver.ae9: driver.c) (actually the driver is an own RTSC packet that is built with the external xdc tool suite).

However, I want to debug code in the driver.c file. Therefore I set a breackpoint in the driver.c file.

Unfortunately, the debugger does not stop on the requested breakpoint! I have to step through the code or find the desired label in the disassembly window.
This is very time consuming.

How would you suggest debuging interrupt handlers then?

Even the old CCS 3.3 was able to recognize breakpoints in library source files. When is CCS 5 going to support that?

regards

Thomas

  • 0
    TI__Guru**** 472441 points

    Hi Thomas,

    Thomas S said:
    Even the old CCS 3.3 was able to recognize breakpoints in library source files. When is CCS 5 going to support that?

    This functionality is supported in v5. Are you working with a debug library with debug symbols generated? Is the breakpoint actually getting properly set at the location you are setting it at? How did you open the source file to set the breakpoint? Do you have the library project open in your workspace?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hi ki

    Thanks for your reply.

    Actually the library is built with the xdc tool suite as mentioned (including the default "xdc.useModule('ti.targets.arm.elf.Arm9')" compiler suite for debugging).

    I do single steps until the debugger opens the refered file. Amazingly when I set a breakpoint in the disassembly file it appears in the "C"-file. But not the other way round.
    If I set a breakpoint in the "C"-file there is just a "small" one without any "symbolic"-address resolution (I had to do this manually).

    Do I have to set additional build options in the xdc tool suite?

    Unfortunately I can't find an "RTSC library Project" in CCSv5. So I created just a dummy project for source editing and build the library with command lines.

    Best regards

    Thomas

  • 0 in reply to Thomas S
    TI__Guru**** 472441 points

    Thomas,

    Are you using the CCSv5.1 release? There were some issues with source line breakpoints in earlier v5 builds so I just want to make sure you are not using some old v5 build.

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hi Ki

    Yes, I'm using CCSv5.1 . Today I'm gonna try the newest release from November 7. (CCSv5.1.09000)

    Thomas

  • 0 in reply to Thomas S
    Intellectual 600 points

    Hi Ki

    Here a screen shot of the breakpoint setting procedure:

    I have set the first breakpoint (line 269) in the Disassembly window. After entering the I2cSlave_Instance_init function I try to set further breakpoints (line 275) in the source code file! A "small" breakpoint marker appears in the source file and Disassembly window. But no "address resolution" is done. When I right click on the breakpoint in the breakpoint list above and select Breakpoint (Code Composer Studio) -> Breakpoint   CCS asks me to enter "Enter program location here (symbol or address)...".

    regards

    Thomas

  • 0 in reply to Thomas S
    Intellectual 600 points

    Hi.

    Unfortunately I haven't heard anything from ti side about this issue for a long time???!!!

    So I spent myself a couple of hours to reproduce the problem with a small example:

    6303.LibraryTest.zip

    Instructions:

    -Open 3 Projects: Test, LibraryBuild (normally I would build with command lines xdc suite), LibraryEdit
    -Build the LibraryBuild project
    -Build the Test project
    -Remove the LibraryBuild project from the Workspace
    -Start debugging the Test project. You won't be able to set breakpoints in the testlib.c source file.
    -If you remove the LibraryEdit project from the Workspace and start again debugging, you will be able to set breakpoints again in testlib.c

    This is just a simplified example of my projects.

    Actually, I have a driver library which I need to build with the xdc suite (Unfortunately there isn't a CCS project available for that yet!).
    Since I need to edit the source files of this library, I created a "LibraryEdit" similar project. Therefore I wasn't able to set breakpoints in those source files anymore.

    Is there a known workaround for this problem? (I found out, that if I create a CCS RTSC project for the "LibraryEdit" I don't get this issue)

    Are there any plans for a XDC build suite project type in CCS? Or at least support a simple project type for file editing, that doesn't show the described issues?

    regards
    Thomas