• State Not Answered
  • Replies 1 reply
  • Subscribers 87 subscribers
  • Views 2316 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 262663
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52840 dongle, nRF Connect, Programmer, ERROR Reopen device failed

cws

Attempting to program an nRF52840 dongle with sniffer_nrf52840dongle_nrf52840_7cc811f.hex, using nRF Connect Programmer v1.4.8, on Windows 7

Upon clicking "Write", the red LED blinks quicker briefly, then goes out, and the log ends with "ERROR Reopen device failed: Timeout while waiting for device  D3C10D53F485 to be attached and enumerated".  After this, none of the nRF Connect programs detect the device until I press Reset, putting it back in bootloader mode.

Here is the log produced by Programmer:

2021-01-08T21:47:57.968Z INFO Application data folder: C:\Users\craig\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-01-08T21:47:58.045Z DEBUG App pc-nrfconnect-programmer v1.4.8 official
2021-01-08T21:47:58.045Z DEBUG App path: C:\Users\craig\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-01-08T21:47:58.045Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-01-08T21:47:58.045Z DEBUG nRFConnect path: C:\Users\craig\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-01-08T21:47:58.045Z DEBUG HomeDir: C:\Users\craig
2021-01-08T21:47:58.045Z DEBUG TmpDir: C:\Users\craig\AppData\Local\Temp
2021-01-08T21:47:58.059Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-01-08T21:47:58.983Z VERBOSE Could not fetch serial number for serial port at COM1
2021-01-08T21:48:16.873Z INFO Using USB SDFU protocol to communicate with target
2021-01-08T21:48:16.887Z INFO Protocol Version:  1 found
2021-01-08T21:48:16.888Z INFO Hardware: 52840 found
2021-01-08T21:48:16.892Z INFO Firmware: Bootloader found
2021-01-08T21:48:16.893Z INFO Firmware: Application found
2021-01-08T21:49:08.459Z INFO Parsing HEX file:  C:\Users\craig\Documents\sheepworks\nRF52\nRF Sniffer\nrf_sniffer_for_bluetooth_le_3.1.0_7cc811f\hex\sniffer_nrf52840dongle_nrf52840_7cc811f.hex
2021-01-08T21:49:08.481Z INFO File was last modified at  1/4/2021, 9:23:07 PM
2021-01-08T21:49:19.498Z INFO Does not need to be reloaded:  C:\Users\craig\Documents\sheepworks\nRF52\nRF Sniffer\nrf_sniffer_for_bluetooth_le_3.1.0_7cc811f\hex\sniffer_nrf52840dongle_nrf52840_7cc811f.hex
2021-01-08T21:49:19.510Z INFO Hash is generated by SHA256
2021-01-08T21:49:19.514Z INFO Performing DFU. This may take a few seconds
2021-01-08T21:49:19.535Z INFO DFU procedure starts. This may take a few seconds.
2021-01-08T21:49:24.424Z INFO DFU for Application completed successfully!
2021-01-08T21:49:24.424Z INFO 0 dfu package(s) left.
2021-01-08T21:49:24.424Z INFO Waiting for device
2021-01-08T21:49:29.427Z ERROR Reopen device failed: Timeout while waiting for device  D3C10D53F485 to be attached and enumerated
2021-01-08T21:49:29.427Z INFO Nordic DFU Trigger Interface was not found.Please physically reset device.
2021-01-08T21:49:29.452Z ERROR Device not found due to failure during DFU
2021-01-08T21:49:30.459Z INFO Target device closed.

Any help would be appreciated.

Also, I am doing this in the hope that I can use this with wireshark to detect extended advertisements from a nRF52810 device.  Can you confirm whether or not nRF Sniffer supports sniffing extended advertisements with the nRF52840?

Thanks,

Craig

  • 0

    Hi Craig, 

    The log is as expected. The device will reset when the upgrade completes and the dongle will no longer show up in nRF Connect because the application used DFU Trigger Library is used, as it is no longer in DFU mode. Then the dongle can start to sniff. If you Install nRF Sniffer correctly, you will see the frame as Figure 2. in the Running nRF Sniffer when you open the Wireshark.  

    Can you confirm whether or not nRF Sniffer supports sniffing extended advertisements with the nRF52840?

    Extended advertising is not yet supported by the nRF Sniffer. You may be able to see the initial packet ADV_EXT_IND but not the actual data extended packets, but not the actually extended packets that follow. See the explanation in this post. 

    -Amanda H.

Related