I am working on an embedded product using the RPi 5, booting via U-Boot. I am working on migrating my CM4 based solution using Buildroot and RAUC to the RPi 5 and I am having an issue enabling the watchdog timer.
With `dtparam=watchdog=on` in the config.txt file, the CM4 properly enables the watchdog timer and the system will automatically reboot if it takes too long for Linux to boot and start 'petting' the watchdog (eg: I drop to a u-boot shell or the kernel crashes when loading).
On the RPi 5, the same `dtparam=watchdog=on` results in the following debug output from the boot loader:
Is there a way to enable the watchdog timer via firmware like there is for the CM4?
With `dtparam=watchdog=on` in the config.txt file, the CM4 properly enables the watchdog timer and the system will automatically reboot if it takes too long for Linux to boot and start 'petting' the watchdog (eg: I drop to a u-boot shell or the kernel crashes when loading).
On the RPi 5, the same `dtparam=watchdog=on` results in the following debug output from the boot loader:
Code:
124.40 MESS:00:02:04.040842:0: dtb_file 'bcm2712-rpi-5-b.dtb'124.46 MESS:00:02:04.046088:0: dtdebug: Trying Device Tree file 'bcm2712-rpi-5-b.dtb'124.53 Loading 'bcm2712-rpi-5-b.dtb' to 0x00000000 offset 0x100124.64 Read bcm2712-rpi-5-b.dtb bytes 81163 hnd 0x2124.82 MESS:00:02:04.082963:0: dtdebug: delete_node(/__local_fixups__)124.23 Read /overlays/overlay_map.dtb bytes 5451 hnd 0x1aa124.26 MESS:00:02:04.126424:0: dtdebug: using platform 'bcm2712'124.35 MESS:00:02:04.135070:0: dtdebug: overlay map loaded124.64 PCIEx1: PWR 0 DET_WAKE 0124.77 Read /config.txt bytes 2245 hnd 0x263124.78 MESS:00:02:04.178617:0: dtparam: watchdog=on124.87 MESS:00:02:04.187725:0: dtdebug: /__overrides__ has no watchdog property124.91 MESS:00:02:04.191939:0: Unknown dtparam 'watchdog' - ignoredStatistics: Posted by cdsteinkuehler — Tue Mar 18, 2025 2:14 pm — Replies 0 — Views 34