SPRUJ55D September 2023 – July 2025 AM263P2 , AM263P2-Q1 , AM263P4 , AM263P4-Q1
The RDC produces one hardware event output which is active high level and active high pulse.
All of the error tracking/diagnostic events can get mapped to generate an event to notify the host an error occurred. The software can emulate a hardware event to verify the full path does not have a fault; this is important for safety.
There are 4 MMRs for SW to interact with:
The reading of IRQSTATUS_RAW_SYS_x shows the status of the RAW event, if set it is active, if cleared it is inactive. Even if set, the external event can be deasserted because it is not enabled along with corresponding event in the IRQSTATUS_SYS_x status(post mask/enable). The writing of IRQSTATUS_RAW_SYS_x allows software emulate emulate a hardware event, but the software must first enable that event by writing to IRQENABLE_SET_SYS_x.
The writing of IRQENABLE_SET_SYS_x is required to enable the hardware event to be asserted.
The reading of IRQSTATUS_SYS_x shows which hardware events are active. It requires the event to get enabled via IRQENABLE_SET_SYS and that the hardware event did occur. To clear the hardware event, software must write 1 to clear that bit in the IRQSTATUS_SYS_x.
The writing of IRQENABLE_CLR_SYS_x allows the software to disable hardware events.
The typical software programming model:
The hardware level event output remains asserted as long as one or more events are active.