This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52840 - Not detected on Win10 PC - anymore

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

Parents Reply Children
  • This worked " 4.Have you tried to press the IF BOOT/RESET button while power cycling the kit? It should then show up as a Removable Storage Device named "BOOTLOADER". Then you can drag-and-drop this file onto the storage device to reprogram the JLINK firmware. "

    I can now see the device. But ... I get errors when trying to use nRFgo or command line. Here's the output from log.log


    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.

  • Try with nrfjprog.exe --recover -f nrf52 --log , and see if that makes any difference.


  • nrfjprog.exe --recover -f nrf52 --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: recover.

    FUNCTION: recover.

    JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

    JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

    FUNCTION: close_dll.

    FUNCTION: close_dll.

    ---- ALSO ----

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

    nrfjprog version: 9.7.0

    JLinkARM.dll version: 6.20b

  • Try to use version 170724 of the nRF5x-OB-JLink-IF found here.

    If it's still not working, you can try a different computer.

    You can also try to program the kit that have the issue, with the kit that is working. If you have 10-pin cable, you can connect the cable to debug out(P19) on the kit that is working, and connect the other end of the cable to Debug in(P18) on the kit that have the issue, and see if you are able to recover the board.

Related