You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working with integrating Caliptra for a number of months now and only today realized that there are two instances of the SHA512 core in the logic. It would be great if the hardware documentation could be updated to state this clearly, as it required delving into the RTL for me to confirm my suspicions (something an integrator of Caliptra ideally should not have to do). In addition, it is imperative that those integrating Caliptra know how many SHA instances exist within it to meet FIPS 140-3 requirements.
Add a mention of a SHA hardware instance that is leveraged by the API, noting that it is a separate instance that uses the same core as the SHA512 accelerator in the cryptographic subsystem w/o some of the surrounding logic.
Update Figure 8 to have a SHA512 accelerator within the SoC interface. Again, it is important that integrators know the number of SHA blocks within Caliptra from the onset, so keeping the initial spec that they would read up to date is necessary.
The text was updated successfully, but these errors were encountered:
I've been working with integrating Caliptra for a number of months now and only today realized that there are two instances of the SHA512 core in the logic. It would be great if the hardware documentation could be updated to state this clearly, as it required delving into the RTL for me to confirm my suspicions (something an integrator of Caliptra ideally should not have to do). In addition, it is imperative that those integrating Caliptra know how many SHA instances exist within it to meet FIPS 140-3 requirements.
Here are my suggested changes:
The text was updated successfully, but these errors were encountered: