• State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 75 subscribers
  • Views 825 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 312817
Options

DK no longer recognised

watarata

I have just started with a new nRF52840DK, and was progressing well with VSCode etc.
I attempted to download Zephyr/samples/bluetooth/beacon to the kit, and it failed mid download (hung)
(Perhaps there is something I failed to appreciate about this samples compatibility .. however..)

Without any changes to connections or switches etc.
The board is no longer recognised in VS Code, and the 52840 CPU is happily running the last downloaded code.(Flashing LEDS and writing to the serial port)
The JLink section appears to be functional, as the 2 Serial ports appear, and work (in the SERIAL MONITOR section of VSCode - pic)
The JLink Drive also turns up in Explorer.
Dropping a Hex file onto this Drive - causes it to disappear after a second or so - indicating the JLink has tried to download to MCU - but it does not change the code.

nrfjprog 'knows about' the jlink, but hangs when attempting to perform any action. ( e.g. --eraseall ...)
My conclusion is that the Target MCU is not responding - possibly due to some boot/ loader being clobbered ??
Is there any way to restore some kind of base to the target MCU?

C:\Users\Owner>nrfjprog --ids --expand
---------- Emulators ----------
serial number:      1050266490
connection type:    USB
-------------------------------

C:\Users\Owner>nrfjprog --com
1050266490    COM5    VCOM0
1050266490    COM4    VCOM1

C:\Users\Owner>nrfjprog --reset
^C                       // <- ^C after some time
C:\Users\Owner>

VS Code details

Parents
  • 0

    SOLVED:

    Well - problem sorted.

    When I went to grab the DK to hook up to different computer, I found that Microsoft had decided to update/reboot my main computer behind my back(as they are want to do).
    After reboot, as a matter of interest, before moving the DK - I fired up VSCode - and lo and behold - the DK Turned up as expected.

    I've been able to upload code & debug just fine since. (Including the Beacon Example which I thought might have been the issue)
    So my CMD terminal windows and VSCode etc were all shutdown (don't know if just closing all of them would have been sufficient ??)

    Something certainly had things locked up, probably best advice for anyone finding something similar is "Try rebooting windows"
    Not at all intuitive - but always the final goto since Win3.11 Stuck out tongue winking eye

    Thanks to all who suggested another machine etc - even when that seemed not likely as it 'was working perfectly and nothing had changed'.

Reply
  • 0

    SOLVED:

    Well - problem sorted.

    When I went to grab the DK to hook up to different computer, I found that Microsoft had decided to update/reboot my main computer behind my back(as they are want to do).
    After reboot, as a matter of interest, before moving the DK - I fired up VSCode - and lo and behold - the DK Turned up as expected.

    I've been able to upload code & debug just fine since. (Including the Beacon Example which I thought might have been the issue)
    So my CMD terminal windows and VSCode etc were all shutdown (don't know if just closing all of them would have been sufficient ??)

    Something certainly had things locked up, probably best advice for anyone finding something similar is "Try rebooting windows"
    Not at all intuitive - but always the final goto since Win3.11 Stuck out tongue winking eye

    Thanks to all who suggested another machine etc - even when that seemed not likely as it 'was working perfectly and nothing had changed'.

Children
Related
Terms of service