![](http://datasheet.mmic.net.cn/390000/TSB42AA4I_datasheet_16839080/TSB42AA4I_74.png)
59
Table 59. Block Receive Format Functions (Continued)
FIELD NAME
destination OffsetHigh,
destination OffsetLow
DESCRIPTION
The concatenation of the destination OffsetHigh and the destination OffsetLow fields
addresses a quadlet in the destination nodes address space. This address must be quadlet
aligned (modulo 4). The upper 4 bits of the destination OffsetHigh field are used as the
response code for lock-response packets and the remaining bits are reserved.
For write request, read responses, and locks, the dataLength field indicates the number of
bytes being transferred. For read requests, the dataLength field indicates the number of
bytes of data to be read. A write-response packet does not use this field. Note that the
number of bytes does not include the head, only the bytes of block data.
The extended_tCode field contains the block extended_tCode to be performed on the data
in the current packet (see Table 611 of the IEEE–1394 standard).
dataLength
extended_tCode
block data
The block data field contains any data being transferred for the current packet. Regardless of
the destination address or memory alignment, the first byte of the data appears in byte 0 of
the first quadlet of this field. The last quadlet of the field is padded with zeros out to four bytes,
if necessary.
The spd field indicates the speed at which the current packet was sent. 00 = 100 Mb/s, 01 =
200 Mb/s, 10 = 400 Mb/s, and 11 is undefined for this implementation.
spd
5.3
Asynchronous Acknowledge Buffer
The acknowledge buffer retains the last six acknowledges returned by external nodes in response to the
last six async packets transmitted from the ceLynx. The host processor can track which acknowledge was
returned for each of the last six asynchronous packets by accessing this buffer via the TXDPSTAT register.
The acknowledge tracking buffer contains a 32-bit quadlet for every asynchronous packet transmitted from
the node. This quadlet contains information on the acknowledge received, the destination ID, the tlabel, retry
code, tcode, and ack count for a transmitted packet.
The TXDPSTAT register (CFR 204h) also gives information on transmitted asynchronous packets. This
register is updated after each full read from the TXDPSTAT register (upper and lower 16 bits). Bits 27:24
give the ACK code for the transmitted packet. The ACK codes are described in Table 510. This ACK code
is from the receiving node if the asynchronous packet was transmitted correctly, or from the transmitter logic
if an error occurred on transmission. An ACK_CODE_COMPLETE (0001b) is written to bits 27:24 for
asynchronous stream packets or broadcast asynchronous packets. The fifth bit (bit 28), which is the first
bit shown in Table 510, is the error bit.
Table 510. ACK Code Meanings
MEANING
ERRORBIT_ACK
CODE
0_0001
DESCRIPTION
ACK_CODE_COMPLETE
The 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 follows.
The node has successfully accepted the packet. If the
packet was a request subaction, a response subaction will
follow later. This code is not returned for a response
subaction.
The packet could not be accepted. The destination
transaction layer may accept the packet on a retry of the
subaction.
The packet could not be accepted. The destination
transaction layer will accept the packet when the node is not
busy during the next occurrence of retry phase A.
The packet could not be accepted. The destination
transaction layer will accept the packet when the node is not
busy during the next occurrence of retry phase B.
0_0010
ACK_CODE_PENDING
0_0100
ACK_CODE_BUSY_X
0_0101
ACK_CODE_BUSY_A
0_0110
ACK_CODE_BUSY_B