CPU stuck after starting debugger

RE: CPU stuck after starting debugger

diogodias — Wed, 19 Jul 2023 11:52:36 GMT

ok, thank you

RE: CPU stuck after starting debugger

Sigurd Hellesvik — Wed, 19 Jul 2023 11:44:34 GMT

I got information from our developers on how to debug the SPU further:

"
the DEFAULT irq handler does not produce enough information to be able to debug. RAMACCERR triggers if the SPU config is violated. To see where the PC is when the RAMACCERR triggers you need to cherry-pick this fix: https://github.com/nrfconnect/sdk-nrf/pull/11723 (with accompanying patches to TF-M). And enable logging with these Kconfigs: https://github.com/SebastianBoe/fw-nrfconnect-nrf-1/commit/a912e335e725ab31bc282e90ddc2662086b6549e#diff-d083cad8c190cd70f8ac39cfa495d2e3be7088b264311f68e6e3a85ca5ed2be6R103

RE: CPU stuck after starting debugger

diogodias — Wed, 19 Jul 2023 11:18:40 GMT

Hello.
No, I tried 2 examples and it didn't happen.
Yes, my code has a bootloader.
Yes, I tried unchecking the "Enable debug options" and it fixed the problem, however, I would like to have that option enabled.
No, I don't use USB.
Sure, the registers:

RE: CPU stuck after starting debugger

Sigurd Hellesvik — Wed, 19 Jul 2023 09:19:24 GMT

Hi,

Do you see the same issue for our examples as well?

Does you code have a bootloader?

Does your code work if you do not have debugging enabled?

Do you use USB in your application or bootloader?

Can you have a look at the SPU registers in the IRQ handler and give me a screenshot?
Something like this:

Regards,
Sigurd Hellesvik