This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The debugger has set two breakpoints at the same address

J-Link V6.12d API Warning
Debugger problem discovered:
The debugger has set two breakpoints at the same address xxxxxx.
------

I use Tessy to do unit test work with Keil uvision. The breakpoint is set by the test
software Tessy at its communication function. In fact, it can run well at Keil Simulator
without Jlink. And now this warning appears with Jlink connecting. Anyway, If I keep
clicking the OK of the warning to go on the test, it can go to the last.

I wonder is there any suggestion to solve this , or how can I just simply disable the
warning?

Parents
  • That's getting to be a bit of a reach.

    Most probable is that the test tool is trying to set break-points to different lines in the code, but either those lines don't generate code, or the optimizer re-arranges or folds things in such a way that the two requests fall on exactly the same code address. If the tools is trying to do this as a way of single stepping or profiling, then it really should be sufficiently aware that the line-to-address translation isn't always going to result in a unique address, or in-order.

    You should discuss with the Tessy developers what their expectations are, and if they have sufficient visibility to see that they are trying to set two breakpoints at the same address.

    Keil has direct support contact points, use those, not the forum.

Reply
  • That's getting to be a bit of a reach.

    Most probable is that the test tool is trying to set break-points to different lines in the code, but either those lines don't generate code, or the optimizer re-arranges or folds things in such a way that the two requests fall on exactly the same code address. If the tools is trying to do this as a way of single stepping or profiling, then it really should be sufficiently aware that the line-to-address translation isn't always going to result in a unique address, or in-order.

    You should discuss with the Tessy developers what their expectations are, and if they have sufficient visibility to see that they are trying to set two breakpoints at the same address.

    Keil has direct support contact points, use those, not the forum.

Children
No data