custom nRF5340 board no bluetooth signal

RE: custom nRF5340 board no bluetooth signal

Bendik Heiskel — Mon, 12 May 2025 11:49:18 GMT

Hi Danny,

Great to hear that you found the issue.

For future designs I recommend you have us review it before producing the boards, this way any issues can be caught earlier in the process, just create a private ticket where you share your design files and one of our HW engineers will give feedback on it.

Best regards,

Bendik

RE: custom nRF5340 board no bluetooth signal

danny0007 — Fri, 09 May 2025 13:02:11 GMT

Hi Bendik Heiskel

good to know.

that means I need the nRF5340DK to flash my custom board.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

By the way, I just found out the issue and make the RF on my baord working.

After double check the datasheet of nRF5340, I found that I forgot to short DECR and DECRF together.

After soldering them togehter, now it's finally working!

I will definitely go back to check this test tools again.

Best Regards

Danny

RE: custom nRF5340 board no bluetooth signal

Bendik Heiskel — Fri, 09 May 2025 12:04:19 GMT

The programming is done using a debugger, it is just a wrapper for nrfutil. It does not do any serial of OTA DFU. When a debugger is connected, it's serial number will be shown in the debugger drop down menu. When pressing the "Flash" button the application will check which device is connected to the debugger and flash the correct test FW to it. The "Get debuggers" button can be used to updated the list of connected debuggers if a debugger is connected after starting the application.

To program you custom board you will either need a standalone debugger, or use the debug out connector on the nRF5340DK.

RE: custom nRF5340 board no bluetooth signal

danny0007 — Fri, 09 May 2025 11:03:51 GMT

Hi Bendik Heiskel

yes, after upgrading the nrfutil, no errors show up again.

"The left side of the GUI is used for flashing the test FW to the DUT and configuring the internal load capacitors for nRF5340 and the nRF54L15."

I'm curous how this programming is done? command via UART or DFU via dongle?

How shall I programm these firmware for DUT into my custom board? nRF connect?

Regards

Danny

RE: custom nRF5340 board no bluetooth signal

Bendik Heiskel — Wed, 07 May 2025 16:04:09 GMT

The main use case for this application is in our test lab for tuning customer boards. It is created in a way that there is one universal test FW for the DUT, which doesn't rely on any external serial connection.

It has most of the functionality of the radio_test sample from the nRF Connect SDK so it can be used for the same type of testing.

All buttons and input fields have tooltips describing the functionality and expected input, just hover over the button/input field for a couple of seconds for it to appear.

The left side of the GUI is used for flashing the test FW to the DUT and configuring the internal load capacitors for nRF5340 and the nRF54L15.

The right side contains the test configuration.

The application supports 5 test modes:

Unmodulated TX: configures the radio to transmit a unmodulated constant carrier at the configured frequency and output power. This is useful for checking that the radio is functioning, tuning the radio matching network to optimize the output power and minimize the harmonic distortion, and for tuning the load capacitance for the 32MHz crystal to minimize frequency offset.
Modulated TX: configures the radio to transmit a constant modulated carrier at a given frequency, output power and datarate. This is useful for measuring occupied bandwidth and bandedge emissions.
RX: configures the radio to RX mode at a given frequency and data rate. This is useful for measuring spurious emissions from the radio in RX mode. It can not be used for actually receiving packets.
RX / Unmodulated TX sweep: configures the radio to constantly be sweeping the TX/RX from a given start frequency to a stop frequency.

[quote user="danny0007"]I have a custom nRF5340 board, which is similar to Thingy53, but my board doesn't have any bluetooth signal, so I only want to do a functional test to check if the RF part on my board works or not at all? [/quote]

For this I recommend using the unmodulated TX test. If you configure it to transmit a carrier at frequency 2440MHz with the maximum output power the nRF5340 can transmit at, 3dBm, you can check both that the board is outputting the correct output power and the frequency offset using a spectrum analyzer. For this test it is best to do the measurements conducted, as this will give the most accurate measurements. If your board have a RF connector this should be easy, if there is no connector on the board you can cut the transmission line after the radio matching network and solder a coax cable to the board. The outer conductor should be soldered to GND while the center conductor to the transmission line.

