nRF5340 Audio DK erased and bricked?

I just got a new set of nRF5340 Audio DKs and I may have been too fast on the trigger trying to flash the boards with example programs.  I'm using VS Code, and I'm a newbie with this workflow (I don't do much coding or firmware these days), so I hurried through opening a sample application, building it, and trying to flash the board.  I got some kind of "are you sure" warning about erasing the chip, but clicked Yes anyway.  The application did not run on the board as I had hoped it would.

Now, in the Connected Devices section of the NRF Connect tab, my device shows as a number, and the "..." button to the right has the Recover Board option grayed out.  

When I try to flash my application to the board, I get the following errors:

I have the same issue with both my boards.  Are they bricked?  Recoverable?  Any help will be greatly appreciated!

Parents Reply Children
  • Hi Rob,

    I just noticed from your logs that you might be trying to flash the hex file of nRF52 onto the 5340 Audio DK.

    This explains the problem. Please so try with the appropriate 5340 file and let me know how it goes.

    -Priyanka

  • Thanks for the help!  I will try that when I get to the office in a couple hours.  

    Is it normal for my board to show up as "a number" in the Connected Devices list?  In a tutorial video it shows up by name, e.g. "nRF5340 Dev Board" or something like that.

  • OK, I was able to rename my boards, so I think you can ignore my question above.  I'll start a new thread on this ticket to describe my latest issues (app doesn't seem to run).

  • If this does not work for either the --recover version or the programmer app, what is the reason for this and how do I fix it?

    I have a total of 3x NRF5340 Audio DK:
    1 is configured as gateway (green light)
    1 as left (blue light)
    1 should be right (light magenta)

    The one that lights magenta does not connect to the gateway and when I try to program this Audio DK, it gets stuck at the programming point "Programming net core on": xxxxxxxxxxxxx headset left" (x's are the number ID of the back) even after 1 hour of waiting (the others only took a few minutes).

    I have tried to reconnect the device to the PC several times and have also run "nrfjprog --recover" but have also got stuck in the recovery process.

    When I plug the Audio DK into the PC, all I get is LED3 flashing (about 500ms off 500ms on) and RGB2 flashing really fast. OBEXT, IFMCU and HUB are also always on. The middle LED is magenta.

    There are two USB serial ports (COM27 and COM28) in the Windows device manager.

    With "nrfjprog -i" I do not get any number.

    And two hours before the device was recognised. in the list of "nrfjprog -i

Related