nRF52 USB instability with USB CDC and USB MSC instantiated

RE: nRF52 USB instability with USB CDC and USB MSC instantiated

Constantin — Fri, 04 Sep 2020 17:58:39 GMT

We just found the solution and it seems to be a fix for https://devzone.nordicsemi.com/f/nordic-q-a/39428/usb-msc-corruption/167555 as well.

We just found out that the file is not corrupted during writing to SD card but when read from SD Card via USB msc interface. If we just plugged in the SD card to our PC the file was completely correct. But if we read it via USB msc the file hat spurious corruptions.

Our fix for the moment was to increase the MSC_WORKBUFFER_SIZE to 2048 bytes.

For now the error did not occur anymore.

RE: nRF52 USB instability with USB CDC and USB MSC instantiated

Jørgen Holmefjord — Fri, 04 Sep 2020 15:28:37 GMT

Can you provide more details on how this issue looks, and post log files, example of corrupted files, etc, and include details about your system environment.

RE: nRF52 USB instability with USB CDC and USB MSC instantiated

Constantin — Fri, 04 Sep 2020 11:29:40 GMT

We are facing the similar issue. If we write to the SDCard there is no error. But if we plugin the USB connection and read the data via msc the data sometimes is corrupted meaning lines are deleted or repeated spuriosly.

But if we plugin the SD card directly to the PC there is no corruption.

Any reason for this?

Current SDK version 15.3.

RE: nRF52 USB instability with USB CDC and USB MSC instantiated

Jørgen Holmefjord — Fri, 05 Jun 2020 10:13:11 GMT

Is it possible to reproduce without an SD card? If not, I will not be able to test/debug your example until I get hold of an SD Card board on Monday.

RE: nRF52 APP_USBD_EVT_DRV_RESET event received instead of APP_USBD_CDC_ACM_USER_EVT_RX_DONE

afontaine — Fri, 05 Jun 2020 09:41:47 GMT

Hi,

Thanks for the suggestion about upgrading the SDK but I would rather keep the 15.2 version and find a workaround.

I found how to reproduce this USB instability with a simple example, based on usbd_msc example (attached main.c modified below). I added USB CDC support and send a frame every minute to the com port.

After several minutes, the com port is no more available and neither the mass storage.

I didn't monitor the USB events for this example.

devzone.nordicsemi.com/.../74106.main.c

Do you see any issue on the USB CDC and MSC implementation that could explain the issue ?

RE: nRF52 APP_USBD_EVT_DRV_RESET event received instead of APP_USBD_CDC_ACM_USER_EVT_RX_DONE

Jørgen Holmefjord — Wed, 03 Jun 2020 13:41:15 GMT

Hi,

Can you check if you are able to reproduce the same issue with SDK 16.0.0? There is a lot of fixes added to the USBD driver and libraries in the releases after SDK 15.2.0.

If not, can you provide a minimal project that can be used to reproduce this behavior?

Best regards,
Jørgen