Getting an error when using Ztest+Twister on nrf5340dk

RE: Getting an error when using Ztest+Twister on nrf5340dk

runsiv — Fri, 20 Feb 2026 14:01:14 GMT

Sorry for the delay, I had to change computer for nrfjprog.

When you are using 2.7 you can use nrfjprog, it is only depricated in newer version of NCS.
I had no issue running the test over RTT with the following sample.yml

sample:
  description: random test
  name: hello world ztest
common:
  tags: tests
  integration_platforms:
    - nrf5340dk/nrf5340/cpuapp
  harness: ztest
  harness_config:
    fixture: rtt
tests:
  sample.ztest.simple:
    tags: tests

It seems strange that you can only enable one peripheral. In general i would presume you would mock it anyway

Regards

Runar

RE: Getting an error when using Ztest+Twister on nrf5340dk

Nathan93 — Wed, 11 Feb 2026 10:49:21 GMT

Hello

Thanks for the response.

Currently using an older sdk

NCS SDK = 2.7.0

Cant use the newer versions/latest version of SDK due to project related constraints.

I tried to remove the runner: nrfjprog but it throws an error : Device Flash Error when I try to run the twister command

1) sensor_app.basic on nrf5340dk/nrf5340/cpuapp error (Device issue (Flash error?))

west twister -p nrf5340dk/nrf5340/cpuapp --device-testing --hardware-map map.yaml -T  .\sensor_app\tests\ -vv

Twister Output Snippet with runner=nrfjprog enabled:

INFO    - The following issues were found (showing the top 10 items):
INFO    - 1) sensor_app.basic on nrf5340dk/nrf5340/cpuapp failed (Timeout)
INFO    -

Additional inputs: Currently cannot use uart0 on the device as I am already using SPIM for another part.
I believe we can use only one peripheral at a time.

Only one of the following peripherals can be enabled: SPI0, SPIM0, SPIS0, TWI0, TWIM0, TWIS0,
UARTE0

RE: Getting an error when using Ztest+Twister on nrf5340dk

runsiv — Wed, 11 Feb 2026 10:07:42 GMT

Hi I will look into your case.
What SDK are you using? I did a quick test without using uart to to verify the rest and it worked without any issue. nrfjprog is deprecated and should not be used for newer SDKs
I suspect there might be an issue with it not selecting the correct core when trying to sett up RTT.

Regards

Runar