Motorola MCF5282 ユーザーズマニュアル
17-24
MCF5282 User’s Manual
MOTOROLA
Programming Model
in the network or transceiver are HBERR, BABR, BABT, LC and RL. Interrupts resulting
from internal errors are HBERR and UN.
from internal errors are HBERR and UN.
Some of the error interrupts are independently counted in the MIB block counters. Software
may choose to mask off these interrupts since these errors will be visible to network
management via the MIB counters.
may choose to mask off these interrupts since these errors will be visible to network
management via the MIB counters.
• HBERR - IEEE_T_SQE
• BABR - RMON_R_OVERSIZE (good CRC), RMON_R_JAB (bad CRC)
• BABT - RMON_T_OVERSIZE (good CRC), RMON_T_JAB (bad CRC)
• LATE_COL - IEEE_T_LCOL
• COL_RETRY_LIM - IEEE_T_EXCOL
• XFIFO_UN - IEEE_T_MACERR
• BABR - RMON_R_OVERSIZE (good CRC), RMON_R_JAB (bad CRC)
• BABT - RMON_T_OVERSIZE (good CRC), RMON_T_JAB (bad CRC)
• LATE_COL - IEEE_T_LCOL
• COL_RETRY_LIM - IEEE_T_EXCOL
• XFIFO_UN - IEEE_T_MACERR
31
30
29
28
27
26
25
24
23
22
21
20
19
18
16
Field HBERR BABR BABT GRA TXF TXB RXF RXB MII EBERR LC
RL
UN
—
Reset
0000_0000_0000_0000
R/W
R/W
15
0
Field
—
Reset
0000_0000_0000_0000
R/W
R/W
Address
IPSBAR + 0x1004
Figure 17-4. Ethernet Interrupt Event
Register (EIR)
Table 17-12. EIR Field Descriptions
Bits
Name
Description
31
HBERR
Heartbeat error. This interrupt indicates that HBC is set in the TCR
register and that the COL input was not asserted within the
Heartbeat window following a transmission.
register and that the COL input was not asserted within the
Heartbeat window following a transmission.
30
BABR
Babbling receive error. This bit indicates a frame was received with
length in excess of RCR[MAX_FL] bytes.
length in excess of RCR[MAX_FL] bytes.
29
BABT
Babbling transmit error. This bit indicates that the transmitted
frame length has exceeded RCR[MAX_FL] bytes. This condition is
usually caused by a frame that is too long being placed into the
transmit data buffer(s). Truncation does not occur.
frame length has exceeded RCR[MAX_FL] bytes. This condition is
usually caused by a frame that is too long being placed into the
transmit data buffer(s). Truncation does not occur.