The following steps are to be
performed by user depending on the error handling and condition control:
- Configure the error event to
affect either low-priority or high-priority interrupt for respective ESM
instance. Error events that cause CPU to go into fault state must be
configured to high-priority interrupt to trigger NMI to respective CPU. For
System ESM instance, high-priority interrupt priority is not
applicable.
- Enable Interrupt generation
for respective error event using Interrupt Enable Set Register. Based on
Step1, the enabled interrupt event when active triggers selected priority
error event.
- Configure Global Enable to
enable all interrupts, this is interrupt mask for all error events.
- If the error event needs to
affect the critical-priority interrupt, set the respective event in the
Critical Priority Interrupt Influence Set Register.
- In Step 1 if the interrupt
priority is set to trigger a high-priority interrupt, watchdog on
high-priority interrupt is enabled at start-up with tie-off unless the user
wants to disable.
- Optionally Lock and Commit
the configurations.
- For System ESM only: If error
needs to be enabled to influence error pin, enable the event using Error Pin
Influence Set Register. Error Pin configurations are only applicable to
System ESM instance.
- For System ESM only: After
Step 7, Enable the Error Pin Monitor using Error Pin Monitor Config Register
and enable Error Pin Monitor Interrupt using the Error Pin Monitor Interrupt
Status/Set Register.
The previous steps can also be
visualized with Figure 7-15 and Figure 7-16. These views
show how each individual error event represented by Error Event_j (where j is the
global error event number from 0 to 255) as an input to the ESM instance can be
configured to then output selected error response to the device.