![](http://datasheet.mmic.net.cn/390000/TSB42AA4I_datasheet_16839080/TSB42AA4I_69.png)
54
Table 54. Block Transmit Format Functions
FIELD NAME
DESCRIPTION
spd
The spd field indicates the speed at which the current packet is to be sent. 00 = 100 Mb/s,
01 = 200 Mb/s, and 10 = 400 Mb/s. For this implementation, 11 is undefined.
tLabel
The tLabel field is the transaction label, which is a unique tag for each outstanding
transaction between two nodes. This field is used to pair up a response packet with its
corresponding request packet.
rt
The rt field is the retry code for the current packet is 00 = new, 01 = retry_X, 10 = retry_A, and
11 = retry_B.
tCode
tCode is the transaction code for the current packet (see Table 610 of IEEE-1394 standard).
priority
The priority level for the current packet. For cable implementation, the value of the bits must
be zero. For backplane implementation, see clauses 5.4.1.3 and 5.4.2.1 of the IEEE-1394
standard.
destinationID
The destinationID field is the concatenation of the 10-bit bus number and the 6-bit node
number that forms the node address to which the current packet is being sent.
destination OffsetHigh,
destination OffsetLow
The concatenation of the destination OffsetHigh and the destination OffsetLow fields
addresses a quadlet in the destination node 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.
dataLength
The dataLength field contains the number of bytes of data to be transmitted in the packet.
extended_tCode
The block extended_tCode to be performed on the data in the current packet (see Table 611
of the IEEE-1394 standard)
block data
The block data field contains the data to be sent. If dataLength is 0, no data should be written
into the FIFO for this field. Regardless of the destination or source alignment of the data, the
first byte of the block must appear in byte 0 of the first quadlet.
5.2
Asynchronous Receive
There are two basic formats for received asynchronous data. The first is for quadlet packets, and the second
is for block packets. The asynchronous receive data buffer can be accessed by either the HSDI or the MCIF.
The data buffers can be accessed by the MCIF through the DB(N)ACC0 register.
The full received packet format with headers and data is shown in Figure 55 and Figure 56. ceLynx can
strip received packet headers on a quadlet basis. This is controlled in the RXDPB(N)CFG0 register bits 03.
For example, the application can choose to strip quadlet headers 0, 1, and 2. The application receives
header 3 and the data. In this example, if ceLynx received an asynchronous block read response packet,
the application receives the dataLength and extended t-code quadlet and the packet data only.
The packet control token gives information about the received packet. For asynchronous packets, the
quadlet is included with the data in the data buffer according to the RXDPB(N)CFG0.INSERTPKT
TOKEN bit. The control token is always attached to receive self-ID packets regardless of the
RXDPB(N)CFG0.INSERTPKTTOKEN setting. The packet control token format for asynchronous and PHY
packets is shown in Figure 55 and Table 55.
30
29
16
15
14
13
12
8
7
6
5
4
3
0
31
rsv
pad
ACK
P
S
SIZE
spd
rsv
rsv
Figure 55. Packet Control Token Format for Asynchronous,
Self-ID, and PHY Packets