[quote user="danny0007"]what are these buttons used for? there is not any output except the "Flash" button, if I click them:
[/quote]

This looks like there could be a issue with the version of nrfutil and nrfutil-device.

Can you run the following commands to check which versions of nrfutil/nrfutil-device you have installed:

nrfutil -V
nrfutil device -V

I have tested with nrfutil version 8.0.0 and nrfutil-device version 2.10.1 which both is the latest versions, and are not able to reproduce the device error.

You can update both to the latest version using:

nrfutil self-upgrade
nrfutil upgrade device

RE: custom nRF5340 board no bluetooth signal

danny0007 — Wed, 07 May 2025 14:46:09 GMT

Hi @Bendik Heiskel

Proud to be the very first user:)

so what's the overall mechanism of the whole test setup?

the python GUI (rf_test.py) controls the connected USB dongle, the USB dongle sends the "Test config" to DUT

and this is the detected DUT, I guess:

what are these buttons used for? there is not any output except the "Flash" button, if I click them:

is my understanding correct?

*************************************************************************

my original problem is:

I have a custom nRF5340 board, which is similar to Thingy53, but my board doesn't have any bluetooth signal, so I only want to do a functional test to check if the RF part on my board works or not at all?

Best regards

Danny

RE: custom nRF5340 board no bluetooth signal

Bendik Heiskel — Tue, 06 May 2025 08:39:11 GMT

Great to hear that it works, you're the first person to try this application other than me. I'll be updating the instructions based on the issues you experienced to make it easier in the future.

The test software can be used to set the radio in different modes. Unmodulated TX sets the radio to transmitt a carrier at a given frequency and output power. With a spectrum analyzer this can be used to verify the output power and frequency accuracy of the radio/32MHz crystal.

By default the settings are configured for a 0dBm carrier on 2440MHz. The firmware on the DUT will start the radio in RX mode waiting for a command from the application, pressing the start button will send the test configuration to the DUT, if this is successfull the start button will turn green. The DUT will automatically cange the radio to the configuration send from the application and start the radio. To use a different test configuration the DUT must be restarted, by either the reset button or by power cycling the board.

What exactly is it you are trying to test?

RE: custom nRF5340 board no bluetooth signal

danny0007 — Tue, 06 May 2025 08:22:29 GMT

Hi Bendik Heiskel

thanks a lot. it seems working.

I copied the libusb-1.0.28\MinGW64\dll\libusb-1.0.dll file in C:\windows\system32

I also flashed the empty_app_core.hex and nrf5349.hex on nRF5340DK board.

USB dongle and nRF5340Dk both are connected to the laptop, then start the GUI. it looks like this:

So what's the next steps, how to perform the RF test?

Regards

Danny

RE: custom nRF5340 board no bluetooth signal

Bendik Heiskel — Mon, 05 May 2025 13:13:21 GMT

Hi Danny,

The "No backend available" error comes from a missing libusb-1.0.dll.

This should have been installed by the libusb-package in the requirements.txt file.

Do you have multiple python versions installed on this computer?

If so, did you run the pip install command using the same python version you are using for running the application?

It is possible to install this dll manually. It can be downloaded form the libusb github repository(in the .7z file):

https://github.com/libusb/libusb/releases

the libusb-1.0.dll file must be placed in C:\windows\system32

Best regards,

Bendik

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Sun, 04 May 2025 21:59:50 GMT

[quote user="danny0007"]

Sorry, I was using the hex\nrf52840.hex.

Ok, now the one you mentioned is flashed.

[/quote]

This is good progress, we are getting somewhere.

The no backen available error i am not sure exactly what is caused by. But i suspect that it has something to do with the premissions or path available in the folder where the app runs.

I will check with the developer and see what voibe the root cause.

Regards,

Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Fri, 02 May 2025 15:47:08 GMT

Sorry, I was using the hex\nrf52840.hex.

Ok, now the one you mentioned is flashed.

I can see the Nordic Semiconductor RF test and WinUSB is installed.

However I get the same error:

