• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 1470 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.

CC C3x-C4x Only steps through disassembly for main

Frank Sibley
Prodigy 20 points


I'm developing on an embedded TMS320C33 using Code Composer 4.10.37 (not Code Composer Studio). After loading the project on the target, I select Debug-->Go Main, but only the Dis-Assembly window with the current PC opens, not the main.c file. Even if I manually open main.c and set a breakpoint in it, I can only step through the dis-assembly window. Other c files in the project don't have this problem: if I step into another file's function from the main dis-assembly, the correct c file opens allowing me to then step-through the c code. I checked all Build Options, and verified I'm generating symbolic debug information; all symbols are global; and that I'm running in RAM.

Thanks for any help.

  • 0
    TI__Guru**** 162895 points

    Frank,

    If you right click on main.c and select mixed-mode does it interleave the assembly for you?  It seems like just for this one file that source association has been lost.  You have already checked that symbolic info is on. You could move the function into a file that is working ok and see if that resolves the problem.

    This toolset is really old.  It could be a bug in the way we were generating debug info or the way the debugger was reading it.  Hopefully moving the function will work around the issue.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 20 points

    Figured out the issue: Some of my file names (including the main c file) had capital letters (for example my main was in a file called "MainProcess.c"). When CC generates the object file, it changes all letters to lower-case ("mainprocess.c") and therefore cannot cross-reference the symbols with the capital-lettered source file.

    Once I changed all my files to lower-case, everything debugs fine.

    Old toolset indeed!

  • 0 in reply to Frank Sibley
    TI__Guru**** 162895 points

    Glad you caught it.  Watch out for spaces in paths and file names as well.  The old tools definitely will not like that.