Skip to content

Conversation

AlexJones0
Copy link

This PR introduces an optional property that provides a mechanism to disable the "all zero/one` data validity check when loading flash seeds as part of keymgr advancement.

The motivation is to support wider usage with unprovisioned flash information pages, which will not have these pages initialized and thus will fail keymgr advancement due to the current lack of flash scrambling.

Copy link

@jwnrt jwnrt left a comment

Choose a reason for hiding this comment

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

Please could you document the property in earlgrey.md (or a new keymgr.md)? I'd like it to be clear that we can drop this when we have scrambling (and correct info pages)

@AlexJones0 AlexJones0 force-pushed the keymgr_flash_check_prop branch 3 times, most recently from 1f82b5c to b5a2150 Compare October 7, 2025 10:56
@AlexJones0 AlexJones0 force-pushed the keymgr_flash_check_prop branch from b5a2150 to edcb5f5 Compare October 7, 2025 10:57
Support a wider range of use cases with unprovisioned flash via an
optional property that makes minimal changes to the code.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
@AlexJones0 AlexJones0 force-pushed the keymgr_flash_check_prop branch from edcb5f5 to cc2e29e Compare October 7, 2025 10:59
Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
@AlexJones0 AlexJones0 force-pushed the keymgr_flash_check_prop branch from cc2e29e to 137beb6 Compare October 7, 2025 11:00
@AlexJones0 AlexJones0 merged commit ed46779 into lowRISC:ot-9.2.0 Oct 7, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants