-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
applications: nrf_desktop: nRF54L - Mcuboot using HW crypto and KMU #19035
base: main
Are you sure you want to change the base?
Conversation
MCUboot memory footprint estimate (using LTO and applied my CRACEN PSA driver optimizations):
|
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: e05a2609f3539ce62d8959eb75a8376495d42e87 more detailssdk-nrf:
Github labels
List of changed files detected by CI (4)
Outputs:ToolchainVersion: b77d8c1312 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
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.
shouldn't we align all build types for the nRF54L15 board target with this new configuration?
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.
Eventually we should. The PR is a draft for @nvlsianpu to let him see our MCUboot configuration with lower memory footprint
@@ -30,6 +27,12 @@ CONFIG_UART_CONSOLE=n | |||
CONFIG_PRINTK=n | |||
CONFIG_USE_SEGGER_RTT=n | |||
|
|||
CONFIG_PSA_USE_CRACEN_CIPHER_DRIVER=n | |||
CONFIG_PSA_USE_CRACEN_AEAD_DRIVER=n | |||
CONFIG_PSA_USE_CRACEN_HASH_DRIVER=n |
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.
Ah, OK the driver only supports sha256, so it is useless with sha512 requirements for ed25519
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.
Is the SHA512 needed for pure ed25519?
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.
OK, so the comment around the HASH driver is misleading because it does not list the sha512.
The SHA512 is needed internally for pure, so it may not require driver.
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.
A am now building app with mcuboot gradually removing the kconfigs listed above and checking whether it still works.
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.
So OK, HASH needs to stay with non-pure
Change increases partition size of MCUboot bootloader. Hardware crypto increases memory footprint of the bootloader. Jira: NCSDK-26885 Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
Change switches to using pure ED25519 signature and hardware crypto. Jira: NCSDK-26885 Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
5df4e74
to
24d943d
Compare
Rebased onto main |
I have implemented some of the Kconfig cut-outs here: #19148 |
Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
24d943d
to
e05a260
Compare
Draft of MCUboot using HW crypto and KMU. MCUboot XiP no revert. Applied some memory footprint optimizations for CRACEN PSA driver.