Errata 172

RE: Errata 172

Jared — Wed, 23 Oct 2019 07:10:05 GMT

Hi,

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

Jared

RE: Errata 172

Roei — Tue, 22 Oct 2019 14:40:58 GMT

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

Thanks!

RE: Errata 172

Jared — Tue, 22 Oct 2019 12:03:30 GMT

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

RE: Errata 172

Roei — Tue, 22 Oct 2019 07:39:26 GMT

Thanks, Jared!

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

RE: Errata 172

Jared — Mon, 21 Oct 2019 08:38:18 GMT

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

RE: Errata 172

Roei — Sun, 20 Oct 2019 08:25:32 GMT

Is there any example for how to use the nrfjprog command in order to read memory?

RE: Errata 172

Roei — Sun, 20 Oct 2019 06:21:08 GMT

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?

RE: Errata 172

Jared — Fri, 18 Oct 2019 13:49:25 GMT

You could use nrfjprog command memrd and read the MODE register.

RE: Errata 172

Roei — Fri, 18 Oct 2019 13:12:26 GMT

Thanks!

What about the kit? How can I know which one I use?

RE: Errata 172

Jared — Fri, 18 Oct 2019 13:06:23 GMT

Hi,

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

best regards

Jared