Cannot load firmware into the nRF52840 dongle through app

[Dmitry_s]

Hello

System:

OS: Windows 10 x64

Application: nRF Connect 2.6.1 (with Bluetooth Low Energy 2.2.0 and Programmer 1.0.2)

Problem:

My device is connected to the COM7(in device manager), but when I'm entering the app It displays that the dongle found at COM8:

When I'm trying to select that device I'm getting the following error: USB DFU detach request sent, but device does not seem to have rebooted

Then I reboot device and app displays that the device is connected to a different COM(the COM it's actually connected to):

I can select it, but when I'm trying to load firmware I'm getting these errors: 

ERROR Reopen device failed: Timeout while waiting for device  F932B6C9CD9B to be attached and enumerated

ERROR Device not found due to failure during DFU

When I'm trying to use Bluetooth Low Energy app(nRF Connect) the connection port displayed as COM8(when just connected and not rebooted yet). I can select that and can use device(connect to other devices etc.).

But when app displays that the device is connected to COM7 the app trying to program dongle and giving an error:

Error while setting up device F932B6C9CD9B: Timeout while waiting for device F932B6C9CD9B to be attached and enumerated

There is full log when I'm trying to load firmware using Programmer:

2019-01-17T13:10:16.120Z INFO Application data folder: C:\Users\user\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2019-01-17T13:10:16.195Z DEBUG App pc-nrfconnect-programmer v1.0.2 official
2019-01-17T13:10:16.195Z DEBUG App path: C:\Users\user\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2019-01-17T13:10:16.195Z DEBUG nRFConnect 2.6.1 is supported by the app (^2.6.0)
2019-01-17T13:10:16.195Z DEBUG nRFConnect path: C:\Users\user\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-01-17T13:10:16.195Z DEBUG HomeDir: C:\Users\user
2019-01-17T13:10:16.195Z DEBUG TmpDir: C:\Users\user\AppData\Local\Temp
2019-01-17T13:10:16.201Z INFO Using nrfjprog library 9.8.1, pc-nrfjprog-js 1.4.1
2019-01-17T13:10:16.203Z VERBOSE Could not fetch serial number for serial port at COM1
2019-01-17T13:10:18.635Z INFO Using USB SDFU protocol to communicate with target
2019-01-17T13:10:18.665Z INFO Protocol Version: 1 found
2019-01-17T13:10:18.666Z INFO Hardware: 52840 found
2019-01-17T13:10:18.670Z INFO Firmware: Bootloader found
2019-01-17T13:10:18.670Z INFO Firmware: SoftDevice found
2019-01-17T13:10:18.670Z INFO Firmware: Application found
2019-01-17T13:12:01.368Z INFO Parsing HEX file: C:\Python27\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v3\connectivity_1.2.3_usb_with_s132_3.1.hex
2019-01-17T13:12:01.371Z INFO File was last modified at 15.01.2019, 19:04:22
2019-01-17T13:12:01.536Z INFO Data block: 0x00000000-0x00000964 (0x00000964 bytes long)
2019-01-17T13:12:01.537Z INFO Data block: 0x00001000-0x0001EBF0 (0x0001DBF0 bytes long)
2019-01-17T13:12:01.537Z INFO Data block: 0x0001F000-0x000300C8 (0x000110C8 bytes long)
2019-01-17T13:12:01.539Z INFO SoftDevice detected, id 0x91 (S132 v3.1.0)
2019-01-17T13:12:03.095Z INFO SdReq for SoftDevice is set as 0x00.
2019-01-17T13:12:03.096Z INFO Hash is generated by SHA256
2019-01-17T13:12:03.097Z INFO Hash is generated by SHA256
2019-01-17T13:12:03.098Z INFO Performing DFU. This may take a few seconds
2019-01-17T13:12:03.114Z INFO DFU procedure starts. This may take a few seconds.
2019-01-17T13:12:10.248Z INFO DFU for SoftDevice completed successfully!
2019-01-17T13:12:10.248Z INFO 1 dfu package(s) left.
2019-01-17T13:12:10.248Z INFO Waiting for device
2019-01-17T13:12:10.256Z INFO DFU procedure starts. This may take a few seconds.
2019-01-17T13:12:15.353Z INFO DFU for Application completed successfully!
2019-01-17T13:12:15.353Z INFO 0 dfu package(s) left.
2019-01-17T13:12:15.353Z INFO Waiting for device
2019-01-17T13:12:20.353Z ERROR Reopen device failed: Timeout while waiting for device F932B6C9CD9B to be attached and enumerated
2019-01-17T13:12:20.353Z INFO Nordic DFU Trigger Interface was not found.Please physically reset device.
2019-01-17T13:12:20.355Z ERROR Device not found due to failure during DFU

[Bjørn Kvaale]

Interesting. I checked the COM port with device manager & nRF Connect Programmer, but both show the same COM port:

Have you taken a look at this dongle programming tutorial already? Are you by any chance using a docking station & attaching the dongle to a usb hub with the docking station? If so, I would recommend connecting the dongle directly to the laptop to see if that helps.

[Dmitry_s]

I checked this tutorial out and it not helped. I'm just trying to program dongle through nRF Connect Programmer but I can't due to errors I described before.The dongle is connected directly to the PC.

[Bjørn Kvaale]

I believe you have done everything correctly. This user experienced a similar issue. Could you try downloading the hex file that Vidar uploaded to see if the DFU was successful?

Most likely, the FW you uploaded does not include the USB DFU trigger needed to make the nRF Programmer app recognize the 52840 dongle.

Have you taken a look at the 52840 dongle user guide available here? It seemed like the DFU completed successfully, but when the DFU completed, it went straight to the application.

This case may also be useful.

[Dmitry_s]

Well, blinky app was uploaded successful(I can see green and red blinks) even with errors described before. I think nRF Connect writing firmware successfully every time but just can't reset the device and thus I have to reconnect dongle automatically every time I load firmware.

So that I think problem is solved, thanks for help.

[Bjørn Kvaale]

Great to hear! Yes, most likely the new FW you upload to the dongle does not include the USB DFU trigger needed to make the nRF programmer app recognize the 52840 dongle.