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

CODECOMPOSER: PC Trace Sometimes Does Not Show The Correct Disassembly

Kier
Mastermind 9520 points

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: AM2634

Hello,

I'm using AM2634.

In the screenshot below, the Disassembly in the PC Trace does not match actual the Disassembly window:

Sometimes it does match as shown here:

To be honest, I'm no assembler expert but my hunch is that it is wrong. Why doesn't it match sometimes please?

  • +1
    TI__Guru**** 475381 points

    Hello,

    Kier said:
    Why doesn't it match sometimes please?

    The trace view actually uses a different (older) symbol manager than the CCS debugger. If you are using the TI ARM clang compiler, the symbol manager used by the CCS debugger has much better support for clang output than then trace view. This would explain why the contents disassembly view is more accurate.

    In your first screenshot, the first discrepancy you pointed out is an example of how the older symbol manager used by the trace view is unable to decode the opcode and hence just has ".word" with the opcode. 

    Note that this inconsistency with the symbol managers is just an issue with CCS Eclipse. The trace functionality in CCS Theia will use the same symbol manager as the CCS debugger.

    Thanks

    ki

  • 0 in reply to Ki
    Mastermind 9520 points

    Thanks for the explanation. I guess I'll just put up with it until I'm able to use Theia.