Errata 172

[Roei]

Hi,

I'm trying to figure out if my device is suffering from errata 172.

* How can I know if I'm using Ble_LR125Kbit or Ble_LR500Kbit?
* I'm trying to use the function bool enable_errata_172 (void). Do you have any example for that?

Thanks!

[Jared]

Hi,

There seems to be a typo in the document, the correct function to call is enable_anomaly_172().

best regards

Jared 

[Roei]

Thanks!

But it's still not clear from the document - which files should I include in order to use this function? Do you have any example?

[Jared]

Hi,

You can look at ble_dtm.c which is used in the dtm example in the SDK. There it's checked if the workaround for nRF52840 Anomaly 172 should be enabled or not:

                    if ((*(volatile uint32_t *)0x40001788) == 0)
                    {
                        anomaly_172_wa_enabled = true;
                    }

nrfjprog command for reading MODE register:

nrfjprog --memrd 0x40001510

regards

Jared

[Roei]

Thanks, Jared!

One more question - is erreta 172 relevant for BLE 4.2?

[Jared]

Hi,

The errata is specific to your IC version. Most of the nRF52840 revisions are affected by errata 172. A good practice is therefore to implement the workaround.

best regards

Jared 

[Roei]

OK, but does it affect Nrf_1Mbit mode, or any other modes which are not Ble_LR125Kbit or Ble_LR500Kbit?

Thanks!

[Jared]

Hi,

Only BLE long range with either 125 kbit or 500 kbit is affected. 

Jared