Intel IXP400 manual Data Abort followed by Unrelated Parity Error Notification

Intel® IXP400 Software

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

Figure 79. Data Abort followed by Unrelated Parity Error Notification

Data Abort		IxParityENAcc		Client Callback
	IxParityENAccParityErrorContextGet(*pecMessage)		Gets Parity	{Both multi and single-bit
	IX_PARITYENACC_SUCCESS		Interrupt Status:	parity error on the MCU
				detected due to non XScale
			Source = Multi-bit	access when Data Abort
			Address = [Multi-bit]	occurred.}

ExamineParityErrorSource

Data abort ignores the non related parity error since the multi-bit parity error is due to access by masters other than XScale.

NOTE: Software applied the priority to select the multi-bit parity interrupt first.

(*IxParityENAccCallback)()	Interrupt-1
IxParityENAccParityErrorContextGet(*pecMessage)	Gets Parity
IX_PARITYENACC_SUCCESS	Interrupt Status:
IxParityENAccParityErrorInterruptClear(*pecMessage)	Source = Multi-bit
IX_PARITYENACC_SUCCESS	Address = [Multi-bit]

(*IxParityENAccCallback)()	Interrupt-2
IxParityENAccParityErrorContextGet(*pecMessage)	Gets Parity
IX_PARITYENACC_SUCCESS	Interrupt Status:
IxParityENAccParityErrorInterruptClear(*pecMessage)	Source = Single-bit
IX_PARITYENACC_SUCCESS	Address = [Single-bit]

B4381-01

Figure 80. Unrelated Parity Error Followed by Data Abort

Data Abort

IxParityENAcc

Client Callback

IxParityENAccDAParityErrorContextGet(*pecMessage)

IX_PARITYENACC_SUCCESS

ExamineParityErrorSource

Data abort ignores the non related parity error.

(*IxParityENAccCallback )()
Gets Parity	{Non-MCU (E .g.,NPE) parity
Interrupt Status:
	error detected when Data
Source = NPE	Abort occurred.}
Address = [X]
IxParityENAccParityErrorContextGet(*pecMessage)
IX_PARITYENACC_SUCCESS
IxParityENAccParityErrorInterruptClear(*pecMessage)
IX_PARITYENACC_SUCCESS

DelayMaxDATriggerTime

Gets Parity

Interrupt Status:

Source = NPE

Address = [X]

B4386-01

In order to avoid a race condition between the data abort handler and the parity error callback, delay has been introduced in the MCU parity event interrupt service routine of the access-layer component. This allows the data abort handler to complete prior to the interrupt service routine returning the parity context information.

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