How to recover bricked nRF52840 dongle (PCA10059)?

RE: How to recover bricked nRF52840 dongle (PCA10059)?

choehyunho — Thu, 18 Nov 2021 12:13:04 GMT

Never mind.

I restart the dongle in bootloader mode, and I can reprogram it in BLE app.

Thank you for your support.

RE: How to recover bricked nRF52840 dongle (PCA10059)?

choehyunho — Thu, 18 Nov 2021 11:28:50 GMT

OK, thanks. Now I can use BLE sniffer successfully.

How can I config my dongle back to use with Bluetooth Low Energy App, or RSSI Viewer App.

I expected to rewrite original bootloader back may solve the problem, but failed.

Tried to use /cfs-file/__key/communityserver-discussions-components-files/4/1512.pca10059_5F00_bootloader.zip & /cfs-file/__key/communityserver-discussions-components-files/4/7853.pca10059_5F00_bootloader_5F00_mbr_5F00_v1.0.1.hex , but both shows the following error in Programmer App.

2021-11-18T11:24:12.210Z ERROR DFU failed: Error message for known extended error code from DFU target: The init packet does not contain a signature. This bootloader requires DFU updates to be signed.
2021-11-18T11:24:14.222Z ERROR Device not found due to failure during DFU

What should I do now?

RE: How to recover bricked nRF52840 dongle (PCA10059)?

Øyvind — Thu, 18 Nov 2021 09:49:03 GMT

[quote user="choehyunho"]I just want my dongle use with BLE app, RSSI Viewer, or Sniffer purpose, because I already have other DKs.[/quote]

Please see the nRF Sniffer for Bluetooth LE documentation.

RE: How to recover bricked nRF52840 dongle (PCA10059)?

choehyunho — Thu, 18 Nov 2021 06:28:34 GMT

Dongle is detected as SDFU com port, and I tried to write ble_connectivity_s140_usb_hci_pca10059.hex, which is in nRF52 SDK.

It seems to be write correctly, but still not working.

Device Manager shows nRF52 Connectivity device in 'Other Device' section, and yellow bang displayed.

I just want my dongle use with BLE app, RSSI Viewer, or Sniffer purpose, because I already have other DKs.

RE: How to recover bricked nRF52840 dongle (PCA10059)?

Øyvind — Wed, 17 Nov 2021 10:07:16 GMT

In the programmer app of nRF Connect for Desktop, when the device is blinking red and connected to USB of computer, does the device list show "Open DFU Bootloader"? Or in the device manager, under COM ports, do you have a nRF52 SDFU USB device?

[quote user="choehyunho"]BTW, is there any prebuilt nRF52840 dongle firmware which can be used with BLE app or RSSI Viewer app[/quote]

Have a look at the BLE App for nRF Connect for Desktop documentation on how to configure the dongle.

RE: How to recover bricked nRF52840 dongle (PCA10059)?

choehyunho — Wed, 17 Nov 2021 09:41:33 GMT

I understood my dongle is in bootloader mode, but don't know how to proceed.

Previously, I connect dongle and run BLE app, it shows dongle as 'Nordic Semiconductor nRF52 Connectivity", or suggested to update firmware to proceed.

But currently, dongle is not shown in device list.

I have tried to write firmware via JLink with Programmer, and not succeeded as above.

I'll try via DFU tomorrow.

BTW, is there any prebuilt nRF52840 dongle firmware which can be used with BLE app or RSSI Viewer app?

RE: How to recover bricked nRF52840 dongle (PCA10059)?

Øyvind — Wed, 17 Nov 2021 09:22:40 GMT

Hello,

If you have programmed the PPK2 firmware on the nRF52, then this will not be detected as a BLE device.

[quote user="choehyunho"]

When pressing reset button and connect to USB, the red LED is blinking like heartbeat.

[/quote]

This is correct to how the "Getting started guide" describes the LED behavior. Did you try to program the dongle with a supported sample, e.g. BLE App Blinky?

