-
Notifications
You must be signed in to change notification settings - Fork 1.4k
applications: nrf_desktop: align dfu config channel with nRF54H IronSide #24865
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.
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
base: main
Are you sure you want to change the base?
applications: nrf_desktop: align dfu config channel with nRF54H IronSide #24865
Conversation
Adapted the DFU module over the Configuration channel in the nRF Desktop application so that it can work with the new nRF54H20 DFU architecture. Enabled support for the DFU module over the Configuration channel in all configurations of the nrf54h20dk/nrf54h20/cpuapp board target. Ref: NCSDK-34151 Signed-off-by: Kamil Piszczek <[email protected]>
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f821943f68c6e0b98855de48ab2d800300cc0072 more detailssdk-nrf:
Github labels
List of changed files detected by CI (5)
Outputs:ToolchainVersion: a7529a11f4 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Memory footprint analysis revealed the following potential issuesapplications.nrf_desktop.zdebug.uart[[email protected]/nrf54h20/cpuapp]: RAM size increased by 785[B] in comparison to the main[3c1547f] branch. - link (cc: @nrfconnect/ncs-si-bluebagel) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-24865/1) |
You can find the documentation preview for this PR here. |
#define PM_ADDRESS_OFFSET (PM_MCUBOOT_PAD_SIZE) | ||
#endif | ||
|
||
#define MCUBOOT_PRIMARY_ID PM_MCUBOOT_PRIMARY_ID |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MCUBOOT_PRIMARY_PARTITION_ID
? (previously PARTITION
word was part of the PM_
prefix)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe MCUBOOT_PRIMARY_SLOT_ID
(for consistency with DFU_SLOT_ID
)?
#define MCUBOOT_PRIMARY_ID DT_FIXED_PARTITION_ID(MCUBOOT_PRIMARY_NODE) | ||
#define MCUBOOT_SECONDARY_ID DT_FIXED_PARTITION_ID(MCUBOOT_SECONDARY_NODE) | ||
|
||
#if DT_REG_ADDR(CODE_PARTITION_NODE) == DT_REG_ADDR(MCUBOOT_PRIMARY_NODE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using DT_FIXED_PARTITION_ADDR
(to improve readability)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw. It would be good to also test IronSide with our fwupd
plugin at some point (to ensure it works there)
#define MCUBOOT_PRIMARY_NODE DT_NODELABEL(slot0_partition) | ||
#define MCUBOOT_SECONDARY_NODE DT_NODELABEL(slot1_partition) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could consider checking if both partitions exist (DT_FIXED_PARTITION_EXISTS
) and start at different addresses
Adapted the DFU module over the Configuration channel in the nRF Desktop application so that it can work with the new nRF54H20 DFU architecture.
Enabled support for the DFU module over the Configuration channel in all configurations of the nrf54h20dk/nrf54h20/cpuapp board target.
Ref: NCSDK-34151