Functional safety requirements for application software
Safety Manual for MPC5777M, Rev. 1.1
NXP Semiconductors 41
3.3.14 Detection of unwanted resets
MC_RGM allows triggering individual resets for MCU modules (for example, using the Peripheral Reset
Registers (RGM_PRST[n]). This can be prohibited by using the access control mechanisms of the
MPC5777M such as the MPU or PAC. In case those are not used, and also to detect spurious resets caused
by SEE, the following describes how such spurious resets can be detected.
Assumption: [SCG18.150]To detect unwanted reset of these modules, software and hardware counter
measures can be applied. Table 1 summarizes these counter measures. [end]
This is a brief description of each of the column headings in Table 1:
• Receiving module – This module is reset.
• Software Control – The register (or registers) which can reset the specified “Receiving Module”.
• Detection – The effect of the unwanted reset of the specified “Receiving Module” and shows some
mechanisms that can detect the module where the event occurred. If multiple mechanisms are
listed, the software can choose the mechanism that better fits its need (unless explicitly specified).
• Software action required – Additional software mechanism, with respect to the application
software, required to detect an unwanted reset of the specified “Receiving Module” (for example,
polling coming from configuration registers).
To Next Page
Loading...
Need help?
General
