PDI1394L11 Datasheet, PDF (17/46 Pages) NXP Semiconductors – 1394 AV link layer controller

Philips Semiconductors
1394 AV link layer controller
Product specification
PDI1394L11
Table 5. Asynchronous Receive Fields
Field Name
Description
destinationID
This field is the concatenation of busNumbers (or all ones for “local bus”) and nodeNumbers (or all ones for
broadcast) for this node.
tLabel
This field is the transaction label, which is used to pair up a response packet with its corresponding request packet.
rt
The retry code for this packet. 00=retry1, 01=retryX, 10=retryA, 11=retryB.
tCode
The transaction code for this packet.
priority
The priority level for this packet (0000 for cable environment).
sourceID
This is the node ID of the sender of this packet.
destinationOffsetHigh, The concatenation of these two field addresses a quadlet in this node’s address space.
destinationOffsetLow
rCode
Response code for response packets.
quadlet data
For quadlet write requests and quadlet read responses, this field holds the data received.
dataLength
The number of bytes of data to be received in a block packet.
extendedTcode
If the tCode indicates a lock transaction, this specifies the actual lock action to be performed with the data in this
packet.
block data
The data received. If dataLength=0, no data will be written into the FIFO for this field. Regardless of the destination
or source alignment of the data, the first byte of the block will appear in the high order byte of the first quadlet.
padding
If the dataLength mod 4 is not zero, then zero–value bytes are added onto the end of the packet to guarantee that a
whole number of quadlets is sent.
u
Unsolicited response tag bit. This bit is set to one (1) if the received response was unsolicited.
ackSent
This field contains the acknowledge code that the link layer returned to the sender of the received packet. For
packets that do not need to be acknowledged (such as broadcasts) the field contains the acknowledge value that
would have been sent if an acknowledge had been required. The values for this field are listed in Table 6 (they also
can be found in the IEEE 1394 standard).
Table 6. Acknowledge codes
Code
0001
Name
ack_complete
Description
The node has successfully accepted the packet. If the packet was a request subaction, the destina-
tion node has successfully completed the transaction and no response subaction shall follow.
0010
ack_pending
The node has successfully accepted the packet. If the packet was a request subaction, a response
subaction will follow at a later time. This code shall not be returned for a response subaction.
0100
ack_busy_X
The packet could not be accepted. The destination transaction layer may accept the packet on a
retry of the subaction.
0101
ack_busy_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 A.
0110
ack_busy_B
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.
1101
ack_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 dataLength field. This
code shall not be returned for any packet that does not have a data block payload.
1110
ack_type_error
A field in the request packet header was set to an unsupported or incorrect value, or an invalid trans-
action was attempted (e.g., a write to a read-only address).
0000, 0011,
0111 – 1100,
and 1111
reserved
1997 Oct 21
17