nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

RE: nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

Kenneth — Wed, 10 Dec 2025 13:50:12 GMT

If you want to work with nrfx make sure to start with the bare metal option we have for the nRF54L15:
https://www.nordicsemi.com/Products/Development-software/nRF-Connect-SDK/Bare-Metal-option-for-nRF54L-Series

Kenneth

RE: nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

wei.zhang — Wed, 10 Dec 2025 06:50:13 GMT

Thank you for your reply! In fact, due to the issue that the time from the cs falling edge of SPI to the generation of SCLK is not fixed, I gave up using Zephyr API to use more underlying NRFX driver, I refer to the sample in the replication: ncs\v3.1.1\modules\hal\nordic\nrfx\samples\src\nrfx_spim_spis\non_blocking

Is my approach feasible?

RE: nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

wei.zhang — Wed, 10 Dec 2025 06:34:58 GMT

Thank you for response!

If I have already configured the callback handler function spim_handler and spis_handler, do I still need the IRQ_CONNECT? In fact, if I add it, the compiler error:

...IRQ_CONNECT or IRQ_DIRECT_CONNECT accidentally been invoked on the same irq multiple times...

RE: nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

momososo — Wed, 10 Dec 2025 00:41:44 GMT

miss IRQ_CONNECT

RE: nRF54L15 DK(ncs v3.1.1) nrfx SPIS receiving program exception

Kenneth — Tue, 09 Dec 2025 19:05:50 GMT

Hello,

Not sure what you already have tried, but presuming if you simply have connected PWM directly to the CLK input of the SPIS, and leave the CLK output from the master unconnected, I don't really see how this should fail no. Maybe checking out some of the SPIS examples in nRF Connect SDK to check that they work as-is is a good start:

Kenneth