USB CDC ACM

RE: USB CDC ACM

Kenneth — Mon, 06 Aug 2018 14:25:38 GMT

Yes.

RE: USB CDC ACM

Nandi — Mon, 30 Jul 2018 06:49:16 GMT

hi,

I have made a HID+MSC composite device. Does this change affect all USB devices?

RE: USB CDC ACM

Kenneth — Tue, 22 May 2018 10:39:25 GMT

You are right there is an error in nrf_drv_usbd_errata.h, the correct implementation of nrf_drv_usbd_errata_type_52840_fp1() should be:

static inline bool nrf_drv_usbd_errata_type_52840_fp1(void)
{
return ( nrf_drv_usbd_errata_type_52840() &&
( ((*(uint32_t *)0xF0000FE8) & 0xF0) == 0x20 ) &&
( ((*(uint32_t *)0xF0000FEC) & 0xF0) == 0x00 ) );
}

This will be fixed in SDKv15.1.

With this change in place, is it your custom board that is now failing, while the EV board works?

RE: USB CDC ACM

Lior Smila — Thu, 17 May 2018 14:19:57 GMT

Hi,

So I'm now able to use USB CDC using the EV board with my application.

Yet, when I move to my board, USB does not seem to activate (nothing but USB power events).

My board has an Engineering Ctype - I saw some erratas dealing with USBD.

I looked on the nRF52840 Engineering C and worked according to it.

In a strange way, nrf_drv_usbd_errata_187 which is relevant for type c , is not recognized by the SW, only when I force to execute the errata code the USB enable started to work - yet only power events active.

Any help is most welcome,

Regards - Lior.

RE: USB CDC ACM

Lior Smila — Wed, 16 May 2018 12:40:11 GMT

devzone.nordicsemi.com/.../USB_5F00_CON_5F00_FAIL.csv

Thank you for your quick response,

I'm using "Beagle" usb recorder - "data center",

I am attaching a usb data records in a .csv format. Can that help you point out the issue?

I'm able to receive the power events (DETECT/UNDETECT) on my application.

It looks like for some reason the com port is not opening on the PC

Another input, the example does not use the "soft device" on it - my application does.

Please your help,

Regards,

Lior.

RE: USB CDC ACM

Kenneth — Tue, 15 May 2018 14:02:22 GMT

Hi,

In general stalling an endpoint is fine in USB protocol - it just informs host that something is not supported. But the it should not stall the SET_CONFIGURATION 1 request, so I assume something has failed when you moved the code to your project.

Hard to say now why it happens - I would suggest to turn on logger on DEBUG level and post logs from APP_USBD and APP_USBD_CDC.

Best regards,
Kenneth