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
Currently, a single bit controls whether the outputs of the main and shadow Ibex core are compared, i.e., a single bit is responsible for enabling / disabling the lockstep:
I agree, something like a MuBi4 or MuBi8 would be adequate for this enablement... I believe other places use MuBi8 for CSR-based enablement, so we could go with that.
Currently, a single bit controls whether the outputs of the main and shadow Ibex core are compared, i.e., a single bit is responsible for enabling / disabling the lockstep:
opentitan/hw/vendor/lowrisc_ibex/rtl/ibex_lockstep.sv
Line 461 in 0424151
Hence, a permanent stuck-at 0 fault could allow an adversary to reduce the FI resilience of Ibex.
I would suggest extending this signal to a multi-bit encoded signal.
FYI @vogelpi @msfschaffner @johannheyszl.
The text was updated successfully, but these errors were encountered: