SEE ATTACHED ERRATA WHICH FOLLOWS THIS DOCUMENT FOR INFORMATION
REGARDING CHANGED SPECIFICATIONS
PDI1394L21
1394 full duplex AV link layer controller
Preliminary specification
Supersedes data of 1999 Mar 30
1999 Aug 06
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
1.0 FEATURES
•IEEE 1394–1995 Standard Link Layer Controller
•Hardware Support for the IEC61883 International Standard of
Digital Interface for Consumer Electronics
•Interface to any IEEE 1394–1995 Physical Layer Interface
•5V Tolerant I/Os
•Single 3.3V supply voltage
•Full-duplex isochronous operation
•Operates with 400/200/100 Mbps physical layer devices
•Dual 4K Byte FIFOs for isochronous data
•Supports single capacitor isolation mode and IEEE 1394–1995,
Annex J. isolation
•4-field deep SYT buffer added to enhance real-time isochronous
synchronization using the AVFSYNC pin
•Generates its own AV port clocks under software control. Select
one of three frequencies: 24.576, 12.288, or 6.144 MHz
2.0 DESCRIPTION
The PDI1394L21, Philips Semiconductors Full Duplex 1394
Audio/Video (AV) Link Layer Controller, is an IEEE 1394–1995
compliant link layer controller featuring 2 embedded AV layer
interfaces. The AV layers are designed to pack and un-pack
application data packets for transmission over the IEEE 1394 bus
using isochronous data transfers. Because of its full duplex
architecture, the PDI1394L21 is capable of receiving and
transmitting isochronous data during the same bus cycle. Two 8 bit
AV ports, each with its own buffer (FIFO), receive and output
isochronous data for transmission and reception of bus packets.
Each port can be configured to receive or transmit, however, the
other port always performs the opposite function. Half duplex
operation is also permitted.
The application data is packetized according to the IEC 61883
International Standard of Interface for Consumer Electronic
Audio/Video Equipment. Both AV layer interfaces are byte-wide
ports capable of accommodating various MPEG–2 and DVC
codecs. An 80C51 compatible byte-wide host interface is provided
for internal register configuration as well as performing
asynchronous data transfers.
The PDI1394L21 is powered by a single 3.3V power supply and the
inputs and outputs are 5V tolerant. It is available in the LQFP100
and TQFP100 packages.
3.0 QUICK REFERENCE DATA
GND = 0V; T
SYMBOL
V
DD
I
DD
SCLKDevice clock49.14749.15249.157MHz
= 25°C
amb
PARAMETERCONDITIONSMINTYPMAXUNIT
Functional supply voltage range3.03.33.6V
Supply current @ VDD = 3.3VOperating75mA
4.0 ORDERING INFORMATION
PACKAGESTEMPERATURE RANGEOUTSIDE NORTH AMERICANORTH AMERICAPKG. DWG. #
100-pin plastic LQFP1000°C to +70°CPDI1394L21BEPDI1394L21BESOT407 AB15
100-pin plastic TQFP1000°C to +70°CPDI1394L21BPPDI1394L21BPSOT386 BB2
NOTE:
This datasheet is subject to change.
Please visit out internet website www.semiconductors.philips.com/1394 for latest changes.
1999 Aug 06
2
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
* INDICATES PIN EQUIPPED WITH INTERNAL BUS HOLD CIRCUIT
ACTIVATED BY THE STATE OF THE ISO_N PIN.
1999 Aug 06
SV00877
3
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
6.0 FUNCTIONAL DIAGRAM
HIF A[8:0]
HOST
HIF D[7:0]
HIF WR_N
HIF RD_N
HIF CS_N
HIF INT_N
RESET_N
PHY D[0:7]
PHY CTL[0:1]
LREQ
ISO_N
SCLK
PHY
CYCLEIN
CYCLEOUT
AV1 D[7:0]
AV1CLK
AV1VALID
AV1SYNC
AV1FSYNCAV2FSYNC
AV LAYER 1
AV1ENKEY
AV1ENDPCK
AV1ERR[1:0]
7.0 INTERNAL BLOCK DIAGRAM
AV1 D[7:0]
AV1CLK
AV1ENDPCK
AV LAYER1
AV1ERR[0:1]
AV2ENDPCK
AV2ERR[0:1]
AV LAYER2
AV1SYNC
AV1VALID
AV1FSYNC
AV1ENKEY
AV2 D[7:0]
AV2CLK
AV2SYNC
AV2VALID
AV2FSYNC
AV2ENKEY
HIF A[8:0]
HIF D[7:0]
HIF WR_N
HIF RD_N
HIF CS_N
HIF INT_N
AV1 LAYER
ISOCHRONOUS
TRANSMITTER/
RECEIVER
AV2 LAYER
ISOCHRONOUS
TRANSMITTER/
RECEIVER
INTERFACE
8-BIT
PDI1394L21
IEEE 1394
FULL DUPLEX
AV LINK LAYER CONTROLLER
9KB BUFFER
MEMORY
(ISOCH & ASYNC
PACKETS)
ASYNC
TRANSMITTER
AND
RECEIVER
VDD
GND
AV2D[7:0]
AV2CLK
AV2VALID
AV2SYNC
AV2ENKEY
AV2ENDPCK
AV2ERR[1:0]
LINK CORE
CONTROL
AND
STATUS
REGISTERS
AV LAYER 2
SV00878
CYCLEOUT
CYCLEIN
PHY D[0:7]
PHY CTL[0:1]
LREQ
ISO_N
SCLK
NOTE: THERE IS ONLY ONE
ISOCHRONOUS RECEIVER
AND ONE ISOCHRONOUS
TRANSMITTER—THEREFORE,
WHEN EITHER AVPORT IS SET
TO TRANSMIT, THE OTHER
AVPORT IS AUTOMATICALLY
SET TO RECEIVE.
RESET_N
1999 Aug 06
SV00879
4
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
8.0 APPLICATION DIAGRAM
MPEG OR DVC
DECODER
MPEG OR DVC
DECODER
HOST CONTROLLER
AV
INTERFACE
AV
INTERFACE
DATA 8/
ADDRESS 9/
INTERRUPT & CONTROL
PDI1394L21
AV LINK
PHY–LINK
INTERFACE
9.0 PIN DESCRIPTION
9.1 Host Interface
PIN No.PIN SYMBOLI/ONAME AND FUNCTION
1, 2, 3, 4, 7, 8,
9, 10
5, 12, 23, 31,
38, 44, 50, 63,
73, 79, 87, 93
6, 13, 24, 32,
39, 45, 49, 64,
72, 78, 88, 94
14, 15, 16, 17,
18, 19, 20, 21,
22
25HIF CS_NI
26HIF WR_NI
27HIF RD_NI
28HIF INT_NO
29RESET_NIReset (active LOW). The asynchronous master reset to the PDI1394L21.
HIF D[7:0]I/OHost Interface Data 7 (MSB) through 0. Byte wide data path to internal registers.
GNDGround reference
V
DD
HIF A[8:0]I
3.3V ± 0.3V power supply
Host Interface Address 0 through 8. Provides the host with a byte wide interface to internal
registers. See description of Host Interface for addressing rules.
Chip Select (active LOW). Host bus control signal to enable access to the FIFO and control and
status registers.
Write enable. When asserted (LOW) in conjunction with HIF CS_N, a write to the PDI1394L21
internal registers is requested. (NOTE: HIF WR_N and HIF RD_N : if these are both LOW in
conjunction with HIF CS_N, then a write cycle takes place. This can be used to connect CPUs
that use R/W_N line rather than separate RD_N and WR_N lines. In that case, connect the
R/W_N line to the HIF WR_N and tie HIF RD_N LOW.)
Read enable. When asserted (LOW) in conjunction with HIF CS_N, a read of the PDI1394L21
internal registers is requested.
Interrupt (active LOW). Indicates a interrupt internal to the PDI1394L21. Read the General
Interrupt Register for more information. This pin is open drain and requires a 1KW pull-up resistor.
PDI1394Pxx
PHY
1394 CABLE
INTERFACE
SV00880
1999 Aug 06
5
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
9.2 AV Interface 1
NOTE: This AV interface may be configured to transmit or receive according to the condition of “DIRAV1” bit in GLOBCSR register
(0X018)—default is transmit.
PIN No.
77, 76, 75, 74,
71, 70, 69, 68
58AV1CLKI/O
57AV1SYNCI/OStart of packet indicator; should only be used when AV1VALID is active.
59AV1FSYNCI/O
56AV1ENDPCKI
60AV1ENKEYI/O
61A V1VALIDI/OIndicates data on AV1 D [7:0] is valid.
53AV1ERR0O
52AV1ERR1OSequence Error. Indicates at least one source packet was lost before the current AV1 D [7:0] data.
PIN SYMBOLI/ONAME AND FUNCTION
AV1 D[7:0]I/OAudio/Video Data 7 (MSB) through 0. Byte-wide interface to the AV layer 1.
External application clock. Rising edge active. This pin can be programmed to output the
application clock. Depending on the configuration of AV Port 1 as transmitter or receiver , the
output enable is located in the ITXPKCTL register (address 0x020) or IRXPKCTL register
(address 0x040).
Programmable frame sync, can be set to input. Frame sync input used for Digital Video (DV). The
signal is time stamped and transmitted in the SYT field of ITXHQ2. Frame sync output. Signal is
derived from SYT field of IRXHQ2.
End of application packet indication from data source. Required only if input packet is not multiple
of 4 bytes. It can be tied LOW for data packets that are 4*N in size.
Encryption key state. Indicates state “1” or “0” of encryption key which matches present port data
during receive mode. Used to input key state during transmit mode.
CRC error, indicates bus packet containing AV1 D [7:0] had a CRC error, the current AV packet is
unreliable.
9.3 AV Interface 2
NOTE: This AV interface may be configured to transmit or receive according to the condition of “DIRAV1” bit in GLOBCSR register—default is
receive.
PIN No.
98, 97, 96, 95,
92, 91, 90, 89
84AV2CLKI/O
83AV2SYNCI/OStart of packet indicator; should only be used when AV2VALID is active.
85AV2FSYNCI/O
82AV2ENDPCKI
86A V2VALIDI/OIndicates data on AV2 D [7:0] is valid.
81AV2ERR0O
80AV2ERR1OSequence Error. Indicates at least one source packet was lost before the current AV2 D [7:0] data.
99AV2ENKEYI/O
PIN SYMBOLI/ONAME AND FUNCTION
AV2 D[7:0]I/OAudio/Video Data 7 (MSB) through 0. Byte-wide interface to the AV layer 2.
External application clock. Rising edge active. This pin can be programmed to output the
application clock. Depending on the configuration of AV Port 2 as transmitter or receiver , the
output enable is located in the ITXPKCTL register (address 0x020) or IRXPKCTL register
(address 0x040).
Programmable frame sync, can be set to input or output. Frame sync input used for Digital Video
(DV). The signal is time stamped and transmitted in the SYT field of ITXHQ2. Frame sync output.
Signal is derived from SYT field of IRXHQ2.
End of application packet indication from data source. Required only if input packet is not multiple
of 4 bytes. It can be tied LOW for data packets that are 4*N in size.
CRC error, indicates bus packet containing AV2 D [7:0] had a CRC error, the current AV packet is
unreliable.
Encryption key state. Indicates state “1” or “0” of encryption key which matches present port data
during receive mode. Used to input key state during transmit mode.
9.4 Phy Interface
PIN No.PIN SYMBOLI/ONAME AND FUNCTION
Data 0 (MSB) through 7 (NOTE: To preserve compatibility to the specified Link-Phy interface of
43, 42, 41, 40,
37, 36, 35, 34
47, 46PHY CTL[0:1]I/OControl Lines between Link and Phy . See 1394 Specification for more information.
48ISO_NI
54LREQO
55SCLKISystem clock. 49.152MHz input from the PHY (the PHY -LINK interface operates at this frequency).
PHY D[0:7]I/O
the IEEE 1394–1995 standard, Annex J, bit 0 is the most significant bit). Data is expected on
PHY D[0:1] for 100Mb/s, PHY D[0:3] for 200Mb/s, and PHY D[0:7] for 400Mb/s. See IEEE
1394–1995 standard, Annex J for more information.
Isolation mode. This pin is asserted (LOW) when an Annex J type isolation barrier is used.
See IEEE 1394–1995 Annex J. for more information. When tied HIGH, this pin enables internal
bushold circuitry on the affected PHY interface pins (see below). Active bushold circuits allow
either the direct connection to PHY pins or the use of the single capacitor isolation mode.
Link Request. Bus request to access the PHY. See IEEE 1394–1995 standard, Annex J for more
information. (Used to request arbitration or read/write PHY registers).
1999 Aug 06
6
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
9.4.1 Bushold and Link/PHY single capacitor
galvanic isolation
9.4.1.1 Bushold
The PDI1394L21 uses an internal bushold circuit on each of the
indicated pins to keep these CMOS inputs from “floating” while being
driven by a 3-Stated device or input coupling capacitor.
Unterminated high impedance inputs react to ambient electrical
noise which cause internal oscillation and excess power supply
current draw.
The following pins have bushold circuitry enabled when the ISO_N
pin is in the logic “1” state:
Pin No.NameFunction
47PHYCTL0PHY control line 0
46PHYCTL1PHY control line 1
54LREQLink request line
43PHYD0PHY data bus bit 0
42PHYD1PHY data bus bit 1
41PHYD2PHY data bus bit 2
40PHYD3PHY data bus bit 3
37PHYD4PHY data bus bit 4
36PHYD5PHY data bus bit 5
35PHYD6PHY data bus bit 6
34PHYD7PHY data bus bit 7
Philips bushold circuitry is designed to provide a high resistance
pull-up or pull-down on the input pin. This high resistance is easily
overcome by the driving device when its state is switched. Figure 1
shows a typical bushold circuit applied to a CMOS input stage. Two
weak MOS transistors are connected to the input. An inverter is also
connected to the input pin and supplies gate drive to both
transistors. When the input is LOW, the inverter output drives the
lower MOS transistor and turns it on. This re-enforces the LOW on
the input pin. If the logic device which normally drives the input pin
were to be 3-Stated, the input pin would remain “pulled-down” by the
weak MOS transistor. If the driving logic device drives the input pin
HIGH, the inverter will turn the upper MOS transistor on,
re-enforcing the HIGH on the input pin. If the driving logic device is
then 3-Stated, the upper MOS transistor will weakly hold the input
pin HIGH.
The PHY’s outputs can be 3-Stated and single capacitor isolation
can be used with the Link; both situations will allow the Link inputs to
float. With bushold circuitry enabled, these pins are provided with dc
paths to ground, and power by means of the bushold transistors;
this arrangement keeps the inputs in known logical states.
INPUT PIN
INTERNAL
CIRCUITS
SV00911
Figure 1. Bushold circuit
9.4.1.2 Single capacitor isolation
The circuit example (Figure 2) shows the connections required to
implement basic single capacitor Link/PHY isolation.
NOTE: The isolation enablement pins on both devices are in their
“1” states, activating the bushold circuits on each part. The bushold
circuits provide local dc ground references to each side of the
isolating/coupling capacitors. Also note that ground
isolation/signal-coupling must be provided in the form of a parallel
combination of resistance and capacitance as indicated in
IEEE 1394–1995.
1999 Aug 06
APPLICATION
6, 13, 24, 32, etc.
LINK
PDI1394L21
APPLICATION GROUND
+3.3V
48
ISO_N
PHY D0
PHY D1
PHY D2
PHY D3
PHYCTL0
PHYCTL1
LREQ
SCLK
43
42
41
40
47
46
54
55
Cc
Cc
Cc = 0.001µF; Cr = 0.1µF
Cc
Cc
Cc
1MEG Ω
Cr
Figure 2. Single capacitor Link/PHY isolation
7
ISOLATED
+3.3V
ISO–
D0
Cc
Cc
Cc
D1
PDI1394Pxx
D2
D3
PHYCTL0
PHYCTL1
LREQ
SYSCLK
PHY
ISOLATED PHY GROUND
SV00912
Philips SemiconductorsPreliminary specification
SYMBOL
PARAMETER
CONDITIONS
UNIT
SYMBOL
PARAMETER
CONDITIONS
UNIT
PDI1394L211394 full duplex AV link layer controller
9.5 Other Pins
PIN No.PIN SYMBOLI/ONAME AND FUNCTION
65, 66, 67RESERVEDNA
51, 62, 100N/CNAThese pins should not be connected or terminated.
30CYCLEINI
33CYCLEOUTOReproduces the 8kHz cycle clock of the cycle master.
11CLK25OAuxiliary clock, value is SCLK/2 (usually 24.576 MHz)
These pins are reserved for factory testing. For normal operation they should be connected to
ground.
Provides the capability to supply an external cycle timer signal for the beginning of 1394 bus
cycles.
LIMITS
MIN.MAX.
11.0 ABSOLUTE MAXIMUM RATINGS
1, 2
In accordance with the Absolute Maximum Rating System (IEC 134). Voltages are referenced to GND (ground = 0V).
LIMITS
MINMAX
I
GND
T
V
T
P
DD
I
IK
V
I
OK
V
I
stg
amb
DC supply voltage–0.5+4.6V
DC input diode current––50mA
DC input voltage–0.5+5.5V
I
DC output diode current–±50mA
DC output voltage–0.5VDD +0.5V
O
DC output source or sink current–±50mA
O
, I
DC VCC or GND current–±150mA
CC
Storage temperature range–60150°C
Operating ambient temperature070°C
Power dissipation per package0.6W
tot
NOTES:
1. Stresses beyond those listed may cause permanent damage to the device. These are stress ratings only and functional operation of the
device at these or any other conditions beyond those indicated under “recommended operating conditions” is not implied. Exposure to
absolute-maximum-rated conditions for extended periods may affect device reliability .
2. The performance capability of a high-performance integrated circuit in conjunction with its thermal environment can create junction
temperatures which are detrimental to reliability. The maximum junction temperature of this integrated circuit should not exceed 150°C.
1999 Aug 06
8
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
11.1 Buffer Memory Sizes
BUFFER MEMORY
Asynchronous Receive Response FIFO64
Asynchronous Receive Request FIFO128
Asynchronous Transmit Response FIFO64
Asynchronous Transmit Request FIFO64
Isochronous (AV) T ransmit Buf fer1024
Isochronous (AV) Receive Buffer1024
12.0 FUNCTIONAL DESCRIPTION
12.1 Overview
The PDI1394L21 is an IEEE 1394–1995 compliant link layer controller. It provides a direct interface between a 1394 bus and various MPEG–2
and DVC codecs. Via this interface, the AV Link maps and unmaps these AV datastreams from these codecs onto 1394 isochronous bus
packets. The AV Link also provides an 8051 compatible microcontroller interface for an attached host controller. Through the host interface port,
the host controller can configure the AV layer for transmission or reception of AV datastreams. The host interface port also allows the host
controller to transmit and receive 1394 asynchronous data packets.
12.2 AV interface and AV layer
The AV interface and AV layer allow AV packets to be transmitted from one node to another. The AV transmitter and receiver within the AV layer
perform all the functions required to pack and unpack AV packet data for transfer over a 1394 network. Once the AV layer is properly configured
for operation, no further host controller service should be required. The operation of the AV layer is full-duplex, i.e., the AV layer can receive and
transmit AV packets at the same time.
12.2.1 The AV Interface
The AV Link provides an 8 bit data path to the AV layer. The 8 bit data path is designed with associated clock and control signals to be
compatible with various MPEG–2 and DVC codecs.
The AV interface port buf fer, if so programmed, can time stamp incoming AV packets. The AV packet data is stored in the embedded memory
buffer , along with its time stamp information. After the AV packet has been written into the AV layer, the AV layer creates an isochronous bus
packet with the appropriate CIP header. The bus packet along with the CIP header is transferred over the appropriate isochronous
channel/packet. The size and configuration of isochronous data packet payload transmitted is determined by the AV layer’s confi guration
registers accessible through the host interface.
The AV interface port waits for the assertion for AVxVALID and AVxSYNC. Note: Do not assert AVxSYNC without AVxVALID. AVxSYNC is
aligned with the rising edge of AVxCLK and the first byte of data on AVxDATA[7:0]. The duration of AVxSYNC is one AVxCLK cycle. AVxSYNC
signals the AV layer that the transfer of an AV packet has begun. At the time the AVxSYNC is asserted, the AV layer creates a new time stamp
in the buffer memory. (This only happens if so configured. The DVC format does not use these time stamps). The time stamp is then transmitted
as part of the source packet header. This allows the AV receiver to provide the AV packet for output at the appropriate time. Only one AVSYNC
pulse is allowed per application packet; if additional sync pulses are presented before the full packet is inputted, a new packet will be started
and the previously inputted packet data will be discarded (and not transmitted) in conjunction with the input error interrupt bit (INPERR, bit 3 of
register 0x02C) being set to flag the error.
When the DV video is enabled (via the format code of the CIP header), the frame synchronization signal AVxFSYNC is time stamped and
placed in the SYT field. The default timestamp value is 3 cycle times (duration of 125ms each) in the future and is transmitted in the SYT field of
the current CIP header; this value is programmable from 2 to 4 cycle times (see section 13.2.1). On the receiver side, when the SYT stamp
matches the cycle timer register, a pulse is generated on the AVxFSYNC output. The timing for AVxFSYNC is independent of AVxCLK.
12.2.2 IEC 61883 International Standard
The PDI1394L21 is specifically designed to support the IEC61883 International Standard of Digital Interface for Consumer Electronic
Audio/Video Equipment. The IEC specification defines a scheme for mapping various types of AV datastreams onto 1394 isochronous data
packets. The standard also defines a software protocol for managing isochronous connections in a 1394 bus called Connection Management
Protocol (CMP). It also provides a framework for transfer of functional commands, called Function Control Protocol (FCP).
12.2.3 CIP Headers
A feature of the IEC61883 International Standard is the definition of Common Isochronous Packet (CIP) headers. These CIP headers contain
information about the source and type of datastream mapped onto the isochronous packets.
The AV Layer supports the use of CIP headers. CIP headers are added to transmitted isochronous data packets at the AV data source. When
receiving isochronous data packets, the AV layer automatically analyzes their CIP headers. The analysis of the CIP headers determines the
method the A V layer uses to unpack the AV data from the isochronous data packets.
The information contained in the CIP headers is accessible via registers in the host interface.
(See IEC61883 International Standard of Digital Interface for Consumer Electronic Audio/Video Equipment for more details on CIP headers).
SIZE
(Quadlets)
1999 Aug 06
9
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.3 The host interface
The host interface allows an 8 bit CPU to access all registers and the asynchronous packet queues. It is specifically designed for an 8051
microcontroller but can also be used with other CPUs. There are 64 register addresses (for quadlet wide registers). To access bytes rather than
quadlets the address spaces is 256 bytes, requiring 8 address lines.
The use of an 8 bit interface introduces an inherent problem that must be solved: register fields can be more than 8 bits wide and be used
(control) or changed (status) at every internal clock tick. If such a field is accessed through an 8 bit interface it requires more than one read or
write cycle, and the value should not change in between to maintain consistency. To overcome this problem accesses to the chip’s internal
register space are always 32 bits, and the host interface must act as a converter between the internal 32 bit accesses and external 8 bit
accesses. This is where the shadow registers are used.
12.3.1 Read accesses
To read an internal register the host interface can make a snapshot (copy) of that specific register which is then made available to the CPU 8
bits at a time. The register that holds the snapshot copy of the real register value inside the host interface is called the read shadow register.
During a read cycle address lines HIF A0 and HIF A1 are used to select which of the 4 bytes currently stored in the read shadow register is
output onto the CPU data bus. This selection is done by combinatorial logic only, enabling external hardware to toggle these lines through
values 0 to 3 while keeping the chip in a read access mode to get all 4 bytes out very fast (in a single extended read cycle), for example into an
external quadlet register.
This solution requires a control line to direct the host interface to make a snapshot of an internal register when needed, as well as the internal
address of the target register. The register address is connected to input address lines HIF A2..HIF A7, and the update control line to input
address line HIF A8. To let the host interface take a new snapshot the target address must be presented on HIF A2..HIF A7 and HIF A8 must be
raised while executing a read access. The new value will be stored in the read shadow register and the selected byte (HIF A0, HIF A1)
appears on the output.
TR
Q
Q
REGISTERS
32
SV00803
CPU
HIF A0..1
HIF A2..7
HIF A8
MUXMUX
83232
READ SHADOW REGISTER
UPDATE/COPY CONTROL
NOTES:
1. It is not required to read all 4 bytes of a register before reading another register. For example, if only byte 2 of register 0x54 is required a
read of byte address 0x100 + (0×54) + 2 = 0x156 is sufficient.
2. The update control line does not necessarily have to be connected to the CPU address line HIF A8. This input could also be controlled by
other means, for example a combinatorial circuit that activates the update control line whenever a read access is done for byte 0. This
makes the internal updating automatic for quadlet reading.
3. Reading the bytes of the read shadow register can be done in any order and as often as needed.
1999 Aug 06
10
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.3.2 Write accesses
To write to an internal register the host interface must collect the 4 byte values into a 32 bit value and then write the result to the target register
in a single clock tick. This requires a register to hold the 32 bit value being compiled until it is ready to be written to the actual target register.
This temporary register inside the host interface is called the write shadow register. During all write cycles address lines HIF A0 and HIF A1
are used to select which of the 4 bytes of the write shadow register is to be written with the value on the CPU data bus. Only one byte can be
written in a single write access cycle.
TR
Q
Q
REGISTERS
32
SV00804
CPU
HIF A0..1
HIF A2..7
HIF A8
MUX
MUX
832
WRITE SHADOW REGISTER
UPDATE/COPY CONTROL
NOTES:
1. It is not required to write all 4 bytes of a register: those bytes that are either reserved (undefined) or don’t care do not have to be written in
which case they will be assigned the value that was left in the corresponding byte of the write shadow register from a previous write
access. For example, to acknowledge an interrupt for the isochronous receiver (external address 0x04C), a single byte write to location
0x100+(0x4C)+3 = 0x14F is sufficient. The value 256 represents setting HIF A8=1. The host interface cannot directly access the FIFOs, but
instead reads from/writes into a transfer register (shown as TR in the Figures above). Data is moved between FIFO and TR by internal logic
as soon as possible without CPU intervention.
2. The update control line does not necessarily have to be connected to the CPU address line HIF A8. This input could also be controlled by
other means, for example a combinatorial circuit that activates the update control line whenever a write access is done for byte 3. This
makes the internal updating automatic for quadlet writing.
3. Writing the bytes of the read shadow register can be done in any order and as often as needed (new writes simply overwrite the old value).
12.3.3 Byte order
The bytes in each quadlet are numbered 0..3 from left (most significant) to right (least significant) as shown in Figure 3. To access a register at
internal address N the CPU should use addresses E:
E = N; to access the upper 8 bits of the register.
E = N + 1; to access the upper middle 8 bits of the register.
E = N + 2; to access the lower middle 8 bits of the register.
E = N + 3; to access the lower 8 bits of the register.
Figure 3. Byte order in quadlets as implemented in the host interface
12.3.4 Accessing the packet queues
Although entire incoming packets are stored in the receiver buffer memory they are not randomly accessible. These buffers act like FIFOs and
only the frontmost (oldest) data quadlet entry is accessible for reading. Therefore only one location (register address) is allocated to each of the
two receiver queues. Reading this location returns the head entry of the queue, and at the same time removes it from the queue, making the
next stored data quadlet accessible.
With the current host interface such a read is in fact a move operation of the data quadlet from the queue to the read shadow register. Once the
data is copied into the read shadow register it is no longer available in the queue itself so the CPU should always read all 4 bytes before
attempting any other read access (be careful with interrupt handlers for the PDI1394L21!).
1999 Aug 06
11
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.3.5 The CPU bus interface signals
The CPU interface is directly compatible with an 8051 microcontroller. It uses a separate HIF RD_N and HIF WR_N inputs and a HIF CS_N chip
select line, all of which are active LOW. There are 9 address inputs (HIF A0..HIF A8) and 8 data in/out lines HIF D0..HIF D7. An open drain
HIF INT_N output is used to signal interrupts to the CPU.
The CPU is not required to run at a clock that is synchronous to the 1394 base clock. The control signals will be resampled by the host interface
before being used internally.
An access through the host interface starts when HIF CS_N = 0 and either HIF WR_N = 0 or HIF RD_N = 0. Typically the chip select signal is
derived from the upper address lines of the CPU (address decode stage), but it could also be connected to a port pin of the CPU to avoid the
need for an external address decoder in very simple CPU systems. When both HIF CS_N = 0 and HIF RD_N = 0 the host interface will start a
read access cycle, so the cycle is triggered at the falling edge of either HIF CS_N or HIF RD_N, whichever is later.
HIF CS_N
T
AS
HIF RD_N
T
HIF WR_N
HIF A8
AS
HIF A0..HIF A7
T
ACC
RSR
n
SV00686
HIF D0..HIF D7
T
ACC
RSR
RSR
O
n
Figure 4. Read cycle signal timing (2 independent read cycles)
HIF CS_N
T
AS
HIF RD_N
HIF WR_N
T
AS
HIF A0..HIF A8
HIF D0..HIF D7
<VALID ADDRESS><VALID ADDRESS>
<WRITE DATA><WRITE DATA>
SV00687
Figure 5. Write cycle signal timing (2 independent write cycles)
12.4 The Asynchronous Packet Interface
The PDI1394L21 provides an interface to asynchronous data packets through the registers in the host interface. The format of the
asynchronous packets is specified in the following sections.
12.4.1 Reading an Asynchronous Packet
Upon reception of a packet, the packet data is stored in the appropriate receive FIFO, either the Request or Response FIFO. The location of the
packet is indicated by either the RREQQQAV or RRSPQAV status bit being set in the Asynchronous Interrupt Acknowledge (ASYINTACK)
register. The packet is transferred out of the FIFO by successive reads of the Asynchronous Receive Request (RREQ) or Asynchronous
Receive Response (RRSP) register. The end of the packet (the last quadlet) is indicated by either the RREQQLASTQ or RRSPQLASTQ bit set
in ASYINTACK. Attempting to read the FIFO when either RREQQQAV bit or RRSPQQAV bit is set to 0 (in the Asynchronous RX/TX interrupt
acknowledge (ASYINT ACK) register) will result in a queue read error.
1999 Aug 06
12
Philips SemiconductorsPreliminary specification
1
No-packet data
3
Block Packet
PDI1394L211394 full duplex AV link layer controller
12.5 Link Packet Data Formats
The data formats for transmission and reception of data are shown below. The transmit format describes the expected organization for data
presented to the link at the asynchronous transmit, physical response, or isochronous transmit FIFO interfaces.
12.5.1 Asynchronous Transmit Packet Formats
These sections describe the formats in which packets need to be delivered to the queues (FIFOs) for transmission. There are four basic formats
as follows:
Each packet format uses several fields (see names and descriptions below). More information about these fields (not the format) can be found
in the 1394 specification. Grey fields are reserved and should be set to zero values.
12.5.1.1 No-data Transmit
The no-data transmit formats are shown in Figures 6 and 7. The first quadlet contains packet control information. The second and third quadlets
contain 16-bit destination ID and either the 48-bit, quadlet aligned destination offset (for requests) or the response code (for responses).
Figure 7. Quadlet/Block Write Response Packet Transmit Format
13
SV00250
SV00249
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
Table 1. No-Data Transmit Format
Field NameDescription
spdThis field indicates the speed at which this packet is to be sent. 00=100 Mbs, 01=200 Mbs, and 10=400 Mbs.
tLabelThis field is the transaction label, which is used to pair up a response packet with its corresponding request packet.
rtThe retry code for this packet. Supported values are: 00=retry1, and 01=retryX.
tCodeThe transaction code for this packet.
DestinationIDContains a node ID value.
DestinationOffsetHigh
DestinationOffsetLow
rCodeResponse code for write response packet.
11 = undefined
The concatenation of these two field addresses a quadlet in the destination node’s address space.
rCodeMeaning
0Node successfully completed requested operation.
1–3Reserved
4Resource conflict detected by responding agent. Request may be retried.
5Hardware error. Data not available.
6Field within request packet header contains unsupported or invalid value.
7Address location within specified node not accessible.
8–FhReserved
12.5.1.2 Quadlet Transmit
Three quadlet transmit formats are shown below. In these figures: The first quadlet contains packet control information. The second and third
quadlets contain 16-bit destination ID and either the 48-bit quadlet-aligned destination offset (for requests) or the response code (for responses).
The fourth quadlet contains the quadlet data for read response and write quadlet request formats, or the upper 16 bits contain the data length
for the block read request format.
Quadlet dataFor quadlet write requests and quadlet read responses, this field holds the data to
Data lengthThe number of bytes requested in a block read request.
1999 Aug 06
See Table 1.
be transferred.
15
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.5.1.3 Block Transmit
The block transmit format is shown below, this is the generic format for reads and writes. The first quadlet contains packet control information.
The second and third quadlets contain the 16-bit destination node ID and either the 48-bit destination offset (for requests) or the response code
and reserved data (for responses). The fourth quadlet contains the length of the data field and the extended transaction code (all zeros except
for lock transaction). The block data, if any, follows the extended transaction code.
dataLengthThe number of bytes of data to be transmitted in this packet
extendedTcodeThe tCode indicates a lock transaction, this specifies the actual lock action to be
block dataThe data to be sent. If dataLength=0, no data should be written into the FIFO for
paddingIf the dataLength mod 4 is not zero, then zero-value bytes are added onto the end
12.5.1.4 Unformatted Transmit
The unformatted transmit format is shown in Figure 13. The first quadlet contains packet control information. The remaining quadlets contain
data that is transmitted without any formatting on the bus. No CRC is appended on the packet, nor is any data in the first quadlet sent. This is
used to send PHY configuration and Link-on packets. Note that the bit-inverted check quadlet must be included in the FIFO since the AV Link
core will not generate it.
See Table 2.
performed with the data in this packet.
this field. Regardless of the destination or source alignment of the data, the first
byte of the block must appear in the high order byte of the first quadlet.
of the packet to guarantee that a whole number of quadlets is sent.
Each packet format uses several fields. More information about most of these fields can be found in the 1394 specification.
1999 Aug 06
17
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
Table 5. Asynchronous Receive Fields
Field NameDescription
destinationIDThis field is the concatenation of busNumbers (or all ones for “local bus”) and nodeNumbers (or all ones for
tLabelThis field is the transaction label, which is used to pair up a response packet with its corresponding request packet.
rtThe retry code for this packet. 00=retry1, 01=retryX, 10=retryA, 11=retryB.
tCodeThe transaction code for this packet.
priorityThe priority level for this packet (0000 for cable environment).
sourceIDThis is the node ID of the sender of this packet.
destinationOffsetHigh,
destinationOffsetLow
rCodeResponse code for response packets.
quadlet dataFor quadlet write requests and quadlet read responses, this field holds the data received.
dataLengthThe number of bytes of data to be received in a block packet.
extendedTcodeIf the tCode indicates a lock transaction, this specifies the actual lock action to be performed with the data in this
block dataThe data received. If dataLength=0, no data will be written into the FIFO for this field. Regardless of the destination
paddingIf the dataLength mod 4 is not zero, then zero-value bytes are added onto the end of the packet to guarantee that a
uUnsolicited response tag bit. This bit is set to one (1) if the received response was unsolicited.
ackSentThis field contains the acknowledge code that the link layer returned to the sender of the received packet. For
broadcast) for this node.
The concatenation of these two field addresses a quadlet in this node’s address space.
packet.
or source alignment of the data, the first byte of the block will appear in the high order byte of the first quadlet.
whole number of quadlets is sent.
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
CodeNameDescription
0001ack_completeThe node has successfully accepted the packet. If the packet was a request subaction, the
0010ack_pendingThe node has successfully accepted the packet. If the packet was a request subaction, a response
0100ack_busy_XThe packet could not be accepted. The destination transaction layer may accept the packet on a
0101ack_busy_AThe packet could not be accepted. The destination transaction layer will accept the packet when the
0110ack_busy_BThe packet could not be accepted. The destination transaction layer will accept the packet when the
1101ack_data_errorThe node could not accept the block packet because the data field failed the CRC check, or because
1110ack_type_errorA field in the request packet header was set to an unsupported or incorrect value, or an invalid
0000, 0011,
0111 – 1100,
and 1111
NOTE:
1. Upon receipt of a broadcast packet, if any ACK code other than ACK_DATA_ERROR is produced, asume packet receipt was OK.
ACK_DATA ERROR indicates the packet was received with an error, appropriate steps should be taken to ignore the packet and inform the
sending node of the error.
reservedThis revision of the AV Link will not generate other acknowledge codes, but may receive them from
destination node has successfully completed the transaction and no response subaction shall follow.
subaction will follow at a later time. This code shall not be returned for a response subaction.
retry of the subaction.
node is not busy during the next occurrence of retry phase A.
node is not busy during the next occurrence of retry phase B.
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.
transaction was attempted (e.g., a write to a read-only address).
newer (1394 A) links. In that case, these new values will show up here.
1999 Aug 06
18
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.5.2.1 No-Data Receive
The no-data receive formats are shown below. The first quadlet contains the destination node ID and the rest of the packet header. The second
and third quadlet contain 16-bit source ID and either the 48-bit, quadlet-aligned destination offset (for requests) or the response code (for
responses). The last quadlet contains packet reception status.
PDI1394L211394 full duplex AV link layer controller
12.5.2.2 Quadlet Receive
The quadlet receive formats are shown below. The first quadlet contains the destination node ID and the rest of the packet header. The second
and third quadlets contain 16-bit source ID and either the 48-bit, quadlet-aligned destination offset (for requests) or the response code (for
responses). The fourth quadlet is the quadlet data for read responses and write quadlet requests, and is the data length and reserved for block
read requests. The last quadlet contains packet reception status.
The block receive format is shown below. The first quadlet contains the destination node ID and the rest of the packet header. The second and
third quadlets contain 16-bit sourceID and either the 48-bit destination offset (for requests) or the response code and reserved data (for
responses). The fourth quadlet contains the length of the data field and the extended transaction code (all zeros except for lock transactions).
The block data, if any, follows the extended code. The last quadlet contains packet reception status.
Figure 20. Block Read or Lock Response Receive Format
12.5.2.4 Self-ID and PHY packets receive
The self-ID and PHY packet receive formats are shown below. The first quadlet contains a synthesized packet header with a tCode of 0xE
(hex). For self-ID information, the remaining quadlets contain data that is received from the time a bus reset ends to the first subaction gap. This
is the concatenation of all the self-ID packets received. Note that the bit-inverted check quadlet is included in the Read Request FIFO and the
application must check it.
The “ackSent” field will either be “ACK_DATA_ERROR” if a non-quadlet-aligned packet is received or there was a data overrun, or
“ACK_COMPLETE” if the entire string of self-ID packets was received.
1999 Aug 06
22
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
For PHY packets, there is a single following quadlet which is the first quadlet of the PHY packet. The check quadlet has already been verified
and is not included.
12.5.2.5 Transaction data confirmation formats
After a packet from one of the queues has been transmitted, the asynchronous transmitter assembles a confirmation (see Figure 23) which is
used to confirm the result of the transmission to the higher layers. Separate confirmations are assembled for request and response
transmissions. Request confirmations are written into the receiver request queue and response confirmations are written into the receiver
response queue.
Figure 23. Request and response confirmation format
Table 7. Confirmation codes
1
CODE
0Non-broadcast packet transmitted; addressed node returned no acknowledge (transaction complete).
1Broadcast packet transmitted or non-broadcast packet transmitted; addressed node returned an acknowledge complete
2Non-broadcast packet transmitted; addressed node returned an acknowledge pending.
4Retry limit exceeded; destination node hasn’t accepted the non-broadcast packet within the maximum number of retries
D
16
E
16
NOTE:
1. All other codes are reserved.
For every packet written in a transmitter queue by the CPU, there will be one confirmation written in the corresponding receiver queue by the AV
layer logic.
DESCRIPTION
(transaction complete).
(transaction complete).
Acknowledge data error received (transaction complete).
Acknowledge type error received (transaction complete).
1999 Aug 06
23
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
12.5.3 Interrupts
The PDI1394L21 provides a single interrupt line (HIF INT_N) for connection to a host controller. Status indications from four major areas of the
device are collected and ORed together to activate HIF INT_N. Status from four major areas of the device are collected in four status registers;
LNKPHYINTACK, ITXINTACK, IRXINTACK, and ASYINTACK. At this level, each individual status can be enabled to generate a chip-leve l
interrupt by activating HIF INT_N. To aid in determining the source of a chip-level interrupt, the major area of the device generating an interrupt
is indicated in the lower 4 bits of the GLOBCSR register. These bits are non-latching Read-Only status bits and do not need to be
acknowledged. To acknowledge and clear a standing interrupt, the bit in LNKPHYINTACK, ITXINTACK, IRXINTACK, or ASYINTACK causing
the interrupt status has to be written to a logic ‘1’; Note: Writing a value of ‘0’ to the bit has no effect.
12.5.3.1 Determining and Clearing Interrupts
When responding to an interrupt event generated by the PDI1394L21, or operating in polled mode, the first register examined is the GLOBCSR
register. The least significant nibble contains interrupt status bits from general sections of the device; the link layer controller, the AV transmitter,
the AV receiver, and the asynchronous transceiver. The bits in GLOBCSR[3:0] are self clearing status bits. They represent the logical OR of all
the enabled interrupt status bits in their section of the AV Link Layer Controller.
Once an interrupt, or status is detected in GLOBCSR, the appropriate interrupt status register needs to be read, see the Interrupt Hierarchy
diagram for more detail. After all the interrupt indications are dealt with in the appropriate interrupt status register, the interrupt status indication
will automatically clear in the GLOBCSR.
All interrupt status bits in the various interrupt status registers are latching unless otherwise noted.
12.5.3.2 Interrupt Hierarchy
HIF INT_N
3210
ITXINT
IRXINT
ASYTX/RX
GLOBCSR (0x018)
LNKPHYINT
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
ITBADFMT
CMDRST
PHYINT
FAIRGAP
ARBGAP
76543210
8
9
10
IRXFULL
IR512LFT
IR256LFT
IR100LFT
6543210
7
8
9
IT512LFT
IT256LFT
IT100LFT
TRMSYT
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
PHYRRX
PHYRST
FSYNC
SEQERR
IRXEMPTY
DBCERR
TRMBP
INPERR
RxDATA
ATBADFMT
CIPTAGFLT
CRCERR
RCVBP
ITXFULL
DISCARD
ITXEMPTY
CYTMOUT
SNT_REJ
HDRERR
TCERR
CYSEC
IRXINTACK (0x04C)
SQOV
ITXINTACK (0x02C)
CYSTART
CYDONE
LNKPHYINTACK (0x008)
CYLOST
CYPEND
1999 Aug 06
RRSPQFULL
RREQQFULL
SIDQAV
RRSPQLASTQ
RREQQLASTQ
RRSPQRDERR
RREQQRDERR
RRSPQQAV
RREQQQAV
TIMEOUT
RCVDRSP
TRSPQFULL
TREQQFULL
Figure 24. Interrupt Hierarchy
24
TREQQWR
TRSPQWR
TRSPQWRERR
TREQQWRERR
ASYINTACK (0x0A0)
SV01076
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.0 REGISTER MAP
Registers are 32 bits (quadlet) wide and all accesses are always done on a quadlet basis. This means that it is not possible to write just the
lower 8 bits, and leave the other bits unaffected (see Section 12.3.2 for more information). The values written to undefined fields/bits are ignored
and thus DON’T CARE.
A full bitmap of all registers is listed in Table 8. The meaning of shading and bit cell values is as follows:
A bit/field with no name written in it and dark shading is reserved and not used.
A bit/field with a name in it and light shading is a READ ONLY (status) bit/field.
A one bit value (0 or 1) written at the bottom of a writeable (control) bit is the default value after power-on-reset.
Table 8. Full Bitmap of all Registers (consists of three tables shown on the following pages)
1999 Aug 06
25
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
REGISTER
ADDRESS
LNKCTL
LNKPHYINTACK
LNKPHYINTE
CYCTM
PHYACS
IDREG
0x000
0x004
0x008
0x00C
0x010
0x014
31
BSYCTRL
IDVALID
RCVSELFID
CYCLE_SECONDSCYCLE_NUMBER
WRPHY
RDPHY
00
24 2316 158 70
NODE IDBUS ID
RST Tx
TxENABLE
PHYRGAD
RxENABLE
RST Rx
00000 1 101
PHYRGDATA
FAIRGAP
CMDRST
000 00 0 00 00 0 00 0000
ECMDRST
EFAIRGAP
000 00 0 00 00 0 00000
000 0 0000 0 0 00 0 00000000 0000 0 000000
000 0000 00000
PHYINT
ARBGAP
EARBGAP
EPHYINT
PART CODE
0000
PHYRST
PHYRRX
EPHYRST
EPHYRRX
VERSION CODE
CYMASTER
CYSOURCE
STRICTISOCH
CYTMREN
RxDATA
ITBADFMT
ATBADFMT
0
EITBADFMT
ERxDATA
EATBADFMT
0
PHYRXADPHYRXDATA
TxRDY
ROOT
0
SNT_REJ
ESNT_REJ
CYCLE_OFFSET
HDRERR
TCERR
ETCERR
EHDRERR
CYTMOUT
ECYTMOUT
ATACK
BUSYFLAG
CYSEC
CYDONE
CYSTART
ECYSEC
ECYSTART
ECYDONE
0
11
CYLOST
CYPEND
ECYLOST
ECYPEND
GLOBCSR
0x018
<RESERVED>
0x01C
ITXPKCTL
0x020
ITXHQ1
0x024
ITXHQ2
0x028
ITXINTACK
0x02C
ITXINTE
0x030
DIRAV1
ENOUTAV2
ENOUTAV1
00
10000
TXAP_CLK
00
FMTFDFSYT
0000 000 0 0 0000
000 0 000 0000000 000000
FNDBS
QPC
000 0 0000000000
0000 000 000 00 00000
EITXINT
EIRXINT
EASYTX/RX
SPH
IT100LFT
0
EIT100LFT
0
ELNKPHYINT
ENXTMSTP
SYT_DELAY
0
00
TRMSYT
IT256LFT
0
EIT256LFT
0
TRMBP
IT512LFT
00 0 00 0 0
0
EIT512LFT
ETRMBP
ETRMSYT
0
00 0 00 0 0
ASYTX/RX
PMTRDELMAXBL
EN_ITX
00
DISCARD
DBCERR
INPERR
EINPERR
EDBCERR
SV00883
ITXINT
IRXINT
LNKIPHYINT
EN_FS
RST_ITX
010
ITXEMPTY
ITXFULL
EITXFULL
EDISCARD
EITXEMPTY
1999 Aug 06
26
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
REGISTER
ADDRESS
<RESERVED>
ITXCTL
0x034
ITXMEM
0x038
0x03C
IRXPKCTL
0x040
IRXHQ1
0x044
IRXHQ2
0x048
24 2316 158 7031
TAGCHANNEL
0000000000 000
RXAP_CLK
00
SID
F0
E0
F1
E1
FMTSYTFDF
QPCFNDBS
0
SPH
SPD
ITM512LFT
ITM100LFT
ITM256LFT
ITXMF
BPAD
DIS_TSC
SPAV
EN_IRX
RMVUAP
SNDIMM
0
100001
ODD/EVEN
ITXMAF
ITXM5AV
EN_FS
ITXME
RST_IRX
IRXINTACK
0x04C
IRXINTE
0x050
IRXCTL
0x054
IRXMEM
0x058
<RESERVED>
0x05C
.
.
.
<RESERVED>
0x07C
IR256LFT
IR100LFT
0
0
0
EIR256LFT0EIR512LFT
EIR100LFT
0
0
TAGCHANNELERRSPD
000 0 0000
IRXFULL
IR512LFT
FSYNC
IRXEMPTY
00000000
EFSYNC
EIRXFULL
EIRXEMPTY
00000000
IRM100LFT
IRM256LFT
CIPTAGFLT
CRCERR
SEQERR
ECRCERR
ECIPTAGFLT
ESEQERR
IRM512LFT
IRXMAF
IRXMF
SQOV
RCVBP
ERCVBP
ESQOV
ODD/EVEN
IRXM5AV
IRXME
1999 Aug 06
SV00884
27
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
REGISTER
ADDRESS
TX_RQ_NEXT
TX_RQ_LAST
TX_RP_NEXT
TX_RP_LAST
ASYCTL
0x080
ASYMEM
0x084
0x088
0x08C
0x090
0x094
31
24 2316 158 70
MAXRCTOSTOF
ATXRST
ARXRST
DIS_BCAST
0
FIRST/MIDDLE QUADLET OF PACKET FOR TRANSMITTER REQUEST QUEUE
LAST QUADLET OF PACKET FOR TRANSMITTER REQUEST QUEUE
FIRST/MIDDLE QUADLET OF PACKET FOR TRANSMITTER RESPONSE QUEUE
LAST QUADLET OF PACKET FOR TRANSMITTER RESPONSE QUEUE
ARXALL
011000 000000011001 00000
RRSPQF
RRSPQAF
TRSPQIDLE
TREQQIDLE
(WRITE ONLY)
(WRITE ONLY)
(WRITE ONLY)
(WRITE ONLY)
RRSPQ5AV
RRSPQE
RREQQF
RREQQAF
RREQQ5AV
RREQQE
TRSPQF
TRSPQAF
TRSPQ5AV
TRSPQE
TREQQF
TREQQAF
TREQQ5AV
TREQQE
RREQ
0x098
RRSP
0x09C
ASYINTACK
0x0A0
ASYINTE
0x0A4
<RESERVED>
0x0A8
.
.
.
<RESERVED>
0x0F8
QUADLET OF PACKET FROM RECEIVER REQUEST QUEUE (TRANSFER REGISTER)
QUADLET OF PACKET FROM RECEIVER RESPONSE QUEUE (TRANSFER REGISTER)
SIDQAV
RRSPQFULL
0000 000 000 00 00000
ERRSPQFULL
0000 000 000 00 00000
RRSPQLASTQ
RREQQFULL
ESIDQAV
ERREQQFULL
ERRSPQLASTQ
RREQQLASTQ
RRSPQRDERR
RREQQRDERR
ERREQQLASTQ
ERRSPQRDERR
ERREQQRDERR
TIMEOUT
RCVDRSP
RRSPQQAV
RREQQQAV
ERRSPQQAV
ERREQQQAV
TRSPQFULL
ETIMEOUT
ETRSPQFULL
ERCVDRSP
TRSPQWRERR
TREQQFULL
TREQQWRERR
ETRSPQWRERR
ETREQQFULL
ETREQQWRERR
TRSPQWR
TREQQWR
ETRSPQWR
ETREQQWR
1999 Aug 06
SV00914
28
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.1 Link Control Registers
13.1.1 ID Register (IDREG) – Base Address: 0x000
The ID register is automatically updated by the attached PHY with the proper Node ID after completion of the bus reset.
Reset Value 0xFFFF0101
Bit 31..22: R/WBUS ID: The 10-bit bus number that is used with the Node ID in the source address for outgoing packets and used to
accept or reject incoming packets. This field reverts to all ‘1’s (0x3FF) upon bus reset.
Bit 21..16:R/WNODE ID: Used in conjunction with Bus ID in the source address for outgoing packets and used to accept or reject
incoming packets. This register auto-updates with the node ID assigned after the 1394 bus Tree-ID sequence.
Bit 15..8:RPAR T CODE: “01” designates PDI1394L21.
Bit 7..0:RVERSION CODE: “02” shows this is revision level 2 of this part.
13.1.2 General Link Control (LNKCTL) – Base Address: 0x004
The General Link control register is used to program the Link Layer isochronous transceiver, as well as the overall link transc eiver. It also
provides general link status.
Reset Value 0x46000002
Bit 31:R/WIDValid (IDVALID): When equal to one, the PDI1394L21 accepts the packets addressed to this node. This bit is
automatically set after selfID complete and node ID is updated.
Bit 30:R/WReceive Self ID (RCVSELFID): When asserted, the self-identification packets, generated by each PHY device on the
bus, during bus initialization are received and placed into the asynchronous request queue as a single packet. Bit 30
also enables the reception of PHY configuration packets in the asynchronous request queue.
Bit 29..27:R/WBusy Control (BSYCTRL): These bits control what busy status the chip returns to incoming packets. The field is
defined below:
000 = use protocol requested by received packet (either dual phase or single phase)
001 = send busy A when it is necessary to send a busy acknowledge (testing/diagnostics)
010 = send a busy B when it is necessary to send a busy acknowledge (testing/diagnostics)
011 = use single phase retry protocol
100 = use protocol requested in packet, always send a busy ack (for all packets)
101 = busy A all incoming packets
110 = busy B all incoming packets are ‘1’
111 = use single phase retry protocol, always send a busy ack
Bit 26:R/WTransmitter Enable (TxENABLE): When this bit is set, the link layer transmitter will arbitrate and send packets.
Bit 25:R/WReceiver Enable (RxENABLE): When this bit is set, the link layer receiver will receive and respond to bus packets.
Bit 21:R/WReset Transmitter (RSTTx): When set to one, this synchronously resets the transmitter within the link layer.
Bit 20:R/WReset Receiver (RSTRx): When set to one, this synchronously resets the receiver within the link layer.
Bit 12:R/WStrict Isochronous (STRICTISOCH): Used to accept or reject isochronous packets sent outside of specified
isochronous cycles (between a Cycle Start and subaction gap). A ‘1’ rejects packets sent outside the specified
cycles, a “0” accepts isochronous packets sent outside the specified cycle.
Bit 11:R/WCycle Master (CYMASTER): When asserted and the PDI1394L21 is attached to the root PHY (ROOT bit = 1), and
the cycle_count field of the cycle timer register increments, the transmitter sends a cycle-start packet. Cycle Master
function will be disabled if a cycle timeout is detected (CYTMOUT bit 5 in LNKPHYINTACK). To restart the Cycle
Master function in such a case, first reset CYMASTER, then set it again.
1999 Aug 06
29
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
Bit 10:R/WCycle Source (CYSOURCE): When asserted, the cycle_count field increments and the cycle_offset field resets for
each positive transition of CYCLEIN. When deasserted, the cycle count field increments when the cycle_offset field
rolls over.
Bit 9:R/WCycle Timer Enable (CYTIMREN): When asserted, the cycle offset field increments.
Bit 6:RTransmitter Ready (TxRDY): The transmitter is idle and ready .
Bit 5:RRoot (ROOT): Indicates this device is the root on the bus. This automatically updates after the self_ID phase.
Bit 4:RBusy Flag (BUSYFLAG): The type of busy acknowledge which will be sent next time an acknowledge is required.
0 = Busy A, 1 = Busy B (only meaningful during a dual-phase busy/retry operation).
Bit 3..0:RAT acknowledge received (ATACK): The last acknowledge received by the transmitter in response to a packet sent
from the transmit-FIFO interface while the ATF is selected (diagnostic purposes).
13.1.3 Link /Phy Interrupt Acknowledge (LNKPHYINTACK) – Base Address: 0x008
The Link/Phy Interrupt Acknowledge register indicates various status and error conditions in the Link and Phy which can be programmed to
generate an interrupt. The interrupt enable register (LNKPHYINTE) is a mirror of this register. Acknowledgment of an interrupt is accomplished
by writing a ‘1’ to a bit in this register that is set. This action reset the bit indication to a ‘0’. Writing a ‘1’ to a bit that is already “0” will have no
effect on the register.
Reset Value 0x00000000
Bit 18: R/WCommand Reset Received (CMDRST): A write request to RESET-START has been received.
Bit 17:R/WFair Gap (FAIRGAP): The serial bus has been idle for a fair-gap time (called subaction gap in the IEEE 1394
specification).
Bit 16:R/WArbitration Reset Gap (ARBGAP): The serial bus has been idle for an arbitration reset gap.
Bit 15:R/WPhy Chip Int (PHYINT): The Phy chip has signaled an interrupt through the Phy interface. This bit becomes active for
any of the following reasons (1) PHY has detected a loop on the bus, (2) cable power has fallen below the minimum
voltage, (3) the PHY arbitration state machine has timed-out usually indicative of a bus loop, (4) a bus cable has
been disconnected. Typically, recognition and notification of any of the above events by the PHY requires between
166 and 500 microseconds; therefore, this bit is not instantaneously set.
Bit 14:R/WPhy Register Information Received (PHYRRX): A register has been transferred by the Physical Layer device into the
Link.
Bit 13:R/WPhy Reset Started (PHYRST): A Phy-layer reconfiguration has started. This interrupt clears the ID valid bit. (Called
Bus Reset in the IEEE 1394 specification).
Bit 11:R/WReceiver has data (RxDATA): The receiver has confirmed data to the receiver response/request FIFO.
Bit 10:R/WIsochronous Transmitter is Stuck (ITBADFMT): The transmitter has detected invalid data at the transmit-FIFO
interface when the ITF is selected.
Bit 9:R/WAsynchronous Transmitter is Stuck (ATBADFMT): The transmitter expected start of new async packet in queue, but
found other data (out of sync with user). Reset to clear.
Bit 8:R/WBusy Acknowledge Sent by Receiver (SNT_REJ): The receiver was forced to send a busy acknowledge to a packet
addressed to this node because the receiver response/request FIFO overflowed.
Bit 7:R/WHeader Error (HDRERR): The receiver detected a header CRC error on an incoming packet that may have been
addressed to this node.
Bit 6:R/WTransaction Code Error (TCERR): The transmitter detected an invalid transaction code in the data at the transmit
FIFO interface.
Bit 5:R/WCycle Timed Out (CYTMOUT): ISOCH cycle lasted more than 125µs from Cycle-Start to Fair Gap: Disables cycle
master function
Bit 4:R/WCycle Second incremented (CYSEC): The cycle second field in the cycle-timer register incremented. This occurs
approximately every second when the cycle timer is enabled.
Bit 3:R/WCycle Started (CYSTAR T): The transmitter has sent or the receiver has received a cycle start packet.
Bit 2:R/WCycle Done (CYDONE): A fair gap has been detected on the bus after the transmission or reception of a cycle start
packet. This indicates that the isochronous cycle is over; Note: Writing a value of ‘0’ to the bit has no effect.
Bit 1:R/WCycle Pending (CYPEND): Cycle pending is asserted when cycle timer offset is set to zero (rolled over or reset) and
stays asserted until the isochronous cycle has ended.
Bit 0:R/WCycle Lost (CYLOST): The cycle timer has rolled over twice without the reception of a cycle start packet. This only
occurs when cycle master is not asserted.
1999 Aug 06
30
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.1.4 Link / Phy Interrupt Enable (LNKPHYINTE) – Base Address: 0x00C
This register is a mirror of the Link/Phy Interrupt Acknowledge (LNKPHYINTACK) register. Enabling an interrupt is accomplished by writing a ‘1’
to the bit corresponding to the interrupt desired.
This register enables the interrupts described in the Link /Phy Interrupt Acknowledge register (LNKPHYINTACK) description. A one in any of the
bits enables that function to create an interrupt. A zero disables the interrupt, however the status is readable in the Link /Phy Interrupt
Acknowledge register.
Reset Value 0x00000000
Bit 31..25: R/W Seconds count: 1-Hz cycle timer counter.
Bit 24..12:R/WCycle Number: 8kHz cycle timer counter.
Bit 11..0:R/WCycle Offset: 24.576MHz cycle timer counter.
13.1.6 Phy Register Access (PHYACS) – Base Address: 0x014
This register provides access to the internal registers on the Phy. There are special considerations when reading or writing to this register. When
reading a PHY register, the address of the register is written to the PHYRGAD field with the RDPHY bit set. The PHY data will be valid when the
PHYRRX bit (LNKPHYINTACK register bit 14) is set. Once this happens the register data is available in the PHYRXDATA, the address of the
register just read is also available in the PHYRXAD fields. When writing a Phy register, the address of the register to be written is set in the
PHYRGAD field and the data to be written to the register is set in PHYRGDATA, along with the WRPHY bit being set. Once the write is
complete, the WRPHY bit will be cleared. Do not write a new Read/Write command until the previous one has been completed. After the Self-ID
phase, PHY register 0 will be read automatically.
Reset Value 0x00000000
Bit 31: R/W Read Phy Chip Register (RDPHY): When asserted, the PDI1394L21 sends a read register request with address
equal to Phy Rg Ad to the Phy interface. This bit is cleared when the request is sent.
Bit 30:R/WWrite Phy Chip Register (WRPHY): When asserted, the PDI1394L21 sends a write register request with address
equal to Phy Rg Ad to the Phy interface. This bit is cleared when the request is sent.
Bit 27..24:R/WPhy Chip Register Address (PHYRGAD): This is the address of the Phy-chip register that is to be accessed.
Bit 23..16:R/WPhy Chip Register Data (PHYRGDATA): This is the data to be written to the Phy-chip register indicated in Phy Rg Ad.
Bit 11..8:RPhy Chip Register Received Address (PHYRXAD): Address of register from which Phy Rx Data came.
Bit 7..0:RPhy Chip Register Received Data (PHYRXDATA): Data from register addressed by Phy Rx Ad.
1999 Aug 06
31
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.1.7 Global Interrupt Status and TX Control (GLOBCSR) – Base Address: 0x018
This register is the top level interrupt status register. If the external interrupt line is set, this register will indicate which major portion of the AV
Link generated the interrupt. There is no interrupt acknowledge required at this level. These bits auto clear when the interrupts in the
appropriate section of the device are cleared or disabled. Control of the AV transceiver is also provided by this register.
Bits 0 to 3 are used to identify which internal modules are currently generating an interrupt. After identifying the module, the appropriate register
in that module must be read to determine the exact cause of the interrupt.
NOTES
1. There can be more than one interrupt source active at the same time.
2. The HIF INT_N signal (pin 28) remains active as long as there is at least one more enabled active interrupt status bit.
Reset Value 0x00010000
Bit 18:R/WEnable output AVPOR T2: A ‘1’ enables AVPORT2 as an output. A ‘0’ sets the 3-State condition on the port. In
3-State condition the port may be used as an input or unused output according to the state of DIRAV1 (bit 16).
Bit 17:R/WEnable output AVPOR T1: A ‘1’ enables AVPORT1 as an output. A ‘0’ sets the 3-State condition on the port. In
3-State condition the port may be used as an input or unused output according to the state of DIRAV1 (bit 16).
Bit 16: R/W Direction of AVPORT1 (DIRAV1): A ‘1’ enables AVPORT1 as a transmitter, thus AVPORT1 pins are inputs. A ‘0’
configures AVPOR T1 as a receiver, AVPORT1 pins are outputs in this configuration. The configuration of AVPORT2
pins is opposite
of AVPORT1 pins. When AVPORT1 is set to transmit, AVPORT2 receives and vice versa.
Bit 11:R/WEnables generation of external interrupt by asynchronous transmitter and receiver module (ASYTX/RX, bit 3) when
set (1). Disables such interrupts when clear (0) (regardless of ASYINTE contents).
Bit 10:R/WEnables generation of external interrupt by the isochronous transmitter module (ITXINT , bit 2) when set (1).
Disables such interrupts when clear (0) (regardless of ITXINTE contents).
Bit 9:R/WEnables generation of external interrupt by the isochronous receiver module (IRXINT, bit 1) when set (1).
Disables such interrupts when clear (0) (regardless of IRXINTE contents).
Bit 8:R/WEnables generation of external interrupt by general link/phy module (LKPHYINT, bit 0) when set (1). Disables such
interrupts when clear (0) (regardless of LNKPHYINTE contents).
Bit 3:RAsynchronous Transmitter/Receiver Interrupt (ASYITX/RX): Interrupt source is in the Asynchronous Transmitter/
Receiver Interrupt Acknowledge/Source register.
Bit 2:RAV Transmitter Interrupt (ITXINT): Interrupt source is in the AV Transmitter Interrupt Acknowledge/Source register.
Bit 1:RAV Receiver Interrupt (IRXINT): Interrupt source is in the AV Receiver Interrupt Acknowledge/Source register.
Bit 0:RLink-Phy Interrupt (LNKPHYINT): Interrupt source is in the Link Phy Interrupt Acknowledge register.
1999 Aug 06
32
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2 AV (Isochronous) Transmitter and Receiver Registers
13.2.1 Isochronous Transmit Packing Control and Status (ITXPKCTL) – Base Address: 0x020
This register allows the user to set up the appropriate AV packets from data entered into the AV interface. The packing and control parameters
(TRDEL, MAXBL, DBS, FN, QPC, and SPH) should never be changed while the transmitter is operating. The only exception to this is the
MAXBL parameter when in MPEG-2 packing mode.
NOTE: When reset of isochronous transmitter is necessary, first disable the transmitter (place bit 4, EN_ITX, LOW), wait for FIFO to empty, then
reset the transmitter (place RST_ITX, bit 0, HIGH). This procedure will ensure that data in the FIFO is transmitted before reset.
Reset Value 0x00000001
Bit 29..28: R/W TXAP_CLK: Application Clock, default mode, ‘00’ the AVxCLK pin is an input. This pin can become an applicatio n
clock for the isochronous Transmitter (and output) by programming it to ‘01’, ‘10’, or ‘11’.
The programming values are:
00Input
0124.576MHz
1012.288MHz
116.144MHz
Note that when enabled as ‘01’, ‘10’, or ‘11’, the AV port that is configured as transmitter and enabled will output this
clock signal on its AVxCLK pin.
Bit 27..16: R/W TRDEL: Transport delay. Value added to cycle timer to produce time stamps. Lower 4 bits add to upper 4 bits of
cycle_offset, (Cycle Timer Register, CYCTM). Remainder adds to cycle_count field.
Bit 15..8:R/WMAXBL: The (maximum) number of data blocks to be put in a payload.
Bit 7:R/WENXTMSTP: Enable External time stamp control. Allows an external time stamp (generated by the application) to be
inserted in place of the link-generated time stamp. Defaults to link generated time stamp. The application must
present the first byte of a quadlet-wide time stamp accompanied by the AVSYNC pulse (and AVVALID) to the
AVPOR T. The external time stamp quadlet is inputted first, followed by the application data packet. The transmitted
packet size is now one quadlet larger than the original isochronous data packet—Set up the isochronous
transmitter accordingly with SPH = 1. CAUTION: Unless valid IEC 61883 time stamp format (based on the link cycle
timer) is used, the receiving node link chip must
be equipped with a time stamp check disabling function similar to
the DIS_TSC bit (register 0X040, Bit 7). Please see section 13.2.8 for details.
Bit 6..5:R/WSYT_DELAY: Programmable delay of AV1FSYNC and AV2FSYNC. Each cycle is 1 bus cycle, 125 ms.
Bit 4:R/WEN_ITX: Enable receipt of new application packets and generation of isochronous bus packets in every cycle. This
bit also enables the Link Layer to arbitrate for the transmitter in each subsequent bus cycle. When this bit is disabled
(0), the current packet will be transmitted and then the transmitter will shut down.
Bit 3..2:R/WPM: packing mode:
00 = variable sized bus packets, most generic mode.
01 = fixed size bus packets.
10 = MPEG–2 packing mode.
11 = No data, just CIP headers are transmitted.
Bit 1:R/WEN_FS:enable generation/insertion of SYT stamps (Time Stamps) in CIP header.
Bit 0:R/WReset Isochronous Transmitter (RST_ITX): causes transmitter to be reset when ‘1’. In order for synchronous reset of
ITX to work properly, an AVxCLK (from either the internal or external source) must be present and ensure that the
reset bit is kept (programmed) HIGH for at least the duration of one AVxCLK period. Failure to do so may cause
the application interface of this module to be improperly reset (or not reset at all). When reset is enabled, all bytes
will be flushed from the FIFO and transmission will cease immediately.
EN_ITX
SV00886
EN_FS
RST_ITX
1999 Aug 06
33
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.2 Common Isochronous Transmit Packet Header Quadlet 1 (ITXHQ1) – Base Address: 0x024
The AV Transmit Packing Control register holds the specification for the packing scheme used on the AV data stream. This information is
included in Common Isochronous Packet (CIP) header quadlet 1.
Reset Value 0x00000000
Bit 16..23:R/WDBS: Size of the data blocks from which AV payload is constructed. The value 0 represents a length of 256 quadlets.
Bit 14..15:R/WFN: (Fraction Number) The encoding for the number of data blocks into which each source packet shall be divided
(00 = 1, 01 = 2, 10 = 4, 11 = 8).
Bit 11..13:R/WQPC: Number of dummy quadlets to append to each source packet before it is divided into data blocks of the
specified size. The value QPC must be less than DBS and less than 2FN.
Bit 10: R/W SPH: Indicates that a 25-bit CYCTM based time stamp has to be inserted before each application packet.
13.2.3 Common Isochronous Transmit Packet Header Quadlet 2 (ITXHQ2) – Base Address: 0x028
The contents of this register are copied to the second quadlet of the CIP header and transmitted with each isochronous packet.
Reset Value 0x00000000
Bit 29..24: R/W FMT: Value to be inserted in the FMT field in the AV header.
Bit 23..0:R/WFDF/SYT: Value to be inserted in the FDF field. When the EN_FS bit in the Transmit Control and Status Register
(ITXPKCTL) is set (=1), the lower 16 bits of this register are replaced by an SYT stamp if a rising edge on
AVFSYNCIN has been detected or all ‘1’s if no such edge was detected since the previous packet. The upper 8 bits
of the register are sent as they appear in the FDF register. When the EN_FS bit in the Transmit Control and Status
Register is unset (=0), the full 24 bits can be set to any application specified value.
1999 Aug 06
34
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.4 Isochronous Transmitter Interrupt Acknowledge (ITXINTACK) – Base Address: 0x02C
The AV Transmitter Interrupt Control and Status register is the interrupt register for the AV transmitter.
Bits 2, 3, and 4 ”auto repair” themselves, i.e. AVLINK will detect the situation and attempt to recover on its own. The host controller still needs to
clear these interrupts to be alerted the next time.
Bits 9 .. 0 are interrupt acknowledge bits; and are defined as:
Bit 9:R/WIT100LFT: Interrupt when transmitter queue reaches 100 quadlets from full. (924 of 1024 quadlets in queue)
Bit 8:R/WIT256LFT: Interrupt when transmitter queue reaches 256 quadlets from full. (768 of 1024 quadlets in queue)
Bit 7:R/WIT512LFT: Interrupt when transmitter queue reaches 50% of full. (512 of 1024 quadlets in queue)
Bit 6: R/W TRMSYT: Interrupt on transmission of a SYT in CIP header quadlet 2
Bit 5:R/WTRMBP: Interrupt on payload transmission/discard complete.
Bit 4:R/WDBCERR: Acknowledge interrupt on Data Block Count (DBC) synchronization loss.
Bit 3:R/WINPERR: Acknowledge interrupt on input error (input data discarded).
Bit 2:R/WDISCARD: Interrupt on lost cycle (payload discarded).
Bit 1:R/WITXFULL: Interrupt on isochronous memory bank full. This is a fatal error, the recommended action is to reset and
re-initialize the transmitter.
Bit 0:R/WITXEMPTY: Interrupt on isochronous memory bank empty.
Other bits will always read ‘0’.
13.2.5 Isochronous Transmitter Interrupt Enable (ITXINTE) – Base Address: 0x030
These are the enabled bits for the AV Transmitter Control.
Reset Value 0x00000000
Bit 15..14: R/W Tag: T ag code to insert in isochronous bus packet header. Should be ‘01’ for IEC 61883 International Standard data.
Bit 13..8:R/WChannel: Isochronous channel number.
Bit 5..4:R/WSpeed: Cable transmission speed (S100, S200, S400).
00 = 100Mbs
01 = 200Mbs
10 = 400Mbs
11 = reserved
Bit 3..0RSync: Code to insert in SY field of isochronous bus packet header. Bit 1 is odd/even bit used for encryption key
(0 = even, 1 = odd). Bit value determined by state of transmit port AVxENKEY pin. Some data encryption schemes
require that an ODD/EVEN bit accompany each application packet sent for the purpose of changing “keys” after
short intervals of time (makes breaking an encryption code more difficult). The PDI1394L21 uses the sync field
ODD/EVEN bit for this purpose. Data is inputted to the transmitting AV port accompanied by the state of the
ODD/EVEN bit presented to the AVx ENKEY pin. The pin state at the rising edge of the AVCLK as the first byte of
the packet determines the ODD/EVEN “key” state for that packet. The ODD/EVEN key state may change as often as
required, provided that 2 key changes do not appear in the transmit FIFO simultaneously. If this rule is observed, the
proper “key” state will accompany the packet on to the 1394 bus and through the receiving node’s receive FIFO. As
the packet is being outputted at the receive node’s PDI1394L21, the accompanying ODD/EVEN key state will be
output. The key state remains for all bytes of the packet. Typical change rates for the ODD/EVEN key are between
1 change per second and a change every 30 seconds.
SPD
ODD/EVEN
SV01016
SY
13.2.7 Isochronous Transmitter Memory Status (ITXMEM) – Base Address: 0x038
The AV Transmitter Memory Status register reports on the condition of the internal memory buffer used to store incoming AV data streams
before transmission over the 1394 bus.
Reset Value 0x00000003
Bit 6:RITM100LFT: Memory has 100 quadlets of space remaining before becoming full.
Bit 5:RITM256LFT: Memory has 256 quadlets of space remaining before becoming full.
Bit 4:RIITM512LFT: Memory is 1/2 full.
Bit 3: RITXMF: memory is completely full, no storage available.
Bit 2:RITXMAF: almost full, exactly one quadlet of storage available.
Bit 1:RITXM5AV: at least 5 more quadlets of storage available.
Bit 0:RITXME: memory bank is empty (zero quadlets stored).
1999 Aug 06
36
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.8 Isochronous Receiver Unpacking Control (IRXPKCTL) – Base Address: 0x040
NOTE: When receiver reset is required, first disable receiver (EN_IRX = 0), then wait until Rx FIFO is emptied, then perform the reset. This will
allow previously received packets to go to the application instead of being lost.
AV Receiver Control Bits.
Bit 29..28: R/W RXAP_CLK: Receiver Application Clock, default mode, ‘00’ the AVxCLK pin is an input. This pin can become an
application clock and output for the isochronous Receiver by programming it to ‘01’, ‘10’, or ‘11’.
The programming values are:
00Input
0124.576MHz
1012.288MHz
116.144MHz
Note that when enabled as ‘01’, ‘10’, or ‘11’, the AV port that is configured as receiver and enabled will output this
clock signal on its AVxCLK pin.
Bit 8:R/WSNDIMM: Send immediately; when set to “1”, this bit will allow a received isochronous packet containing a CRC
error to be output immediately (without regard to the time stamp value). This bit defaults to “0”. In default (reset)
mode, the packet will be output with respect to the time stamp value, even if there is a CRC error.
CAUTION: If there is an error in the time stamp, the packet may be held far into the future. This will affect
subsequently received packets.
Bit 7:R/WDIS_TSC: Disable Time Stamp Checking. Defaults to “0”, time stamp checking is enabled. When time stamp
checking is disabled, the time stamp accompanying a packet is output before the packet to the application for use
by the application. This adds an extra quadlet of data to the received data stream; the application must be capable
of handling this extra 4 bytes. Note: The term “Time Stamp” used here refers only to source packet header (full
quadlet) time stamps; it does not mean SYT field hardware synchronization stamps. Also see ENXTMSTP bit in
register X020 for transmit node application time stamp formatting and inputting.
Bit 6: R/W RMVUAP: Remove unreliable packets from memory, do not attempt delivery
Bit 5:RSPAV: Source packet available for delivery in buffer memory.
Bit 4:R/WEN_IRX: Enable receiver operation. Value is only checked whenever a new bus packet arrives, so enable/disable
while running is ‘graceful’, meaning any transfers in process will be completed before this bit is asserted.
Bit 2..3:R/WBPAD: Value indicating the amount of byte padding to be removed from the last data quadlet of each source packet,
from 0 to 3 bytes. This is in addition to quadlet padding as defined in IEC 61883 International Standard.
Bit 1:R/WEN_FS: Enable processing of SYT stamps.
Bit 0:R/WRST_IRX: causes the receiver to be reset when ‘1’. In order for synchronous reset of IRX to work properly, the
application must supply an AVCLK and ensure that the reset bit is kept (programmed) HIGH for at least the duration
of one AVCLK period. Failure to do so may cause the application interface of this module to be improperly reset (or
not reset at all).
EN_IRX
SV00887
EN_FS
RST_IRX
1999 Aug 06
37
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.9 Common Isochronous Receiver Packet Header Quadlet 1 (IRXHQ1) – Base Address: 0x044
This quadlet represents the last received header value when AV receiver is operating.
Reset Value 0x00000000
Bit 31..30: R E0: End of Header, F0: Format: Always set to 00 for first AV header quadlet
Bit 29..24RSID: Source ID, contains the node address of the sender of the isochronous data.
Bit 23.16:RDBS: Size of the data blocks fr om which AV payload i s constructe d. The value 0 represents a length of 256 quadlets.
Bit 15..14:RFN (Fraction Number): The encoding for the number of data blocks into which each source packet has been divided
(00 = 1, 01 = 2, 10 = 4, 11 = 8) by the transmitter of the packet.
Bit 13..11:RQPC: Number of dummy quadlets appended to each source packet before it was divided into data blocks of the
specified size.
Bit 10:RSPH: Indicates that a CYCTM based time stamp is inserted before each application packet (25 bits specified in the
IEC 61883 International Standard).
13.2.10 Common Isochronous Receiver Packet Header Quadlet 2 (IRXHQ2) – Base Address: 0x048
Reset Value 0x0000FFFF
Bit 31..30: R E1: End of Header, F1: Format: Should be set to 10 for second AV header quadlet.
Bit 29..24:RFMT: Value inserted in the Format field.
Bit 23..0:RFDF/SYT: If ‘‘EN FS” in Register IRXPKCTL (0x040) is set to ‘1’, then lower 16-bits are interpreted as SYT.
13.2.11 Isochronous Receiver Interrupt Acknowledge (IRXINTACK) – Base Address: 0x04C
Reset Value 0x00000000
Bit 10:R/WIR100LFT: Isochronous memory bank is 100 quadlets from full. (924 of 1024 quadlets in queue)
Bit 9:R/WIR256LFT: Isochronous data memory bank is 256 quadlets from full. (768 of 1024 quadlets are in the queue)
Bit 8:R/WIR512LFT: Isochronous data memory bank is 50% full. (512 of 1024 quadlets are in the queue)
Bit 7: R/W IRXFULL: Isochronous data memory bank has become full. This is a fatal error, the recommended action is to reset
and re-initialize the receiver.
Bit 6:R/WIRXEMPTY: Isochronous data memory bank has become empty.
Bit 5:R/WFSYNC: Pulse at fsync output.
Bit 4:R/WSEQERR: Sequence error of data blocks.
Bit 3:R/WCRCERR: CRC error in bus packet.
Bit 2:R/WCIPTAGFLT: Faulty CIP header tag (E,F bits). i.e.: The CIP header did not meet the standard and the whole packet
is ignored.
Bit 1:R/WRCVBP: Bus packet processing complete.
Bit 0:R/WSQOV: Status queue overflow. This is a fatal error, the recommended action is to reset and re-initialize the receiver.
1999 Aug 06
38
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.12 Isochronous Receiver Interrupt Enable (IRXINTE) – Base Address: 0x050
Reset Value 0x00000000
Bit 17..16: R SPD: Speed of last received isochronous packet (S100 .. S400).
00 = 100 Mbps
01 = 200 Mbps
10 = 400 Mbps
11 = Reserved
Bit 15..14:R/WTAG: Isochronous tag value (must match) for AV format, ‘01’ for IEC 61883 International Standard data.
Bit 13..8:R/WCHAN: Channel number to receive isochronous data.
Bit 7..4:RERR: Error code for last received isochronous AV packet.
Table 9. Error Codes
CodeNameMeaning
0000reserved
0001ack_complete
0010
through
reserved
1100
1101ack_data_error
1110
and
reserved
1111
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 shall follow.
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.
Bit 3..0:RSYNC: Last received SY code in isochronous bus packet header. Bit 1 is odd/even encryption bit key. State of this bit
will be outputted at active (receiving) AVPOR T on the AVxENKEY pin while the accompanying application packet is
being outputted. Also see Section 13.2.6 for a description of the operation of this bit..
1999 Aug 06
39
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.2.14 Isochronous Receiver Memory Status (IRXMEM) – Base Address: 0x058
Reset Value 0x00000003
Bit 6:RIRM100LFT: FIFO is 100 quadlets from full.
Bit 5:RIRM256LFT: FIFO is 256 quadlets from full.
Bit 4:RIRM512LFT: FIFO is
Bit 3: RIRXMF: Full: no space available.
Bit 2:RIRXMAF: Almost full: exactly one quadlet of storage available.
Bit 1:RIRXM5AV: At least 5 more quadlets of storage available.
Bit 0:RRXME: Memory bank is empty (no data committed).
1
/2 full.
1999 Aug 06
40
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.3 Asynchronous Control and Status Interface
13.3.1 Asynchronous RX/TX Control (ASYCTL) – Base Address: 0x080
Reset Value 0x00300320
Bit 23:R/WDIS_BCAST: Disable the reception of broadcast packets.
Bit 22: R/W ARXRST: Asynchronous receiver reset. This bit will auto clear when the link layer state machine is idle.
Bit 21:R/WATXRST: Asynchronous transmitter reset
Bit 20:R/WARXALL: Receive and filter only RESPONSE packets. When set (1), all responses are stored. When clear (0), only
solicited responses are stored.
Bit 19..16:R/WMAXRC: Maximum number of asynchronous transmitter single phase retries
Bit 15..13:R/WTOS: Time out seconds, integer of 1 second of the split transaction time out timer. Resets to “000”. This timer is set
to the maximum amount of time the transmitter will wait for a pending response before the transmitter will begin
transmitting the next available request packet. Also see TOF bits of this timer.
Bit 12..0:R/WTOF: Time out fractions, integer of 1/8000 second. Resets to 0320h, which is 100 milliseconds. During the timeout of
the split transaction timer, subsequent split transactions are blocked. If it is desired to transmit multiple split
transactions this can be accomplished by following this procedure: (1) set the split transaction timer value to “0”, (2)
disable the split time–out interrupt (TIMEOUT, bit 7 in register 0x0A0); (3) clear (set to “0”) the unsolicited response
filter bit (ARXALL, bit 20 in register 0x080). Now use tLabels (transaction Labels, see section 12.5.1) to pair
transmitted packets with received packets. Use software timers to time–out the subsequent pending responses.
13.3.2 Asynchronous RX/TX Memory Status (ASYMEM) – Base Address: 0x084
Unused bits read ‘0’. The information in this register is primarily used for diagnostics.
Bit 17:RTRSPQIDLE: Transmitter response queue is idle. Indicates that the transfer register for this queue is empty.
Bit 16:RTREQQIDLE: Transmitter request queue is idle. Indicates that the transfer register for this queue is empty.
Bit 15:RRRSPQF: Receiver response queue full.
Bit 14:RRRSPQAF: Receiver response queue almost full (precisely 1 more quadlet available).
Bit 13:RRRSPQ5AV: Receiver response queue at least 5 quadlets available.
Bit 12:RRRSPQE: Receiver response queue empty.
Bit 11:RRREQQF: Receiver request queue full.
Bit 10:RRREQQAF: Receiver request queue almost full (precisely 1 more quadlet available).
Bit 9:RRREQQ5AV : Receiver request queue at least 5 quadlets available.
Bit 8:RRREQQE: Receiver request queue empty.
Bit 7:RTRSPQF: Transmitter response queue full.
Bit 6:RTRSPQAF: Transmitter response queue almost full (precisely 1 more quadlet available).
Bit 5:RTRSPQ5AV : T ransmitter response queue at least 5 quadlets available.
Bit 4:RTRSPQE: Transmitter response queue empty.
Bit 3:RTREQQF: Transmitter request queue full.
Bit 2:RTREQQAF: Transmitter request queue almost full (precisely 1 more quadlet available).
Bit 1:RTREQQ5AV : T ransmitter request queue at least 5 quadlets available.
Bit 0:RTREQQE: Transmitter request queue empty.
1999 Aug 06
41
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
13.3.3 Asynchronous Transmit Request Next (TX_RQ_NEXT) – Base Address: 0x088
Reset Value 0x00000C00
Bit 31..17: R/W Unused bits read ‘0’
Bit 16: R/W RRSPQFULL: Receiver response queue did become full. Write a “1” to this bit to reset the interrupt.
Bit 15: R/WRREQQFULL: Receiver request queue did become full. Write a “1” to this bit to reset the interrupt.
Bit 14:R/WSIDQAV: Current quadlet in RREQ is self ID data. This bit is set only after a bus reset, not after reception of PHY
packets other than self IDs. This interrupt automatically resets when the quadlet is read.
Bit 13:R/WRRSPQLASTQ: Current quadlet in RRSP is last quadlet of packet. This interrupt automatically resets when the
quadlet is read.
Bit 12:R/WRREQQLASTQ: Current quadlet in RREQ is last quadlet of packet. This interrupt automatically resets when the
quadlet is read.
Bit 11:R/WRRSPQRDERR: Receiver response queue read error (transfer error) or bus reset occurred.
When set (1), this queue is blocked for read access. Write a “1” to this bit to reset the interrupt.
Bit 10:R/WRREQQRDERR: Receiver request queue read error (transfer error) or bus reset occurred.
When set (1), this queue is blocked for read access. Write a “1” to this bit to reset the interrupt.
Bit 9:R/WRRSPQQAV: Receiver response queue quadlet available (in RRSP). This interrupt automatically resets when the
quadlet is read.
Bit 8:R/WRREQQQAV : Receiver request queue quadlet available (in RREQ). This interrupt automatically resets when the
quadlet is read.
Bit 7: R/WTIMEOUT: Split transaction response timeout. Write a “1” to this bit to reset the interrupt.
Bit 6:R/WRCVDRSP: Solicited response received (within timeout interval). Write a “1” to this bit to reset the interrupt.
Bit 5:R/WTRSPQFULL: Transmitter response queue did become full. Write a “1” to this bit to reset the interrupt.
Bit 4:R/WTREQQFULL: Transmitter request queue did become full. W rite a “1” to this bit to reset the interrupt.
Bit 3:R/WTRSPQWRERR: Transmitter response queue write error (transfer error). Write a “1” to this bit to reset the interrupt.
Bit 2:R/WTREQQWRERR: Transmitter request queue write error (transfer error). Write a “1” to this bit to reset the interrupt.
Bit 1:R/WTRSPQWR : Transmitter response queue written (transfer register emptied). Write a “1” to this bit to reset the interrupt.
1999 Aug 06
43
Philips SemiconductorsPreliminary specification
ILInput leakage current
IOZ3-State output current
PDI1394L211394 full duplex AV link layer controller
Bit 0:R/WTREQQWR: Transmitter request queue written (transfer register emptied). Write a “1” to this bit to reset the interrupt.
13.3.10 Asynchronous RX/TX Interrupt Enable (ASYINTE) – Base Address: 0x0A4
PDI1394L211394 full duplex AV link layer controller
16.5 CYCLEIN/CYCLEOUT Timings
SCLK
CYCLEIN
CYCLEOUT
16.6 RESET Timings
CYCLEIN
RESET_N
50%50%50%
t
CWH
t
CWL
t
CP
Figure 31. CYCLEIN Waveform
50%50%
t
CD
50%50%
Figure 32. CYCLEOUT Waveforms
t
RESET
SV00696
t
CD
SV00697
50%50%
Figure 33. RESET_N Waveform
SV00698
1999 Aug 06
48
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
TQFP100: plastic thin quad flat package; 100 leads; body 14 x 14 x 1.0 mmSOT386-1
1999 Aug 06
49
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
LQFP100: plastic low profile quad flat package; 100 leads; body 14 x 14 x 1.4 mmSOT407-1
1999 Aug 06
50
PDI1394L21 1394 FULL DUPLEX AV LINK LAYER CONTROLLER
(These errata refer to the data sheet dated 1999 August 6)
Chip Errata:
E-1. Self-ID Packet Issues:
ERRATA LIST FOR THE PHILIPS
Description of expected operation:
placed in the Read Request Queue. Refer to section 12.5.2.4 (Self-ID and PHY packets receive) in the
“PDI1394L21 1394 Full Duplex AV Link Layer Controller” data sheet for the proper format of a self-ID packet.
Description of observed behavior:
Request Queue with no accompanying self-ID and acknowledge quadlet. This type of self-ID is valid ONL Y for a
node which is not connected to any other node (node standing alone). This partial self-ID packet results from a
recent node connection (hot plug) event or Link/PHY hardware reset.
Solution or work around:
E-2. AVFSYNC pin function at high FSYNC pulse repetition rates:
Description of expected operation:
node and the isochronous receiver of the receiving node, a pulse introduced at the FSYNC pin on the transmitting
A V port of the transmitting node will produce an SYT field time stamp in the next bus packet which will, in turn,
produce a pulse at the FSYNC pin of the receiving A V port on the receiving node at a time corresponding to the
expiration of the SYT field time stamp, with the SYT Delay introduced at the transmitter taken into account.
Description of observed behavior:
greater than 2 KHz (dependant upon the setting of the SYT Delay bits) the system operates as expected for a
short period of time (about 100 milliseconds), then operates erratically thereafter.
Solution or work around:
SYT Delay = 2 bus cycles, maximum rep rate = 3,200; SYT Delay = 3 bus cycles, maximum rep rate = 3,200;
SYT Delay = 4 bus cycles, maximum rep rate = 4,200.
Issue a software bus reset and read the self IDs generated by that reset.
Do not use above the following rep rates with the corresponding SYT Delay settings:
After bus reset, the queues are flushed and a self-ID packet should be
Occasionally 0x000000E0 and 0x00000010 quadlets are found in the Read
With the EN_FS bits set on the isochronous transmitter of the transmitting
At rep rates below 2 KHz, the system works as expected. At rep rates
E-3. AVENKEY pin function:
Description of expected operation:
a transmitted isochronous packet by means of reading the ENKEY pin on the transmitting A V port while the first
byte of an application packet is being inputted. The ENKEY state of the first inputted byte is the state of all packet
bytes.
Description of observed behavior:
internal clock cycle, occasionally some of the bytes in a packet are keyed with the wrong state. This results in
packets getting “stuck” in the isochronous transmit FIFO and causing FIFO overfill.
Solution or work around:
proper synchronization. The AVCLK signal must rise 8 to 41 nS before the CLK25 signal rises for proper
operation at 12.288 MHz. It is the AVCLK signal which introduces the state of the ENKEY pin (and all
others) to the AV port interface logic. Please consult Philips IEEE 1394 Applications Engineering Group
(1394@philips.com) for use of this function at other AVCLK frequencies.
Errata To the PDI1394L21 1394 Full Duplex AV Link Layer Controller (Data Sheet dated: 1999 August 6).
Input key states only with reference to the CLK25 signal of the link chip to assure
This pin / function is intended to attach a specific “key” state to each byte of
Unless the state of the ENKEY pin is inputted within a certain part of the link
Philips Semiconductors
August 6, 1999
Philips SemiconductorsPreliminary specification
PDI1394L211394 full duplex AV link layer controller
Data sheet status
Data sheet
status
Objective
specification
Preliminary
specification
Product
specification
Product
status
Development
Qualification
Production
Definition
This data sheet contains the design target or goal specifications for product development.
Specification may change in any manner without notice.
This data sheet contains preliminary data, and supplementary data will be published at a later date.
Philips Semiconductors reserves the right to make changes at any time without notice in order to
improve design and supply the best possible product.
This data sheet contains final specifications. Philips Semiconductors reserves the right to make
changes at any time without notice in order to improve design and supply the best possible product.
[1]
[1] Please consult the most recently issued datasheet before initiating or completing a design.
Definitions
Short-form specification — The data in a short-form specification is extracted from a full data sheet with the same type number and title. For
detailed information see the relevant data sheet or data handbook.
Limiting values definition — Limiting values given are in accordance with the Absolute Maximum Rating System (IEC 134). Stress above one
or more of the limiting values may cause permanent damage to the device. These are stress ratings only and operation of the device at these or
at any other conditions above those given in the Characteristics sections of the specification is not implied. Exposure to limiting values for extended
periods may affect device reliability.
Application information — Applications that are described herein for any of these products are for illustrative purposes only. Philips
Semiconductors make no representation or warranty that such applications will be suitable for the specified use without further testing or
modification.
Disclaimers
Life support — These products are not designed for use in life support appliances, devices or systems where malfunction of these products can
reasonably be expected to result in personal injury . Philips Semiconductors customers using or selling these products for use in such applications
do so at their own risk and agree to fully indemnify Philips Semiconductors for any damages resulting from such application.
Right to make changes — Philips Semiconductors reserves the right to make changes, without notice, in the products, including circuits, standard
cells, and/or software, described or contained herein in order to improve design and/or performance. Philips Semiconductors assumes no
responsibility or liability for the use of any of these products, conveys no license or title under any patent, copyright, or mask work right to these
products, and makes no representations or warranties that these products are free from patent, copyright, or mask work right infringement, unless
otherwise specified.
Philips Semiconductors
811 East Arques Avenue
P.O. Box 3409
Sunnyvale, California 94088–3409
Telephone 800-234-7381
Copyright Philips Electronics North America Corporation 1999
All rights reserved. Printed in U.S.A.
Date of release: 08-99
Document order number:9397 750 05512
1999 Aug 06
52
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.