Intel IXP400 manual Data Abort Caused by Parity Error

Intel® IXP400 Software

Access-Layer Components: Parity Error Notifier (IxParityENAcc) API

Figure 81. Data Abort Caused by Parity Error

Data Abort	IxParityENAcc		Client Callback
		Gets Parity
	IxParityENAccParityErrorContextGet(*pecMessage)	Interrupt Status:
	IX_PARITYENACC_SUCCESS	Source = Multi-bit
	IxParityENAccParityErrorInterruptClear(*pecMessage)	Address = [Multi-bit]	{Multi-bit parity error
			on MCU detected when
		Clear Parity
	IX_PARITYENACC_SUCCESS		Data Abort occurred.}
		Interrupt:
		Source = Multi-bit
		Address = [Multi-bit]
			Parity Interrupt will
			not fire.
			B4382-01

Figure 82. Parity Error Notification Followed by Related Data Abort

Data Abort	IxParityENAcc		Client Callback
		(*IxParityENAccCallback )()
		Gets Parity	DelayMaxDATriggerTime
IxParityENAccDAParityErrorContextGet(*pecMessage)
		Interrupt Status:
	IX_PARITYENACC_SUCCESS	Source = Multi-bit
IxParityENAccDAParityErrorInterruptClear(*pecMessage)		Address = [Multi-bit]	{Multi-bit parity error
		Clear Parity	on MCU observed when
	IX_PARITYENACC_SUCCESS		Data Abort occurred.}
		Interrupt:
		Source = Multi-bit
		Address = [Multi-bit]
		IxParityENAccParityErrorContextGet(*pecMessage)
		IX_PARITYENACC_NOPARITY
			B4387-01

This scenario shown in Figure 83 can occur because the order in which the interrupts are triggered for a parity error and a related data abort are not guaranteed.

Programmer’s Guide	IXP400 Software Version 2.0	April 2005
	Document Number: 252539, Revision: 007	245