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

Export ECC violation signals to the top level as status outputs #147

Closed
calebofearth opened this issue Dec 11, 2023 · 0 comments · Fixed by #151
Closed

Export ECC violation signals to the top level as status outputs #147

calebofearth opened this issue Dec 11, 2023 · 0 comments · Fixed by #151

Comments

@calebofearth
Copy link

As was done in the Caliptra VeeR core instance (here), it is useful to export SRAM ECC status signals so that integrators can make use of the status for RAS features. In some cases, ECC errors may occur that render the VeeR core unable to execute recovery code (such as code that reads internal mcause/mscause registers). Some ECC errors are not reported explicitly (such as an ICCM ECC error during an LSU read), so there is no way to diagnose corrupted bits as the root cause of the issue in lab debug.

tmichalak added a commit that referenced this issue Jan 4, 2024
Export ICCM/DCCM ECC error signals
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 a pull request may close this issue.

1 participant