I have a shipping product with S132 2.0.1 with multiple problems with the LFRC clock.
There are seemingly at least 4 errata that apply (77, 132, 146, 192).
Are there workarounds for these errata with S132?
Does S132 implement any of these errata?
I have a shipping product with S132 2.0.1 with multiple problems with the LFRC clock.
There are seemingly at least 4 errata that apply (77, 132, 146, 192).
Are there workarounds for these errata with S132?
Does S132 implement any of these errata?
Hi,
This is not a problem if you are using the S132, since it will be calibrated when softdevice is enabled.
This should not be a problem either unless you actively disable and try to enable the softdevice again.
You should check that the softdevice you have support configuring 500ppm tolerance when using LFRC oscillator, I do not remember if the S132v2.0.1 support this since it is rather old. I know this have been possible for quite some time. The problem may be that you experience frequent disconnects if this is not possible in some cases (since the peers will not be able to maintain synchronization).
As stated in the text, this workaround is only included in S132v6.0.0 (and newer).
Hope that helps.
Best regards,
Kenneth
Hi,
This is not a problem if you are using the S132, since it will be calibrated when softdevice is enabled.
This should not be a problem either unless you actively disable and try to enable the softdevice again.
You should check that the softdevice you have support configuring 500ppm tolerance when using LFRC oscillator, I do not remember if the S132v2.0.1 support this since it is rather old. I know this have been possible for quite some time. The problem may be that you experience frequent disconnects if this is not possible in some cases (since the peers will not be able to maintain synchronization).
As stated in the text, this workaround is only included in S132v6.0.0 (and newer).
Hope that helps.
Best regards,
Kenneth