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
Until now, a single instance of the register file containing 32-bit
data words and 7-bit ECC tags was used. While the input of the
register file was driven by the main core, the output of the
register file was distributed to the main and the shadow core.
In this commit, we are splitting up the data and ECC parts into two
different register file instances:
- (1) This instance is driven by the main core and only operates on
the 32-bit data words. The outputs (32-bit data words) are
forwarded to the main and the shadow core.
- (2) This instance is driven by the shadow core and only operates
on the 7-bit ECC words. The 7-bit ECC output is combined with
the delayed 32-bit data output of the (1) RF instance. The
shadow core uses ECC checkers to check if data and ECC (a)
match and (b) are not manipulated using FI.
This helps us to save around 6 kGE of area.
Signed-off-by: Pascal Nasahl <nasahlpa@lowrisc.org>
* ``cp_pc_mismatch_err`` - PC mismatch error seen.
342
344
343
345
The :ref:`security features Ibex implements <security>` are given specific security countermeasure names in OpenTitan (see 'Security Countermeasures' in the `Comportability Definition and Specification <https://opentitan.org/book/doc/contributing/hw/comportability/index.html#security-countermeasures>`_ documentation section).
@@ -358,6 +360,8 @@ The mapping between security countermeasures and coverpoints that demonstrate it
0 commit comments