• State Verified Answer
  • Replies 2 replies
  • Subscribers 74 subscribers
  • Views 1209 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 302484
Options

nRF52840-Dongle bricked on first program

notaprogrammer

Hardware:
nRF52840-Dongle

Utilities:
nRF Connect for Desktop v3.12.0 (Win10)
Programmer v3.0.4
sniffer_nrf52840dongle_nrf52840_4.1.1.hex

Plugged in Dongle and was properly recognized by the OS and within the Programmer tool and had the blinking Red light when plugged in.

Attempted first programming of nRF52840 Dongle using the sniffer_nrf52840dongle_nrf52840_4.1.1.hex file.

After uploading the image, the device memory could no longer be read.  There are no longer any lights on the dongle when plugging in.  Programmer identifies the device as 'UNKNOWN_FAMILY' and does not allow me to write any new hex files to the device.

I attempted all recovery solutions I could find on the forums:

Attempted pressing SW1 and then selecting the device in Programmer.  No change.

Pressing RESET disconnects the device in Programmer.  When re-connecting the same issue remains.

Tried holding RESET button while plugged in, or even while plugging in (power cycling) the dongle.  No change, and it does not show up as a USB drive so I cannot drop any bootloaders.

Attempted nrfjprog -f NRF52 --recover  in both Windows 10 CLI and Linux CLI.

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.

Dongle is plugged directly into a PC USB port (no cables or hubs).
I do not have an external SEGGER/J-Link Device.  Are there any additional recovery steps I can perform, or corrected procedures to what I have already attempted?
Can anyone identify what I did wrong so that I don't bork my other dongle as well?

Logs from the original Write are attached, as well as a screenshot of the current Programmer UI.

Current Error logs when connecting to the device are below:

2023-02-07T06:22:56.773Z DEBUG Application data folder: C:\Users\User\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2023-02-07T06:22:56.828Z INFO Using nrf-device-lib-js version: 0.4.13
2023-02-07T06:22:56.829Z INFO Using nrf-device-lib version: 0.12.8
2023-02-07T06:22:56.829Z INFO Using nrfjprog DLL version: 10.16.0
2023-02-07T06:22:56.829Z INFO Using JLink version: JLink_V7.66a
2023-02-07T06:22:56.856Z DEBUG App pc-nrfconnect-programmer v3.0.4 official
2023-02-07T06:22:56.856Z DEBUG App path: C:\Users\User\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2023-02-07T06:22:56.857Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2023-02-07T06:22:56.857Z DEBUG nRFConnect path: C:\Users\User\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-02-07T06:22:56.857Z DEBUG HomeDir: C:\Users\User
2023-02-07T06:22:56.857Z DEBUG TmpDir: C:\Users\User\AppData\Local\Temp
2023-02-07T06:23:08.299Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via USB SDFU protocol
2023-02-07T06:23:08.383Z ERROR Error when fetching device versions: readFwInfo error (Origin: "Error when starting nrfdl_fw_read_info")

