Skip to content

veer: Handle fatal hardware errors of the MCI - #748

Open
swenson wants to merge 1 commit into
OpenPRoT:mainfrom
swenson:claude/caliptra-mci-veer-errors
Open

swenson wants to merge 1 commit into
OpenPRoT:mainfrom
swenson:claude/caliptra-mci-veer-errors

Conversation

@swenson

@swenson swenson commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

veer_mci reads, acknowledges and triggers the pending aggregated errors from the SoC, enables the MCI interrupt for a set of events from the MCI's four groups of events, and reads the errors in the MCI's records.

The runtime image logs the recorded errors when it starts. On the MCI's collision or internal error event, or an aggregated fatal error of the Caliptra core or the MCU's DCCM, its interrupt handler writes FW_EXTENDED_ERROR_INFO and FW_ERROR_FATAL and stops the MCU.

docs/src/design/caliptra-mcu/ is added and lists the events and errors of the MCI, their causes, and what the runtime image does about each.

The host tests pass. The on-device test and the runtime test pass on the emulator and on the VCK190 FPGA. The emulator does not model the aggregated errors (see chipsalliance/caliptra-mcu-sw#2378), so the on-device test triggers them only on the FPGA.

The MCU mailbox driver comes next.

veer_mci reads, acknowledges and triggers the pending aggregated errors
from the SoC, enables the MCI interrupt for a set of events from the
MCI's four groups of events, and reads the errors in the MCI's records.

The runtime image logs the recorded errors when it starts. On the MCI's
collision or internal error event, or an aggregated fatal error of the
Caliptra core or the MCU's DCCM, its interrupt handler writes
FW_EXTENDED_ERROR_INFO and FW_ERROR_FATAL and stops the MCU.

docs/src/design/caliptra-mcu/ lists the events and errors of the MCI,
their causes, and what the runtime image does about each.

The host tests pass. The on-device test and the runtime test pass on
the emulator and on the VCK190 FPGA. The emulator does not model the
aggregated errors, so the on-device test triggers them only on the
FPGA.

The MCU mailbox driver comes next.

Assisted-by: Claude:claude-fable-5-2

This branch has not been deployed

No deployments
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.

1 participant