![](http://datasheet.mmic.net.cn/390000/TSB42AA4I_datasheet_16839080/TSB42AA4I_75.png)
510
Table 510. ACK Code Meanings (Continued)
ERRORBIT_ACK
CODE
0_1011
MEANING
DESCRIPTION
ACK_CODE_BUSY_TARDY
The node could not accept the packet because the link and
higher layers are in a suspended state. The destination node
will restore full functionality to the link and transaction layers
and may accept the packet on a retransmission in a
subsequent fairness interval.
0_1100
ACK_CONFLICT_ERROR
A resource conflict prevented the packet from being
accepted.
0_1101
ACK_CODE_DATA_ERROR
The 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 block payload.
0_1110
ACK_TYPE_ERROR
A field in the request packet header was set to a n
unsupported or incorrect value, or an invalid transaction was
attempted (e.g., a write to a read-only address).
The node could not accept the packet because the
destination_offset field in the request was set to an address
not accessible in the destination node.
This is caused when a subaction gap was detected before
an ACK arrived.
0_1111
ACK_ADDRESS_ERROR
1_0000
EVT_MISSING_ACK
1_0001
EVT_TCODE_ERR
This is caused when a bad tCode is associated with this
packet. If buffer flush is enabled in TXDP CFR, then the
associated TX buffer is flushed.
This is caused by the ceLynx hardware when the transmit
packet has an incorrect format.
1_0010
EVT_PKT_FORMAT_ERROR
1_0011
EVT_UNKNOWN
This is caused when an error condition has occurred that
cannot be represented by any other event codes defined
herein.
Not supported
1_0100
EVT_BUSY_ACK_RETRY_
EXHAUSTED
TXDPSTAT bits 15:8 give information on the packet identifier. For asynchronous packets, this is the tlabel
and retry code for the transmitted asynchronous packet. For asynchronous stream packets, this is the
isochronous tag and channel number. In general, bits 15:8 in TXDPSTAT correspond to bits 15:8 of the first
quadlet of a transmitted packet.
The count value indicates how many acknowledges are present in the buffer. The ACKCNT field starts at
zero and increments (to a max value of six), with each acknowledge that is loaded into this buffer. A read
from an empty buffer returns all zeroes. The buffer can hold up to 6 quadlets. Once the buffer is full, or more
than six asynchronous transmits have occurred without a single read from the buffer, no more writes occur
to the stack. In this case, it is presumed the host is not concerned with tracking the ACKs returned.
30 29 28
24 23 22 21
15
8
4
3
2
0
31
16
NODEID
ACKCODE
E
PACKETID
TCODE
ACKCNT
Full bit name is ACK_ERR.
Figure 58. Acknowledge Buffer Format