6. Event Notification > Event Summary
122
Tsi578 User Manual
June 6, 2016
Integrated Device Technology
www.idt.com
6.2
Event Summary
describes all the events that can be raised within the Tsi578 and whether these events generate
a interrupt, a port-write, or both.
Table 13: Tsi578 Events
Event Name
(Status Bit)
Type
Description
Interface
Where
Event
Occurs
Can
Generate
Interrupt
Can
Generate
Port-write
Max Retry
Occurred
Error
This event occurs when a port’s retry counter reaches the
configured retry counter threshold. The same retry counter
is incremented for retries of all packets (it is not a
per-packet retry counter).
The status of this event is contained in the
IMP_SPEC_ERR bit in the
and the MAX_RETRY bit in the
.
The Retry Counter is reset in the following situations:
• Counter reaches threshold
• A packet acceptance is received
• A packet non-acceptance is received
RapidIO Yes
Yes
Illegal
Transaction
Error
This event occurs when an inbound port receives a
transaction with one of the following errors:
• Unmapped entry in LUT
• Reserved TT field value for data packet or maintenance
packet with a hop count not equal to zero
The status of this event is contained in the
IMP_SPEC_ERR bit in the
and the ILL_TRANS_ERR bit in the
.
RapidIO Yes
Yes
LUT Parity
Error
Error
This event occurs when a parity error is detected when a
port is performing a destination ID lookup (refer to
Port x LUT Parity Error Info CSR”
The status of this event is contained in the
IMP_SPEC_ERR bit in the
and the LUT_PAR_ERR bit in the
“RapidIO Port x Interrupt Status Register” on page 326
RapidIO Yes
Yes
Error Rate
Failed
Threshold
Reached
Error
This event occurs when the error rate counter in the
“RapidIO Port x Error Rate CSR” on page 304
reaches the
selected Link-Failed threshold found in the
Error Rate Threshold CSR” on page 306.
For more detail
about the Error Rate reporting mechanism, see
.
The status of this event is contained in the OUTPUT_FAIL
bit in the
“RapidIO Port x Error and Status CSR”
.
RapidIO Yes
Yes