Xiao Nrf54l15 restting

[Muba2520]

Hi there,

I have uploaded the BLE sounding reflector code on the xiao nrf54l15 module and after the upload i am getting this on my serial monitor

*** Using Zephyr OS v4.2.99-ec78104f1569 ***
I: Starting Channel Sounding Initiator Sample
I: SoftDevice Controller build revision:
I: 9b 8f ac c3 1d 42 ae 44 |.....B.D
I: fa cd 1f c3 48 a0 b4 2f |....H../
I: cf 29 ee 3d |.).=
E: ***** MPU FAULT *****
E: Data Access Violation
E: MMFAR Address: 0x9
E: r0/a1: 0x00000001 r1/a2: 0x00000000 r2/a3: 0xc4ec4ec5
E: r3/a4: 0x00000008 r12/ip: 0x00000000 r14/lr: 0x0002385f
E: xpsr: 0x01000000
E: s[ 0]: 0x00000000 s[ 1]: 0x00000000 s[ 2]: 0x00000000 s[ 3]: 0x00000102
E: s[ 4]: 0x20007448 s[ 5]: 0x00000000 s[ 6]: 0x20006ad4 s[ 7]: 0x20006acc
E: s[ 8]: 0x00000000 s[ 9]: 0x0003d213 s[10]: 0x00000000 s[11]: 0x00024095
E: s[12]: 0x20007448 s[13]: 0x0002f2f5 s[14]: 0x200049a8 s[15]: 0x20006a6c
E: fpscr: 0x20006ad4
E: Faulting instruction address (r15/pc): 0x00023888
E: >>> ZEPHYR FATAL ERROR 19: Unknown error on CPU 0
E: Current thread: 0x200049a8 (unknown)
E: Resetting system

I am using nrf SDK v3.2.1

[Vidar Berg]

Hello,

I wasn't able to replicate this here with SDK v3.2.1. Can you confirm that this is the build target you are using:

? 

The log output I got:

Best regards,

Vidar

[Muba2520]

Hi Vidar,
Thanks a lot for your reply
I was able to resolve that issue, the issue was that i was erasing the flash using pyocd and flashing the code using west that was causing some issue i don't know what but i switch from this to erasing the flash and flashing the code both with pyocd and now i am not facing it. I don't know what exactly went wrong it would be wonderful if you can explain me what was wrong there

[Vidar Berg]

Glad to hear you found a way to work around this. Unfortunately, I'm afraid I don't have a good explanation for this. We use J-link for our boards, but even if there was an issue with the pyocd programming sequence, I don't see how it would lead to this runtime failure. The runtime error suggests that there is a bug in the FW.