Arm
®
CoreLink™ GIC-600AE Generic Interrupt Controller
Technical Reference Manual
Document ID: 101206_0003_04_en
Issue: 04
Functional Safety
messages. The error recovery software does not have the SM information from the remote GIC
block that had this fault, so it must perform error recovery by resetting that remote GIC block and
the AXI4-Stream interconnect components.
6.2.5.1 Enabling or disabling a Safety Mechanism
All Safety Mechanisms are enabled on reset, except for the MBIST REQ Safety Mechanism.
To enable or disable a Safety Mechanism, write to the FMU_SMEN register. FMU_SMEN.BLK
selects the GIC block, and FMU_SMEN.SMID selects the specific Safety Mechanism in the GIC
block to be enabled or disabled.
The following P-Channel and Q-Channel SMs cannot be disabled through the FMU_SMEN register:
•
GICD SMs 12, 13, and 31
•
PPI SM 4
•
ITS SM 5
•
SPI SM 3
These SMs must be disabled using design time parameters or tie-offs. For more information, see
6.10 P-Channel and Q-Channel protection on page 232.
MBIST REQ SMs are not enabled on reset, and must be enabled after reset. For more information,
see 6.13 DFT protection on page 247.
6.2.5.2 Injecting an error in a Safety Mechanism
To inject an error into a Safety Mechanism, write to the FMU_SMINJERR register.
The FMU_SMINJERR.BLK field specifies the GIC block, and the FMU_SMINJERR.SMID field
specifies the SM into which to inject the error.
FMU_STATUS.idle protects the FMU_SMINJERR register. See FMU idle on page 208.
This method injects only one error. No clearing of error injection is required.
By introducing error through the software, the error injection feature can be used to test the
software error recovery handler.
The ClkGate override Safety Mechanisms do not support error injection.
Copyright © 2018–2020, 2022 Arm Limited (or its affiliates). All rights reserved.
Non-Confidential
Page 202 of 268
To Next Page
Loading...
Need help?
General
