How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Mon, 09 Feb 2026 12:46:00 GMT

Thank you very much! I appreciate the explanation. I'll use Twister for these tests, but in any case, it's working now with the changes made in the device tree in all cases.

It's really cool to have a good example that I can use for doing this type of device testing.

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

segl-nordic — Mon, 09 Feb 2026 12:31:54 GMT

Unfortunately, I have no idea why

$> west build -p -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_8MHz

fails while Twister passes on that test.
I'm unable to reproduce the issue locally. For me both Twister and west build/flash work.

When You run Twister, it compiles and executes all test configurations found in testcase.yaml (that match target with platform_allow list, filters, etc.). In case of zephyr/tests/drivers/spi/spi_controller_peripheral on nrf54lm20dk that's 11 test configurations:
drivers.spi.spi_mode0
drivers.spi.spi_mode1
drivers.spi.spi_mode2
drivers.spi.spi_mode3
...

You can see this after enabling Twister debug logs
$> python3 ./zephyr/scripts/twister -T zephyr/tests/drivers/spi/spi_controller_peripheral/ --platform nrf54lm20dk/nrf54lm20a/cpuapp --ninja --device-testing --jobs 1 --hardware-map /home/segl/workspace/ncs/my_setup.map --log-level debug

You can limit Twister test scope with (see output from python3 ./zephyr/scripts/twister --help):
-T TESTSUITE_ROOT, --testsuite-root TESTSUITE_ROOT
Base directory to recursively search for test cases. All testcase.yaml files under here will be processed. May be called multiple
times. Defaults to the 'samples/' and 'tests/' directories at the base of the Zephyr tree.

-s TEST, --test TEST, --scenario TEST
Run only the specified test suite scenario. These are named by 'path/relative/to/Zephyr/base/section.subsection_in_testcase_yaml', or
just 'section.subsection' identifier. With '--testsuite-root' option the scenario will be found faster.

So, to limit Twister execution to drivers.spi.spi_8MHz try
$> python3 ./zephyr/scripts/twister -T zephyr/tests/drivers/spi/spi_controller_peripheral/ --platform nrf54lm20dk/nrf54lm20a/cpuapp --ninja --device-testing --jobs 1 --hardware-map /home/segl/workspace/ncs/my_setup.map -s drivers.spi.spi_8MHz

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Mon, 09 Feb 2026 11:43:55 GMT

Hi segl-nordic,

Using the command above that you supplied me, I can indeed confirm that it works with or without zephyr,pm-device-runtime-auto;.

This was the result when I ran with and without the device tree changes. (Note: I removed my changes to the prj.conf file so that Twister can communicate with the serial port).

However, when I simply flash one of the tests, then it does not work without zephyr,pm-device-runtime-auto added.

Using the Logic Analyzer, I can see that there's far less traffic on the SPI lines than if I run it manually as before, using:

$> west build -p -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_8MHz

$> west flash

I haven't dived into the details, but I'm wondering if it's only running a subset of tests, rather than a full list of tests, when using Twister.

Does this make sense? What could the explanation for this be?

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Mon, 09 Feb 2026 09:54:46 GMT

Hi segl-nordic,

Very cool, thank you very much. That looks extremely promising; I'll give this a shot and see how it goes.

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

segl-nordic — Mon, 09 Feb 2026 09:40:50 GMT

Test requires fixture `gpio_spi_loopback`
See https://github.com/nrfconnect/sdk-zephyr/blob/main/tests/drivers/spi/spi_controller_peripheral/testcase.yaml#L8

Twister call should be f.e.:
python3 ./zephyr/scripts/twister -T zephyr/tests/drivers/spi/spi_controller_peripheral/ --platform nrf54lm20dk/nrf54lm20a/cpuapp --ninja --device-testing --jobs 1 --device-serial /dev/serial/by-id/usb-SEGGER_J-Link_001051895427-if02 --fixture gpio_spi_loopback

OR
python3 ./zephyr/scripts/twister -T zephyr/tests/drivers/spi/spi_controller_peripheral/ --platform nrf54lm20dk/nrf54lm20a/cpuapp --ninja --device-testing --jobs 1 --hardware-map /home/segl/workspace/ncs/my_setup.map --fixture gpio_spi_loopback

OR
python3 ./zephyr/scripts/twister -T zephyr/tests/drivers/spi/spi_controller_peripheral/ --platform nrf54lm20dk/nrf54lm20a/cpuapp --ninja --device-testing --jobs 1 --hardware-map /home/segl/workspace/ncs/my_setup.map
While HW map has list of fixtures available on the DK:

- connected: true
  id: '001051895427'
  platform: nrf54lm20dk/nrf54lm20a/cpuapp
  product: J-Link
  runner: nrfutil
  serial: /dev/serial/by-id/usb-SEGGER_J-Link_001051895427-if02
  fixtures: ['gpio_spi_loopback']

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

Susheel Nuguru — Sun, 08 Feb 2026 16:17:36 GMT

