Failure to burn nRF52840 on the nRF52840 DK

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Mon, 13 May 2019 13:38:09 GMT

seems as old as mine... strange there were 2 different board versions released on the same week (14) 2017.

is your board version 1.0.0?

RE: Failure to burn nRF52840 on the nRF52840 DK

Jules — Fri, 10 May 2019 12:49:04 GMT

I have exactly the same issue with a PCA10056
v0.0.1
2017.14

RE: Failure to burn nRF52840 on the nRF52840 DK

Jørgen Holmefjord — Tue, 23 Apr 2019 15:04:13 GMT

Unfortunately, this is a very old board. I would recommend that you replace it with a v1.x.0 DK.

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Sun, 21 Apr 2019 08:55:44 GMT

nRF52840-Preview-DK.

PCA10056
V0.9.1
2017.14

RE: Failure to burn nRF52840 on the nRF52840 DK

Jørgen Holmefjord — Wed, 17 Apr 2019 14:01:39 GMT

Which revision of the DK do you have?

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Wed, 17 Apr 2019 10:40:04 GMT

all we ever burned to this DK is the DFU Bootloader and example HEX, from here :
<SDK 15.3>\examples\dfu\secure_dfu_test_images\ble\nrf52840.
I don't believe any constantly send to UART.
I just tried to recover the BLE MCU, using this:

nrfjprog -f nrf52 --recover

And it did not work:

C:\Users\Koby>nrfjprog --reset -f nrf52
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

C:\Users\Koby>nrfjprog -f nrf52 --recover
Recovering device. This operation might take 30s.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Wed, 17 Apr 2019 07:49:45 GMT

After the board's nRF52840 stopped responding, I've started using the board as a debugger/burner, via its "Debug out" port. It is still capable in that way.
prior to the defect, I haven't connected it to anything besides the computer's USB port via J2.
I can try to burn the defective nRF52840 via the "Debug in" port, just to know if the defect is in the BLE chip, or the path from the PCA10056 to the BLE chip.

RE: Failure to burn nRF52840 on the nRF52840 DK

Nguyen Hoan Hoang — Tue, 16 Apr 2019 17:28:02 GMT

First thing that comes in mind. Is it protected some how ? Try to unlock it using nrfjprog. Second thing, does your firmware stream something to UART constantly ?

RE: Failure to burn nRF52840 on the nRF52840 DK

Jørgen Holmefjord — Tue, 16 Apr 2019 14:39:02 GMT

I'm not aware of anything in FW or flashing procedure that could brick the chip. Did you apply any conditions outside the Absolute maximum ratings to the chip?

If you have a second DK, you can try flashing the chip through the debug out/debug in interfaces.

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Tue, 16 Apr 2019 06:27:35 GMT

So I guess I'm still stuck with this problem.Anything else I can try?

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Mon, 15 Apr 2019 14:18:26 GMT

Hello.
No modifications were made to the board.

I already tried to reprogram the bootloader in the link you've provided, and that did not help.
Another board I'm working with, with the same process, still works fine, but
3 new DK boards are on their way to my company, but I'm afraid that something in my FW burn process damages them, and I would like to avoid damaging the new ones as well.

RE: Failure to burn nRF52840 on the nRF52840 DK

Jørgen Holmefjord — Mon, 15 Apr 2019 11:47:34 GMT

Hi,

Have you made any modifications to the DK board?

Can you try reflashing the interface MCU firmware (J-Link OB debugger), by holding IF/BOOT (reset) button while powering the board, and dragging the firmware (J-Link OB-SAM3U128-V2-NordicSemi 170724.bin) to the BOOTLOADER removable drive?

Best regards,
Jørgen

RE: Failure to burn nRF52840 on the nRF52840 DK

kobyatom — Mon, 15 Apr 2019 10:15:43 GMT

If you're referring to LED 5, it is flashing several times in the 1st second after turn on, and then remains steadily on.

RE: Failure to burn nRF52840 on the nRF52840 DK

cbd — Mon, 15 Apr 2019 08:46:05 GMT

What state is the interface chip LED in?