Renesas IDT Tsi574, User Manual

Page: 124 / 514

6. Event Notification > Error Rate Thresholds 124
Tsi574 User Manual
June 6, 2016
Integrated Device Technology
www.idt.com
6.3 Error Rate Thresholds
There are two event thresholds in the Tsi574: the Error Rate Failed Threshold Reached and the Error
Rate Degraded Threshold Reached. These events notify the system that errors are occurring on a
RapidIO interface at a rate that requires special attention.
The error rate detection threshold function works as follows:
• Each RapidIO port maintains a single error counter that is incremented each time one of the
RapidIO errors is encountered (see
Table 13 )
— The port’s hardware can be configured to automatically decrement this counter. The rate at
which the counter is decremented is configurable through the “RapidIO Port x Error Rate
CSR” on page 296 .
• There are two thresholds configured per port on the Tsi574: Error Rate Failed Threshold Reached
and the Error Rate Degraded Threshold Reached. These thresholds specify the counter level at
which the port is considered either degraded or failed.
Control
Symbol Not
Accepted Error This event is raised when a RapidIO port receives a
“Packet-Not-Accepted” Control Symbol.
The status of this event is contained in the CS_NOT_ACC
bit of the
“RapidIO Port x Error Detect CSR” on page 286
RapidIO Yes Yes
1
Packet CRC
Error Error This event is raised when a RapidIO port receives a packet
with a CRC error.
The status of this event is contained in the PKT_CRC_ERR
bit of the
“RapidIO Port x Error Detect CSR” on page 286
RapidIO Yes Yes
1
I
2
C Event Status
and
Error This event is raised when the I
2
C block has an internal
interrupt.
The status of this event is contained in the I2C bit in the
“Global Interrupt Status Register” on page 377 , which is a
logical OR of all bits in “I
2
C Interrupt Status Register” when
the corresponding bits in “I
2
C Interrupt Enable Register”
are enabled.
I
2
C Yes No
Multicast
Latency
Exceeded Error This event occurs when a multicast request for a particular
port cannot be transmitted in the time specified by the RIO
Multicast Latency Timer. This results in the MC_LAT being
set in the Global Interrupt Status Register. The port does
not receive multicast requests unless or until the
appropriate error bit in the
“RapidIO Multicast Maximum
Latency Counter CSR” on page 384 is cleared.
Multicast Yes Yes
For error events related to Maintenance Packets with hop count =0, see Table 3
a.Part of Error Rate Failed/ Degraded Threshold counter
Table 13: Tsi574 Events (Continued)
Event Name
(Status Bit) Type Description
Interface
Where
Event
Occurs
Can
Generate
Interrupt
Can
Generate
Port-write