nrf54l15 bus fault on system off

Hello, 

I'm trying to put the nRF54L15DK into System Off mode, using sdk & toolchain version v2.8.0.

The provided example (\samples\nfc\system_off) works on my evaluation board when selecting nrf54l15dk/nrf54l15/cpuapp, 
but my minimal implementation fails with bus fault when selecting nrf54l15dk/nrf54l15/cpuapp/ns as target board:

E: ***** BUS FAULT *****
E: Precise data bus error
E: BFAR Address: 0x0
E: r0/a1: 0x40120000 r1/a2: 0x00081d77 r2/a3: 0xffffffff
E: r3/a4: 0x00000001 r12/ip: 0x00000000 r14/lr: 0x0006b91b
E: xpsr: 0x21000000
E: Faulting instruction address (r15/pc): 0x0007b936
E: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
E: Current thread: 0x20015780 (main)

The fault always happens when assigning 1 to p_reg->SYSTEMOFF:

NRF_STATIC_INLINE void nrf_regulators_system_off(NRF_REGULATORS_Type * p_reg)
{
    p_reg->SYSTEMOFF = REGULATORS_SYSTEMOFF_SYSTEMOFF_Msk;
    __DSB();

    /* Solution for simulated System OFF in debug mode */
    while (true)
    {
        __WFE();
    }
}

As I understand it, the regulators are accessible in my non-secure code per default anyway, 
do I need to configure something else?

As a Beginner, the BFAR Address 0x0 seems wrong, but at least r0/a1: 0x4012 0000 seems to match the non-secure register for regulators per the documentation, 
but probably I'm misinterpreting?


Any help is highly appreciated!


 

Parents
  • Hi,

    This is not supported yet. We have an internal planning ticket for adding support for TF-M and system off on nRF54L15, but I do not have a timeline for it. Please use nrf54l15dk/nrf54l15/cpuapp for now.

    Br,
    Kenneth

  • Hi,

    I saw this thread from about a year ago where it was mentioned that System OFF is not supported on nRF54L15 when using TF-M (cpuapp/ns).

    Could you please confirm whether this is now supported in the latest nRF Connect SDK versions?
    If so, which SDK version introduced the support?

    If it is still not supported, is there any recommended workaround for applications that require TF-M (e.g. due to KMU usage) but also need System OFF?

    For reference, I am currently using nRF Connect SDK v3.1.0.

    Thanks.

Reply
  • Hi,

    I saw this thread from about a year ago where it was mentioned that System OFF is not supported on nRF54L15 when using TF-M (cpuapp/ns).

    Could you please confirm whether this is now supported in the latest nRF Connect SDK versions?
    If so, which SDK version introduced the support?

    If it is still not supported, is there any recommended workaround for applications that require TF-M (e.g. due to KMU usage) but also need System OFF?

    For reference, I am currently using nRF Connect SDK v3.1.0.

    Thanks.

Children
Related