Dongle in bad state

[Shai]

Hi,

After trying to flush a program to the dongle with no success, the dongle got into a state where it's not recognize by windows and no LED flashes on it when plugged to a PC.

When pressing the reset button the red LED blincks.

How can I recover it?

[Amanda Hsieh]

Hi Shai, 

Please refer to the Program application using nRF Connect Programmer section in this tutorial. 

-Amanda H.

[Shai]

I’m familiar with that tutorial. 
however it’s not clear enough. 
when the dongle is such state what does it mean?

 Is it the bolder? 
the MBR?
he UICR?

 Can you point to a specific section in the tutorial?

[Shai]

What I’m trying to say is that I followed it, clear so the files and flush only the softDevice, and still seems to be dead

[Amanda Hsieh]

Hi Shai, 

After pressing the reset button the red LED blincks, please use nRF Connect Programmer to flash the ble_app_blinky_pca10059_s140.hex under <nRF5_SDK>\examples\ble_peripheral\ble_app_blinky\hex which already contains MBR, SD and application.

-Amanda H.

[Shai]

Thanks Amanda,

After flushing it (ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10059_s140.hex) I got the following errors (check last 4 lines):

2019-12-06T01:38:49.515Z INFO 1 dfu package(s) left.
2019-12-06T01:38:49.515Z INFO Waiting for device
2019-12-06T01:38:49.519Z INFO DFU procedure starts. This may take a few seconds.
2019-12-06T01:38:52.674Z INFO DFU for Application completed successfully!
2019-12-06T01:38:52.674Z INFO 0 dfu package(s) left.
2019-12-06T01:38:52.675Z INFO Waiting for device
2019-12-06T01:38:57.677Z ERROR Reopen device failed: Timeout while waiting for device ED2E1880AA79 to be attached and enumerated
2019-12-06T01:38:57.677Z INFO Nordic DFU Trigger Interface was not found.Please physically reset device.
2019-12-06T01:38:57.678Z ERROR Device not found due to failure during DFU
2019-12-06T01:38:57.891Z INFO Target device closed.

The green LED is turned on, but nRF Connect doesn't detect the dongle till I reset it.

[Amanda Hsieh]

Hi Shai, 

This worked as we expect. 

The device will reset when the upgrade completes and the dongle will no longer show up in nRF Connect unless the application used DFU Trigger Library is used, as it is no longer in DFU mode. You will get an error stating "Reopen device failed" in this case, and have to push the RESET button in order to make it show up in nRF Connect Programmer again.

Please also see this tutorial. 

-Amanda H 

[Shai]

Hi Amanda,

I've followed all of the tutorials and still haven't figured it out.

At that mode, when it's no longer in DFU mode, it is not detected by the host, and therefore useless (as I cannot read anything fro the serial port.

Should I add the DFU Trigger Library to my project (which is based on examples\ble_central\ble_app_rscs_c)?

If the answer is yes - how do I do it?

If not - what should I do?

My evaluation time is about to expire...

---------------------

Meantime I've added ../../../../../../components/libraries/bootloader/dfu to user include directories, and enable it in sdk_config, but I still get  undefined reference to `nrf_dfu_trigger_usb_init'.

Not sure that's the right direction...

[Amanda Hsieh]

Hi Shai,

Shai said:

Should I add the DFU Trigger Library to my project (which is based on examples\ble_central\ble_app_rscs_c)?

Yes. If you add the DFU Trigger Library (USB) to your custom device firmware, you will be able to trigger the DFU from nRF Connect for Desktop without using any buttons. For documentation, see DFU Trigger Library (USB), which is part of the nRF5 SDK v15.3.0. See Programming nRF52840 Dongle.

 

Shai said:

enable it in sdk_config, but I still get  undefined reference to `nrf_dfu_trigger_usb_init'.

 I would suggest you start from <nRF5_SDK>\examples\dfu\open_bootloader\pca10059_usb_debug

-Amanda H