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

[fi] Reset OT on CW310 #249

Closed
nasahlpa opened this issue Dec 8, 2023 · 0 comments · Fixed by #260
Closed

[fi] Reset OT on CW310 #249

nasahlpa opened this issue Dec 8, 2023 · 0 comments · Fixed by #260
Assignees

Comments

@nasahlpa
Copy link
Member

nasahlpa commented Dec 8, 2023

Currently, when OT is not responding, we re-program the bitstream on CW310. As this takes some time, we could:

  • Check whether the bitstream on CW310 is still ok (CRC check)
  • And only reset OT if it is OK
@nasahlpa nasahlpa self-assigned this Dec 8, 2023
nasahlpa added a commit to nasahlpa/ot-sca that referenced this issue Dec 14, 2023
Previously, we re-programmed the FPGA when a FI crashed OpenTitan
running on CW310. As this took quite some time, we now read the
INITB pin - this pin returns false or none when the FPGA is not
programmed or the bitstream CRC does not match.
In this case, we are re-programming the bistream.

When the bitstream is OK, we simply reset OpenTitan by using
the power on reset pin (POR_N is mapped to USB_A14 on CW310).

This significantly increases the FI rate.

Closes lowRISC#249.

Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa added a commit that referenced this issue Dec 18, 2023
Previously, we re-programmed the FPGA when a FI crashed OpenTitan
running on CW310. As this took quite some time, we now read the
INITB pin - this pin returns false or none when the FPGA is not
programmed or the bitstream CRC does not match.
In this case, we are re-programming the bistream.

When the bitstream is OK, we simply reset OpenTitan by using
the power on reset pin (POR_N is mapped to USB_A14 on CW310).

This significantly increases the FI rate.

Closes #249.

Signed-off-by: Pascal Nasahl <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant