• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1027 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP430G2452: Debugging MSP430 assembly-only code - missing RAM symbols

Jonathan Guy1
Prodigy 90 points
Part Number: MSP430G2452

Tool/software: Code Composer Studio

I'm debugging MSP430 assembly code (no C). Debugging works fine, but I'd really like to be able to evaluate RAM variables without having to resort to looking up the address and using the memory browser. Does assembly-only debug in CCS provide symbolic representation of RAM variables? It seems like there should be a way to make this happen.

  • 0
    TI__Intellectual 2625 points

    The debugger relies on debug information generated by the compiler to display the values of variables.

    If you write in assembly code only, your assembler tool must have the capability to generate debug info. 

    For TI assembler, you may use debug directives to ask the tool to generate debug info.

    -Raymond.

  • 0 in reply to Raymond Pang
    Prodigy 90 points

    For anyone else that has this issue, the problem with no symbolic info appears to be due to COFF vs ELF. This was an old project and because CCS couldn't find the older tools, it defaulted to the newer (ELF) copiler. The binary worked but the assembly symbols were not available, presumably because CCS expected COFF. Once I fixed the path to the older 3.3.x compiler, symbols are now available during assembly debugging.