I'm working with Vybrid VF61x SoC, and debugging code on the M4 core running MQX.
I would like to single-step some code in an ISR, and while I can set the break point and break into the ISR, after that the debugger seems gets stuck,
I cannot resume the CPU or single step, and thus can only abort the session.
I see JLinkGDBServer output on console as-if stuck in some infinite loop, tracing at fast rate as for e.g.:
Read 4 bytes @ address 0x3F802804 (Data = 0x3F00062D)
Read 4 bytes @ address 0x3F802804 (Data = 0x3F00062D)
....
<repeat .... >
I still can Cntrl-C it, and kill the connection to JLink and so the IDE's connection to the debugger luckily exists gracefully.
Any idea what is going on? What is special setting I'm missing or way to enable setting a break point in an ISR here?
I would like to single-step some code in an ISR, and while I can set the break point and break into the ISR, after that the debugger seems gets stuck,
I cannot resume the CPU or single step, and thus can only abort the session.
I see JLinkGDBServer output on console as-if stuck in some infinite loop, tracing at fast rate as for e.g.:
Read 4 bytes @ address 0x3F802804 (Data = 0x3F00062D)
Read 4 bytes @ address 0x3F802804 (Data = 0x3F00062D)
....
<repeat .... >
I still can Cntrl-C it, and kill the connection to JLink and so the IDE's connection to the debugger luckily exists gracefully.
Any idea what is going on? What is special setting I'm missing or way to enable setting a break point in an ISR here?