Repository navigation
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
veer_mcireads, 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_INFOandFW_ERROR_FATALand 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.