• State Verified Answer
  • Replies 15 replies
  • Subscribers 70 subscribers
  • Views 2740 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 322332
Options

Unable to Flash Blinky

a.calpitojr@gmail.com

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.

  • 0 in reply to [email protected]

    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.

  • 0 in reply to kriswilk

    I had the same issue going through the nRF Connect SDK Fundamentals course.

    I had installed J-Link 7.96g and got the error "ERROR: No debuggers were discovered."

    I ran nrfjprog -i and saw no devices connected

    Uninstalled J-Link and installed 7.88j and the device showed up and I was able to flash.

    Uninstalled J-Link and reinstalled latest and the device still shows up. Something missing in that later version I guess.

    Gonna leave a note in the course feedback.

  • 0 in reply to robbsadler

    I had an identical experience as robbsadler. New laptop.  Issue was resolved by rolling back to J-link v7.88.  Also uninstalled v7.88 and re-installed 7.96h.  Issue remained solved.

    Seems like a pattern.

  • 0

    I had the same issue and resolved it by installing J-link v7.88. Definitely a pattern.

  • 0 in reply to BrettS

    I had a problem with the 7.94e that got installed automatically with the nRF Command Line Tools install.  I went to segger.com and download the latest Jlink software and documentation pack (7.96I as of this post).  All of sudden my nRF5340DK Jlink shows up in the JLink Configurator.  So I guess it was a driver issue with the older version of Jlink.  Now it's working.

Related