Fullscreen 2023-02-07T04_57_47.774Z-log.txt Download 
2023-02-07T04:57:48.090Z DEBUG Application data folder: C:\Users\User\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2023-02-07T04:57:48.148Z INFO Using nrf-device-lib-js version: 0.4.13
2023-02-07T04:57:48.148Z INFO Using nrf-device-lib version: 0.12.8
2023-02-07T04:57:48.148Z WARN Unable to detect version of nrfjprog DLL.
2023-02-07T04:57:48.148Z WARN Unable to detect version of JLink.
2023-02-07T04:57:48.176Z DEBUG App pc-nrfconnect-programmer v3.0.4 official
2023-02-07T04:57:48.176Z DEBUG App path: C:\Users\User\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2023-02-07T04:57:48.176Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2023-02-07T04:57:48.176Z DEBUG nRFConnect path: C:\Users\User\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-02-07T04:57:48.176Z DEBUG HomeDir: C:\Users\User
2023-02-07T04:57:48.176Z DEBUG TmpDir: C:\Users\User\AppData\Local\Temp
2023-02-07T04:57:48.178Z INFO Installed JLink version does not match the provided version (V7.66a)
2023-02-07T04:58:10.785Z INFO Parsing HEX file:  C:\Users\User\Downloads\nrf_sniffer_for_bluetooth_le_4.1.1\hex\sniffer_nrf52840dongle_nrf52840_4.1.1.hex
2023-02-07T04:58:10.795Z INFO File was last modified at  2/6/2023, 11:53:17 PM
2023-02-07T04:58:10.835Z INFO Update files regions according to Application core
2023-02-07T04:58:10.835Z INFO Parse memory regions for file
2023-02-07T04:59:41.168Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via USB SDFU protocol
2023-02-07T04:59:41.751Z INFO Update files regions according to Application core
2023-02-07T04:59:41.751Z INFO Parse memory regions for file
2023-02-07T04:59:49.217Z INFO Does not need to be reloaded:  C:\Users\User\Downloads\nrf_sniffer_for_bluetooth_le_4.1.1\hex\sniffer_nrf52840dongle_nrf52840_4.1.1.hex
2023-02-07T04:59:49.219Z INFO Hash is generated by SHA256
2023-02-07T04:59:49.222Z INFO Performing DFU. This may take a few seconds
2023-02-07T04:59:49.242Z INFO Opening serial port for SDFU programming: 0%
2023-02-07T04:59:49.664Z INFO Opening serial port for SDFU programming: 100%
2023-02-07T04:59:49.786Z INFO Uploading image through SDFU: 0%
2023-02-07T04:59:50.065Z INFO Uploading image through SDFU: 1%
2023-02-07T04:59:50.084Z INFO Uploading image through SDFU: 3%
2023-02-07T04:59:50.103Z INFO Uploading image through SDFU: 4%
2023-02-07T04:59:50.122Z INFO Uploading image through SDFU: 5%
2023-02-07T04:59:50.306Z INFO Uploading image through SDFU: 7%
2023-02-07T04:59:50.325Z INFO Uploading image through SDFU: 8%
2023-02-07T04:59:50.344Z INFO Uploading image through SDFU: 10%
2023-02-07T04:59:50.363Z INFO Uploading image through SDFU: 11%
2023-02-07T04:59:50.533Z INFO Uploading image through SDFU: 13%
2023-02-07T04:59:50.551Z INFO Uploading image through SDFU: 14%
2023-02-07T04:59:50.570Z INFO Uploading image through SDFU: 16%
2023-02-07T04:59:50.589Z INFO Uploading image through SDFU: 17%
2023-02-07T04:59:50.775Z INFO Uploading image through SDFU: 19%
2023-02-07T04:59:50.794Z INFO Uploading image through SDFU: 20%
2023-02-07T04:59:50.813Z INFO Uploading image through SDFU: 22%
2023-02-07T04:59:50.832Z INFO Uploading image through SDFU: 23%
2023-02-07T04:59:51.017Z INFO Uploading image through SDFU: 25%
2023-02-07T04:59:51.036Z INFO Uploading image through SDFU: 26%
2023-02-07T04:59:51.055Z INFO Uploading image through SDFU: 28%
2023-02-07T04:59:51.075Z INFO Uploading image through SDFU: 29%
2023-02-07T04:59:51.260Z INFO Uploading image through SDFU: 30%
2023-02-07T04:59:51.279Z INFO Uploading image through SDFU: 32%
2023-02-07T04:59:51.299Z INFO Uploading image through SDFU: 33%
2023-02-07T04:59:51.317Z INFO Uploading image through SDFU: 35%
2023-02-07T04:59:51.501Z INFO Uploading image through SDFU: 36%
2023-02-07T04:59:51.520Z INFO Uploading image through SDFU: 38%
2023-02-07T04:59:51.539Z INFO Uploading image through SDFU: 39%
2023-02-07T04:59:51.558Z INFO Uploading image through SDFU: 41%
2023-02-07T04:59:51.729Z INFO Uploading image through SDFU: 42%
2023-02-07T04:59:51.748Z INFO Uploading image through SDFU: 44%
2023-02-07T04:59:51.767Z INFO Uploading image through SDFU: 45%
2023-02-07T04:59:51.786Z INFO Uploading image through SDFU: 47%
2023-02-07T04:59:51.970Z INFO Uploading image through SDFU: 48%
2023-02-07T04:59:51.989Z INFO Uploading image through SDFU: 50%
2023-02-07T04:59:52.008Z INFO Uploading image through SDFU: 51%
2023-02-07T04:59:52.027Z INFO Uploading image through SDFU: 52%
2023-02-07T04:59:52.212Z INFO Uploading image through SDFU: 54%
2023-02-07T04:59:52.231Z INFO Uploading image through SDFU: 55%
2023-02-07T04:59:52.250Z INFO Uploading image through SDFU: 57%
2023-02-07T04:59:52.269Z INFO Uploading image through SDFU: 58%
2023-02-07T04:59:52.455Z INFO Uploading image through SDFU: 60%
2023-02-07T04:59:52.474Z INFO Uploading image through SDFU: 61%
2023-02-07T04:59:52.495Z INFO Uploading image through SDFU: 63%
2023-02-07T04:59:52.512Z INFO Uploading image through SDFU: 64%
2023-02-07T04:59:52.696Z INFO Uploading image through SDFU: 66%
2023-02-07T04:59:52.715Z INFO Uploading image through SDFU: 67%
2023-02-07T04:59:52.734Z INFO Uploading image through SDFU: 69%
2023-02-07T04:59:52.753Z INFO Uploading image through SDFU: 70%
2023-02-07T04:59:52.923Z INFO Uploading image through SDFU: 72%
2023-02-07T04:59:52.942Z INFO Uploading image through SDFU: 73%
2023-02-07T04:59:52.961Z INFO Uploading image through SDFU: 75%
2023-02-07T04:59:52.980Z INFO Uploading image through SDFU: 76%
2023-02-07T04:59:53.164Z INFO Uploading image through SDFU: 77%
2023-02-07T04:59:53.183Z INFO Uploading image through SDFU: 79%
2023-02-07T04:59:53.203Z INFO Uploading image through SDFU: 80%
2023-02-07T04:59:53.222Z INFO Uploading image through SDFU: 82%
2023-02-07T04:59:53.406Z INFO Uploading image through SDFU: 83%
2023-02-07T04:59:53.425Z INFO Uploading image through SDFU: 85%
2023-02-07T04:59:53.444Z INFO Uploading image through SDFU: 86%
2023-02-07T04:59:53.462Z INFO Uploading image through SDFU: 88%
2023-02-07T04:59:53.634Z INFO Uploading image through SDFU: 89%
2023-02-07T04:59:53.653Z INFO Uploading image through SDFU: 91%
2023-02-07T04:59:53.672Z INFO Uploading image through SDFU: 92%
2023-02-07T04:59:53.691Z INFO Uploading image through SDFU: 94%
2023-02-07T04:59:53.878Z INFO Uploading image through SDFU: 95%
2023-02-07T04:59:53.897Z INFO Uploading image through SDFU: 97%
2023-02-07T04:59:53.916Z INFO Uploading image through SDFU: 98%
2023-02-07T04:59:53.934Z INFO Uploading image through SDFU: 100%
2023-02-07T04:59:54.071Z INFO All dfu images have been written to the target device
2023-02-07T04:59:54.073Z DEBUG Will wait for device C79371C19754
2023-02-07T04:59:54.225Z INFO Target device closed
2023-02-07T04:59:57.074Z DEBUG Timeout when waiting for attachment of device with serial number C79371C19754
2023-02-07T04:59:57.074Z ERROR Failed to write: Error: Timeout while waiting for device  C79371C19754 to be attached and enumerated
2023-02-07T05:02:45.969Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via USB SDFU protocol
2023-02-07T05:02:46.053Z ERROR Error when fetching device versions: readFwInfo error (Origin: "Error when starting nrfdl_fw_read_info")
2023-02-07T05:03:04.211Z INFO Target device closed
2023-02-07T05:03:12.672Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via USB SDFU protocol
2023-02-07T05:03:12.755Z ERROR Error when fetching device versions: readFwInfo error (Origin: "Error when starting nrfdl_fw_read_info")
2023-02-07T05:05:37.554Z INFO Target device closed
2023-02-07T05:05:40.072Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via USB SDFU protocol
2023-02-07T05:05:40.155Z ERROR Error when fetching device versions: readFwInfo error (Origin: "Error when starting nrfdl_fw_read_info")

Parents Reply
  • +1 in reply to Kenneth

    Thanks.  I didn't notice any clearly called-out steps in article itself that were able to resolve my situation, since the "Programmer" utility wouldn't recognize the dongle and I don't have a $400 programmer.  However, in the comments section I did just find the below nugget regarding the "Connect BLE" Utility and it somehow allowed me to recover the device.

    Online  in reply to brianreinhold

    The nRF Connect Programmer will not destroy your dongle. But you need to re-flash it with the connectivity firmware that is used by pc-ble-driver. The easiest way to do this is to press the reset button so that it enters DFU mode, and then select the dongle in nRF Connect BLE. When you do it will ask you if it should flash the connectivity firmware.

Children
No Data
Related
Terms of service