Post Go back to editing

U-Boot Watchdog Issue on SC573-EZKIT after reset command

Thread Summary

The user encountered an issue where the watchdog timer fails to trigger a reboot after a software reset on the SC573-EZKIT board running U-Boot. The final answer suggests applying a patch from the 'wdt_fix' branch to resolve the problem, which has been confirmed to work by another user. The issue is also noted to be fixed in the upcoming ADSP-Linux Yocto Release version 5.0.0.
AI Generated Content
Category: Software
Product Number: ADSP-SC573

Hi,

Problem Description:

We are using U-Boot on an SC573-EZKIT board with the watchdog enabled. We confirmed the watchdog is properly configured by rebuilding U-Boot with watchdog support enabled in the device tree .dtsi file.

Our testing shows an unexpected behavior related to the reset command:

  • Expected Behavior: When we use the panic command from the U-Boot command-line interface (CLI), the watchdog correctly triggers a reboot of the board after a few seconds.

  • Unexpected Behavior: If we first execute the reset command and then, in the subsequent U-Boot session, run the panic command, the system freezes. The watchdog fails to trigger, and a reboot does not occur.

Question:

Could you explain why the reset command appears to disable or interfere with the watchdog functionality in the subsequent U-Boot session? Can you please provide a solution or a workaround to ensure the watchdog remains active after a software reset.

Thanks!

  • We will check with ADSP-Linux Yocto Release version 5.0.0 if we can reproduce on our end.

  • I have reproduced the issue, will check in more details

  • Hi  ,

    Thank you for reporting this issue.

    Could you apply the following patch to your meta layer and try the same again?



    diff --git a/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi.inc b/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi.inc
    index c202195..e8f1a69 100644

    --- a/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi.inc
    +++ b/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi.inc
    @@ -31,7 +31,7 @@ python() {
             d.setVar('UBOOT_SOM', d.getVar('UBOOT_SOM_FILE') + " " + d.getVar('UBOOT_SOM_FALCON_FILE'))
     }
     
    -UBOOT_BRANCH ?= "main"
    +UBOOT_BRANCH ?= "wdt_fix"
     
     # On the SC598, we can't boot directly from the eMMC due to default speed configuration issues
     # We can boot the SPL from OSPI or QSPI and then subsequently boot U-Boot Proper from eMMC
    diff --git a/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi_2023.04.bb b/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi_2023.04.bb
    index ccbff7f..22d9fd9 100644
    --- a/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi_2023.04.bb
    +++ b/meta-adi-adsp-sc5xx/recipes-bsp/u-boot/u-boot-adi_2023.04.bb
    @@ -2,7 +2,7 @@ inherit adsp-sc5xx-compatible
     
     require u-boot-adi.inc
     
    -SRCREV = "dd19d915e05516b3b4efd2ae03afab8bd29dea0e"
    +SRCREV = "861744a26ef88c33780d831247cd893ab00a7775"
     
     UBOOT_INITIAL_ENV = ""

    This will be fixed in the upcoming yocto release. 

  • Hi  ,

    I tested the single-line change in the source present in the "wdt_fix" branch and it worked, as we are not using Yocto for building. Many thanks for your support.

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.