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

Question

Hi, 
 As the subject states. 
 I would like to run the tests at zephyr/tests/drivers/spi/spi_controller_peripheral as intended in testcase.yml. I can verify that I have the correct pins setup, as seen in the SPI traces below. 
 I've tried using the following: 
 $> ./scripts/twister --generate-hardware-map map.yml #Creates a map.yml with the two nRF54LM20-DKs currently connected $> ./scripts/twister --device-testing --hardware-map map.yml -T tests/drivers/spi/spi_controller_peripheral/ 
 But this doesn't run, or flash anything. It appears to skip all tests instead. 
 I can use the following on both boards to run one of the tests (using the 8MHz overlay), and I can see some good output on the SPI lines with a logic analyzer 
 $> west build -b nrf54lm20dk/nrf54lm20a/cpuapp . -T drivers.spi.spi_8MHz $> west flash 
 But I can't see any test results from ztest. Furthermore, it seems to only run test_basic(), which perhaps fails? Because it only does this once. 
 Is it possible to run all tests on these two boards? What's the command to do that?

Susheel Nuguru · Accepted Answer

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; };

segl-nordic · Answer

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

tylerh · Answer

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] 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] 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] 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] 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

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

Top Replies