nRF52832 Revision 2 Errata

[Justin]

Hi,

How can I understand what all Errata's are applicable to softdevice and are taken care of?

For my application I am aware of the modules/peripherals being used and the erratas can be linked/matched.

[Karl Ylvisaker]

Hi,

The erratas for nRF52832 revision 2 can be seen here.
The changelog for fixed erratas that are no longer present in revision 2, can be seen here.

Is this what you were looking for?

Best regards,
Karl

[Justin]

Hi Karl,

I am looking for the erratas that are taken care by softdevice and the ones that are not applicable to softdevice.

For e.g.

Is there a list of hardware the softdevice uses? Almost certain the following aren't used, but need confirmation:
POWER - RAM[x]
SAADC
SPIM
RESETREAS
LPCOMP
MWU
FPU(Floating Point Unit)
PWM

Does the softdevice use the following? If so, does it control for the specified errata?
TIMER
WDT

Does the softdevice control for the specified errata for the following?
RADIO

[Karl Ylvisaker]

Hi,

I assume you meant "does the SoftDevice incorporate the workaround" when you said "control for the specific errata", please let me know if I have misunderstood.
If there are specific erratas for specific chip revisions you are concerned about, please see their individual documentation.

Justin said:

Does the softdevice control for the specified errata for the following

For example, the [102] RADIO errata for nRF52832 revision 1 is documented here.
In the workaround, the SoftDevice version and SDK library version that incorporates a workaround is specified.
The same goes for the documentation of the other erratas.

Justin said:

Does the softdevice use the following? If so, does it control for the specified errata?
TIMER
WDT

You could see the documentation for TIMER and WDT here(revision 1). If it is not specified that the SoftDevice incorporates the workaround, then you would have to incorporate it in your application. You have not specified which revision you are working with, nor which WDT errata you are referring to.

Justin said:

Is there a list of hardware the softdevice uses? Almost certain the following aren't used, but need confirmation:

You have not specified which SoftDevice you are working with. As an example, you can see here which hardware peripherals that the SD112 requires, and when they might be available to your application.

Best regards,
Karl

 

[Justin]

Hi Karl,

Thanks for clarification.

I am using S132 v6.0.0 and the chip model is NRF52832_xxAA_REV2.

1. Is there a list of hardware peripherals that this version of softdevice use?

2. Errata 78 - Does soft device use timer STOP task?

3. Radio related Erratas - 91, 138, 143, 182, 204 - Has softdevice incorporated these workarounds?

Being a medical device the erratas are extremely important to us and have to provide justification for each and every errata.

Thanks,

Justin

[Karl Ylvisaker]

Hello Justin,

Justin said:

Thanks for clarification.

No problem at all, I am happy to help!

Justin said:

I am using S132 v6.0.0 and the chip model is NRF52832_xxAA_REV2.

Great, that makes things a lot clearer.

1. Here you can see the hardware peripheral requirements of the S132, and which of them might be available to your application.

2. The BLE activities of S132 is using MPSL multitimer(TIMER0). In MPSL, TASKS_STOP is called, followed by TASKS_SHUTDOWN when resetting the multitimer. Thus, the S132's use of the TIMER0 is not affected by the Errata [78] TIMER.
However, if you use any other timer instances in your application, you need to make sure that you use TASKS_SHUTDOWN instead of TASKS_STOP, to avoid the increase in power consumption when the timer is stopped.

3. Please click the erratas in question in this menu. If the "Workaround" section does not specifically mention that the workaround is incorporated in the S132 SoftDevice, then it is not. However, not that far from all erratas are applicable to the SoftDevice.

Justin said:

Being a medical device the erratas are extremely important to us and have to provide justification for each and every errata.

Absolutely, I fully understand. Let me know if there should be any more questions, any time!

Best regards,
Karl