nRF54L Errata support in nRF Connect SDK
This page summarizes the nRF54L Series anomalies and their workarounds that are currently implemented in the nRF Connect SDK.
nRF54L Series Errata documents contain descriptions of identified hardware anomalies for the relevant SoCs:
Some of the anomalies can be fixed by applying workarounds directly in the software components, requiring minimal or zero effort from the end user.
Errata status definitions
- Not applicable
The anomaly is not applicable for the given device.
- Not implemented
The anomaly is applicable for the given device but the workaround is not implemented in the nRF Connect SDK.
- Enabled
The workaround is implemented and enabled by default.
- Available
The workaround is implemented, but specific action is required to enable it. Refer to the provided information on how to enable the workaround.
Errata workaround status per device
Refer to the following table for the current workaround list:
Anomaly ID |
Status |
|---|---|
1 |
Not implemented |
6 |
Not implemented |
7 |
Enabled |
8 |
Enabled |
16 |
Enabled |
17 |
Not implemented |
18 |
Not implemented |
20 |
Not implemented |
21 |
Not implemented |
22 |
Not implemented |
23 |
Not implemented |
24 |
Not implemented |
25 |
Not implemented |
26 |
Not implemented |
30 |
Available when |
31 |
Enabled |
32 |
Enabled |
37 |
Enabled |
39 |
Enabled |
41 |
Not implemented |
44 |
Not implemented |
47 |
Not implemented |
48 |
Enabled |
49 |
Not implemented |
50 |
Not applicable |
59 |
Not applicable |
63 |
Not applicable |
69 |
Not applicable |
102 |
Not applicable |
104 |
Not applicable |
105 |
Not applicable |
Anomaly ID |
Status |
|---|---|
1 |
Not implemented |
6 |
Not implemented |
7 |
Enabled |
8 |
Enabled |
16 |
Enabled |
17 |
Not implemented |
18 |
Not implemented |
20 |
Not implemented |
21 |
Not implemented |
22 |
Not implemented |
23 |
Not implemented |
24 |
Not implemented |
25 |
Not implemented |
26 |
Not implemented |
30 |
Available when |
31 |
Enabled |
32 |
Enabled |
37 |
Enabled |
39 |
Enabled |
41 |
Not implemented |
44 |
Not implemented |
47 |
Not implemented |
48 |
Enabled |
49 |
Not implemented |
50 |
Not applicable |
59 |
Not applicable |
63 |
Not applicable |
69 |
Not applicable |
102 |
Not applicable |
104 |
Not applicable |
105 |
Not applicable |
Anomaly ID |
Status |
|---|---|
1 |
Not implemented |
6 |
Not implemented |
7 |
Enabled |
8 |
Enabled |
16 |
Enabled |
17 |
Not implemented |
18 |
Not implemented |
20 |
Not implemented |
21 |
Not implemented |
22 |
Not implemented |
23 |
Not implemented |
24 |
Not implemented |
25 |
Not implemented |
26 |
Not implemented |
30 |
Available when |
31 |
Enabled |
32 |
Enabled |
37 |
Enabled |
39 |
Enabled |
41 |
Not implemented |
44 |
Not implemented |
47 |
Not implemented |
48 |
Enabled |
49 |
Not implemented |
50 |
Not applicable |
59 |
Not applicable |
63 |
Not applicable |
69 |
Not applicable |
102 |
Not applicable |
104 |
Not applicable |
105 |
Not applicable |
Anomaly ID |
nRF54LM20A |
nRF54LM20B |
|---|---|---|
1 |
Not applicable |
Not applicable |
6 |
Not applicable |
Not applicable |
7 |
Enabled |
Enabled |
8 |
Enabled |
Enabled |
16 |
Not applicable |
Not applicable |
17 |
Not applicable |
Not applicable |
18 |
Not applicable |
Not applicable |
20 |
Not applicable |
Not applicable |
21 |
Not applicable |
Not applicable |
22 |
Not applicable |
Not applicable |
23 |
Not applicable |
Not applicable |
24 |
Not applicable |
Not applicable |
25 |
Not applicable |
Not applicable |
26 |
Not implemented |
Not implemented |
30 |
Available when |
Available when |
31 |
Enabled |
Enabled |
32 |
Enabled |
Enabled |
37 |
Enabled |
Enabled |
39 |
Enabled |
Enabled |
41 |
Not applicable |
Not applicable |
44 |
Not implemented |
Not implemented |
47 |
Not implemented |
Not implemented |
48 |
Not applicable |
Not applicable |
49 |
Not implemented |
Not implemented |
50 |
Not implemented |
Not implemented |
59 |
Not implemented |
Not implemented |
63 |
Not implemented |
Not implemented |
69 |
Enabled |
Enabled |
102 |
Not implemented |
Not implemented |
104 |
Not implemented |
Not implemented |
105 |
Not implemented |
Not implemented |
Anomaly ID |
Status |
|---|---|
1 |
Not applicable |
6 |
Not applicable |
7 |
Enabled |
8 |
Enabled |
16 |
Not applicable |
17 |
Not applicable |
18 |
Not applicable |
20 |
Not implemented |
21 |
Not applicable |
22 |
Not applicable |
23 |
Not applicable |
24 |
Not applicable |
25 |
Not applicable |
26 |
Not applicable |
30 |
Available when |
31 |
Not applicable |
32 |
Not applicable |
37 |
Enabled |
39 |
Not applicable |
41 |
Not applicable |
44 |
Not implemented |
47 |
Not applicable |
48 |
Not applicable |
49 |
Not implemented |
50 |
Not applicable |
59 |
Not applicable |
63 |
Not implemented |
69 |
Enabled |
102 |
Not implemented |
104 |
Not applicable |
105 |
Not applicable |
Anomaly ID |
nRF54LS05A |
nRF54LS05B |
|---|---|---|
1 |
Not applicable |
Not applicable |
6 |
Not applicable |
Not applicable |
7 |
Enabled |
Enabled |
8 |
Enabled |
Enabled |
16 |
Not applicable |
Not applicable |
17 |
Not applicable |
Not applicable |
18 |
Not applicable |
Not applicable |
20 |
Not implemented |
Not implemented |
21 |
Not applicable |
Not applicable |
22 |
Not applicable |
Not applicable |
23 |
Not applicable |
Not applicable |
24 |
Not applicable |
Not applicable |
25 |
Not applicable |
Not applicable |
26 |
Not applicable |
Not applicable |
30 |
Available when |
Available when |
31 |
Not applicable |
Not applicable |
32 |
Not applicable |
Not applicable |
37 |
Enabled |
Enabled |
39 |
Enabled |
Enabled |
41 |
Not applicable |
Not applicable |
44 |
Not implemented |
Not implemented |
47 |
Not applicable |
Not applicable |
48 |
Not applicable |
Not applicable |
49 |
Not implemented |
Not implemented |
50 |
Not applicable |
Not applicable |
59 |
Not implemented |
Not implemented |
63 |
Not implemented |
Not implemented |
69 |
Enabled |
Enabled |
102 |
Not applicable |
Not applicable |
104 |
Not applicable |
Not applicable |
105 |
Not implemented |
Not implemented |
1 You can set the anomaly workaround appliance frequency using the CONFIG_CLOCK_CONTROL_NRF_HFINT_CALIBRATION_PERIOD Kconfig option.
Its value must be tuned in accordance to application-specific operating temperature and expected power consumption.
2 Enabling the CONFIG_CLOCK_CONTROL_NRF_HFINT_CALIBRATION Kconfig option on the nRF54LS05 SoC causes application to go into bus fault, which is already a recognized known issue (see the NRFX-9318 item in the known issues page on the main branch).