Bricked nRF52832 with Segger J-link, can't recover it

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Wed, 02 May 2018 04:50:39 GMT

Problem got solved a while ago, the reset button was connected wrongly. The button was pulling the reset line down all the time, the reset isn't enabled before first time programming, but it is when you program the blinky code and therefor cannot be programmed anymore until the reset line is released.

Thanks everybody for helping.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Fri, 09 Feb 2018 07:20:16 GMT

stripped all the parts from the board, only left the nRF52832 on it and is now supplied by the programmer. Verified that SWDCLK and SWDIO are connected correctly (chip to programmer) and not shorted. Still the same.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Fri, 09 Feb 2018 07:19:18 GMT

updated everything to the latest version, see log below;

--------------------------------------------------------------------------------
nrfjprog.exe --recover --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Fri, 09 Feb 2018 03:45:06 GMT

Tried both options, same result

RE: Bricked nRF52832 with Segger J-link, can't recover it

Jay Tyzzer — Thu, 08 Feb 2018 20:34:21 GMT

Are you supplying the DUT with its own power?

RE: Bricked nRF52832 with Segger J-link, can't recover it

Jay Tyzzer — Thu, 08 Feb 2018 20:32:37 GMT

Have you updated the Segger J-Link firmware on the pc and on the board? Are you powering your board up independently of the Dev kit? This is a must.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Simen August Tinderholt — Thu, 08 Feb 2018 17:57:22 GMT

I see you're using quite an old version of nRFJProg, could you try to update it? There are some stability improvements when it comes to recover on the newer versions that might benefit you.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Hung Bui — Thu, 08 Feb 2018 10:27:01 GMT

It's hard to tell what can be wrong. The programmer complains that Could not power-up debug power domain.

My suggestion is to try testing on an unpopulated board without any other components, make sure the SWD pins are connected properly and the chip and the debugger share the same ground (not just ground detect pin in the header)

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Thu, 08 Feb 2018 05:17:03 GMT

That didn't make a difference

RE: Bricked nRF52832 with Segger J-link, can't recover it

Hung Bui — Wed, 07 Feb 2018 07:27:19 GMT

Please try to use shorter cable. Try to have something less than 10cm from the header of the programmer. Your total cable length in the photo seems to be about 30 cm or more. There will be lots of parasitic resistance and inductance. Also please don't twist/tie the cables together.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Wed, 07 Feb 2018 07:07:35 GMT

I am sure that VDD get's 3.3V

RE: Bricked nRF52832 with Segger J-link, can't recover it

Hung Bui — Wed, 07 Feb 2018 06:56:44 GMT

Please send a close up photo of the set-up.

Make sure you provided correct 3.3V on VDD. You can also use VDD from the DK.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Wed, 07 Feb 2018 06:40:43 GMT

I also have tried it with a Segger J-link directly with the same results;

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Wed, 07 Feb 2018 06:22:40 GMT

See the picture below on how it is connected. The chip is externally supplied wit 3.3V on the VCC.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Hung Bui — Tue, 06 Feb 2018 12:12:01 GMT

Please take a photo of your setup. Make sure you connect the Vref pin to the DK. I suspect there could be a problem with the SWD connections or the power of the chip.

Usually, you won't be able to brick the chip by just flashing softdevice or application to it.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Tue, 06 Feb 2018 09:09:56 GMT

I've connected the target board to the debug output of Nordik DK 400150 to make sure the issue is not cause by the J-link. The target board is supplied with an external 3.0V

nrfjprog.exe -f NRF52 --recover --log
nrfjprog verion 8.5.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: recover.
FUNCTION: recover.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Communication timed out: Requested 20 bytes, received 0 bytes !
Could not read hardware status!
JLinkARM.dll Connect returned error -257.
Could not transfer JTAG data.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
JLinkARM.dll IsHalted returned error -1.
FUNCTION: close_dll.
FUNCTION: close_dll.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Sparqq — Tue, 06 Feb 2018 07:35:03 GMT

I've tried to recover it with nrfjprog, but it gives the following error;

nrfjprog.exe -f NRF52 --recover --log

WARNING: No logging will be possible since nrfjprog.exe has no write permission
WARNING: to the current directory.
Recovering device. This operation might take 30s.
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.

The log file is as follows:

--------------------------------------------------------------------------------
nrfjprog.exe -f NRF52 --recover --log
nrfjprog verion 8.5.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: recover.
FUNCTION: recover.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll Connect returned error -261.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
AP-IDR: 0x00000000, Type: JTAG-AP
JLinkARM.dll IsHalted returned error -1.
FUNCTION: close_dll.
FUNCTION: close_dll.

RE: Bricked nRF52832 with Segger J-link, can't recover it

Hung Bui — Mon, 05 Feb 2018 12:29:04 GMT

Please try to use nrfjprog.exe tool to recover/programming. Make sure you select --family NRF52.

Please try to test first using non-softdevice application, for example blinky application.