Revision 0.2
March 10, 2000
-
25-
Register Descriptions
Technologies, Inc.
WeConnect
Table 3. Packet Event Codes
Code
00/10
Event Tcode Error
Name
DMA
AT, AR,
IT, IR, IT
Meaning
A bad Tcode is associated with this packet. The packet was flushed.
01/11
Event Short
Packet
The received data length was less than the packet’s data length (IR packet-per-buffer
mode only).
The received data length was greater than the packet’s data length (IR packet-per-
buffer mode only).
A subaction gap was detected before an ack arrived
An underrun occurred on the corresponding FIFO and the packet was truncated.
A receive FIFO overflowed during the reception of an isochronous packet.
An unrecoverable error occurred while the Host Controller was reading a descriptor
block.
An error occurred while the Host Controller was attempting to read from host memory
in the data stage of descriptor processing.
Event Data Write
AR, IR, IT An error occurred while the Host Controller was attempting to write to host memory
in the data stage of descriptor processing.
Event Bus Reset
AR
Identifies a PHY packet in the receive buffer as being the synthesized bus reset packet
Event Timeout
AT
Indicates that the asynchronous transmit response packet expired and was not
transmitted
Event Tcode Error
AT
A bad Tcode is associated with this packet. The packet was flushed.
Reserved
02/12
Event Long Packet
IR
03/13
Event Missing Ack
04/14
Event Underrun
05/15
Event Overrun
06/16
Event Descriptor
AT
AT, IT
IR
AT, AR,
IT, IR
AT, IT
Read
07/17
Event Data Read
08/18
09/19
0A/1A
0B
0C-
0D/1B
-1D
0E/1E
Event Unknown
AT, AR,
IT, IR
AT
An error condition has occurred that cannot be represented by any other defined event
codes
Sent by the link side of the output FIFO when asynchronous packets are being flushed
due to a bus reset
The destination node has successfully accepted the packet. If the packet was a request
subaction, the destination node has successfully completed the transaction and no
response subaction shall follow.
The ack / err code for transmitted PHY, isochronous and broadcast packets, none of
which yield an ack code, will be set by hardware to “Ack Complete” unless an “Event
Underrun” or “Event Data Read” occurs.
The destination node has successfully accepted the packet. If the packet was a request
subaction, a response subaction will follow at a later time. This code is not returned
for a response subaction.
0F/1F
Event Flushed
11
Ack Complete
AT, AR,
IT, IR
12
Ack Pending
AT, AR
13
14
Reserved
Ack Busy X
AT
The packet could not be accepted after max “ATretries” attempts and the last ack
received was “Ack Busy X.”
The packet could not be accepted after max “ATretries” attempts and the last ack
received was “Ack Busy A." OHCI does not support the dual phase retry protocol for
transmitted packets, so this ack should not be received.
The packet could not be accepted after max “ATretries” attempts and the last ack
received was “Ack Busy B" (see note for “Ack Busy A”).
15
Ack Busy A
AT
16
Ack Busy B
AT
17-1C
1D
Reserved
Ack Data Error
AT, IR
The destination node could not accept the block packet because the data field failed
the CRC check or because the length of the data block payload did not match the
length contained in the “Data Length” field. This code is not returned for any packet
that does not have a data blocik payload.
Returned when a received block write request or received block read request is greater
than “max_rec”
1E
Ack Type Error
AT, AR
1F
Reserved