Skip to content
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

[fuse_ctrl, integration] Fix fuse_ctrl background checks init error #90

Merged

Conversation

andrea-caforio
Copy link
Contributor

@andrea-caforio andrea-caforio commented Feb 10, 2025

This reinstates the background checks in the fuse_ctrl provisioning smoke tests by fixing the order of registers write to enable the periodic integrity and consistency checks.

The CHECK_TIMEOUT register needs to be written before INTEGRITY_CHECK_PERIOD and CONSISTENCY_CHECK_PERIOD or an unintended timeout error is triggered.

Related OpenTitan PR: lowRISC/opentitan#26188

This reinstates the background checks in the fuse_ctrl provisioning
smoke tests by fixing the order of registers write to enable the
periodic integrity and consistency checks.

The CHECK_TIMEOUT register needs to be written before
INTEGRITY_CHECK_PERIOD and CONSISTENCY_CHECK_PERIOD or an unintended
timeout error is triggered.

Signed-off-by: Andrea Caforio <[email protected]>
Copy link

linux-foundation-easycla bot commented Feb 10, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

In the fuse_ctrl an integrity/consistency check is triggered as soon as
either the `INTEGRITY_CHECK_PERIOD` or `CONSISTENCY_CHECK_PERIOD`
registers are written. The following check, depending on the number of
instantiated partitions, may last for hundreds of cycles. Writing a
value into the `CHECK_TIMEOUT` register while the checks are still
ongoing will trigger an unnecessary timeout error that transfers the
fuse_ctlr into an error state.

This commit adjusts the documentation to make it clear that the
`CHECK_TIMEOUT` register should be written before
`INTEGRITY_CHECK_PERIOD` and `CONSISTENCY_CHECK_PERIOD`. Following the
Programmer's Guide verbatim before may lead to implementations that
trigger this unintended error condition.

Signed-off-by: Andrea Caforio <[email protected]>
@ekarabu ekarabu self-requested a review February 20, 2025 15:21
@ekarabu ekarabu merged commit 228dd26 into chipsalliance:main Feb 20, 2025
1 check 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.

2 participants