My nrf52840dk stopped working after programming

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Mon, 13 May 2019 13:42:43 GMT

Glad to hear 🙂 Hope you have a nice day!

Cheers,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Mon, 13 May 2019 09:14:02 GMT

Got a replacement. Thanks a lot for your excellent support

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Wed, 08 May 2019 07:16:53 GMT

Hi Avi,

If you still have issues recovering this board, please send me a direct message with your address and phone number (DHL requirement) and I'll make sure you get a replacement kit.

Cheers,

Håkon

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Tue, 07 May 2019 11:12:13 GMT

And that is fine, but J3 also applies a voltage to the device, and tries to enumerate the chip.

If the nRF device is asserting early in the boot process, where the default behavior is to perform a soft-reset, it will be hard to attach the debugger in order to connect + recover, as the soft-reset will disrupt the debugger. By putting in the USB connector on J3 as well, you might get the firmware to run further, and thus be able to perform the "nrfjprog --recover -f nrf52" command in time.

If this still does not work, try this batch file while you try to reset the device (connect a wire to P0.18 and touch that one to GND):

https://devzone.nordicsemi.com/f/nordic-q-a/45078/nrf52832-not-connected-anymore-after-first-trying-to-debug-keil/177579#177579

Kind regards,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Tue, 07 May 2019 09:40:17 GMT

I did. J3 is not detected.

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Tue, 07 May 2019 09:18:40 GMT

Could you try to connect a USB to both J2 and J3?

RE: My nrf52840dk stopped working after programming

Avi — Tue, 07 May 2019 07:35:01 GMT

I am not connecting a USB to J3. I did it once when I tried to program the 802.15.4 sniffer.

I tried in another computer with new installation of NRF tools

Not working there as well

Is there another way to program the board besides the Programmer via USB?

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Tue, 07 May 2019 07:24:36 GMT

Hi,

Most of my "normal tricks" does not seem to recover your board. Since you originally programmed in the 802.15.4 sniffer (USB variant), are you also connecting a usb to "nRF USB" (J3) when trying to recover the board?

Have you also tried to recover the board using another computer?

Kind regards,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Mon, 06 May 2019 13:20:04 GMT

Any idea?

RE: My nrf52840dk stopped working after programming

Avi — Fri, 03 May 2019 08:58:13 GMT

Here is what I got:

2019-May-03 11:57:06 --------------------------------------------------------------------------------
2019-May-03 11:57:06 nrfjprog --recover -f nrf52 --log
2019-May-03 11:57:06 nrfjprog version 9.8.1
2019-May-03 11:57:06 --------------------------------------------------------------------------------
2019-May-03 11:57:06 nRF_open_dll
2019-May-03 11:57:06 . nRF52_open_dll
2019-May-03 11:57:06 . . nRF52_dll_version
2019-May-03 11:57:06 nRF_enum_emu_snr
2019-May-03 11:57:06 . nRF52_enum_emu_snr
2019-May-03 11:57:06 . . nRF52_enum_emu_snr
2019-May-03 11:57:06 nRF_enum_emu_snr
2019-May-03 11:57:06 . nRF52_enum_emu_snr
2019-May-03 11:57:06 . . nRF52_enum_emu_snr
2019-May-03 11:57:06 nRF_connect_to_emu_with_snr
2019-May-03 11:57:06 . nRF52_connect_to_emu_with_snr
2019-May-03 11:57:06 . . nRF52_is_connected_to_emu
2019-May-03 11:57:06 . . nRF52_enum_emu_snr
2019-May-03 11:57:06 . . nRF52_connect_to_emu_with_snr
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: Hardware: V1.00
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: S/N: 683927383
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: TELNET listener socket opened on port 19021
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Starting webserver
2019-May-03 11:57:06 . . . nRF52_connect_to_emu_without_snr: JLink: (0065ms, 0072ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Webserver running on local port 19080
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0089ms, 0096ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns O.K.
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0107ms, 0114ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_GetHWStatus(...)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0017ms, 0142ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: There is no generic nRF52 device in J-Link, so we select NRF52832_xxAA.

2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("Device = NRF52832_xxAA", ...).
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: XML file found at: C:\Program Files (x86)\SEGGER\JLink_V640\JLinkDevices.xml
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0008ms, 0166ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: C:\Program Files (x86)\SEGGER\JLink_V640\JLinkDevices.xml evaluated successfully.
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0122ms, 0280ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetRestartOnClose = 0", ...).
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0008ms, 0304ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("DisableFlashDL", ...).
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0007ms, 0327ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetDbgPowerDownOnClose = 1", ...).
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0007ms, 0349ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0008ms, 0372ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_TIF_Select(JLINKARM_TIF_SWD)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0019ms, 0400ms total)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_SetSpeed(2000)
2019-May-03 11:57:07 . . . nRF52_connect_to_emu_without_snr: JLink: (0026ms, 0434ms total)
2019-May-03 11:57:07 nRF_recover
2019-May-03 11:57:07 . nRF52_recover
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: returns 0x01
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: (0022ms, 0468ms total)
2019-May-03 11:57:07 . . nRF52_is_connected_to_device
2019-May-03 11:57:07 . . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()
2019-May-03 11:57:07 . . nRF52_is_connected_to_device: JLink: returns FALSE
2019-May-03 11:57:07 . . nRF52_is_connected_to_device: JLink: (0017ms, 0493ms total)
2019-May-03 11:57:07 . . nRF52_readback_status
2019-May-03 11:57:07 . . . nRF52_is_ctrl_ap_available
2019-May-03 11:57:07 . . . . nRF52_read_access_port_register
2019-May-03 11:57:07 . . . . . nRF52_coresight_configure
2019-May-03 11:57:07 . . . . . nRF52_coresight_configure: JLink: JLINK_CORESIGHT_Configure()
2019-May-03 11:57:07 . . . . . nRF52_coresight_configure: JLink: returns 0
2019-May-03 11:57:07 . . . . . nRF52_coresight_configure: JLink: (0115ms, 0616ms total)
2019-May-03 11:57:07 . . . . . nRF52_power_debug_and_system_regions
2019-May-03 11:57:07 . . . . . . nRF52_write_debug_port_register
2019-May-03 11:57:07 . . . . . . nRF52_write_debug_port_register: JLink: JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
2019-May-03 11:57:07 . . . . . . nRF52_write_debug_port_register: JLink: returns -1
2019-May-03 11:57:07 . . . . . . nRF52_write_debug_port_register: JLink: (0016ms, 0640ms total)
2019-May-03 11:57:07 . . . . . . nRF52_write_debug_port_register: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

2019-May-03 11:57:07 . . . . . nRF52_power_debug_and_system_regions: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

2019-May-03 11:57:07 nRF_close_dll
2019-May-03 11:57:07 . nRF52_close_dll
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: returns 0x01
2019-May-03 11:57:07 . . nRF52_is_connected_to_emu: JLink: (0014ms, 0662ms total)
2019-May-03 11:57:07 . . nRF52_disconnect_from_emu
2019-May-03 11:57:07 . . . nRF52_is_connected_to_device
2019-May-03 11:57:07 . . . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()
2019-May-03 11:57:07 . . . nRF52_is_connected_to_device: JLink: returns FALSE
2019-May-03 11:57:07 . . . nRF52_is_connected_to_device: JLink: (0014ms, 0683ms total)
2019-May-03 11:57:07 . . . nRF52_unpower_debug_and_system_regions
2019-May-03 11:57:07 . . nRF52_disconnect_from_emu: JLink: JLINK_Close()

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Fri, 03 May 2019 08:32:48 GMT

Please upgrade to the latest, and use "nrfjprog --recover -f nrf52".

Kind regards,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Thu, 02 May 2019 14:15:50 GMT

As I wrote above - this is the log I got:

I ran the command nrfjprog --eraseall --log and got the following result.

--------------------------------------------------------------------------------
C:\Users\avipa\Dropbox\Projects\Mesh\Controller\BLE5\nrfjprog.exe --eraseall --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_device_version.
FUNCTION: read_device_version.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.

RE: My nrf52840dk stopped working after programming

Avi — Thu, 02 May 2019 14:14:58 GMT

I am already using nrfjprog version 9.7.1

Should I upgrade?

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Thu, 02 May 2019 14:13:13 GMT

Hi,

Could you try to upgrade nrfjprog to the latest version (it's a part of the nRF5x command line tools), then use the recover function?

nrfjprog --recover -f nrf52

Kind regards,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Thu, 02 May 2019 10:15:56 GMT

RE: My nrf52840dk stopped working after programming

Avi — Thu, 02 May 2019 10:12:46 GMT

SB41 is not cut. I will attach a picture also. I also tried to short the header - but still - I cannot access the memory

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Thu, 02 May 2019 10:08:01 GMT

It looks like "SB41" is cut from the picture, but it's hard to see. If that is the case, you'll need to short the pin header next to it.

Everything else looks to be OK.

Kind regards,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Thu, 02 May 2019 08:11:04 GMT

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Thu, 02 May 2019 07:53:57 GMT

Could you take a picture of the whole DK, and share it with me? So I can check all the switches etc.

Cheers,

Håkon

RE: My nrf52840dk stopped working after programming

Avi — Wed, 01 May 2019 10:15:13 GMT

If this will help to analyze what happened and how to fix The last thing that I did while the 52840dk worked was to follow the guidelines in https://github.com/NordicSemiconductor/nRF-Sniffer-for-802.15.4/blob/master/README.md

I probably did something wrong (maybe programmed something into J3).

How can I fix it and bring back my 52840dk functionality? I cannot see the memory content any more and not able to program it.

RE: My nrf52840dk stopped working after programming

Avi — Tue, 30 Apr 2019 12:02:35 GMT

I ran the command nrfjprog --eraseall --log and got the following result.

Strange since it shows like my 5284dk is a NRF52832_XXAA device

RE: My nrf52840dk stopped working after programming

Avi — Tue, 30 Apr 2019 09:57:36 GMT

Now the led is ON. I put the J-Link OB-SAM3U128-V2-NordicSemi 170724 file into the bootloader folder . But the NRF connect is stuck - it cannot read the content of the 52840 dk

RE: My nrf52840dk stopped working after programming

Avi — Tue, 30 Apr 2019 09:50:46 GMT

I did as you suggested, one cable is connected to J2. nrf Power source is at Vdd. VextNrf switch is at Off.

There is no light in the led. I tried to toggle the switch no light. Only if the switch point to USB - it lights

RE: My nrf52840dk stopped working after programming

Håkon Alseth — Tue, 30 Apr 2019 09:31:07 GMT

[quote user=""][/quote]

My usb cable is connected to J2

I am using USB power source (VDD option is not working)

The second switch is at default sate

and the VEXT-NRF is "On"

With this configuration, you need to have both J2 and "nRF USB" connected with one USB cable each. I would recommend that you set the main switch SW9 to position "VDD power" (and VEXT-NRF to OFF) unless you are applying power to the nRF externally.

If the kit does not fully light up when powering from J2, you can try to toggle the "power" switch on/off a couple of times.

Could you try this and report back?

Kind regards,

Håkon