You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add release documentation for nRF54H20 SoC binaries v0.9.1.
Combine changelog entries from the previous version with some new ones.
Ref: NCSDK-31339
Signed-off-by: Håkon Amundsen <[email protected]>
Signed-off-by: Jonathan Nilsen <[email protected]>
(cherry picked from commit 71ae1a4)
Copy file name to clipboardExpand all lines: doc/nrf/releases_and_maturity/abi_compatibility.rst
+23-9Lines changed: 23 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ The following table illustrates ABI compatibility between different versions of
28
28
29
29
* - |NCS| versions
30
30
- Compatible nRF54H20 SoC binaries version
31
-
* - |NCS| v2.9.0-nRF54H20
32
-
- `nRF54H20 SoC Binaries v0.8.0`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
31
+
* - |NCS| v2.9.0-nRF54H20-1-rc2
32
+
- `nRF54H20 SoC Binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
33
33
* - |NCS| v2.9.0
34
34
- `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions.
35
35
* - |NCS| v2.8.0
@@ -47,17 +47,22 @@ The following table illustrates ABI compatibility between different versions of
47
47
ABI compatibility ensures that the Secure Domain and System Controller firmware binaries do not need to be recompiled each time the application, radio binaries, or both are recompiled, as long as they are based on a compatible |NCS| version.
48
48
Additionally, maintaining ABI compatibility allows the nRF54H20 SoC binary components to work together without recompilation when updating to newer |NCS| versions.
49
49
50
-
nRF54H20 SoC Binaries v0.8.0 changelog
50
+
nRF54H20 SoC Binaries v0.9.1 changelog
51
51
**************************************
52
52
53
53
The following sections provide detailed lists of changes by component.
54
54
55
-
Secure Domain Firmware (SDFW) v9.0.0
55
+
Secure Domain Firmware (SDFW) v10.1.0
56
56
=====================================
57
57
58
58
Added
59
59
-----
60
60
61
+
* GPIO DRIVECTRL for P6 and P7 on nRF54H20 is now corrected by SDFW on boot.
62
+
This addresses an issue where some devices has this incorrectly configured.
63
+
* Added support for TLS-1.3 in the PSA crypto service.
64
+
* Added support for ED25519 pre-hashed in the PSA crypto service.
65
+
* The SDFW now uses a watchdog timer with a timeout of 4 seconds.
61
66
* Purge protection can be enabled over ADAC.
62
67
* Clock control is enabled in SDFW.
63
68
* Global domain power request service is integrated in SDFW.
@@ -66,10 +71,15 @@ Added
66
71
Updated
67
72
-------
68
73
69
-
* Local domain reset will trigger a global reset.
70
-
``RESETINFO`` will contain both the global and local reset reason.
71
-
* All processors are booted regardless of whether they have firmware.
72
-
They are booted in halted mode if no firmware is present.
74
+
* A local domain reset now triggers a global reset.
75
+
``RESETINFO`` contains both the global and local reset reasons.
76
+
* All processors now boot regardless of whether they have firmware.
77
+
If no firmware is present, they boot in halted mode.
78
+
* Reduced power consumption from the Secure Domain when tracing is enabled.
79
+
* Increased the number of possible concurrent PSA operations to 8.
80
+
* The ETR buffer location is now read from the UICR.
81
+
Enabling ETR tracing now requires configuring the location.
82
+
* The SDFW no longer immediately resets on a fatal error.
73
83
74
84
Removed
75
85
-------
@@ -80,9 +90,12 @@ Removed
80
90
Fixed
81
91
-----
82
92
93
+
* An issue where SDFW exited the sleep state for a short duration after boot completion.
94
+
* An issue where replies to ADAC SSF commands contained a large amount of additional zero values at the end of the message.
95
+
* An issue where permission checks for pointer members in the SSF PSA crypto service requests were incorrect.
83
96
* An issue with invoking crypto service from multiple threads or clients.
0 commit comments