imx7ulp a7 blocks and watchdog is not triggered when m4 is down

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx7ulp a7 blocks and watchdog is not triggered when m4 is down

503 Views
Louson
Contributor I

Hello,

I am using the imx7ulp in dual memory boot. The A7 and the M4 boot separately.

If I erase the M4's memory (in uboot):

U-Boot > sf probe
U-Boot > sf erase 0x0 0x30000; 

The boot fails in kernel space, main errors are concerning rpmsg :

[ 18.257919] imx_rpmsg_rtc rtc-rpmsg: hctosys: unable to read the hardware clock

It seems fine to me that the A7 does not boot because the rpmsg connection is not established. But I supposed the watchdog should trigger after its period (40s). Instead, the core remains alive but in a dead-end.

I'd like my board to reset at that point and fall back to uboot.

I tried to play with the configs CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED and CONFIG_WATCHDOG_OPEN_TIMEOUT but it didn't affect anything.

Any idea ?

0 Kudos
1 Reply

487 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

I would like to know, which Linux version you're running for your test?

Also, have you enabled in menuconfig the following?
Device Drivers > Watchdog Timer Support > IMX7ULP Watchdog.

Providing the complete log would be good as well.

Regards,
Aldo.

0 Kudos