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
Updated the nRF54H20 DK entry in board configuration documentation of
the nRF Desktop application to align the description with the recent
migration to the IronSide SE architecture.
Ref: NCSDK-35488
Signed-off-by: Kamil Piszczek <[email protected]>
Copy file name to clipboardExpand all lines: applications/nrf_desktop/board_configuration.rst
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,11 +196,12 @@ Sample mouse or dongle (``nrf54h20dk/nrf54h20/cpuapp``)
196
196
The :option:`CONFIG_DESKTOP_BLE_ADV_CTRL_ENABLE` and :option:`CONFIG_DESKTOP_BLE_ADV_CTRL_SUSPEND_ON_USB` Kconfig options are enabled in mouse configurations to improve the USB High-Speed report rate.
197
197
* In ``debug`` configurations, logs are provided through the UART.
198
198
For detailed information on working with the nRF54H20 DK, see the :ref:`ug_nrf54h20_gs` documentation.
199
-
* The configurations use the Software Updates for Internet of Things (SUIT) and support firmware updates using the :ref:`nrf_desktop_dfu`.
199
+
* The configurations use the MCUboot bootloader built in the direct-xip mode (``MCUBOOT+XIP``) and support firmware updates using the :ref:`nrf_desktop_dfu`.
200
200
Configurations acting as HID peripherals also support firmware updates using the :ref:`nrf_desktop_dfu_mcumgr`.
201
+
For more details on MCUboot, see :ref:`nrf_desktop_bootloader`.
201
202
202
-
.. note::
203
-
The nRF Desktop application does not build or run for the ``nrf54h20dk/nrf54h20/cpuapp`` board target due to the IronSide SE migration.
204
-
See the ``NCSDK-34299`` in the :ref:`known_issues` page for more information.
205
-
The :ref:`nrf_desktop` documentation may still refer to concepts that were valid before the IronSide SE migration (for example, to the SUIT solution).
206
-
The codebase and documentation will be updated in the future releases to address this issue.
203
+
All configurations enable hardware cryptography for the MCUboot bootloader.
204
+
The MCUboot bootloader uses the :ref:`ug_crypto_architecture_implementation_standards_ironside` for hardware cryptography.
205
+
The application image is verified using a pure ED25519 signature.
206
+
In all configurations, the MCUboot bootloader uses a merged image slot that combines both application and radio core images.
207
+
For more details on nRF54H Series DFU, see :ref:`ug_nrf54h20_mcuboot_dfu`.
0 commit comments