Informed internally. Hopefully some maintainers from Nordic will look at that and approve soon.

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Fri, 06 Feb 2026 12:17:53 GMT

Hi Susheel,

I've added this fix to the Zephyr project, as this spi driver test sits in the upstream Zephyr project: https://github.com/zephyrproject-rtos/zephyr/pull/103524

If there's anyone from Nordic that can approve it, then it will be fixed in the upcoming nRF Connect SDK.

Regards,

Tyler

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Wed, 04 Feb 2026 07:58:22 GMT

Thanks a lot Susheel, that seems to have worked!

00> *** Booting nRF Connect SDK v3.2.1-d8887f6f32df ***
00> *** Using Zephyr OS v4.2.99-f3f1c3dacc9c ***
00> Running TESTSUITE spi_controller_peripheral
00> ===================================================================
00> START - test_basic
00>  PASS - test_basic in 0.011 seconds
00> ===================================================================
00> START - test_basic_async
00>  PASS - test_basic_async in 0.011 seconds
00> ===================================================================
00> START - test_basic_zero_len
00>  PASS - test_basic_zero_len in 0.011 seconds
00> ===================================================================
00> START - test_basic_zero_len_async
00>  PASS - test_basic_zero_len_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx
00>  PASS - test_only_rx in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_async
00>  PASS - test_only_rx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks
00> [00:00:05.067,707] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks_async
00> [00:00:06.068,529] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_only_tx
00>  PASS - test_only_tx in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_async
00>  PASS - test_only_tx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks
00> [00:00:09.091,344] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks_async
00> [00:00:10.092,165] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_short_rx
00>  PASS - test_short_rx in 0.011 seconds
00> ===================================================================
00> START - test_short_rx_async
00>  PASS - test_short_rx_async in 0.011 seconds
00> ===================================================================
00> TESTSUITE spi_controller_peripheral succeeded
00> 
00> ------ TESTSUITE SUMMARY START ------
00> 
00> SUITE PASS - 100.00% [spi_controller_peripheral]: pass = 10, fail = 0, skip = 4, total = 14 duration = 0.114 seconds
00>  - PASS - [spi_controller_peripheral.test_basic] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_async] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_zero_len] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_zero_len_async] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_rx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_rx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks_async] duration = 0.001 seconds
00>  - PASS - [spi_controller_peripheral.test_only_tx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_tx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks_async] duration = 0.001 seconds
00>  - PASS - [spi_controller_peripheral.test_short_rx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_short_rx_async] duration = 0.011 seconds
00> 
00> ------ TESTSUITE SUMMARY END ------
00> 
00> ===================================================================
00> PROJECT EXECUTION SUCCESSFUL

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

Susheel Nuguru — Tue, 03 Feb 2026 09:40:49 GMT

I do not think anything is wrong with the chip but i think it is related to zephyr,pm-device-runtime-auto settings for the nRF54LM20.

The right side is for nRF54L15DK default overlay file

try adding this in your project overlay file and see if that helps?

dut_spis: &spi21 {
...
zephyr,pm-device-runtime-auto;
};

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Mon, 02 Feb 2026 12:02:13 GMT

I did a few tests. It appears that this could be a problem with the nRF54LM20, the implementation of this test on that board, or both.

Running this command works successfully using an nRF54L15-DK, see the output here:

$> west build -p -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_mode0

00> *** Booting nRF Connect SDK v3.2.1-d8887f6f32df ***
00> *** Using Zephyr OS v4.2.99-f3f1c3dacc9c ***
00> Running TESTSUITE spi_controller_peripheral
00> ===================================================================
00> START - test_basic
00>  PASS - test_basic in 0.011 seconds
00> ===================================================================
00> START - test_basic_async
00>  PASS - test_basic_async in 0.011 seconds
00> ===================================================================
00> START - test_basic_zero_len
00>  PASS - test_basic_zero_len in 0.011 seconds
00> ===================================================================
00> START - test_basic_zero_len_async
00>  PASS - test_basic_zero_len_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx
00>  PASS - test_only_rx in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_async
00>  PASS - test_only_rx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks
00> [00:00:05.066,559] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks_async
00> [00:00:06.067,370] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_only_tx
00>  PASS - test_only_tx in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_async
00>  PASS - test_only_tx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks
00> [00:00:09.090,196] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks_async
00> [00:00:10.091,007] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_short_rx
00>  PASS - test_short_rx in 0.011 seconds
00> ===================================================================
00> START - test_short_rx_async
00>  PASS - test_short_rx_async in 0.011 seconds
00> ===================================================================
00> TESTSUITE spi_controller_peripheral succeeded
00> 
00> ------ TESTSUITE SUMMARY START ------
00> 
00> SUITE PASS - 100.00% [spi_controller_peripheral]: pass = 10, fail = 0, skip = 4, total = 14 duration = 0.114 seconds
00>  - PASS - [spi_controller_peripheral.test_basic] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_async] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_zero_len] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_basic_zero_len_async] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_rx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_rx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks_async] duration = 0.001 seconds
00>  - PASS - [spi_controller_peripheral.test_only_tx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_only_tx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks_async] duration = 0.001 seconds
00>  - PASS - [spi_controller_peripheral.test_short_rx] duration = 0.011 seconds
00>  - PASS - [spi_controller_peripheral.test_short_rx_async] duration = 0.011 seconds
00> 
00> ------ TESTSUITE SUMMARY END ------
00> 
00> ===================================================================
00> PROJECT EXECUTION SUCCESSFUL

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

tylerh — Thu, 29 Jan 2026 08:33:35 GMT

Hi Susheel,

It looks like you're right. This is intended to run as loop-back mode. I'm able to get further by running it on the same board, as opposed to two different boards.

It looks like all of the tests are failing, however. Here's a snippet that I got from J-Link RTT Viewer after building this firmware:

$> west build -p -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_mode0

00> *** Booting nRF Connect SDK v3.2.1-d8887f6f32df ***
00> *** Using Zephyr OS v4.2.99-f3f1c3dacc9c ***
00> Running TESTSUITE spi_controller_peripheral
00> ===================================================================
00> START - test_basic
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:16
00>  FAIL - test_basic in 0.011 seconds
00> ===================================================================
00> START - test_basic_async
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:16
00>  FAIL - test_basic_async in 0.011 seconds
00> ===================================================================
00> START - test_basic_zero_len
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:8
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:8
00>  FAIL - test_basic_zero_len_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:253: run_test: rv not equal to 0
00> 
00>  FAIL - test_only_rx in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_async
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:253: run_test: rv not equal to 0
00> 
00>  FAIL - test_only_rx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks
00> [00:00:06.070,176] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_rx_in_chunks_async
00> [00:00:07.070,997] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_rx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_only_tx
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:16
00>  FAIL - test_only_tx in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_async
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:16
00>  FAIL - test_only_tx_async in 0.011 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks
00> [00:00:10.094,888] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks in 0.001 seconds
00> ===================================================================
00> START - test_only_tx_in_chunks_async
00> [00:00:11.095,709] <err> spi_nrfx_spis: Scattered buffers are not supported
00>  SKIP - test_only_tx_in_chunks_async in 0.001 seconds
00> ===================================================================
00> START - test_short_rx
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:12
00>  FAIL - test_short_rx in 0.011 seconds
00> ===================================================================
00> START - test_short_rx_async
00> 
00>     Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/spi/spi_controller_peripheral/src/main.c:247: run_test: (periph_rv not equal to srx_len)
00> Got: 0 but expected:12
00>  FAIL - test_short_rx_async in 0.011 seconds
00> ===================================================================
00> TESTSUITE spi_controller_peripheral failed.
00> 
00> ------ TESTSUITE SUMMARY START ------
00> 
00> SUITE FAIL -   0.00% [spi_controller_peripheral]: pass = 0, fail = 10, skip = 4, total = 14 duration = 0.114 seconds
00>  - FAIL - [spi_controller_peripheral.test_basic] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_basic_async] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_basic_zero_len] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_basic_zero_len_async] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_only_rx] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_only_rx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_rx_in_chunks_async] duration = 0.001 seconds
00>  - FAIL - [spi_controller_peripheral.test_only_tx] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_only_tx_async] duration = 0.011 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks] duration = 0.001 seconds
00>  - SKIP - [spi_controller_peripheral.test_only_tx_in_chunks_async] duration = 0.001 seconds
00>  - FAIL - [spi_controller_peripheral.test_short_rx] duration = 0.011 seconds
00>  - FAIL - [spi_controller_peripheral.test_short_rx_async] duration = 0.011 seconds
00> 
00> ------ TESTSUITE SUMMARY END ------
00> 
00> ===================================================================
00> PROJECT EXECUTION FAILED

I'm building with these additions to prj.conf to see the log output.

CONFIG_SPI=y
CONFIG_SPI_SLAVE=y
CONFIG_GPIO=y
CONFIG_POLL=y
CONFIG_SPI_ASYNC=y
CONFIG_ZTEST=y

CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_BACKEND_RTT=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y
CONFIG_CONSOLE=y
CONFIG_PRINTK=y

CONFIG_UART_CONSOLE=n

Do you know why this might be the case?

Additionally, to my question above, do you know if there's someone that might be able to describe how this could be done using Twister on this hardware, in an automated test environment?

Regards,

Tyler

RE: How does one run zephyr/tests/drivers/spi/spi_controller_peripheral on two nRF54LM20-DKs?

Susheel Nuguru — Wed, 28 Jan 2026 18:25:01 GMT

I do not think this test is meant to run on two different boards. They seems to be designed to run on the same core with SPIM and SPIS from the same device. The design expects a loopback. What you got when you run west build -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_8MHz might just be lucky as that particular test might just be pushing our data from the master. That said, I am no expert in this setup, so we need to see if there is someone else with better knowledge in twister and ztests can comment here.