Bricked PCA10056 52840 DK

RE: Bricked PCA10056 52840 DK

Priyanka — Thu, 28 Nov 2024 02:36:22 GMT

Happy to help. 🙂

RE: Bricked PCA10056 52840 DK

fe7565 — Wed, 27 Nov 2024 22:42:32 GMT

Thank you very much for your patience The Interface MCU bin solved the issue, the 52840DK is back to factory settings.

RE: Bricked PCA10056 52840 DK

Priyanka — Wed, 27 Nov 2024 07:36:52 GMT

Hi Tom,

Are you asking whether it's possible to re-upload the J-Link firmware onto your debugger chip?

If your interface MCU is the SEGGER chip (this should be your case, since you mentioned you have the v2.0.1 DK, but please re-check), then it should be possible to re-flash the J-Link fw using the programmer app, by putting the DK in Bootloader mode. You should be able to find the appropriate firmware from the following location:

But if the interface MCU is the 5340 SoC, then I'm afraid it's not possible to re-flash the J-Link fw onto it.

Regards,

Priyanka

RE: Bricked PCA10056 52840 DK

fe7565 — Tue, 26 Nov 2024 20:20:31 GMT

Now that I can program the 52840DK board again, how to restore the factory firmware image, as if came when new?

RE: Bricked PCA10056 52840 DK

fe7565 — Mon, 25 Nov 2024 08:25:26 GMT

I followed your directions: 5430DK Debug Out to 52840DK Debug In, and it worked as far as able to see 52840DK in Programmer and flashed the hex file "blinky" on it.

The four LEDs flash, but Windows does not recognize it us a mass storage device and also Programmer cannot see it either without the 5340DK acting as the debugger probe. Also, the nRF Connect Desktop -> Quick Start does not recognize it either as a 52840DK development board. Is there a bootloader hex or some other firmware to restore the factory nRF52840DK firmware on the board?

Is there one in the nRF5_SDK_17.1.0_ddde560 example folder?

EDIT: uploaded the FDU secure bootloader BLE S140 image and it works, but still does not show up as development board. How to restore it to have USB and mass storage firmware, like it came when new?

RE: Bricked PCA10056 52840 DK

Priyanka — Mon, 25 Nov 2024 08:14:56 GMT

Hi Tom,

Did you try connecting as I had mentioned in my previous reply? Do you get issues then too?

-Priyanka

RE: Bricked PCA10056 52840 DK

fe7565 — Mon, 25 Nov 2024 06:17:33 GMT

I connected the 5340 DK with the 52840 DK in this way: RE: External programming Using nRF52-DK

I am using the P20 method: devzone.nordicsemi.com/.../programming-custom-nrf5340-board-using-nrf5340-development-kit

But nRF Connect Desktop -> Programmer can see the 5340 DK board, and if I remove the VTG cable then it maps out the memory of the 5340DK. But when I re-connect (as it should be) the VTG cable, it says "core protection status is unknown...etc "Press erase all button to recover protected memory" . But in Programmer (nRF Connect Desktop) if I try to "erase all", I get this red error message:

01:31:27.237 Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1

EDIT: let me check again, because I connected the 5349DK SWDCLK and SDWIO from P20 with the P20 of the bricked 52840DK, and I believe those do not connect to the SOC.

RE: Bricked PCA10056 52840 DK

Priyanka — Thu, 21 Nov 2024 06:07:28 GMT

Hi Tom,

Apologies for the delay.

In order to flash the nRF52840SoC on the nRF52840-DK, you can use the 10-pin DebugIN port: https://docs.nordicsemi.com/bundle/ug_nrf52840_dk/page/UG/dk/hw_debug_in_trace.html

And connect this to the debugger SoC on the 5340DK using it's DebugOUT port: https://docs.nordicsemi.com/bundle/ug_nrf5340_dk/page/UG/dk/ext_programming_support_P19.html

-Priyanka

RE: Bricked PCA10056 52840 DK

fe7565 — Wed, 20 Nov 2024 15:04:47 GMT

Just checking if there are any developments suggestions on this. Thank you.

RE: Bricked PCA10056 52840 DK

fe7565 — Mon, 18 Nov 2024 06:37:00 GMT

Thank you for the reply. The sticker says PCA10056 / 2.0.1 / 2020.20 / 683880610.

When I connect the J2 USB port (long side) of the PCA10056 DK to my Windows laptop and turn on POWER on the board, nothing happens. No LEDs, no sign of any device in Windows and in nRF Connect Desktop -> Programmer 4.2.2.

If I disconnect the board, leave the POWER switch ON and hold down the IF BOOT/RESET button while reconnecting the J2 USB...then the LED5 starts flashing, and BOOTLOADER mass storage device shows up in Windows (with 108KB of 128KB free). It does not show up in nRF Connect Desktop -> Programmer. And after about 30 seconds the BOOTLOADER mass storage device disappears on its own, while LED5 remains flashing on the board.

I have a nRF5340 DK, PCA 10095, 2.0.0., 2022.4 and several nRF52840 PCA10059 dongles. I also have the J-Link Edu Mini.

It's a bit late here tonight, but if you could describe how to flash the PCA10056 with the PCA 10095 or with the J-Link Edu Mini, I will do that tomorrow.

EDIT: when I connect the J-Link EDU Mini to SWD CLK/IO/GND/V-in pins on the PCA10056 DK and I open Programmer 4.2.2., J-link shows up as device, and the Programmer is trying to read the DK memory, but get this error message in red color:

Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1)

Error: Failed with exit code 1. One or more batch tasks failed: - [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1), code: Generic. Message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1).

RE: Bricked PCA10056 52840 DK

Priyanka — Mon, 18 Nov 2024 05:33:25 GMT

Hi Tom,

Could you tell me the revision on your DK? (white sticker on DK)

When you connect the J2 USB and normally switch on the DK, is it being detected ?

If you have any other DK could you please try flashing the problematic DK using that, or if you have any other debugger, could you try flashing your DK using that? This will help us isolate the issue to the Debug chip.

Regards,

Priyanka

RE: Bricked PCA10056 52840 DK

fe7565 — Sat, 16 Nov 2024 18:01:56 GMT

The files inside the USB mass storage that appears in Windows for a few seconds when doing a RESET:

-fseventsd (yellow folder)

.metadata_never_index

.Trashes

bootload.htm