• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 56 subscribers
  • Views 8035 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.

Can't set breakpoints in C source files

Jared55122
Prodigy 70 points
Other Parts Discussed in Thread: TMS320F28335

I recently upgraded to code composer studio 4.2.1.00004.  Since the upgrade I am unable to set breakpoints in the C source code windows.  The breakpoints still work in the disassembly (main) window and I can flash the TMS320F28335 microcontroller with updated code, so i belive my hardware and the XDS510 USB JTAG to be working.  When I try to set a breakpoint in a C source window and enable it, I get the following breakpoint manager error msg:

"No code is associated with "C:/a_long_path_chain/my_file.c" line 81 in any loaded symbols.

any suggestions on how to correct this? 

Sincerely,

Jared

  • 0
    TI__Genius 16510 points

    CCS is not finding any symbolic debug info for the outfie you have loaded. The DWARF debug info is encoded in the outfile if you have turned on generation of this info in the compiler options, optimizations have not caused the source code area of interest to be removed, and the DWARF info has not been stripped in a post -build step. As a start, please check that your project build options include "-g" or "--symdebug:dwarf".

  • 0 in reply to AndyW
    Prodigy 70 points

    Andy,

    I checked the C2000 compiler options and it was not set to "Full symbolic debug ((--symdebug:dwarf, -g).  I restored this setting and the breakpoints appear to be working again.  Thank you for your assistance. 

    Sincerely,

    Jared

  • 0 in reply to AndyW
    Intellectual 560 points

    I am seeing the same problem with CCS V5.0.2 even with "Full symbolic debug ((--symdebug:dwarf, -g)." enabled, and I am using XDS510 USB PLUS for DM8148 board, I believe the symbol .map file was loaded everytime when I load the .out file.   But the breakpoint can be toggled, not "enabled", or else the same error message will show up.

    It cannot be enabled either as hardware or software breakpoint, and I don't know the difference between C/C++ breakpoint vs. CCS breakpoint either?

    Could you please help me out?

    Thanks,

    Philip

  • 0 in reply to Tianhua Chu
    TI__Genius 16520 points

    Hi Phillip,

    C/C++ breakpoint is meant for gdb debugger breakpoint and CCS breakpoint is for TI debugger breakpoint. These options dictates the toggle (double clicks) breakpoint action in the editor, outline view, project view, etc... We are working with the open source community to make things easier, so you don't need to switch betwen these options when you toggle breakpoint.

    Patrick 

  • 0 in reply to Patrick Chuong
    Intellectual 560 points

    Thanks for your reply.

    The issue is still the error message comes up when I try to enable the breakpoint in my c code. I don't know what kind of steps needed to let CCS know the symbol file is there?

     

    Regards,

    Philip

     

  • 0 in reply to Tianhua Chu
    TI__Guru**** 471801 points

    Try going to mixed mode in the disassembly view and see if you see assembly instructions associated with the source file you are trying to set a breakpoint at.

  • 0 in reply to Ki
    Intellectual 560 points

    Yes I am seeing that breakpoints can be enabled in the assembly instructions with the source files in the mixed mode.

    I think it is because I am using source files in a "linked folder" under my CCS project file, physically my source files exist in other directories.

    In this case, when I open the file from the  "linked folder", I cannot enable breakpoint, but go to a line and right click to "Code Composer Studio Breakpoiont" -->Breakpoint to set the breakpoint. But it will not show in the source file, instead in the breakpoint tab from debug perspective, it will show up. Now if I choose "go to file" on a row from the breakpoint table, it brings me to the source file, in term of the absolute path. In this file opened, the breakpoint shows there. But when the program is being debugged, the current PC cursor does not show up in this "absolute" file, but only in the "linked folder" file.

    So, looks like, if a "linked folder" is used to hold source files, breakpoint cannot be put on the source code. On the otherhand, the PC cusor always sticks on the source code opened from the relative subdirectory ("linked folder" ). They just don't come together.

    I don't know if this is a defect or there is something I can do to overcome it?

     

    Thanks,

    Philip

     

     

  • 0 in reply to Tianhua Chu
    Prodigy 70 points

    I am having the same issue - was a solution ever found?  Thanks,