nRF52832 Revision 2 Errata

RE: nRF52832 Revision 2 Errata

Justin — Mon, 16 Mar 2020 22:34:46 GMT

Thanks Karl for all your help.

RE: nRF52832 Revision 2 Errata

Karl Ylvisaker — Thu, 12 Mar 2020 09:10:56 GMT

[quote user="johnmjustin"]Thanks Karl for the help and looking into it.[/quote]

No problem at all, I am happy to help.

[quote user="johnmjustin"]1. How can I use the timer until the crystal has started?[/quote]

You are able to use the timer(trigger on rising and falling edges) at any time, but all crystals have a transient period during startup before their frequencies are stable.
Are you familiar with this? In essence, during this startup period the frequency of the oscillation is not constant, which quickly leads to trouble if you attempt to use it during this time.
The errata concerns the possibility to receive the EVENTS_HFCLKSTARTED event before the crystal is stable. It would therefore be a problem if you have a crystal with a long startup time, while your code starts executing at the beginning of this received event.
Does this clarify things?

[quote user="johnmjustin"]2. Is there any sample code or solution for this errata?[/quote]

There is no official example code for this, but the solution is as stated in the workaround. First, you will need to find the worst-case startup time for your crystal. This should be documented in the crystals datasheet. If the worst-case startup time is shorter than 400 µs, no further action is required.
If the worst-case startup time is longer than 400 µs, then you need to ensure that the worst-case startup time has passed, before you start using components that rely on the HFCLK, such as the radio. You may do this using an internal timer.

Best regards,
Karl

RE: nRF52832 Revision 2 Errata

Justin — Wed, 11 Mar 2020 22:34:21 GMT

[quote userid="87869" url="~/f/nordic-q-a/58826/nrf52832-revision-2-errata/239296"]Absolutely, I fully understand. Let me know if there should be any more questions, any time![/quote]

Thanks Karl for the help and looking into it.

I have question related to Errata 68.

The Errata workaround says

" the software must ensure, using a timer, that the crystal has had enough time to start up before using peripherals that require the HFXO."

1. How can I use the timer until the crystal has started?

2. Is there any sample code or solution for this errata?

Thanks,

Justin

RE: nRF52832 Revision 2 Errata

Karl Ylvisaker — Wed, 11 Mar 2020 10:22:31 GMT

Hello Justin,

[quote user="johnmjustin"]Thanks for clarification.[/quote]

No problem at all, I am happy to help!

[quote user="johnmjustin"]I am using S132 v6.0.0 and the chip model is NRF52832_xxAA_REV2.[/quote]

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.

[quote user="johnmjustin"]Being a medical device the erratas are extremely important to us and have to provide justification for each and every errata.[/quote]

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

Best regards,
Karl

RE: nRF52832 Revision 2 Errata

Justin — Wed, 11 Mar 2020 00:45:03 GMT

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

RE: nRF52832 Revision 2 Errata

Karl Ylvisaker — Tue, 10 Mar 2020 09:06:42 GMT

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.

[quote user="johnmjustin"]Does the softdevice control for the specified errata for the following[/quote]

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.

[quote user="johnmjustin"]Does the softdevice use the following? If so, does it control for the specified errata?
TIMER
WDT[/quote]

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.

[quote user="johnmjustin"]Is there a list of hardware the softdevice uses? Almost certain the following aren't used, but need confirmation:[/quote]

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

RE: nRF52832 Revision 2 Errata

Justin — Mon, 09 Mar 2020 23:41:54 GMT

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

RE: nRF52832 Revision 2 Errata

Karl Ylvisaker — Mon, 09 Mar 2020 08:02:49 GMT

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