nRF52832 Errata 78 , 182 , 204

RE: nRF52832 Errata 78 , 182 , 204

Sawada — Fri, 19 Jul 2019 05:58:39 GMT

Thanks for investigating.
This thread close because it resolved.

RE: nRF52832 Errata 78 , 182 , 204

haakonsh — Wed, 17 Jul 2019 12:11:29 GMT

The SoftDevices are not affected by Errata 204 as they always transition radio states through the DISABLE task.

Errata 204 is also only valid when using an external PA, and whether or not you need to take care of this unwanted emission depends on which kind of regulatory standard you are testing against. For your case, probably a close to worldwide certification, at least as far as the requirements go, you will probably run into the ETSI EN 300 328 which from what I understand is the most 'problematic' standard. In any case it is at least to some extent dependent on how you define the radio operation, personally I think it makes sense to consider the unwanted emission a part of the TX emission, and as such you should not need to worry about it as long as you do not use the channels at the bottom of the band (or transition through DISABLED for those). Also, there is no strict requirement for this, and it is not tested for, it is only found if you dig extra into the actual emissions and interpret the standard the most strict possible way.

RE: nRF52832 Errata 78 , 182 , 204

Sawada — Wed, 17 Jul 2019 00:57:19 GMT

Implemented measures for Errata 182 in SDK 13.1, referring to SDK 15.3. Thank you.

We apologize for the inconvenience, but I would like the 204 response method.

RE: nRF52832 Errata 78 , 182 , 204

haakonsh — Tue, 16 Jul 2019 09:49:20 GMT

I don't think so.

The MDK of SDK15.3 has a workaround for Errata 182 at least. I'm still investigating whether Errata 204 is covered by SDK 15.3.

RE: nRF52832 Errata 78 , 182 , 204

Sawada — Thu, 11 Jul 2019 23:37:52 GMT

Thank you very much.

1. Thank you for answering. close.

2. I using "SDK_13.1.0". Is it implemented?

3. Please confirm.

RE: nRF52832 Errata 78 , 182 , 204

haakonsh — Thu, 11 Jul 2019 09:24:02 GMT

The app_timer library uses RTC1 who's not a TIMER and is therefore not applicable to you.
The RADIO erratas have workarounds that are already implemented in newer SoftDevice versions, you do not need to worry about them.