• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 261 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.

TMS320F28054F: ESTOP0 and Hardware Breakpoints Not Triggering in CCS Theia (Works Fine in CCSv8)

Justus Weinhold
Prodigy 10 points

Part Number: TMS320F28054F

Tool/software:

Dear Engineers,

I am working on a C2000 device (please specify exact device, e.g., TMS320F2837x) and have recently migrated my development environment from CCSv8 to CCS Theia. In CCSv8, I was able to place a software breakpoint using the __asm(" ESTOP0") instruction and also set hardware breakpoints at that same location without any issues. The processor would halt execution as expected.

After switching to CCS Theia, I can confirm that the code path containing the ESTOP0 instruction is indeed reached, but the program does not stop. Additionally, I cannot set a hardware breakpoint at that location in CCS Theia. Both of these approaches worked flawlessly in CCSv8.

I have verified the following:

  • The debugger connection is active and targeting the correct core.
  • The code containing ESTOP0 is present in the final binary (verified via disassembly).
  • Real-Time mode is disabled.
  • __asm volatile(" ESTOP0") was also tried.
  • The same setup (hardware, device, probe) worked under CCSv8 without changes.

Are there known differences, limitations, or additional settings required in CCS Theia for software and hardware breakpoints on C2000 devices? Any guidance, known issues, or configuration tips would be greatly appreciated.

Thank you in advice!