topic Debug address space question in i.MX RT Crossover MCUs

Debug address space question

mspenard603 — Wed, 12 Apr 2023 13:48:34 GMT

Hi,
iMXRT1062, MCUxpresso v11.7.0, SDK 2.12.1

My application locks up and Debug shows it in various 0x2xxxxx addresses as seen below.

I have a watchdog, which never triggers. And a HardFault_Handler() and BusFault_Handler defined which never gets hit either. Nor are the fault registers showing anything. DWT continues to count up and PC continues to move. So I'm a bit confused what is going on.

ITC is from 0x0 to 0x20000. So it's not in there. Is 0x20d108 anything?

Re: Debug address space question

mspenard603 — Wed, 12 Apr 2023 15:10:14 GMT

Oh, its BootROM. So how/why would an application jump there? And how do I guard against this? As it's overriding my Watchdog.

Re: Debug address space question

mspenard603 — Wed, 12 Apr 2023 17:00:48 GMT

SRC->SRSR = 0x2. I.e., the lockup_sysresetreq bit is set.

How can I more properly handle when that happens?

Re: Debug address space question

mspenard603 — Thu, 13 Apr 2023 12:26:01 GMT

Hrm, it's spinning its wheels in BootROM on XIP flash boards. But on generic QSPI flash it reboots. I assume that's because the CPU Lockup reset sequence doesn't provide the needed JEDEC reset sequence XIP flash needs? I don't suppose there's a way for CPU Lockup reset to reset XIP as well is there?

Regardless, is there a way I can customize what happens with CPU Lockup? I'd like the watchdog to always handle everything.