Kind regards,
Øyvind

RE: How to recover bricked nRF52840 dongle (PCA10059)?

choehyunho — Wed, 17 Nov 2021 05:48:44 GMT

Hi.

When pressing reset button and connect to USB, the red LED is blinking like heartbeat.

But, still not detected as proper nRF device when using BLE app, and if I tried to rewrite default bootloader using Programmer app, the following message is shown while reading device map.

2021-11-17T05:41:28.773Z INFO Application data folder: C:\Users\firebird\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-11-17T05:41:28.849Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-11-17T05:41:28.849Z DEBUG App path: C:\Users\firebird\.nrfconnect-apps\external\3.7 compatible apps\node_modules\pc-nrfconnect-programmer
2021-11-17T05:41:28.849Z DEBUG nRFConnect 3.7.1, required by the app is (^3.6.0)
2021-11-17T05:41:28.849Z DEBUG nRFConnect path: C:\Users\firebird\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-11-17T05:41:28.849Z DEBUG HomeDir: C:\Users\firebird
2021-11-17T05:41:28.849Z DEBUG TmpDir: C:\Users\firebird\AppData\Local\Temp
2021-11-17T05:41:28.862Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-11-17T05:41:39.386Z INFO Using nrfjprog to communicate with target
2021-11-17T05:41:39.961Z INFO Using J-Link Software version 7.58
2021-11-17T05:41:40.387Z INFO Segger serial:  50128807
2021-11-17T05:41:40.387Z INFO Segger speed:  2000  kHz
2021-11-17T05:41:40.387Z INFO Segger version:  J-Link V10 compiled Nov  2 2021 12:14:50
2021-11-17T05:41:40.414Z INFO Core probed: 50128807
2021-11-17T05:41:40.415Z INFO Core RAM: 256KiB
2021-11-17T05:41:40.415Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-17T05:41:40.565Z INFO Model: NRF52840_xxAA_REV2.
2021-11-17T05:41:50.844Z ERROR Error while getting readback protection
2021-11-17T05:42:04.060Z INFO Parsing HEX file:  C:\Users\firebird\Downloads\pca10059_bootloader\graviton_bootloader_mbr_v1.0.1-[nRF5_SDK_15.0.1-1.alpha_f76d012].hex
2021-11-17T05:42:04.071Z INFO File was last modified at  2018. 5. 22. 오전 8:20:20
2021-11-17T05:42:18.403Z INFO Using nrfjprog to communicate with target
2021-11-17T05:42:28.717Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: Unknown value (ffffff24)

2021-11-17T05:43:11.568Z INFO Target device closed.
2021-11-17T05:43:15.746Z INFO Using nrfjprog to communicate with target
2021-11-17T05:43:16.230Z INFO Using J-Link Software version 7.58
2021-11-17T05:43:16.655Z INFO Segger serial:  50128807
2021-11-17T05:43:16.655Z INFO Segger speed:  2000  kHz
2021-11-17T05:43:16.655Z INFO Segger version:  J-Link V10 compiled Nov  2 2021 12:14:50
2021-11-17T05:43:16.655Z INFO Core probed: 50128807
2021-11-17T05:43:16.655Z INFO Core RAM: 256KiB
2021-11-17T05:43:16.655Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-17T05:43:16.818Z INFO Model: NRF52840_xxAA_REV2.
2021-11-17T05:43:27.143Z ERROR Error while getting readback protection
2021-11-17T05:43:39.043Z INFO Using nrfjprog to communicate with target
2021-11-17T05:43:49.339Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: Unknown value (ffffff24)

RE: How to recover bricked nRF52840 dongle (PCA10059)?

Øyvind — Tue, 16 Nov 2021 16:26:22 GMT

Hello,

Sorry to hear about this issue. Just to verify, have you tried holding the reset button while inserting the dongle in USB?

Will need some time to figure out what is going on, and will provide an answer by tomorrow.

Kind regards,
Øyvind