Unable to Flash Blinky

[[email protected]]

Hello,

I just got started with the nRF5340 DK.  I went through the example which instructs how to load the "Blinky" applications, build it, and then flash it to the Board.

Everything works except for flashing it to the board.  I get the following error:

* Executing task: nRF Connect: Build: blinky/build (active)

Building blinky
west build --build-dir c:/nordic/myapps/blinky/build c:/nordic/myapps/blinky

[0/16] Performing build step for 'tfm'
ninja: no work to do.
* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: blinky/build (active)

Flashing build to 1050099720
west flash -d c:\nordic\myapps\blinky\build --skip-rebuild --dev-id 1050099720

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\nordic\myapps\blinky\build\zephyr\merged.hex
ERROR: No debuggers were discovered.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 41: nrfjprog --program 'c:\nordic\myapps\blinky\build\zephyr\merged.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050099720

* The terminal process terminated with exit code: 41.
* Terminal will be reused by tasks, press any key to close it.

[Einar Thorsrud]

Hi,

You get the "ERROR: No debuggers were discovered" error (which is also what status 41 indicate) for some reason.

Can you see if the debugger is found with "nrfjprog -i"?

If that works, can you successfully do an "nrfjprog --recover --coprocessor CP_NETWORK && nrfjprog --recover"?

[[email protected]]

Hello,

nothing seems to happen when I try that.  Here is a screenshot of what I am seeing.

[Einar Thorsrud]

Hi,

I see. There are a few things we can check:

1. Verify that you are using the USB port on the left side on the DK, as thi sis the one that is connected to the onboard debugger.
2. Verify that SW6 is in the default position

If it still does not work, can you try a different USB cable and avoid any USB hubs? Also, have you done any modifications on the DK? If still no luck, please upload a photo of your DK so that I can see both switch positions and how it is connected.

[[email protected]]

Hello,

I have tried multiple different use cables for both the nRF5340 and nRF5340DK,

I have verified that the USB is connected to the left side of the DK, and I have tried every USB port on my PC.

and I have verified that SW6 is set to default.

Attached are some pictures for reference.

The only thing left I can try is to install everything on a difference PC.

[[email protected]]

Hello,

I have tried installing everything from scratch on a different PC, and same results:

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: \blinky\build\zephyr\merged.hex
ERROR: No debuggers were discovered.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 41: nrfjprog --program '\blinky\build\zephyr\merged.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050126393

These are the installation instructions I am following. Is this the correct procedure for installing everything?

developer.nordicsemi.com/.../install_ncs.html

[kriswilk]

I was just having the EXACT same problem. I have an nRF52840-DK and nRF52-DK, a brand new PC with Windows 11, and had freshly installed VS Code, nRF command line tools, and extension pack for VSC. Was trying the same blinky app from the SDK fundamentals course, following the instructions to the letter.

Only deviation was that I had also installed the latest J-Link Software (7.94k, from yesterday).

I was getting the exact same errors, J-Link Configurator was not seeing either DK, and in Device Manager, there was a "BULK device" and two "USB-Serial" devices (but not the usual "JLink CDC" type). Very weird.

Out of curiosity, I uninstalled JLink 7.94k and installed an older version, 7.88j. Suddenly the DKs were seen by Configurator and all worked fine in VSC.

Then (even more strangely), I uninstalled 7.88j and reinstalled 7.94k, and everything still seems to be working. Need to try rebooting to see if it survives that.

Maybe give this a shot and report back?

[[email protected]]

You are a lifesaver!

I had JLink 7.94e installed.  I believe this was automatically installed during the installation process/instructions.

I then installed 7.88j as you suggested, and it worked!  

Hopefully the installation instructions can be updated to use working versions of JLink.

[kriswilk]

On one hand, I'm very glad to hear that the same process worked for you, too. If you upgrade to 7.94k as I did, does it continue working? It did for me.

On the other hand, I'm hoping Nordic can shed some light on WHY this would be a problem at all, especially if you were using the J-Link installed by the Command Line Tools. That's a problem, especially for a beginner.

In case it matters, the onboard firmware on my DKs was from fall 2022. After all my tinkering and getting everything working, I upgraded the DKs to the latest J-Link firmware (2023-10-30). Everything still working.

Looking forward to hearing what Nordic thinks happened here. Really hoping they can reproduce the problem to investigate it fully.