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

FW: Force the CPU to hang on errors #168

Merged
merged 2 commits into from
Mar 18, 2024
Merged

FW: Force the CPU to hang on errors #168

merged 2 commits into from
Mar 18, 2024

Conversation

dehanj
Copy link
Member

@dehanj dehanj commented Mar 14, 2024

Instead of using a software loop on errors, we halt the CPU.

For the users it is no difference, the LED will be flashed RED by hw instead.

@dehanj dehanj linked an issue Mar 14, 2024 that may be closed by this pull request
@dehanj dehanj requested a review from mchack-work March 14, 2024 14:12
Since we now use assert() and feed the CPU an unimplemented
instruction we have no need for this.
Copy link
Member

@mchack-work mchack-work left a comment

Choose a reason for hiding this comment

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

I removed the unused function forever_redflash(). Doesn't change the digest since it was unused anyway.

Tested on real hardware by running a signer, signing and verifying.

Tested on real hw by sending garbage that tickled the assert.

Everything looks good. Approving.

@mchack-work mchack-work merged commit e2bd38c into main Mar 18, 2024
1 check passed
@mchack-work mchack-work deleted the 112-force-cpu-hang branch March 18, 2024 15:41
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.

Force CPU-hang on errors in FW
2 participants