USBD Errata 187 in QIAAC0 Silicon

RE: USBD Errata 187 in QIAAC0 Silicon

Håkon Alseth — Wed, 25 Jul 2018 11:36:55 GMT

Hi,

We always recommend that you develop using a production revision of the IC. SDK v15 has removed workarounds for older engineering devices (on USBD atleast).

Kind regards,

Håkon

RE: USBD Errata 187 in QIAAC0 Silicon

silivanov — Fri, 13 Jul 2018 07:07:48 GMT

It helped me!

But now on the other (older revisions controllers) does not work, where should be the value 0x10.

How to rewrite nrf_drv_usbd_errata_type_52840_fp1 () function so that, depending on the revision of the controller substitutes the required value (0x10 or 0x20)

RE: USBD Errata 187 in QIAAC0 Silicon

Sigurd — Tue, 12 Jun 2018 07:17:00 GMT

Hi,

Unfortunately, we have a bug in our SDK 15.0, in file nrf_drv_usbd_errata.h::nrf_drv_usbd_errata_type_52840_fp1().

This has been reported internally, and will be addressed in future versions of the SDK.

static inline bool nrf_drv_usbd_errata_type_52840_fp1(void)

{

return ( nrf_drv_usbd_errata_type_52840() &&

( ((*(uint32_t *)0xF0000FE8) & 0xF0) == 0x10 ) &&

( ((*(uint32_t *)0xF0000FEC) & 0xF0) == 0x00 ) );

}

The bold highlight should be 0x20 (not 0x10) for engineering C and revision 1 devices. So please change the "== 0x10" to "== 0x20", it should apply the workaround for engineering C and the final product.