Regards
Danny

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Fri, 02 May 2025 06:42:01 GMT

The dongle does not need a softdevice with this setup so this should not be needed. Are you using the rf_test_dongle_nrf52840_dongle.hex found it the dongle firmware folder? just drag it in to the programmer app.

How does the prompt show up ?

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Tue, 29 Apr 2025 14:24:45 GMT

I'm trying to flash the nRF52840 dongle with nrf52840.hex via nRF connect.

which softDevice shall I select?

I tried several, get this error:

Regard

Danny

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Tue, 29 Apr 2025 13:50:05 GMT

Sorry for the ambiguity,

So the python application together with the nRF52840 dongle acts as the tools to enable testing on the custom board\DK of your choice.

So the python app + the dongle with the dongle firmware is part of the tools to enable testing.

The DK\custom board and the hex file with only the name of the device is the Device Under Testing(DUT), This unit only needs power to work after the firmware is flashed.

The python app + dongle activates the DUT mode of choice wirelessly over the radio. A power cycle of the DUT is needed to reset the device and make it except new commands.

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Tue, 29 Apr 2025 12:49:05 GMT

but my custom board is based on nRF5340.

Even if it's working with nRF52840 dongle, how can this rf_test code help me with debugging the RF function of my nRF5340 custom board?

My thoughts is first to test the rf_test code with nRF5340DK, then move the code to my custom board.

Begards

Danny

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Tue, 29 Apr 2025 12:15:34 GMT

[quote user="danny0007"]I got a USB dongle with nRF52840, I flashed the rf_test_dongle_nrf52840_dongle.hex file with nRF Connect Programmer. how to use it in this case?[/quote]

You said earlier you had a nRF52840 dongle?

The nRF5340DK is not supported as the "Dongle" unit here in this application.

" Only nRF52840DK and dongle have been tested."

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Tue, 29 Apr 2025 11:55:07 GMT

in my case, it's nRF5340DK, not dongle. I can only see two CDC devices.

Yes, it's connected as I do the update and install.

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Tue, 29 Apr 2025 11:45:36 GMT

Is the dongle connected when you do the driver update\install?

It should be a name with Nordic Semiconductor RF test

This is the dongle and it should be changed to the usb driver.

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Tue, 29 Apr 2025 09:15:46 GMT

Hi JONATHAN LL

1. I'm using USB J2 IMCU USB.

2. Zadig-->Options--> List All Devices

the CDC(Interface 2) and CDC(Interface 0) are for the IMCU USB.

I have install WinUSB for both.

When not enable "List All Devices", on devices will be shown.

3. Python version

PS C:\nordic\rf_test> python --version
Python 3.12.4

Regards

Danny

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Tue, 29 Apr 2025 08:10:34 GMT

[quote user="danny0007"]a. which USB port on nRF5340DK will be used for this communicaton? IMCU USB or nRF5340 USB?[/quote]

USB connector J2, its the one fir the IMCU.

[quote user="danny0007"]b. " Use Zadig to install the driver: https://zadig.akeo.ie/", which device shall I choose to install the driver?[/quote]

The WinUSB driver that shows up should work. I belive tis the default option that shows up.

I belive the DK you have is programmed correctly from the info in your logs.

What version of python are you running? Currently we have only tested this with different versions of Python 12.

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Mon, 28 Apr 2025 19:57:36 GMT

Hi JONATHAN LL

I cannot reproduce your results:

1. python3 -m pip install libusb-package
Requirement already satisfied: libusb-package in c:\users\xxx\appdata\local\programs\python\python312\lib\site-packages (1.0.26.3)
Requirement already satisfied: importlib_resources in c:\users\xxx\appdata\local\programs\python\python312\lib\site-packages (from libusb-package) (6.5.2)
PS C:\nordic\rf_test>

2. Programm the both hex files for netcore and appcore via nRF connect:

21:18:09.560

Reading readback protection status for Network core completed

21:18:25.552

Recovering Application core

21:18:25.552

Recovering Application core 0%

21:18:26.782

Recovering Application core 100%

21:18:26.783

Recovering Application core completed

21:18:26.835

Recovering Network core

