-
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
tests: add tests for KMU and keys provisioning #18456
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 843da3edd796a38053cb5e53abe5bfa5b0293b5f more detailssdk-nrf:
Github labels
List of changed files detected by CI (20)
Outputs:ToolchainVersion: b44b7a08c9 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
31496e6
to
8189f9c
Compare
8189f9c
to
b68d618
Compare
failed after rebasing to #18366,
|
Hey, can you try to rebase on this and see if it fixes your build issue? |
works with that change, thank you! |
Add two test applications with test scenarios automated with pytest. Keys are provisioned with the `west ncs-provision` command. The tests verify if the applications boot and if the keys are correct. Signed-off-by: Grzegorz Chwierut <[email protected]>
b68d618
to
843da3e
Compare
Add two test applications with test scenarios automated with pytest.
Frist: verify_west_ncs_provision - application with hardcoded keys only to check if command
west ncs-provission
writes proper keys.Second: hello_for_kmu - hello_world based app with MCUboot, keys are uploaded with west command and application is flashed. Checked if app is booted when using correct keys and not booted with wrong keys.
To test one can use command:
${ZEPHYR_BASE}/scripts/twister --device-testing -p nrf54l15dk/nrf54l15/cpuapp --device-serial /dev/ttyACM1 --west-flash="--erase" -T tests/subsys/kmu -vv --no-clean