Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nrf_desktop migration guide cs3 - ncs2.7 #1

Closed
wants to merge 1 commit into from
Closed

nrf_desktop migration guide cs3 - ncs2.7 #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions ...ration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,38 @@ General

The previously used SOC1-based board files have been removed.

nRF Desktop
-----------

You need to make the following changes for :ref:`nrf_desktop` application to work in the same way as in the release v2.4.99-cs3.

* Due to the migration to the new hardware model, commonly referred as "hardware model v2", the board target of the nRF54H20 DK has changed to ``nrf54h20dk/nrf54h20/cpuapp``.
The build command for the application has changed and it is now:

.. code-block:: console

west build -b nrf54h20dk/nrf54h20/cpuapp
Comment on lines +85 to +87
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.. code-block:: console
west build -b nrf54h20dk/nrf54h20/cpuapp
.. code-block:: console
west build -b nrf54h20dk/nrf54h20/cpuapp


* The :ref:`ipc_radio` image serves purpose as universal network core image for hci_ipc rpc_host and IEEE 802.15.4 remote image.
Due to that radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the :ref:`zephyr:bluetooth-hci-ipc-sample` sample from ``sdk-zephyr``.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Due to that radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the :ref:`zephyr:bluetooth-hci-ipc-sample` sample from ``sdk-zephyr``.
Due to this, the radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the :ref:`zephyr:bluetooth-hci-ipc-sample` sample from ``sdk-zephyr``.

Radio core image configuration files have been moved from :file:`configuration/nrf54h20dk_nrf54h20_cpuapp/child_image/hci_rpmsg` to :file:`configuration/nrf54h20dk_nrf54h20_cpurad/images/ipc_radio` directory.
* Due to transition to sysbuild, the configuration enabling the radio core image has been moved from the main application image configuration to the sysbuild configuration.
See the following sysbuild Kconfig options related to the radio core image configuration:

* ``SB_CONFIG_NRF_DEFAULT_IPC_RADIO``
* ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC``
zycz marked this conversation as resolved.
Show resolved Hide resolved

* The :file:`dfu_mcumgr_suit.c` module has been merged with :file:`dfu_mcumgr.c`.
The ``CONFIG_DESKTOP_DFU_MCUMGR_SUIT_ENABLE`` Kconfig option had been removed and replaced by :ref:`CONFIG_DESKTOP_DFU_BACKEND_SUIT <config_desktop_app_options>`.
The :file:`dfu_mcumgr_suit.c` is no longer needed as in |NCS| v2.7 the dfu_mcumgr module can be properly adapted to support the SUIT DFU.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The :file:`dfu_mcumgr_suit.c` is no longer needed as in |NCS| v2.7 the dfu_mcumgr module can be properly adapted to support the SUIT DFU.
The :file:`dfu_mcumgr_suit.c` file is no longer needed as in the |NCS| v2.7.0 the :ref: `nrf_desktop_dfu_mcumgr` module can be properly adapted to support the SUIT DFU.

* The USB High-Speed is supported only in the USB next stack.
New USB next stack has been integrated into the nRF Desktop application and can be enabled using the :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` Kconfig option.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
New USB next stack has been integrated into the nRF Desktop application and can be enabled using the :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` Kconfig option.
New USB next stack has been integrated into the nRF Desktop application and you can enable it using the :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` Kconfig option.

It is now enabled by default in the nRF54H20 DK configurations.
An USB HID-class instance is now configured through a separate DTS node compatible with ``zephyr,hid-device``.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An USB HID-class instance is now configured through a separate DTS node compatible with ``zephyr,hid-device``.
A USB HID-class instance is now configured through a separate DTS node compatible with ``zephyr,hid-device``.

See :ref:`nrf_desktop_usb_state` documentation for details related to USB-next stack integration.
* Align flash writes in the :ref:`nrf_desktop_dfu` to the flash write block size of the non-volatile memory.
This is needed because the :ref:`CONFIG_SOC_FLASH_NRF_MRAM_ONE_BYTE_WRITE_ACCESS <config_desktop_app_options>` Kconfig option is no longer available and MRAMC requiers writes of the size of the whole MRAM word to the MRAM.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This is needed because the :ref:`CONFIG_SOC_FLASH_NRF_MRAM_ONE_BYTE_WRITE_ACCESS <config_desktop_app_options>` Kconfig option is no longer available and MRAMC requiers writes of the size of the whole MRAM word to the MRAM.
This is needed because the :ref:`CONFIG_SOC_FLASH_NRF_MRAM_ONE_BYTE_WRITE_ACCESS <config_desktop_app_options>` Kconfig option is no longer available and MRAMC requires writes to the MRAM.
The size must be equal to the full MRAM word.


Security
========

Expand Down
Loading