21:18:26.838

Recovering Network core 0%

21:18:39.198

Recovering Network core 100%

21:18:39.199

Recovering Network core completed

21:18:39.233

Writing HEX to Application core

21:18:39.566

Writing HEX to Application core 33%

21:18:39.566

Writing HEX to Application core 33%

21:18:39.573

Writing HEX to Application core 67%

21:18:39.574

Writing HEX to Application core 44%

21:18:39.574

Writing HEX to Application core 40%

21:18:39.574

Writing HEX to Application core 47%

21:18:39.574

Writing HEX to Application core 53%

21:18:39.574

Writing HEX to Application core 60%

21:18:39.585

Writing HEX to Application core 67%

21:18:39.585

Writing HEX to Application core 55%

21:18:39.585

Writing HEX to Application core 44%

21:18:39.658

Writing HEX to Application core 55%

21:18:39.681

Writing HEX to Application core 67%

21:18:39.681

Writing HEX to Application core 100%

21:18:39.682

Writing HEX to Application core completed

21:18:39.724

Writing HEX to Network core

21:18:39.974

Writing HEX to Network core 33%

21:18:39.974

Writing HEX to Network core 33%

21:18:39.983

Writing HEX to Network core 67%

21:18:39.994

Writing HEX to Network core 44%

21:18:39.994

Writing HEX to Network core 40%

21:18:39.994

Writing HEX to Network core 47%

21:18:39.994

Writing HEX to Network core 53%

21:18:40.006

Writing HEX to Network core 60%

21:18:40.016

Writing HEX to Network core 67%

21:18:40.016

Writing HEX to Network core 55%

21:18:40.016

Writing HEX to Network core 44%

21:18:40.275

Writing HEX to Network core 55%

21:18:40.283

Writing HEX to Network core 67%

21:18:40.283

Writing HEX to Network core 100%

21:18:40.284

Writing HEX to Network core completed

21:18:40.313

Loading core information for Application core

21:18:40.313

Loading core information for Application core 0%

21:18:40.314

Update files regions according to Application core

21:18:40.314

Parse memory regions for file

21:18:40.314

Update files regions according to Network core

21:18:40.314

Parse memory regions for file

21:18:40.321

Loading core information for Application core 100%

21:18:40.321

Loading core information for Application core completed

21:18:40.322

Update files regions according to Application core

21:18:40.322

Parse memory regions for file

21:18:40.322

Update files regions according to Network core

21:18:40.322

Parse memory regions for file

21:18:40.365

Loading core information for Network core

21:18:40.365

Loading core information for Network core 0%

21:18:40.367

Update files regions according to Application core

21:18:40.367

Parse memory regions for file

21:18:40.367

Update files regions according to Network core

21:18:40.367

Parse memory regions for file

21:18:40.373

Loading core information for Network core 100%

21:18:40.373

Loading core information for Network core completed

21:18:40.374

Update files regions according to Application core

21:18:40.374

Parse memory regions for file

21:18:40.374

Update files regions according to Network core

21:18:40.374

Parse memory regions for file

21:18:42.692

Reading readback protection status for Application core

21:18:42.693

Reading readback protection status for Application core 0%

21:18:42.695

Reading readback protection status for Application core 100%

21:18:42.695

Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'

21:18:42.695

Reading readback protection status for Application core completed

21:18:42.710

Reading readback protection status for Network core

21:18:42.711

Reading readback protection status for Network core 0%

21:18:42.713

Reading readback protection status for Network core 100%

21:18:42.713

Network core protection status 'NRFDL_PROTECTION_STATUS_NONE'

21:18:42.713

Reading readback protection status for Network core completed

3. start the rf_test.py

get the same result:
Error calling Python override of QThread::run(): Traceback (most recent call last):
File "C:\nordic\rf_test\src\gui\logic.py", line 128, in run
with Dongle() as dongle:
^^^^^^^^
File "C:\nordic\rf_test\src\modules\rf_test_dongle_api.py", line 52, in __init__
self.dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\xxx\AppData\Local\Programs\Python\Python312\Lib\site-packages\usb\core.py", line 1321, in find
raise NoBackendError('No backend available')
usb.core.NoBackendError: No backend available

my questions:

a. which USB port on nRF5340DK will be used for this communicaton? IMCU USB or nRF5340 USB?

b. " Use Zadig to install the driver: https://zadig.akeo.ie/", which device shall I choose to install the driver?

Best regards

Danny

RE: custom nRF5340 board no bluetooth signal

danny0007 — Mon, 28 Apr 2025 19:28:18 GMT

Hi JONATHAN LL

I cannot reproduce your results:

1. python3 -m pip install libusb-package
Requirement already satisfied: libusb-package in c:\users\qingc\appdata\local\programs\python\python312\lib\site-packages (1.0.26.3)
Requirement already satisfied: importlib_resources in c:\users\qingc\appdata\local\programs\python\python312\lib\site-packages (from libusb-package) (6.5.2)
PS C:\nordic\rf_test>

2. Programm the both hex files for netcore and appcore via nRF connect:

21:18:09.560

Reading readback protection status for Network core completed

21:18:25.552

Recovering Application core

21:18:25.552

Recovering Application core 0%

21:18:26.782

Recovering Application core 100%

21:18:26.783

Recovering Application core completed

21:18:26.835

Recovering Network core

21:18:26.838

Recovering Network core 0%

21:18:39.198

Recovering Network core 100%

21:18:39.199

Recovering Network core completed

21:18:39.233

Writing HEX to Application core

21:18:39.566

Writing HEX to Application core 33%

21:18:39.566

Writing HEX to Application core 33%

21:18:39.573

Writing HEX to Application core 67%

21:18:39.574

Writing HEX to Application core 44%

21:18:39.574

Writing HEX to Application core 40%

21:18:39.574

Writing HEX to Application core 47%

21:18:39.574

Writing HEX to Application core 53%

21:18:39.574

Writing HEX to Application core 60%

21:18:39.585

Writing HEX to Application core 67%

21:18:39.585

Writing HEX to Application core 55%

21:18:39.585

Writing HEX to Application core 44%

21:18:39.658

Writing HEX to Application core 55%

21:18:39.681

Writing HEX to Application core 67%

21:18:39.681

Writing HEX to Application core 100%

21:18:39.682

Writing HEX to Application core completed

21:18:39.724

Writing HEX to Network core

21:18:39.974

Writing HEX to Network core 33%

21:18:39.974

Writing HEX to Network core 33%

21:18:39.983

Writing HEX to Network core 67%

21:18:39.994

Writing HEX to Network core 44%

21:18:39.994

Writing HEX to Network core 40%

21:18:39.994

Writing HEX to Network core 47%

21:18:39.994

Writing HEX to Network core 53%

21:18:40.006

Writing HEX to Network core 60%

21:18:40.016

Writing HEX to Network core 67%

21:18:40.016

Writing HEX to Network core 55%

21:18:40.016

Writing HEX to Network core 44%

21:18:40.275

Writing HEX to Network core 55%

21:18:40.283

Writing HEX to Network core 67%

21:18:40.283

Writing HEX to Network core 100%

21:18:40.284

Writing HEX to Network core completed

21:18:40.313

Loading core information for Application core

21:18:40.313

Loading core information for Application core 0%

21:18:40.314

Update files regions according to Application core

21:18:40.314

Parse memory regions for file

21:18:40.314

Update files regions according to Network core

21:18:40.314

Parse memory regions for file

21:18:40.321

Loading core information for Application core 100%

21:18:40.321

Loading core information for Application core completed

21:18:40.322

Update files regions according to Application core

21:18:40.322

Parse memory regions for file

21:18:40.322

Update files regions according to Network core

21:18:40.322

Parse memory regions for file

21:18:40.365

Loading core information for Network core

21:18:40.365

Loading core information for Network core 0%

21:18:40.367

Update files regions according to Application core

21:18:40.367

Parse memory regions for file

21:18:40.367

Update files regions according to Network core

21:18:40.367

Parse memory regions for file

21:18:40.373

Loading core information for Network core 100%

21:18:40.373

Loading core information for Network core completed

