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

nRF51 dongle device not recognized by nRF connect programmer

I bought nRF51 dongle from mouser.com. I wanted to put nRF sniffer firmware on it using the guide on the web site. I tried using nRF connect programmer but it can not talk to the device. After mocking around for a couple of hours I figured I need to upgrade some firmware bits from mbed and that did not really help (maybe I should not have been doing any of that .. ).

First there was this USB device in Linux:

Bus 003 Device 006: ID 1366:1015 SEGGER 

After mbed upgrade (https://armmbed.github.io/DAPLink/?board=Nordic-nRF51-Dongle) and bootloader upgrade (https://os.mbed.com/blog/entry/DAPLink-bootloader-update/) I get this device in Linux:

Bus 001 Device 021: ID 0d28:0204 NXP LPC1768

None of the above made nRF connect programmer work it always says:

2020-07-09T14:10:24.714Z ERROR Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.

I tried CLI utils and no success as well:

$ nrfjprog -f NRF51 --program ../nrf_sniffer_for_bluetooth_le_3.0.0_129d2b3/hex/sniffer_pca10031_129d2b3.hex –-chiperase
ERROR: There is no debugger connected to the PC.

I can see /dev/ttyACM0 and it is writable by the user, as well as is /deb/bus/usb/..:

$ lsusb 
Bus 001 Device 022: ID 0d28:0204 NXP LPC1768
$ groups
.. dialout .. plugdev ..
$ ll /dev/ttyACM0
crw-rw-rw- 1 root dialout 166, 0 Jul 9 16:25 /dev/ttyACM0
$ ll /dev/bus/usb/001/022
crw-rw-rw- 1 root plugdev 189, 21 Jul 9 16:24 /dev/bus/usb/001/022

What should I do to the the nRF sniffer firmware on the device?

TIA,

//hinxx

Parents Reply Children
No Data
Related