SPRUJ55D September 2023 – July 2025 AM263P2 , AM263P2-Q1 , AM263P4 , AM263P4-Q1
The Configuration Error Interrupt indicates that there is an inconsistency in the configuration of one (or more) Error Group N MMRs. In such inconsistencies, the internal copies of any of the MMRs caused by a SER associated with Error Group N, the corresponding raw status will be set in the Config Error Interrupt Raw Status/Set Register (Base Address + 0x10). If the corresponding bit is enabled, a Configuration Error Interrupt will be triggered.
The Configuration Error Interrupt is not enabled by default and it should be enabled by the processor by writing:
Write the respective Error group bit which needs to be monitored for Configuration Error
Config Error Interrupt Enabled Set Register (Base Address + 0x18)
Enable the Configuration Error Interrupt in VIM for CPU which is configuring the ESM
When a Configuration Error Interrupt is received, the acting processor should follow these steps:
Read the Config Error Interrupt Enabled Status/Clear Register (Base Address + 0x14) to determine which Group as a configuration error
Write the correct values to the following registers
Error Group N Interrupt Enabled Set Register (Base Address + 0x400 + N*0x20 + 0x08)
Error Group N Interrupt Enabled Clear Register (Base Address + 0x400 + N*0x20 + 0x0C)
Error Group N Interrupt Priority Register (Base Address + 0x400 + N*0x20 + 0x10)
Error Group N Error Pin Influence Set Register (Base Address + 0x400 + N*0x20 + 0x14)
Error Group N Error Pin Influence Clear Register (Base Address + 0x400 + N*0x20 + 0x18)
The raw status of any pending interrupts may be inconsistent. Servicing the interrupt will return it to consistency (Error Group N Event Raw Status/Set Register (Base Address + 0x400 + N*0x20 + 0x00))
Write a 1 to the appropriate bits in the Config Error Interrupt Enabled Status/Clear Register (Base Address + 0x14)
This will clear the raw status
If the error event is still asserted (or re-asserted) the raw status will be set back to 1
If there are no additional errors, the level interrupt will go low
If there are additional Configuration Error enabled error events pending, then a new pulse will be generated and the level interrupt will remain asserted
If there are no additional Low Priority enabled error events pending, there will be no new pulse