nRF52840 Dongle support

Question

nRF52840 Dongle support

istirbu opened this issue 6 years ago · comments

Igor Stirbu commented 6 years ago

Hello,

Is it possible to get a hex for nRF52840 Dongle?

Thanks!

Rafał Kuźnia · Answer 1 · Fri Dec 14 2018 23:14:08 GMT+0800 (China Standard Time)

Hi,
Hex for nRF52840 dongle will hopefully be coming after this weekend.

Cheers.

Igor Stirbu · Answer 2 · Fri Dec 14 2018 23:15:34 GMT+0800 (China Standard Time)

@e-rk Thanks a lot!

Rafał Kuźnia · Answer 3 · Tue Dec 18 2018 20:43:29 GMT+0800 (China Standard Time)

Hi,
Here (#10) is a current pull request with dongle support.
Feedback is very welcome.

Igor Stirbu · Answer 4 · Wed Dec 19 2018 01:59:32 GMT+0800 (China Standard Time)

Hi @e-rk, thanks for the update. But I'm missing something, I can't flash program the dongle with nRF Connect - Programmer app, I have only the reset option enabled. Can you help with any information?

Rafał Kuźnia · Answer 5 · Wed Dec 19 2018 21:05:03 GMT+0800 (China Standard Time)

Hey,
Have you selected nrf802154_sniffer_dongle.hex file? It looks like the programmer doesn't allow flashing the device when a wrong file is chosen, because it would overwrite the MBR section. Changes from the PR I linked earlier have been merged today so please pull the newest commit if you haven't already.
Hope it helps.

Igor Stirbu · Answer 6 · Wed Dec 19 2018 22:21:29 GMT+0800 (China Standard Time)

I was able to flash the dongle firmware, and verified that the start/end addresses and size match after flashing. Though, unplugging and plugging back did not make the dongle visible, still had to press the reset button. After the reset, the led is blinking red. Not sure if it matters.

I've upgraded to wireshark 2.6.3 (Win 10) and copied the py/bat files to extcap. The plugin was detected properly, but after the capture starts, no data is detected (I have a couple of zigbee devices around).

I've tried to run the python script from a Linux VM to test the output, but I get the same error as in Wireshark:

python nrf802154_sniffer.py --dev=/dev/ttyACM0 --channel=11 --extcap-interface=nrf802154 --fifo='/tmp/nrf' --capture
2018-12-19 16:18:51,585 [ERROR] Nrf802154Sniffer (/dev/ttyACM0) channel 11 did not reply properly to setup commands. Is it flashed properly? Recieved:

And after the colon there is no data.

Rafał Kuźnia · Answer 7 · Wed Dec 19 2018 23:15:24 GMT+0800 (China Standard Time)

The reset button should not be clicked after flashing because then the device enters DFU mode and sniffer application is not running.
When you plug the device does anything appear in Windows device manager?

Igor Stirbu · Answer 8 · Thu Dec 20 2018 04:14:11 GMT+0800 (China Standard Time)

The dongle does not appear in the Ports list when plugged in (first picture). But after pressing reset, in DFU mode it's listed properly (second picture).

Rafał Kuźnia · Answer 9 · Thu Dec 20 2018 22:16:45 GMT+0800 (China Standard Time)

I have checked on Windows 10 as well and indeed the device does not communicate with the system correctly due to driver issue. Currently I don't have an option to check how it works on older Windows operating systems, but I can confirm that Ubuntu 18.04 running natively is able to talk with the device.
I have also tested other USB applications on Win10 and they too have the same problem with the USB driver, which indicates a broader issue.
Unfortunately there is not much I can do at this point until beginning of January.

Sorry for that and have a great holidays.

Igor Stirbu · Answer 10 · Fri Dec 21 2018 07:25:08 GMT+0800 (China Standard Time)

Thanks a lot for the update! Happy holidays!

Rafał Kuźnia · Answer 11 · Fri Jan 04 2019 19:26:19 GMT+0800 (China Standard Time)

Hi,
I have come back to this issue and it turns out that at this moment this only happens to you and me. The sniffer can be plugged practically out of the box to other Windows 10 machines I have tested, however I am still unable to properly set up the driver for this sniffer on my own computer.

I don't know if you have exactly the same problem as me, because mine turned out to be far broader than I have previously anticipated and is not limited to nRF52 devices.
Can you try manually selecting Microsoft USB Serial driver for both devices that appear after plugging the dongle in Device manager? If the driver installation fails can you post the error message that appears?

Sorry I can't be of more help right now.

Igor Stirbu · Answer 12 · Sat Jan 05 2019 04:29:54 GMT+0800 (China Standard Time)

Hi @e-rk,

Thanks for the follow up! The dongle is detected as a composite device and has two entries: https://imgur.com/a/Xewr8f5 . For the 'nRF52 USB Product' entry I cannot update the driver. After right clicking->'Update driver'->'Search automaticallly....' I get the 'unable to install your nRF52 USB product'. When selecting manually and pointing to 'c:\windows\system32\drivers' folder, it does not detect any driver. For both entries the VID is 1915 and PID is 0154.

Thank you!

Rafał Kuźnia · Answer 13 · Mon Jan 07 2019 16:52:31 GMT+0800 (China Standard Time)

I think the sniffer should be ready to run with Wireshark now.
The COM9 port should be responsible for communication with the sniffer application.
The second interface with the warning sign should be the DFU trigger interface, which enables the dongle to enter DFU mode after receiving a signal over USB, without having to press reset button. I'm not sure why the automatic update doesn't select the correct driver for this one. You can either ignore it or you can try finding and manually selecting Nordic DFU trigger driver in device properties. I think the driver should come with nRF Connect for desktop.

Igor Stirbu · Answer 14 · Wed Jan 16 2019 04:18:00 GMT+0800 (China Standard Time)

hi @e-rk , the dongle works fine and I can see the traffic! Thank you!