nRF54L15 (QFN48 REV 2) : Stopping WDT (WDT31) does not decrease sleep current (~2 µA)

Title: nRF54L15: Stopping WDT (WDT31) in PM state entry does not decrease sleep current (~2 µA)

Device: nRF54L15

NCS / Zephyr Version: ncs 3.4.0 and zephyr 4.4.0

Description:
Hello,

I am trying to minimize System ON sleep current on the nRF54L15 by stopping the watchdog (WDT31) prior to entering sleep, and re-starting it upon waking up.

According to the electrical specification, active WDT consumes approximately 2.2 µA (LFXO) / 2.8 µA. However, when successfully executing the stop sequence in Zephyr's PM notifier (pm_state_entry), I do not observe any measurable reduction in sleep current.

My Stop Procedure:

  1. Configured WDT31->CONFIG with STOPEN = 1 during initialization.
  2. Inside pm_state_entry:
    • Set WDT31->TSEN = 0x6E524635
    • Triggered WDT31->TASKS_STOP = 1
    • Polled WDT31->RUNSTATUS until RUNSTATUSWDT == 0 (confirmed it completes).
    • Cleared WDT31->TSEN = 0.
  3. In pm_state_exit: Re-configured and re-started the watchdog.

Questions:

  1. Does executing TASKS_STOP on the WDT peripheral actually power down its internal logic to save the ~2–2.8 µA listed under IWDT0 / IWDT1, or does the base consumption remain because the Low Power domain / LFCLK (PCLK32KI) is still requested by the Zephyr kernel/system timer?

  2. Is the ~2.2 µA – 2.8 µA figure in the datasheet primarily the overhead of the LF clock source (LFRC/LFXO) rather than the digital logic of the WDT itself?

  3. What is the expected net current difference between an actively running WDT vs. a stopped WDT when the device is in System ON sleep and LFCLK is already kept active by other peripherals?
Parents
  • Hello,

    The datasheet lists the system run current, not the current of the WDT alone. Also note that the measurements for the WDT only includes 32K of RAM retained which is less than a typical application: https://docs.nordicsemi.com/r/bundle/ps_nrf54l15/page/chapters/current_consumption/doc/current_consumption.html-unique_1734966674 

    Best regards,

    Vidar

  • Hi Vidar,

    Thank you for clarifying that the datasheet figures reflect total system run current (with 32 KB RAM retention) rather than standalone peripheral consumption.

    To clarify my observation: my base application sleep current without the WDT initialized is around 6 µA. When the WDT is enabled, the sleep current increases by roughly 2–3 µA to around 8–9 µA.

    My goal is to eliminate this extra 2–3 µA overhead during System ON sleep. I implemented the stop sequence (CONFIG.STOPEN = 1, writing 0x6E524635 to TSEN, and triggering TASKS_STOP) prior to entering sleep [Stopping the watchdog]. However, even after RUNSTATUS confirms the WDT has stopped, the current consumption remains at 8–9 µA instead of returning to the 6 µA baseline.

    Questions:

    1. Is there an additional step or power-gating requirement needed after executing TASKS_STOP to allow the underlying domain/clocks to shut down and achieve the 6 µA base level in System ON?
    2. Or does initializing/using the WDT peripheral permanently hold that power domain active for the remainder of System ON execution?

    Best regards,
    Antony

Reply
  • Hi Vidar,

    Thank you for clarifying that the datasheet figures reflect total system run current (with 32 KB RAM retention) rather than standalone peripheral consumption.

    To clarify my observation: my base application sleep current without the WDT initialized is around 6 µA. When the WDT is enabled, the sleep current increases by roughly 2–3 µA to around 8–9 µA.

    My goal is to eliminate this extra 2–3 µA overhead during System ON sleep. I implemented the stop sequence (CONFIG.STOPEN = 1, writing 0x6E524635 to TSEN, and triggering TASKS_STOP) prior to entering sleep [Stopping the watchdog]. However, even after RUNSTATUS confirms the WDT has stopped, the current consumption remains at 8–9 µA instead of returning to the 6 µA baseline.

    Questions:

    1. Is there an additional step or power-gating requirement needed after executing TASKS_STOP to allow the underlying domain/clocks to shut down and achieve the 6 µA base level in System ON?
    2. Or does initializing/using the WDT peripheral permanently hold that power domain active for the remainder of System ON execution?

    Best regards,
    Antony

Children
No Data
Related