NRF52840DK USB CDC driver error!

[atong]

Hi. Does anyone know where I can download the CDC ACM diver for windows 7?

I am running the example on the nRF52 dev kit, but I get an error as windows can't find the driver.

project path:nRF5_SDK_15.0.0_a53641a\examples\peripheral\usbd\pca10056\blank\arm5_no_packs.

usb_drivers path:nRF5_SDK_15.0.0_a53641a\examples\usb_drivers.

now,the device have a nRF52 USB CDC Demo,but the driver fail.

[Sigurd]

Hi,

Did you try to update the driver?

Could you test with SDK 15.1 ? You can download it here.

[atong]

 Hi,thank you!

I have a try your method, the problem of the dirver remains unsolved.

[Sigurd]

It could be that windows have problems with the path you are using. Could you try to copy the usb_drivers folder to C, and install it from there instead. I.e. C:\usb_drivers, and then install the driver from that folder instead.

The folder should contain the nordic_cdc_acm.cat and nordic_cdc_acm.inf file:

Then in Device Manager, right click on the nRF52 device, and select "Update Driver Software":

Select Browse my computer for driver software:

Select the new folder, C:\usb_drivers, and click next

[zk017]

BootLoader project: nRF5_SDK_15.0.0_a53641a\examples\dfu\secure_bootloader\pca10056_usb_debug,

I copy the SDK15.2 usb driver to c drive root folder, and get the same result.

[Sigurd]

1) Do you have administrator privileges on your windows user-account ?

2) Could you translate this to english?:

[zk017]

1. yeah, I have the administrator privileges . 

 2.the paragraph of service installation  in this INF is invalid

[Sigurd]

Hi,

This looks like some sort of windows driver issue on this particular windows 7 machine. You could go through the windows community forum, and see if any the solutions found at that forum works for you.

You should also try to install nRF Connect for Desktop on the machine, and see if any of the drivers that are installed as part of the install fixes the issue.

[Adrian Eggenberger]

Hi Sigurd

i just struggled over the same issue yesterday and manually using a driver that was installed by the nRF Connect installer worked as expected. This works ok as a workaround, but for the final product we would prefer to have a driver that can be installed by an installer or something similar.

What is the reason why the example driver is not accepted by Windows 7? Can it be that the problem is the missing signature for the example driver? It seems the the driver that comes with nRF Connect is signed and the example driver is not.

What options do we have to get a working driver for all Windows versions from Windows 7 and newer?

Regards Adrian

[Sigurd]

Hi Adrian,

An installer for the final product sounds like a good idea. In nRFConnect we have an installer, see this github page.