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

[Sparqq]

After setting up the tool chain and confirm it is compiling correctly by flashing the Proximity build into the dev kit PCA10040 and confirmed with the Android App it is fully working. Now I wanted to try out my board my own designed board and flash the same files (softdevice and application) into the nRF52832 with nRFgo Studion and a Segger J-link. Loading of the softdevice (S132) worked, but loading of the application failed and now I cannot connect to the chip anymore. 

Pressing the recover button in nRFGo Studio it is not resolving the issue. 

[Hung Bui]

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. 

[Sparqq]

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.

[Sparqq]

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.

[Hung Bui]

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. 

[Sparqq]

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

[Sparqq]

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

[Hung Bui]

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. 

[Sparqq]

I am sure that VDD get's 3.3V

[Hung Bui]

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.  

[Sparqq]

That didn't make a difference 

[Hung Bui]

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)