• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 1465 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 V5, EM430F6137RF900 Software Breakpoint

KC57012
Prodigy 110 points

Hello,

I am currently using CCS V5 Beta with EM430F6137RF900 dev board.

Here's an article that I want to implement with the system that we have here;

http://processors.wiki.ti.com/index.php/Software_Breakpoints_in_the_IDE

However, with the dev tools that I have, it does not look like it supports any of the ESTOP assembly instructions.

I looked at the manual to see if they had any similar instructions, but I could not find one.

Is there a way to implement a software breakpoints described in the page with EM430F6137RF900 and CCS V5?

 

Thank you!

  • 0
    Guru 227245 points

    The MSP430 does not support software breakpoints as described.
    So the sentence 'every TI architecture has this' in this article is wrong.

    However,m there are two ways to implement this kind of software breakpoints with little effort.

    First, you can define a function
    void estop(void);

    You can set a breakpoint inside this function and call it whereever you want a breakpoint.
    It includes, however, a function call, so compiler optimizations are affected and you'll need to return from the function with single-stepping to get back to the point you wanted the breakpoint.
    But it is the most simple way and always works.

    the more complicated way is to define a global variable ESTOP and set a read trigger on it. Each time you read the variable, a breakpoint is triggered. A read trigger, so no breakpoint is triggered on variable init (where it is written to). Of course, any read-modify-write instruction (such as ESTOP++ in C or ADD #0,&ESTOP in ASM) will trigger the breakpoint.

    Don't ask me how to set this kind of breakpoints in the different IDEs, I don't use any of them. I only know that the EEM inside the MSPs supports this.

**Attention** This is a public forum