[RTL+DOC] [2.1] Expose life-cycle state valid and volatile-unlock signals at caliptra_ss_top #966
Conversation
This file contains hidden or 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
…nal' with updated timestamp and hash after successful run
calebofearth
approved these changes
Dec 1, 2025
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.
This PR exposes fuse- and LC-derived life-cycle signals (caliptra_ss_life_cycle_steady_state_o, caliptra_ss_otp_state_valid_o, and caliptra_ss_volatile_raw_unlock_success_o) at the caliptra_ss_top level.
It also updates the integration spec to describe how SoC integrators should use these signals alongside the LC_STATE register, including behavior on fuse errors/escalation and how volatile-unlock transitions are indicated.
Resolving #963