PDI1394L40BEGA ST-Ericsson Inc, PDI1394L40BEGA Datasheet - Page 36

• Manufacturer Part Number: PDI1394L40BEGA
• Description: IC IEEE 1394 LINK CTRLR 144-LQFP
• Manufacturer: ST-Ericsson Inc

Specifications of PDI1394L40BEGA

• Applications: AV,TV, VTR
• Interface: IEEE 1394
• Voltage - Supply: 3 V ~ 3.6 V
• Package / Case: 144-LQFP
• Mounting Type: Surface Mount
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 568-1176; PDI1394L40BE,551; PDI1394L40BE-S

This section describes the asynchronous receive packet formats. Four basic asynchronous data packet formats and one confirmation format exist:
Philips Semiconductors
12.6.2.7 Asynchronous Receive Packet Formats
Table 2. Asynchronous Data Packet Formats
Each packet format uses several fields. More information about most of these fields can be found in the 1394 specification.
Table 3. Asynchronous Receive Fields
2000 Dec 15
destinationID
tLabel
rt
tCode
priority
sourceID
destinationOffsetHigh,
destinationOffsetLow
rCode
quadlet data
dataLength
extendedTcode
block data
padding
u
ackSent
status
1394 enhanced AV link layer controller
Field Name
ITEM
1
1
2
2
3
4
5
This field is the concatenation of busNumbers (or all ones for “local bus”) and nodeNumbers (or all ones for
broadcast) for this node.
This field is the transaction label, which is used to pair up a response packet with its corresponding request packet.
tLables are also used as identifiers to associate a Link data confirmation (see 12.6.2.13) with the corresponding
request, response, or asynchronous stream packet.
The retry code of the received packet; see the 1394 specification.
The transaction code for this packet.
The priority level for this packet (0000 for cable environment).
This is the node ID of the sender of this packet.
The concatenation of these two field addresses a quadlet in this node’s address space.
Response code for the received packet; see the 1394 specification.
For quadlet write requests and quadlet read responses, this field holds the data received.
The number of bytes of data to be received in a block packet.
If the tCode indicates a lock transaction, this specifies the actual lock action to be performed with the data in this
packet.
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.
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.
Unsolicited response tag bit. This bit is set to one (1) if the received response was unsolicited.
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 4 (they also
can be found in the IEEE 1394 standard).
This field is used for asynchronous streams.
No packet data
No-packet data
Quadlet packet
Quadlet packet
Block Packet
Self-ID / PHY packet
Confirmation packet
0000
0001
0010–1100
1101
1110–1111
FORMAT
Reserved.
packet OK.
Reserved.
Data CRC error and/or block size mismatch have been detected.
Reserved.
Quadlet read requests
Quadlet/block write responses
Quadlet write requests
Quadlet read responses
Block read requests
Block write requests
Block read responses
Lock requests
Lock responses
Concatenated self-ID / PHY packets
Confirmation of packet transmission
32
Description
USAGE
TRANSACTION CODE
PDI1394L40
Preliminary specification
B
E
4
2
0
6
5
1
7
9
hex
hex
8