Dec 08, 2020
11:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 08, 2020
11:27 PM
Hello everyone,
I found that when the MCU is suspended by a DEBUG instruction in debug mode, the Run, Step In and Step Over will not work anymore. The code execution will be always stuck at this DEBUG instruction.
Is the DEBUG instruction skippable? Or should I use something else to implement the software breakpoint similar to ARM's BKPT instruction?
Thanks.
I found that when the MCU is suspended by a DEBUG instruction in debug mode, the Run, Step In and Step Over will not work anymore. The code execution will be always stuck at this DEBUG instruction.
Is the DEBUG instruction skippable? Or should I use something else to implement the software breakpoint similar to ARM's BKPT instruction?
Thanks.
3 Replies
Dec 09, 2020
10:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 09, 2020
10:51 AM
I'm not sure what debugger you're using, but you can force the PC register to be somewhere else. In iSYSTEM for example, you can right-click on an instruction and "goto".
Dec 09, 2020
06:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 09, 2020
06:40 PM
UC_wrangler wrote:
I'm not sure what debugger you're using, but you can force the PC register to be somewhere else. In iSYSTEM for example, you can right-click on an instruction and "goto".
I'm using the miniWiggler debugger on TriBoard TC233 and Application Kit TC297 board.
Modifying the PC register takes effect, but it's a bit cumbersome.
And I tried the "Run to Line" in Debug menu in AURIX Development Studio. It still cannot skip the DEBUG instruction.
Dec 10, 2020
01:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 10, 2020
01:52 AM
There is no automatic skip of any instruction available. You must set the PC manually to the instruction behind the debug instruction or ask the debugger vendor to add such a feature. Please note that the debug instruction will be interpreted as nop only when the OCDS is switched off and there is no debugger connected.