github-mirrors/neorv32
1
0
Fork 0
mirror of https://github.com/stnolting/neorv32.git synced 2025-04-24 22:27:21 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

[ug] add note: hardcoded EBREAK instructions

Browse source
This commit is contained in:
stnolting 2022-05-28 18:59:46 +02:00
parent 9e48a5370d
commit 3d9a7645eb
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/userguide/debugging_with_ocd.adoc
View file

@ -249,11 +249,12 @@ Breakpoint 1, 0x00000690 in neorv32_cpu_delay_ms ()
Continuing.
--------------------------
.BREAK instructions in your program code
.Hardcoded EBREAK Instructions In The Program Code
[TIP]
If your original application code uses the BREAK instruction (for example for some OS calls/signaling) this
instruction will cause an enter to debug mode when executed. These situation cannot be continued using gdb's
`c` command and have to be "stepped-over" using the single-step command `s`.
`c` nor can they be "stepped-over" using the single-step command `s`. You need to declare the `ebreak` instruction
as breakpoint to be able to resume operation after executing it. See https://sourceware.org/pipermail/gdb/2021-January/049125.html
:sectnums: