nRF52840 - Not detected on Win10 PC - anymore

[simonnrf52]

Hi,

I have nRF52840 dev board which was detected and LEDs were coming on. I tried programming the prebuilt throughput hex file in nRFgo Studio.

C:\Projects\NORDIC\nRF5_SDK_14.0.0_3bcc1f7\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput\hex\ble_app_att_mtu_throughput_pca10056_s140.hex

Now, no LEDs come on, it isn't detected as a drive on the PC and I can't find/erase it using nRFgo Studio of the command line tool.

I have a second board which does light up (factory default program) which I haven't reprogrammed. I need two for the throughput demo.

(1) Have I "bricked" one of the boards? (2) Is there a way of recovering it?

The power source switch is on VDD The other switch is on Default

[simonnrf52]

Thanks for your continued efforts.

I tried the bootloader.

Unfortunately there was no difference.

---

Just checking I am doing it right:

• Hold BOOT RESET

• Connect USB to External Supply (not nRF USB)

• File Explorer displays Bootloader folder

• Drag bootloader .bin file onto drive.

• Once file is copied Bootloader folder disappears and LED on dev board flashes.

• LED continues to flash until USB cycled

• Board appears as JLINK drive on PC

At this point I would expect to be able to erase the device using nrfjprog -e or program it by dragging the ble_app_att_mtu_throughput_pca10056_s140.hex file onto the drive and cycling the USB. Neither works.

I have pasted the latest log outputs much further below.

---

Question

Can you please point me towards where I can find more information about how to copy from one device to another?

I've found P19 and P18 and can get a cable made up.

Not sure what the process is.

---

Log Outputs

nrfjprog --program ble_app_att_mtu_throughput_pca10056_s140.hex --log

nrfjprog verion 9.7.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: 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.

---

nrfjprog -e --log

nrfjprog verion 9.7.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: 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.

---

nrfjprog --clockspeed 500 --program ble_app_att_mtu_throughput_pca10056_s140.hex --log

nrfjprog verion 9.7.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: 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.

---

C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin>nrfjprog -I

683657997

---

C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin>nrfjprog -v

nrfjprog version: 9.7.0

JLinkARM.dll version: 6.20b

---

Screen Shots

[Sigurd]

You can find more information about the Debug in/out port here and here.

Note that if you have done any modification to the solder bridges, you should restore them to default state.

---

• Have you tried a different USB cable? Faulty cables are surprisingly often the issue.
• Can you measure the supply voltage on the nRF Device? The error indicates that the debugger is not able to detect the device, and is normally shown when there is a mechanical issue with the wiring or connectors (a contact issue).
• Can you try this guide? devzone.nordicsemi.com/.../