nRF52 DK stopped working abruptly and is not recoverable

[Pravin Carvalho]

I was running an application we have recently developed and it was connected to my phone when the LED1 started glowing faintly and then the bluetooth connection dropped. After this point the device stopped advertising and I am unable to flash a new softdevice or firmware.

I am able to run the dev kit in the bootloader mode if I hold down the BOOT/RESET button and flash a new bootloader. However, any attempts to communicate with the nRF chip return the following error.

. . . . nRFXX_write_debug_port_register: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

. . . nRFXX_power_debug_and_system_regions: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

I am using nRF command line tools v9.7.3 and Jlink version v632e on MacOS. The full log is attached below

--------------------------------------------------------------------------------
./nrfjprog -s 682466191 --recover --log
nrfjprog version 9.7.3
--------------------------------------------------------------------------------
nRF_open_dll
. nRFXX_open_dll
. . nRFXX_dll_version
nRF_enum_emu_snr
. nRFXX_enum_emu_snr
nRF_enum_emu_snr
. nRFXX_enum_emu_snr
nRF_connect_to_emu_with_snr
. nRFXX_connect_to_emu_with_snr
. . nRFXX_is_connected_to_emu
. . nRFXX_connect_to_emu_without_snr
. . . nRFXX_is_connected_to_emu
. . . nRFXX_enum_emu_snr
. . nRFXX_connect_to_emu_without_snr: JLink: Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 24 2017 17:30:12
. . nRFXX_connect_to_emu_without_snr: JLink: Updating firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
. . nRFXX_connect_to_emu_without_snr: JLink: Updating firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
. . nRFXX_connect_to_emu_without_snr: JLink: Replacing firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 24 2017 17:30:12
. . nRFXX_connect_to_emu_without_snr: JLink: Replacing firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 24 2017 17:30:12
. . nRFXX_connect_to_emu_without_snr: JLink: Waiting for new firmware to boot
. . nRFXX_connect_to_emu_without_snr: JLink: Waiting for new firmware to boot
. . nRFXX_connect_to_emu_without_snr: JLink: New firmware booted successfully
. . nRFXX_connect_to_emu_without_snr: JLink: New firmware booted successfully
. . nRFXX_connect_to_emu_without_snr: JLink: Hardware: V1.00
. . nRFXX_connect_to_emu_without_snr: JLink: S/N: 682466191
. . nRFXX_connect_to_emu_without_snr: JLink: TELNET listener socket opened on port 19021
. . nRFXX_connect_to_emu_without_snr: JLink: WEBSRV Starting webserver
. . nRFXX_connect_to_emu_without_snr: JLink: (21299ms, 21306ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 000:008
. . nRFXX_connect_to_emu_without_snr: JLink: WEBSRV Webserver running on local port 19080
. . nRFXX_connect_to_emu_without_snr: JLink: (21299ms, 21306ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 000:008
. . nRFXX_connect_to_emu_without_snr: JLink: returns O.K.
. . nRFXX_connect_to_emu_without_snr: JLink: (21299ms, 21306ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:308
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_GetHWStatus(...)
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x00
. . nRFXX_connect_to_emu_without_snr: JLink: (0008ms, 21314ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:317
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("Device = NRF52832_xxAA", ...).
. . nRFXX_connect_to_emu_without_snr: JLink: XML file found at: /Applications/SEGGER/JLink/JLinkDevices.xml
. . nRFXX_connect_to_emu_without_snr: JLink: (0023ms, 21339ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:318
. . nRFXX_connect_to_emu_without_snr: JLink: /Applications/SEGGER/JLink/JLinkDevices.xml evaluated successfully.
. . nRFXX_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
. . nRFXX_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x00
. . nRFXX_connect_to_emu_without_snr: JLink: (0071ms, 21387ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:390
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetRestartOnClose = 0", ...).
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x01
. . nRFXX_connect_to_emu_without_snr: JLink: (0001ms, 21389ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:391
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("DisableFlashDL", ...).
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x00
. . nRFXX_connect_to_emu_without_snr: JLink: (0000ms, 21389ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:391
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetDbgPowerDownOnClose = 1", ...).
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x01
. . nRFXX_connect_to_emu_without_snr: JLink: (0000ms, 21389ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:392
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x00
. . nRFXX_connect_to_emu_without_snr: JLink: (0000ms, 21390ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:392
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_TIF_Select(JLINKARM_TIF_SWD)
. . nRFXX_connect_to_emu_without_snr: JLink: returns 0x00
. . nRFXX_connect_to_emu_without_snr: JLink: (0003ms, 21393ms total)
. . nRFXX_connect_to_emu_without_snr: JLink: T98699380 021:395
. . nRFXX_connect_to_emu_without_snr: JLink: JLINK_SetSpeed(2000)
. . nRFXX_connect_to_emu_without_snr: JLink: (0000ms, 21393ms total)
nRF_read_connected_emu_snr
. nRFXX_read_connected_emu_snr
. . nRFXX_is_connected_to_emu
. . nRFXX_is_connected_to_emu: JLink: T98699380 021:396
. . nRFXX_is_connected_to_emu: JLink: JLINK_IsOpen()
. . nRFXX_is_connected_to_emu: JLink: returns 0x01
. . nRFXX_is_connected_to_emu: JLink: (0000ms, 21393ms total)
nRF_read_device_family
. nRFXX_read_device_family
. . nRFXX_is_connected_to_emu
. . nRFXX_is_connected_to_emu: JLink: T98699380 021:397
. . nRFXX_is_connected_to_emu: JLink: JLINK_IsOpen()
. . nRFXX_is_connected_to_emu: JLink: returns 0x01
. . nRFXX_is_connected_to_emu: JLink: (0000ms, 21393ms total)
. . nRFXX_read_access_port_register
. . . nRFXX_coresight_configure
. . . nRFXX_coresight_configure: JLink: T98699380 021:397
. . . nRFXX_coresight_configure: JLink: JLINK_CORESIGHT_Configure()
. . . nRFXX_coresight_configure: JLink: returns 0
. . . nRFXX_coresight_configure: JLink: (0102ms, 21495ms total)
. . . nRFXX_power_debug_and_system_regions
. . . . nRFXX_write_debug_port_register
. . . . nRFXX_write_debug_port_register: JLink: T98699380 021:499
. . . . nRFXX_write_debug_port_register: JLink: JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
. . . . nRFXX_write_debug_port_register: JLink: returns -1
. . . . nRFXX_write_debug_port_register: JLink: (0003ms, 21498ms total)
. . . . nRFXX_write_debug_port_register: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

. . . nRFXX_power_debug_and_system_regions: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

nRF_close_dll
. nRFXX_close_dll
. . nRFXX_is_connected_to_emu
. . nRFXX_is_connected_to_emu: JLink: T98699380 021:503
. . nRFXX_is_connected_to_emu: JLink: JLINK_IsOpen()
. . nRFXX_is_connected_to_emu: JLink: returns 0x01
. . nRFXX_is_connected_to_emu: JLink: (0000ms, 21498ms total)
. . nRFXX_disconnect_from_emu
. . nRFXX_disconnect_from_emu: JLink: T98699380 021:510
. . nRFXX_disconnect_from_emu: JLink: JLINK_Close()

[Martin Lesund]

Hi Pravin,

 

Please go through the list in this thread. (use jlink version 6.22g)

Have you cut any of the solder bridges og done any modifications of the nRF52DK?

[Pravin Carvalho]

Hi Martin,

I tried this with Jlink version 6.22g and got the same output. I have also not modified any of the solder bridges and the kit was stationary on my desk when this issue occurred so it is unlikely to be caused by any physical damage.

I am currently powering the kit only via USB. Is there a way to check if the nRF SOC is getting the right voltage?

[Pravin Carvalho]

I've also tried the steps provided in the link you had shared.

1. I am able to reprogram the JLink firmware

2. The measured voltage is 2.8v

3. While attempting to connect with JLink Commander I get the following message.

Connecting to target via SWD
Cannot connect to target.

[Martin Lesund]

Hi Pravin,

How do you measure the voltage?

USB provides 5v and will be regulated down to 3.3V through an on-board voltage regulator.

My assumption is that the kit is powered by the battery by still being connected via USB. If so, take out the battery and connect via USB and power cycle the board.

(it is not optimal to have the battery connected when you are running via USB.)

 

[Pravin Carvalho]

Hi Martin,

I removed the battery and measured the voltage across the "nRF Current Measurement" to Ground.

Yeah I did see that the documentation mentioned 3.3V. What would be the right way to measure this voltage?

Thanks for your help.