[223] USBD: Unexpected behavior after reset

This anomaly applies to Revision 2, build codes QDAA-C00.

It was inherited from the previous IC revision Engineering B.

Symptoms

The USBD might behave unexpectedly.

Conditions

USBD is enabled for the first time after a reset (USBD.ENABLE=1).

Consequences

The USBD internal state might not be reset correctly,
Note: This failure has not been reported or reproduced under test at the time of publication.

Workaround

When enabling the USBD for the first time after a reset, disable and re-enable. Wait for the status signal NRF_USBD->EVENTCAUSE set to USBD_EVENTCAUSE_READY after enabling, then disable and re-enable.

Parent topic: New and inherited anomalies