Spinlock assertion fail on nRF5340 custom board

RE: Spinlock assertion fail on nRF5340 custom board

Håkon Alseth — Tue, 21 Apr 2026 08:28:21 GMT

Hi,

I am glad to hear that you found a workaround to the issue.

Let me know if the issue reappears or similar. Hope you have a wonderful day!

Kind regards,

Håkon

RE: Spinlock assertion fail on nRF5340 custom board

Michael Crevier — Mon, 20 Apr 2026 18:01:13 GMT

Hi,

I checked where the LR address points, but it didn’t provide much insight into the root cause:

arm-zephyr-eabi-addr2line.exe -e zephyr\zephyr.elf 0x00070e55
C:/ncs/v3.2.4/zephyr/include/zephyr/spinlock.h:308

In the meantime, I investigated further and noticed that CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE was set to 4 instead of 16 (as in the devkit configuration). After adjusting that value and slightly increasing CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE, this issue appears to be resolved.

Thanks,

Michael

RE: Spinlock assertion fail on nRF5340 custom board

Håkon Alseth — Mon, 20 Apr 2026 12:06:19 GMT

Hi,

The first part is the originating fault:

[00:00:51.429,687] <err> os: ***** BUS FAULT *****
[00:00:51.429,687] <err> os:   Precise data bus error
[00:00:51.429,718] <err> os:   BFAR Address: 0x4
[00:00:51.429,748] <err> os: r0/a1:  0x20001d20  r1/a2:  0x0019b6ff  r2/a3:  0x20000f10
[00:00:51.429,748] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00070e55
[00:00:51.429,779] <err> os:  xpsr:  0x81100225
[00:00:51.429,809] <err> os: s[ 0]:  0x00010000  s[ 1]:  0x00000001  s[ 2]:  0x00000150  s[ 3]:  0x0006f38d
ASSERTION FAIL [z_spin_lock_valid(l)] @ WEST_TOPDIR/zephyr/include/zephyr/spinlock.h:136
        Invalid spinlock 0x2000ba70

Which memory area does "0x2000ba70" belong to according to your build/appname/zephyr/zephyr.map file? This is potentially the thread/stack that is overflowing.

Also, what function is the LR address pointing towards? use addr2line to resolve this.

Kind regards,

Håkon