Topic : Rlink - No Hardware breakpoints available

Post Information	Post
May 26, 2015 - 4:59pm Guest account	Ride7 Version: 7.52.15.007 RKit-ARM for Ride 7 The problem is that when I try to debug I can't set any breakpoints. The breakpoint list is empty and I have also deleted all breakpoints. Sometimes I'm able to set one but if I make a step then I also get a message that there are no breakpoints available. If I then clear the breakpoint I can't set them anymore. What can I do? How am I supposed to debug if I can't set breakpoints?

Post Information	Post
+1 0 -1 May 26, 2015 - 5:00pm Etienne Cassin	Hello, The number of hardware breakpoints available depends on the target CPU. (STR7, STM32F4, STM32F0, LPC, LM3S, etc) Which CPU are you using? Also, C-level stepping tries to use breakpoints. If there are not enough left it gives you a message, but then you can tell it to perform the step in assembler steps. Did you try that? Which version of the RKit-ARM (not Ride) are you using? (it might be an old bug... ;/ ) One thing you can do to improve your debugging experience is to place the function(s) that you plan to debug in RAM. This uses more memory that it should, and usually the RAM is not big enough for holding the whole application, but there is no limit to the number of breakpoints that you can place in RAM, so debugging in RAM is much easier. Then after fixing the function you can put it back in flash for production. See this example for how to place a function in RAM using our tools: <Ride>\Examples\ARM\REva\REvaTest There are other examples for this, depending on your CPU and board. Search for "ramfunc". Disabling optimization can also improve debugging. (you can disable optimization for only one file or one function) I hope it helps. Best Regards, Vincent

Hello,

The number of hardware breakpoints available depends on the target CPU. (STR7, STM32F4, STM32F0, LPC, LM3S, etc)
Which CPU are you using?

Also, C-level stepping tries to use breakpoints. If there are not enough left it gives you a message, but then you can tell it to perform the step in assembler steps. Did you try that?

Which version of the RKit-ARM (not Ride) are you using? (it might be an old bug... ;/ )

One thing you can do to improve your debugging experience is to place the function(s) that you plan to debug in RAM. This uses more memory that it should, and usually the RAM is not big enough for holding the whole application, but there is no limit to the number of breakpoints that you can place in RAM, so debugging in RAM is much easier. Then after fixing the function you can put it back in flash for production.

See this example for how to place a function in RAM using our tools:
<Ride>\Examples\ARM\REva\REvaTest

There are other examples for this, depending on your CPU and board. Search for "ramfunc".

Disabling optimization can also improve debugging. (you can disable optimization for only one file or one function)

I hope it helps.

Best Regards,

Vincent