Debug address space question

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Debug address space question

788件の閲覧回数
mspenard603
Contributor IV

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?

Untitled.png

0 件の賞賛
返信
3 返答(返信)

767件の閲覧回数
mspenard603
Contributor IV

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.

0 件の賞賛
返信

776件の閲覧回数
mspenard603
Contributor IV

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

How can I more properly handle when that happens?

0 件の賞賛
返信

780件の閲覧回数
mspenard603
Contributor IV

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

0 件の賞賛
返信