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

nRF52 Dongle as sniffer

I have programed the nRF52 dongle as sniffer using the hex file from the 3.1 release using nRF Connect programmer. When I plug dongle I expect a COM port to be created in Windows, but this is not the case. Consequently it is not being detected in Wireshark.

Parents
  • I appear to be missing an INF file with USB\VID_1915&PID_522A&MI_00. The inf file in the SDK has

    [DeviceList.NTx86]
    %NORDIC_CDC_ACM_EXAMPLE%      =DriverInstall, USB\VID_1915&PID_520F&MI_00
    %NORDIC_BLE_UART_EXAMPLE%     =DriverInstall, USB\VID_1915&PID_521A&MI_00
    %NORDIC_USB_CDC_CONNECTIVITY% =DriverInstall, USB\VID_1915&PID_521B&MI_00
    %NORDIC_SDFU_USB_EXAMPLE%     =DriverInstall, USB\VID_1915&PID_521F&MI_00

Reply
  • I appear to be missing an INF file with USB\VID_1915&PID_522A&MI_00. The inf file in the SDK has

    [DeviceList.NTx86]
    %NORDIC_CDC_ACM_EXAMPLE%      =DriverInstall, USB\VID_1915&PID_520F&MI_00
    %NORDIC_BLE_UART_EXAMPLE%     =DriverInstall, USB\VID_1915&PID_521A&MI_00
    %NORDIC_USB_CDC_CONNECTIVITY% =DriverInstall, USB\VID_1915&PID_521B&MI_00
    %NORDIC_SDFU_USB_EXAMPLE%     =DriverInstall, USB\VID_1915&PID_521F&MI_00

Children
Related