nrf_desktop migration guide cs3 - ncs2.7 #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
3 times, most recently
from
65a2d87
to
3e88e12
Compare
mkapala-nordic
suggested changes
Jun 19, 2024
| @@ -74,6 +74,40 @@ General | |||
|
|
|||
| The previously used SOC1-based board files have been removed. | |||
|
|
|||
| NRF Desktop | |||
| NRF Desktop | ||
| ----------- | ||
|
|
||
| The following changes have to be made for nrf_desktop application to work in the same way as in the release v2.4.99-cs3 . |
There was a problem hiding this comment.
Suggested change
| The following changes have to be made for nrf_desktop application to work in the same way as in the release v2.4.99-cs3 . | |
| The following changes have to be made for :ref:`nrf_desktop` application to work in the same way as in the release v2.4.99-cs3 . |
|
|
||
| The following changes have to be made for nrf_desktop application to work in the same way as in the release v2.4.99-cs3 . | ||
|
|
||
| * Because of hardware model v2 the building command for application has changed and it is now: |
There was a problem hiding this comment.
maybe something like that to show that only the <board> part has changed?
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 the ``nrf54h20dk/nrf54h20/cpuapp``.
|
|
||
| west build -b nrf54h20dk/nrf54h20/cpuapp | ||
|
|
||
| * For radio core image hci_rpmsg was removed and replaced with ipc_radio. |
There was a problem hiding this comment.
Suggested change
| * For radio core image hci_rpmsg was removed and replaced with ipc_radio. | |
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI IPC sample from ``sdk-zephyr``. |
| west build -b nrf54h20dk/nrf54h20/cpuapp | ||
|
|
||
| * For radio core image hci_rpmsg was removed and replaced with ipc_radio. | ||
| * Sample uses default memory map. |
There was a problem hiding this comment.
Suggested change
| * Sample uses default memory map. | |
| * Application uses the default memory map. |
Comment on lines
93
to
108
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. | ||
| See commits how to integrate it to nrf_desktop application: | ||
|
|
||
| * https://github.com/nrfconnect/sdk-nrf/commit/3c1a3ec4b7e9df3aa70333c761655ea7bb38bc8e | ||
| * https://github.com/nrfconnect/sdk-nrf/commit/290d421ee505e6f57decd48a5aea78f238060865 | ||
| * https://github.com/nrfconnect/sdk-nrf/commit/c57fc2d78f87345929d6395bfcf40f83ff9b33b5 | ||
| * https://github.com/nrfconnect/sdk-nrf/commit/16492f54dbe6d89f37fcd499bf34346118edb327 |
There was a problem hiding this comment.
Do we need those commit list here?
It is not "how to integrate it" but "how it has been integrated".
Won't the information that the USB High-Speed is only available on the USB next stack thus needed for nRF54H be enough?
There was a problem hiding this comment.
Question for rest should we place commits here?
There was a problem hiding this comment.
let's wait for others input then.
If commits won't be necessary then consider replacing it with something like:
* 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.
It is now enabled by default in the nRF54H20 DK configurations.
| * https://github.com/nrfconnect/sdk-nrf/commit/c57fc2d78f87345929d6395bfcf40f83ff9b33b5 | ||
| * https://github.com/nrfconnect/sdk-nrf/commit/16492f54dbe6d89f37fcd499bf34346118edb327 | ||
|
|
||
| * Radio core configuration files have been moved from :file:`configuration/nrf54h20dk_nrf54h20_cpuapp/child_image/hci_rpmsg` to :file:`configuration/nrf54h20dk_nrf54h20_cpurad` directory. |
There was a problem hiding this comment.
Isn't it related to sysbuild? Also we migrated to the ipc_radio, and this sentence for me suggests that we have hci_rpmsg configs still in the app.
There was a problem hiding this comment.
Will place it near information that we remove hci_rpmsg. Yes it is sysbuild info but still I think it is worth placing it here to show how it impacts this application
There was a problem hiding this comment.
So maybe:
* Due to the migration to sysbuild, radio core image configuration files have been moved from the :file:`configuration/nrf54h20dk_nrf54h20_cpuapp/child_image` to :file:`configuration/nrf54h20dk_nrf54h20_cpurad/images` directory.
Comment on lines
103
to
111
| * Align FLASH writes in dfu application module to FLASH write block of non-volatile memory. | ||
| See commit: https://github.com/nrfconnect/sdk-nrf/commit/becbed095fa9f732d2e3a4b21a65fd8f36694601 |
There was a problem hiding this comment.
Do we need commit here?
It is just an improvement of nRF Desktop in my opinion, is it worth to mention it here?
Suggested change
| * Align FLASH writes in dfu application module to FLASH write block of non-volatile memory. | |
| See commit: https://github.com/nrfconnect/sdk-nrf/commit/becbed095fa9f732d2e3a4b21a65fd8f36694601 | |
| * Align FLASH writes in the :ref:`nrf_desktop_dfu` to FLASH write block size of the non-volatile memory. | |
| See commit: https://github.com/nrfconnect/sdk-nrf/commit/becbed095fa9f732d2e3a4b21a65fd8f36694601 |
There was a problem hiding this comment.
same as above regarding keeping commits
There was a problem hiding this comment.
- Commits -> ok, let's wait for others input.
- Note itself -> Do we even need that note ("It is just an improvement of nRF Desktop IMO")
Comment on lines
105
to
106
| * Due to transition to sysbuild build system options regarding usage of radio core have been moved from prj.conf to sysbuild.conf. | ||
| NRF Desktop nRF54H20 significant options which are set in sysbuild.conf: |
There was a problem hiding this comment.
Suggested change
| * Due to transition to sysbuild build system options regarding usage of radio core have been moved from prj.conf to sysbuild.conf. | |
| NRF Desktop nRF54H20 significant options which are set in sysbuild.conf: | |
| * Due to transition to sysbuild, configuration of radio core image has been moved from the main application configuration to the sysbuild configuration. | |
| See the following sysbuild Kconfig options related to the radio core image configuration: |
|
|
||
| * For radio core image hci_rpmsg was removed and replaced with ipc_radio. | ||
| * Sample uses default memory map. | ||
| * Module :file:`dfu_mcumgr_suit.c` had been merged to :file:`dfu_mcumgr.c`. |
There was a problem hiding this comment.
Suggested change
| * Module :file:`dfu_mcumgr_suit.c` had been merged to :file:`dfu_mcumgr.c`. | |
| * Module :file:`dfu_mcumgr_suit.c` has been merged with :file:`dfu_mcumgr.c`. |
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
from
3e88e12
to
f82d50f
Compare
|
|
||
| * Align FLASH writes in the :ref:`nrf_desktop_dfu` to FLASH write block size of the non-volatile memory. | ||
| See commit: https://github.com/nrfconnect/sdk-nrf/commit/becbed095fa9f732d2e3a4b21a65fd8f36694601 | ||
| * Due to transition to sysbuild, configuration of radio core image has been moved from the main application configuration to the sysbuild configuration. |
There was a problem hiding this comment.
please move it before * Application uses the default memory map. to group radio core related stuff
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
from
f82d50f
to
52da3d4
Compare
MarekPieta
suggested changes
Jun 21, 2024
|
|
||
| west build -b nrf54h20dk/nrf54h20/cpuapp | ||
|
|
||
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI IPC sample from ``sdk-zephyr``. |
There was a problem hiding this comment.
Looking at configurations it used to use HCI RPMsg, right?
| west build -b nrf54h20dk/nrf54h20/cpuapp | ||
|
|
||
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI IPC sample from ``sdk-zephyr``. | ||
| * Radio core configuration files have been moved from :file:`configuration/nrf54h20dk_nrf54h20_cpuapp/child_image/hci_rpmsg` to :file:`configuration/nrf54h20dk_nrf54h20_cpurad` directory. |
There was a problem hiding this comment.
Radio core image configuration files ..... to :file:`configuration/nrf54h20dk_nrf54h20_cpurad/images/ipc_radio`
..._maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst
Show resolved
Hide resolved
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. | ||
| See commits "how it has been integrated to nrf_desktop application: |
There was a problem hiding this comment.
Maybe we could link to USB state module documentation here instead of adding links to commits?
..._maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst
Outdated
Show resolved
Hide resolved
|
|
||
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI IPC sample from ``sdk-zephyr``. | ||
| * Radio core configuration files have been moved from :file:`configuration/nrf54h20dk_nrf54h20_cpuapp/child_image/hci_rpmsg` to :file:`configuration/nrf54h20dk_nrf54h20_cpurad` directory. | ||
| * Due to transition to sysbuild, configuration of radio core image has been moved from the main application configuration to the sysbuild configuration. |
There was a problem hiding this comment.
configuration enabling radio core image
There was a problem hiding this comment.
main application image configuration
|
|
||
| * ``SB_CONFIG_NRF_DEFAULT_IPC_RADIO`` | ||
| * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC`` | ||
| * Application uses the default memory map. |
There was a problem hiding this comment.
Consider explicitly mentioning that it no longer defines an application-specific memory map.
| * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC`` | ||
| * Application uses the default memory map. | ||
| * Module :file:`dfu_mcumgr_suit.c` has been merged with :file:`dfu_mcumgr.c`. | ||
| The ``CONFIG_DESKTOP_DFU_MCUMGR_SUIT_ENABLE`` Kconfig option had been removed and replaced by :kconfig:option:`CONFIG_DESKTOP_DFU_BACKEND_SUIT`. |
There was a problem hiding this comment.
Fix references to nRF Desktop specific Kconfigs - use the following syntax:
:ref:`CONFIG_DESKTOP_FN_KEYS_SWITCH <config_desktop_app_options>`
| * The :file:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | ||
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :kconfig:option:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. |
There was a problem hiding this comment.
Please also inform that USB HID configuration is different now (it was moved to DTS)
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
from
52da3d4
to
d96074f
Compare
MarekPieta
reviewed
Jun 21, 2024
|
|
||
| * Application uses the default memory map based on Zephyr board files and no longer defines an application-specific memory map. | ||
| * Module :file:`dfu_mcumgr_suit.c` 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`. |
There was a problem hiding this comment.
nRF Desktop Kconfig option references are still wrong.
| The ``CONFIG_DESKTOP_DFU_MCUMGR_SUIT_ENABLE`` Kconfig option had been removed and replaced by :ref:`CONFIG_DESKTOP_DFU_BACKEND_SUIT`. | ||
| * The :file:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | ||
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next new stack for USB support. |
| * The :file:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | ||
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. |
There was a problem hiding this comment.
to enable it in nRF Desktop application
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. | ||
| USB HID-class instance is now configured through a separate DTS node compatible with ``zephyr,hid-device``. |
| * Moved to using USB-next new stack for USB support. | ||
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT` has been added to enable it. | ||
| USB HID-class instance is now configured through a separate DTS node compatible with ``zephyr,hid-device``. | ||
| See usb_state documentation on how to integrate USB-next stack: :ref:`nrf_desktop_usb_state`. |
There was a problem hiding this comment.
See :ref:nrf_desktop_usb_state documentation for details related to USB-next stack integration
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
from
d96074f
to
8a1755a
Compare
MarekPieta
approved these changes
Jun 21, 2024
peknis
suggested changes
Jun 24, 2024
| nRF Desktop | ||
| ----------- | ||
|
|
||
| The following changes have to be made for :ref:`nrf_desktop` application to work in the same way as in the release v2.4.99-cs3. |
There was a problem hiding this comment.
Suggested change
| The following changes have to be made for :ref:`nrf_desktop` application to work in the same way as in the release v2.4.99-cs3. | |
| You need to make the following changes for the :ref:`nrf_desktop` application to work in the same way as in the release v2.4.99-cs3. |
|
|
||
| The following changes have to be made 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 the ``nrf54h20dk/nrf54h20/cpuapp``. |
There was a problem hiding this comment.
Suggested change
| * 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 the ``nrf54h20dk/nrf54h20/cpuapp``. | |
| * 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 following changes have to be made 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 the ``nrf54h20dk/nrf54h20/cpuapp``. | ||
| Building command for application has changed and it is now: |
There was a problem hiding this comment.
Suggested change
| Building command for application has changed and it is now: | |
| The build command for the application has changed and it is now: |
|
|
||
| west build -b nrf54h20dk/nrf54h20/cpuapp | ||
|
|
||
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI RPMsg sample from ``sdk-zephyr``. |
There was a problem hiding this comment.
Link to the Zephyr BT sample? Is it this one https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/samples/bluetooth/hci_ipc/README.html?
|
|
||
| * Radio core now uses the :ref:`ipc_radio` application from ``sdk-nrf`` instead of the Bluetooth HCI RPMsg 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, configuration enabling radio core image has been moved from the main application image configuration to the sysbuild configuration. |
There was a problem hiding this comment.
Suggested change
| * Due to transition to sysbuild, configuration enabling radio core image has been moved from the main application image configuration to the sysbuild configuration. | |
| * 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. |
| * Application uses the default memory map based on Zephyr board files and no longer defines an application-specific memory map. | ||
| * Module :file:`dfu_mcumgr_suit.c` 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:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. |
There was a problem hiding this comment.
Suggested change
| * The :file:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | |
| * The :file:`prj_suit_smp.conf` configuration for the nRF54H20 DK has been removed. |
There was a problem hiding this comment.
Removed sentence as it is to nrf_desktop specific. Disused offline with Francesco
| * Module :file:`dfu_mcumgr_suit.c` 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:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | ||
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. |
There was a problem hiding this comment.
Suggested change
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | |
| DFU over SMP is now enabled by default in the ``debug`` and ``release`` configurations. |
There was a problem hiding this comment.
Removed sentence as it is to nrf_desktop specific. Disused offline with Francesco
| * The :file:`prj_suit_smp.conf` configuration for nRF54H20 DK has been removed. | ||
| Now DFU over SMP is enabled by default in the ``debug`` and ``release`` configurations. | ||
| * Moved to using USB-next stack for USB support. | ||
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT <config_desktop_app_options>` has been added to enable it in nRF Desktop application. |
There was a problem hiding this comment.
Suggested change
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT <config_desktop_app_options>` has been added to enable it in nRF Desktop application. | |
| A new kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT <config_desktop_app_options>` has been added to enable it in nRF Desktop application. |
| New kconfig option :ref:`CONFIG_DESKTOP_USB_STACK_NEXT <config_desktop_app_options>` has been added to enable it in nRF Desktop application. | ||
| An 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 FLASH write block size of the non-volatile memory. |
There was a problem hiding this comment.
Suggested change
| * Align FLASH writes in the :ref:`nrf_desktop_dfu` to FLASH write block size of the non-volatile memory. | |
| * Align flash writes in the :ref:`nrf_desktop_dfu` to the flash write block size of the non-volatile memory. |
| An 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 FLASH write block size of the non-volatile memory. | ||
| It's needed as :ref:`CONFIG_SOC_FLASH_NRF_MRAM_ONE_BYTE_WRITE_ACCESS <config_desktop_app_options>` is no longer available. |
There was a problem hiding this comment.
Suggested change
| It's needed as :ref:`CONFIG_SOC_FLASH_NRF_MRAM_ONE_BYTE_WRITE_ACCESS <config_desktop_app_options>` is no longer available. | |
| 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. |
mkapala-nordic
approved these changes
Jun 24, 2024
zycz
force-pushed
the
Add_nrf_desktop_migration_guide
branch
from
8a1755a
to
9d3f735
Compare
peknis
suggested changes
Jun 25, 2024
Comment on lines
+85
to
+87
| .. code-block:: console | ||
|
|
||
| west build -b nrf54h20dk/nrf54h20/cpuapp |
There was a problem hiding this comment.
Suggested change
| .. code-block:: console | |
| west build -b nrf54h20dk/nrf54h20/cpuapp | |
| .. code-block:: console | |
| west build -b nrf54h20dk/nrf54h20/cpuapp |
| 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``. |
There was a problem hiding this comment.
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``. |
| 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. | ||
| * 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. |
There was a problem hiding this comment.
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. |
|
|
||
| * 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. |
There was a problem hiding this comment.
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. | ||
| 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``. |
There was a problem hiding this comment.
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``. |
| An 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. |
There was a problem hiding this comment.
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. |
|
Changes are being added in Francesco PR: nrfconnect#15760 Please comment changes there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
nrf_desktop migration guide cs3 - ncs2.7