21:18:40.374

Update files regions according to Application core

21:18:40.374

Parse memory regions for file

21:18:40.374

Update files regions according to Network core

21:18:40.374

Parse memory regions for file

21:18:42.692

Reading readback protection status for Application core

21:18:42.693

Reading readback protection status for Application core 0%

21:18:42.695

Reading readback protection status for Application core 100%

21:18:42.695

Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'

21:18:42.695

Reading readback protection status for Application core completed

21:18:42.710

Reading readback protection status for Network core

21:18:42.711

Reading readback protection status for Network core 0%

21:18:42.713

Reading readback protection status for Network core 100%

21:18:42.713

Network core protection status 'NRFDL_PROTECTION_STATUS_NONE'

21:18:42.713

Reading readback protection status for Network core completed

3. start the rf_test.py

get the same result:
Error calling Python override of QThread::run(): Traceback (most recent call last):
File "C:\nordic\rf_test\src\gui\logic.py", line 128, in run
with Dongle() as dongle:
^^^^^^^^
File "C:\nordic\rf_test\src\modules\rf_test_dongle_api.py", line 52, in __init__
self.dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\qingc\AppData\Local\Programs\Python\Python312\Lib\site-packages\usb\core.py", line 1321, in find
raise NoBackendError('No backend available')
usb.core.NoBackendError: No backend available

RE: custom nRF5340 board no bluetooth signal

JONATHAN LL — Mon, 28 Apr 2025 17:41:04 GMT

[quote user="danny0007"]still not working, and no UART console is recognised on the nRF5340 USB port of nRF5340DK board.[/quote]

Make sure you run the requierments file.

and also maybe try this: python3 -m pip install libusb-package

As for the DK and flashing:
If you are unsure use the nRF connect for desktop programmer app.

You can add both Hex files here and see them and then you can confirm if the DK has the same when you read its memory.

Regards,
Jonathan

RE: custom nRF5340 board no bluetooth signal

danny0007 — Fri, 25 Apr 2025 15:16:28 GMT

I suppose you also tested it on nRF5340DK.

Could you please share me how you exactly flash the board?

RE: custom nRF5340 board no bluetooth signal

danny0007 — Fri, 25 Apr 2025 13:51:40 GMT

so you mean empty_app_core.hex needs to be flashed on the app core of nRF5340DK and
nrf5340.hex on the net core of nRF5340DK? I did it like this:

still not working, and no UART console is recognised on the nRF5340 USB port of nRF5340DK board.

PS C:\nordic\rf_test> py rf_test.py -V
2025-04-25 15:45:40.816 | DEBUG | __main__:<module>:31 - Starting GUI
2025-04-25 15:45:40.841 | DEBUG | src.gui.logic:run:117 - Getting connected debuggers
Error calling Python override of QThread::run(): Traceback (most recent call last):
File "C:\nordic\rf_test\src\gui\logic.py", line 128, in run
with Dongle() as dongle:
^^^^^^^^
File "C:\nordic\rf_test\src\modules\rf_test_dongle_api.py", line 52, in __init__
self.dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\qingc\AppData\Local\Programs\Python\Python312\Lib\site-packages\usb\core.py", line 1321, in find
raise NoBackendError('No backend available')
usb.core.NoBackendError: No backend available
2025-04-25 15:45:41.611 | DEBUG | src.modules.nrfutil_wrapper:get_device_version:165 - 1050021434: Getting device version: NRF5340_xxAA_REV1
2025-04-25 15:47:47.791 | DEBUG | src.modules.nrfutil_wrapper:get_device_version:165 - 1050021434: Getting device version: NRF5340_xxAA_REV1
2025-04-25 15:47:47.792 | DEBUG | src.modules.nrfutil_wrapper:program:139 - 1050021434: Programming file: C:\nordic\rf_test\hex/nrf5340.hex Core: Core.NETWORK
2025-04-25 15:47:48.188 | ERROR | src.modules.nrfutil_wrapper:handle_nrfutil_return:77 - Error: One or more program tasks failed:
* 1050021434: Device error: QSPI is not a valid peripheral option for external flash programming (Generic)