Fully Supports Provisions of IEEE
1394–1995 Standard for High Performance
Serial Bus† and the P1394a Supplement
(Draft 2.0)
D
Full P1394a Support Includes: Connection
Debounce, Arbitrated Short Reset,
Multispeed concatenation, Arbitration
Acceleration, Fly-by Concatenation, Port
Disable/Suspend/Resume
D
Provides Six P1394a Fully Compliant Cable
Ports at 100/200/400 Megabits per Second
(Mbits/s)
D
Cable Ports Monitor Line Conditions for
Active Connection to Remote Node
D
Power-Down Features to Conserve Energy
in Battery Powered Applications include:
Automatic Device Power-Down during
Suspend, Device Power-Down Pin, Link
Interface Disable via LPS, and Inactive
Ports Powered Down
D
Logic Performs System Initialization and
Arbitration Functions
D
Encode and Decode Functions Included for
Data-Strobe Bit Level Encoding
D
Incoming Data Resynchronized to Local
Clock
description
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
D
Single 3.3 V Supply Operation
D
Interface to Link Layer Controller Supports
Low Cost TI Bus-Holder Isolation and
Optional Annex J Electrical Isolation
D
Data Interface to Link-Layer Controller
Through 2/4/8 Parallel Lines at 49.152 MHz
D
Low Cost 24.576-MHz Crystal Provides
Transmit, Receive Data at 100/200/400
Mbits/s, and Link-Layer Controller Clock at
49.152 MHz
D
Interoperable with Link-Layer Controllers
Using 3.3-V and 5-V Supplies
D
Interoperable with Other Physical Layers
(PHY) Using 3.3-V and 5-V Supplies
D
Node Power Class Information Signaling
for System Power Management
D
Cable Power Presence Monitoring
D
Separate Cable Bias (TPBIAS) for Each Port
D
Register Bits Give Software Control of
Contender Bit, Power Class Bits, Link
Active Bit and P1394a Features
D
Fully Interoperable with FIreWire and
i.LINK Implementation of IEEE Std 1394
The TSB41L V06 provides the digital and analog transceiver functions needed to implement a six-port node in
a cable-based IEEE 1394 network. Each cable port incorporates two differential line transceivers. The
transceivers include circuitry to monitor the line conditions as needed for determining connection status, for
initialization and arbitration, and for packet reception and transmission. The TSB41L V06 is designed to interface
with a Link Layer Controller (LLC), such as the TSB12LV22, TSB12LV21, TSB12LV31, TSB12LV41, or
TSB12LV01.
The TSB41LV06 requires only an external 24.576 MHz crystal as a reference. An external clock may be
provided instead of a crystal. An internal oscillator drives an internal phase-locked loop (PLL), which generates
the required 393.216 MHz reference signal. This reference signal is internally divided to provide the clock
signals used to control transmission of the outbound encoded Strobe and Data information. A 49.152 MHz clock
signal is supplied to the associated LLC for synchronization of the two chips and is used for resynchronization
of the received data. The power-down (PD) function, when enabled by asserting the PD terminal high, stops
operation of the PLL.
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of
Texas Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
†
Implements technology covered by one or more patents of Apple Computer, Incorporated and SGS Thompson, Limited.
i.LINK is a trademark of Sony Corporation
FireWire is a trademark of Apple Computers Incorporated.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of Texas Instruments
standard warranty. Production processing does not necessarily include
testing of all parameters.
The TSB41L V06 supports an optional isolation barrier between itself and its LLC. When the ISO input terminal
is tied high, the LLC interface outputs behave normally . When the ISO terminal is tied low, internal differentiating
logic is enabled, and the outputs are driven such that they can be coupled through a capacitive or transformer
galvanic isolation barrier as described in IEEE 1394a section 5.9.4. T o operate with TI Bus Holder isolation the
ISO
on the PHY terminal must be tied HIGH.
Data bits to be transmitted through the cable ports are received from the LLC on two, four or eight parallel paths
(depending on the requested transmission speed) and are latched internally in the TSB41LV06 in
synchronization with the 49.152 MHz system clock. These bits are combined serially , encoded, and transmitted
at 98.304, 196.608, or 392.216 Mbits/s (referred to as S100, S200, and S400 speed, respectively) as the
outbound data-strobe information stream. During transmission, the encoded data information is transmitted
differentially on the TPB cable pair(s), and the encoded strobe information is transmitted differentially on the
TPA cable pair(s).
During packet reception the TP A and TPB transmitters of the receiving cable port are disabled, and the receivers
for that port are enabled. The encoded data information is received on the TPA cable pair, and the encoded
strobe information is received on the TPB cable pair. The received data-strobe information is decoded to recover
the receive clock signal and the serial data bits. The serial data bits are split into two, four or eight bit parallel
streams (depending upon the indicated receive speed), resynchronized to the local 49.152 MHz system clock
and sent to the associated LLC. The received data is also transmitted (repeated) on the other active (connected)
cable ports.
Both the TPA and TPB cable interfaces incorporate differential comparators to monitor the line states during
initialization and arbitration. The outputs of these comparators are used by the internal logic to determine the
arbitration status. The TPA channel monitors the incoming cable common-mode voltage. The value of this
common-mode voltage is used during arbitration to set the speed of the next packet transmission. In addition,
the TPB channel monitors the incoming cable common-mode voltage on the TPB pair for the presence of the
remotely supplied twisted-pair bias voltage.
The TSB41L V06 provides a 1.86 V nominal bias voltage at the TPBIAS terminal for port termination. The PHY
contains two independent TPBIAS circuits. This bias voltage, when seen through a cable by a remote receiver,
indicates the presence of an active connection. This bias voltage source must be stabilized by an external filter
capacitor of 1 µF.
The line drivers in the TSB41L V06 operate in a high-impedance current mode, and are designed to work with
external 110 Ω line-termination resistor networks in order to match the 1 10-Ω cable impedance. One network
is provided at each end of a twisted-pair cable. Each network is composed of a pair of series-connected 56-Ω
resistors. The midpoint of the pair of resistors that is directly connected to the twisted pair A terminals is
connected to its corresponding TPBIAS voltage terminal. The midpoint of the pair of resistors that is directly
connected to the twisted-pair B terminals is coupled to ground through a parallel R-C network with
recommended values of 5 kΩ and 220 pF. The values of the external line termination resistors are designed
to meet the standard specifications when connected in parallel with the internal receiver circuits. An external
resistor connected between the R0 and R1 terminals sets the driver output current, along with other internal
operating currents. This current setting resistor has a value of 6.3-kΩ ±0.5%. This may be accomplished by
placing a 6.34-kΩ ±0.5% resistor in parallel with a 1-MΩ resistor.
When the power supply of the TSB41L V06 is 0 V while the twisted-pair cables are connected, the TSB41L V06
transmitter and receiver circuitry will present a high impedance to the cable and will not load the TPBIAS voltage
at the other end of the cable.
2
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 3
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
When the TSB41LV06 is used with one or more of the ports not brought out to a connector, the twisted–pair
terminals of the unused ports must be terminated for reliable operation. For each unused port, the TPB+ and
TPB– terminals should be tied together and then pulled to ground, or the TPB+ and TPB– terminals should be
connected to the suggested termination network. The TP A+ and TPA– and TPBIAS terminals of an unused port
may be left unconnected. The TPBias terminal should be connected to a 1-µF capacitor to ground or left floating.
The TESTM, SE, and SM terminals are used to set up various manufacturing test conditions. For normal
operation, the TESTM terminal should be connected to VDD, SE should be tied to ground through a 1-kΩ resistor,
while SM should be connected directly to ground.
Four package terminals are used as inputs to set the default value for four configuration status bits in the self–ID
packet, and are hardwired high or low as a function of the equipment design. The PC0–PC2 terminals are used
to indicate the default power-class status for the node (the need for power from the cable or the ability to supply
power to the cable). See T able 9 for power-class encoding. The C/LKON terminal is used as an input to indicate
that the node is a contender for either isochronous resource manager (IRM) or bus manager (BM).
The PHY supports suspend/resume as defined in the IEEE P1394a specification. The suspend mechanism
allows pairs of directly–connected ports to be placed into a low power conservation state while maintaining a
port–to–port connection between 1394 bus segments. While in a low–power state, a port is unable to transmit
or receive data transaction packets. However, a port in a low power state is capable of detecting connection
status changes and detecting incoming TPBias. When all six ports of the TSB41L V06 are suspended all circuits
except the bandgap reference generator and bias detection circuits are powered down resulting in significant
power savings. For additional details of suspend/resume operation refer to the P1394a specification. The use
of suspend/resume is recommended for new designs.
The port transmitter and receiver circuitry is disabled during power-down (when the PD input terminal is
asserted high), during reset (when the RESET
to the port, or when controlled by the internal arbitration logic. The TPBIAS is disabled during power–down,
during reset, or when the port is disabled as commanded by the LLC.
The CNA (cable-not-active) terminal provides a high output when all twisted-pair cable ports are disconnected,
and can be used along with LPS to determine when to power–down the TSB41LV06. The CNA output is not
debounced. In a PD terminal initiated power down, the CNA detection circuitry remains enabled.
The LPS (link power status) terminal works with the C/LKON terminal to manage the power usage in the node.
The LPS signal from the LLC indicates to the PHY that the LLC is powered up and active. During LLC
power-down mode, as indicated by the LPS input being low for more than 2.6 µs, the TSB41L V06 deactivates
the PHY-LLC interface to save power . The TSB41LV06 will continue the necessary repeater function required
for network operation during this low power state.
If the PHY receives a link-on packet from another node, the C/LKON terminal is activated to output a
square-wave signal. The LLC recognizes this signal, reactivates any powered-down portions of the LLC, and
notifies the PHY of its power-on status via the LPS terminal. The PHY confirms notification by deactivating the
square-wave signal on the C/LKON terminal, and then enables the PHY-link interface.
input terminal is asserted low), when no active cable is connected
C/LKON27CMOSI/OBus manager contender programming input and link-on output. On hardware
CNA21CMOSOCable not active output. This pin is asserted high when there are no ports
CPS32CMOSICable power status input. This pin is normally connected to cable power through
CTL0
CTL1
D0 – D710, 11, 14, 15, 16,
DGND1, 2, 6, 20, 25, 26,
DV
DD
FILTER0
FILTER1
ISO31CMOSILink interface isolation control input. This pin controls the operation of output
51, 75, 76, 81, 82,
90
44, 45, 57, 63, 69,
77, 78, 79, 80
7
8
17, 18, 19
33, 100
4, 9, 13, 22, 34,
35, 99
91
92
TYPEI/ODESCRIPTION
Supply–Analog circuit ground pins. These pins should be tied together to the low
Supply–Analog circuit power pins. A combination of high frequency decoupling
CMOS
5 V tol
CMOS
5 V tol
Supply–Digital circuit ground pins. These pins should be tied together to the low
Supply–Digital circuit power pins. A combination of high frequency decoupling capacitors
CMOSI/OPLL filter pins. These pins are connected to an external capacitance to form a
impedance circuit board ground plane.
capacitors near each pin are suggested, such as paralleled 0.1 µF and 0.001 µF.
Lower frequency 10 µF filtering capacitors are also recommended. These supply
pins are separated from PLLVDD and DVDD internal to the device to provide noise
isolation. They should be tied at a low impedance point on the circuit board.
reset, this pin is used to set the default value of the contender status indicated
during self-ID. Programming is done by tying the pin through a 10 kΩ resistor to a
high (contender) or low (not contender). The resistor allows the link-on output to
override the input.
Following hardware reset, this pin is the link-on output, which is used to notify the
LLC to power-up and become active. The link-on output is a square-wave signal
with a period of approximately 163 ns (8 SYSCLK cycles) when active. The
link-on output is deasserted low when the LPS input pin is active.
receiving incoming bias voltage.
a 400-kΩ resistor. This circuit drives an internal comparator that is used to detect
the presence of cable power.
I/OControl I/Os. These bidirectional signals control communication between the
TSB41L V06 and the LLC. Bus holders are built into these terminals.
I/OData I/O’s. These are bidirectional data signals between the TSB41L V06 and the
LLC. Bus Holders are built into these terminals.
impedance circuit board ground plane.
near each pin are suggested, such as paralleled 0.1 µF and 0.001 µF. Lower
frequency 10 µF filtering capacitors are also recommended. These supply pins
are separated from PLLVDD and AVDD internal to the device to provide noise
isolation. They should be tied at a low impedance point on the circuit board.
lag-lead filter required for stable operation of the internal frequency multiplier PLL
running off of the crystal oscillator . A 0.1 µF ±10% capacitor is the only external
component required to complete this filter.
differentiation logic on the CTL and D pins. If an optional isolation barrier of the
type described in Annex J of IEEE Std 1394-1995 is implemented between the
TSB41L V06 and LLC, the ISO
logic. If no isolation barrier is implemented (direct connection), or TI bus holder
Isolation is implemented, the ISO
differentiation logic. For additional information refer to TI application note
Bus Galvanic Isolation
pin should be tied low to enable the differentiation
pin should be tied high to disable the
Serial
, SLLA011.
6
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 7
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
Terminal Functions (Continued)
TERMINAL
NAMENO.
LPS24CMOS
LREQ3CMOS
PC0
PC1
PC2
PD23CMOS
PLLGND94, 95Supply–PLL circuit ground pins. These pins should be tied together to the low impedance
PLLV
DD
RESET98CMOSILogic reset input. Asserting this pin low resets the internal logic. An internal
R0
R1
SE42CMOSIT est control input. This input is used in manufacturing test of the TSB41LV06. For
SM43CMOSITest control input. This input is used in manufacturing test of the TSB41L V06. For
SYSCLK5CMOSOSystem clock output. Provides a 49.152 MHz clock signal, synchronized with
TESTM41CMOSIT est control input. This input is used in manufacturing test of the TSB41LV06. For
TPA0+
TPA1+
TPA2+
TPA3+
TPA4+
TPA5+
28
29
30
93Supply–PLL circuit power pins. A combination of high frequency decoupling capacitors
83
84
39
55
61
67
73
88
TYPEI/ODESCRIPTION
5 V tol
5 V tol
CMOSIPower class programming inputs. On hardware reset, these inputs set the default
5 V tol
Bias–Current setting resistor pins. These pins are connected to an external resistance
CableI/OTwisted-pair cable A differential signal pins. Board traces from each pair of
ILink power status input. This pin is used to monitor the power status of the LLC,
and is connected to either the VDD supplying the link layer controller through a
1kΩ resistor, or to a pulsed output which is active when the LLC is powered. The
pulsed output is useful when using an isolation barrier. If this input is low for more
than 2.6 µs, the LLC is considered powered-down. If this input is high for more
than 20 ns, the LLC is considered powered-up. If the LLC is powered-down, the
PHY-LLC interface is disabled, and the TSB41LV06 will perform only the basic
repeater functions required for network initialization and operation. Bus holder is
built into this terminal.
ILLC request input. The LLC uses this input to initiate a service request to the
TSB41L V06. Bus Holder is built into this terminal.
value of the power–class indicated during self-ID. Programmed is done by tying
the pins high or low. Refer to Table 9 for encoding.
IPower-down input. A high on this pin turns off all internal circuitry except the
cable-active monitor circuits, which control the CNA output. Bus Holder is built
into this terminal.
circuit board ground plane.
near each pin are suggested, such as paralleled 0.1 µF and 0.001 µF. Lower
frequency 10 µF filtering capacitors are also recommended. These supply pins
are separated from DVDD and AVDD internal to the device to provide noise
isolation. They should be tied at a low impedance point on the circuit board.
pull–up resistor to VDD is provided so only an external delay capacitor in parallel
with a resistor is required for proper power-up operation (see
the
applications information section
input, and may also be driven by an open-drain type driver.
to set the internal operating currents and cable driver output currents. A
resistance of 6.30 kΩ ±0.5% is required to meet the IEEE Std 1394-1995 output
voltage limits.
normal use this pin should be tied to GND through a 1-kΩ resistor.
normal use this pin should be tied to GND.
data transfers, to the LLC.
normal use this pin should be tied to VDD.
positive and negative differential signal pins should be kept matched and as short
as possible to the external load resistors and to the cable connector.
12Supply–5–V VDD pin. This pin should be connected to the LLC VDD supply when a 5–V
96
97
CableI/OTwisted-pair cable A differential signal pins. Board traces from each pair of
CableI/OTwisted-pair cable B differential signal pins. Board traces from each pair of
CableI/OTwisted-pair cable B differential signal pins. Board traces from each pair of
CableI/OTwisted-pair bias output. This provides the 1.86 V nominal bias voltage needed
Crystal–Crystal oscillator inputs. These pins connect to a 24.576 MHz parallel resonant
positive and negative differential signal pins should be kept matched and as short
as possible to the external load resistors and to the cable connector.
positive and negative differential signal pins should be kept matched and as short
as possible to the external load resistors and to the cable connector.
positive and negative differential signal pins should be kept matched and as short
as possible to the external load resistors and to the cable connector.
for proper operation of the twisted–pair cable drivers and receivers, and for
signaling to the remote nodes that there is an active cable connection. Each of
these pins must be decoupled with a 1.0 µF capacitor to ground.
LLC is used, and should be connected to the PHY DVDD when a 3–V LLC is used.
A combination of high frequency decoupling capacitors near this pin is
suggested, such as paralleled 0.1 µF and 0.001 µF . When this pin is tied to a 5–V
supply, all pin Bus Holders are disabled, regardless of the state of the ISO
When this pin is tied to a 3–V supply, Bus Holders are enabled when the ISO
high.
fundamental mode crystal. The optimum values for the external shunt capacitors
are dependent on the specifications of the crystal used
the applications information section).
(see crystal selection in
pin.
pin is
absolute maximum ratings over operating free-air temperature range (unless otherwise noted)
Supply voltage range, V
Input voltage range, V
5V tolerant I/O supply voltage range, VDD_
5V tolerant input voltage range, VI_
Output voltage range at any output, V
Lead temperature 1,6 mm (1/16 inch) from case for 10 seconds260_C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
†
Stresses beyond those listed under absolute maximum ratings 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.
NOTES: 1. All voltage values, except differential I/O bus voltages, are with respect to network ground.
8
2. HBM is Human Body Model, MM is Machine Model.
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 9
Suppl
oltage, V
High level in ut voltage,V
IH
Low level in ut voltage, V
IL
R
l
°C
Differential input voltage, V
mV
Common-mode input voltage, V
V
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
DISSIPATION RATING TABLE
PACKAGE
‡
PZP
§
PZP
†
This is the inverse of the traditional junction-to-ambient thermal resistance (R
‡
1 oz. trace and copper pad with solder.
§
1 oz. trace and copper pad without solder.
NOTE: For more information, refer to TI application note
TI literature number SLMA002.
TA ≤ 25_C
POWER RATING
4.48 W56.02 mW/°C1.96 W
2.28 W35.44 mW/°C0.685 W
recommended operating conditions
PARAMETERMINTYP
pp
y v
-
-
Output current, I
Maximum junction temperature TJ (see
values listed in therma
θJA
characteristics table)
Power-up reset time, t
Receive input jitter
Receive input skew
†
All typical values are at VDD = 3.3 V and TA = 25°
‡
For a node that does not source power, see Section 4.2.2.2 in IEEE 1394a.
DD
p
p
O
p
p
ID
IC
pu
Source power node33.33.6V
Nonsource power node2.7
Case 1 (Bus Holder): ISO=VDD, V
Case 2 (5V Tol): ISO
LPS, PD, LREQ, CTL0, CTL1, D0–D7
C/LKON, PC0, PC1, PC2, ISO0.7×V
RESET0.6×V
Case 1 (Bus Holder): ISO=VDD, V
Case 2 (5V Tol): ISO
LPS, PD, LREQ, CTL0, CTL1, D0–D7
Off state differential voltageDrivers disabled, See Figure 120mV
OFF
Limits defined as algebraic sum of TPA+ and TPA– driver currents. Limits also apply to TPB+ and TPB– algebraic sum of driver currents.
Limits defined as absolute limit of each of TPB+ and TPB– driver currents.
4. Idle (receive cycle start on port0, xmt cycle start on ports 1 through 5), VDD = 3.3 V, TA = 25°C.
p
†
‡
‡
low.
See Note 3273
See Note 4166
= V
†
DD_5V
DD_5V
,
DD
DD
DD_5V
DD_5V
DD_5V
DD_5V
,
= V
,
= V
= V
DD
= VDD,
= V
DD
= VDD,
DD
DD
4.77.5V
2.8
VDD–0.4
0.4
0.051
–1–0.05
VDD/2+0.3VDD/2+0.9
V
+1
ref
VDD/2–0.9VDD/2–0.3
V
+0.2
ref
µ
400 KΩ resistor
VDD = 2.7 V, IOH = –4 mA2.2
VDD = 3 V to 3.6 V,
IOH = –4 mA
Annex J; IOH = –9 mA
ISO
= 0 V, V
IOL = 4 mA0.4
Annex J; IOH = 9 mA
ISO
= 0 V, V
ISO = 3.6 V, VDD = 3.6 V,
=
I
V
DD_5V
ISO = 0 V, VDD 3.6 V5µA
VO= VDD or 0 V±5µA
VI = 1.5 V–80–40–20
VI = 0 V–90–45–22
ISO = 0 V ,V
ISO = 0 V, V
V
= VDD × 0.42
ref
ISO = 0 V,V
ISO = 0 V, V
V
= VDD × 0.42
ref
V
V
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
11
Page 12
TSB41LV06
gy
°C/W
gy
°C/W
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
thermal characteristics
PARAMETERTEST CONDITION
R
R
R
R
†
Usage of thermally enhanced PowerPad PZP package is assumed in all three test conditions.
Junction-to-free-air thermal resistance
θJA
Junction-to-case-thermal resistance
θJC
Junction-to-free-air thermal resistance
θJA
Junction-to-case-thermal resistance
θJC
Board mounted, No air flow,
High conductivity TI recommended test board,
Chip soldered or greased to thermal land with 1 oz.
copper
Board mounted, No air flow,
High conductivity TI recommended test board with
thermal land but no solder or grease thermal
connection to thermal land with 1 oz. copper
switching characteristics
PARAMETERTEST CONDITIONMINTYPMAXUNIT
Jitter, transmitBetween TPA and TPB±0.15ns
Skew, transmitBetween TPA and TPB±0.10ns
trTP differential rise time, transmit10% to 90%,At 1394 connector0.51.2ns
tfTP differential fall time, transmit90% to 10%,At 1394 connector0.51.2ns
tsuSetup time, CTL0, CTL1, D0–D7, LREQ to SYSCLK50% to 50%See Figure 25ns
thHold time, CTL0, CTL1, D0–D7, LREQ after SYSCLK50% to 50%See Figure 22ns
tdDelay time, SYSCLK to CTL0, CTL1, D0–D750% to 50%See Figure 3211ns
†
MINTYPMAXUNIT
17.85
0.12
28.22
0.12
°
°
12
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 13
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PARAMETER MEASUREMENT INFORMATION
TPAx+
TPBx+
56 Ω
TPAx–
TPBx–
Figure 1. Test Load Diagram
SYSCLK
t
t
su
h
Dx, CTLx, LREQ
Figure 2. Dx, CTLx, LREQ Input Setup and Hold Time Waveforms
SYSCLK
t
d
Dx, CTLx
Figure 3. Dx and CTLx Output Delay Relative to SYSCLK Waveforms
There are 16 accessible internal registers in the TSB41LV06. The configuration of the registers at addresses
0 through 7 (the base registers) is fixed, while the configuration of the registers at addresses 8 through Fh (the
paged registers) is dependent upon which one of eight pages, numbered 0 through 7, is currently selected. The
selected page is set in base register 7.
The configuration of the base registers is shown in T able 1 and corresponding field descriptions given in T able 2.
The base register field definitions are unaffected by the selected page number.
A reserved register or register field (marked as Reserved or Rsvd in the register configuration tables below) is
read as 0, but is subject to future usage. All registers in pages 2 through 6 are reserved.
Physical ID6RdThis field contains the physical address ID of this node determined during self-ID. The physical-ID is invalid
R1RdRoot. This bit indicates that this node is the root node. The R bit is reset to 0 by bus-reset, and is set to 1 during
CPS1RdCable-power-status. This bit indicates the state of the CPS input pin. The CPS pin is normally tied to serial bus
RHB1Rd/WrRoot-holdoff bit. This bit instructs the PHY to attempt to become root after the next bus-reset. The RHB bit is
IBR1Rd/WrInitiate bus-reset. This bit instructs the PHY to initiate a long (166 µs) bus-reset at the next opportunity. Any
Gap_Count6Rd/WrArbitration gap count. This value is used to set the subaction (fair) gap, arb-reset gap, and arb-delay times.
Extended3RdExtended register definition. For the TSB41LV06 this field is 1 11b, indicating that the extended register set is
Num_Ports4RdNumber of ports. This field indicates the number of ports implemented in the PHY. For the TSB41LV06 this
PHY_Speed3RdPHY speed capability. For the TSB41LV06 PHY this field is 010b, indicating S400 speed capability .
after a bus-reset until self-ID has completed as indicated by an unsolicited register-0 status transfer.
tree-ID if this node becomes root.
cable power through a 400 kΩ resistor. A 0 in this bit indicates that the cable power voltage has dropped below
its threshold for guaranteed reliable operation.
reset to 0 by hardware reset and is unaffected by bus-reset.
receive or transmit operation in progress when this bit is set will complete before the bus-reset is initiated. The
IBR bit is reset to 0 by hardware reset or bus-reset.
The gap count may be set either by a write to this register or by reception or transmission of a PHY_CONFIG
packet. The gap count is set to 3Fh by hardware reset or after two consecutive bus-resets without an
intervening write to the gap count register (either by a write to the PHY register or by a PHY_CONFIG packet).
implemented.
field is 6.
14
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 15
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
Table 2. Base Register Field Descriptions (Continued)
FIELDSIZETYPEDESCRIPTION
Delay4RdPHY repeater data delay. This field indicates the worst case repeater data delay of the PHY, expressed as
L1Rd/WrLink-active status. This bit indicates that this node’s link is active. The logical AND of this bit and the LPS
C1Rd/WrContender status. This bit indicates that this node is a contender for the bus or isochronous resource
Jitter3RdPHY repeater jitter. This field indicates the worst case difference between the fastest and slowest repeater
Pwr_Class3Rd/WrNode power class. This field indicates this node’s power consumption and source characteristics, and is
RPIE1Rd/WrResuming port interrupt enable. This bit, if set to 1, enables the port event interrupt (PIE) bit to be set
ISBR1Rd/WrInitiate short arbitrated bus-reset. This bit, if set to 1, instructs the PHY to initiate a short (1.30 µs) arbitrated
CTOI1Rd/WrConfiguration time-out interrupt. This bit is set to 1 when the arbitration controller times-out during tree-ID
CPSI1Rd/WrCable power status interrupt. This bit is set to 1 whenever the CPS input transitions from high to low indicating
STOI1Rd/WrState time-out interrupt. This bit indicates that a state time-out has occurred. This bit is reset to 0 by hardware
PEI1Rd/WrPort event interrupt. This bit is set to 1 on any change in the connected, bias, disabled, or fault bits for any port
EAA1Rd/WrEnable accelerated arbitration. This bit enables the PHY to perform the various arbitration acceleration
EMC1Rd/WrEnable multi-speed concatenated packets. This bit enables the PHY to transmit concatenated packets of
144+(delay × 20) ns. For the TSB41LV06 this field is 0.
active status is replicated in the L field (bit 9) of the self-ID packet. This bit is set to 1 by hardware reset and is
unaffected by bus-reset.
manager. This bit is replicated in the c field (bit 20) of the self-ID packet. This bit is set to the state specified by
the C/LKON input pin upon hardware reset and is unaffected by bus-reset.
data delay, expressed as (JITTER+1) × 20 ns. For the TSB41LV06 this field is 0.
replicated in the pwr field (bits 21–23) of the self-ID packet. This field is set to the state specified by the
PC0–PC2 input pins upon hardware reset and is unaffected by bus-reset. See Table 9.
whenever resume operations begin on any port. This bit is reset to 0 by hardware reset and is unaffected by
bus-reset.
bus-reset at the next opportunity. This bit is reset to 0 by bus-reset.
NOTE: Legacy IEEE Std 1394-1995 compliant PHYs may not be capable of performing short bus-resets.
Therefore, initiation of a short bus-reset in a network that contains such a legacy device will result in a long
bus-reset being performed.
start, and may indicate that the bus is configured in a loop. This bit is reset to 0 by hardware reset, or by writing
a 1 to this register bit.
NOTE: If the network is configured in a loop, only those nodes that are part of the loop should generate a
configuration time-out interrupt. All other nodes should instead time-out waiting for the tree-ID and/or self-ID
process to complete and then generate a state time-out interrupt and bus-reset.
that cable power may be too low for reliable operation. This bit is reset to 0 by hardware reset, or by writing a 1
to this register bit.
reset, or by writing a 1 to this register bit.
for which the port interrupt enable (PIE) bit is set. Additionally, if the resuming port interrupt enable (RPIE) bit
is set, the PEI bit is set to 1 at the start of resume operations on any port. This bit is reset to 0 by hardware
reset, or by writing a 1 to this register bit.
enhancements defined in P1394a (ACK-accelerated arbitration, asynchronous fly-by concatenation, and
isochronous fly-by concatenation). This bit is reset to 0 by hardware reset and is unaffected by bus-reset.
NOTE: The EAA bit should be set only if the attached LLC is P1394a compliant. If the LLC is not P1394a
compliant, use of the arbitration acceleration enhancements may interfere with isochronous traffic by
excessively delaying the transmission of cycle-start packets.
differing speeds in accordance with the protocols defined in P1394a. This bit is reset to 0 by hardware reset
and is unaffected by bus-reset.
NOTE: The use of multi-speed concatenation is completely compatible with networks containing legacy
IEEE Std 1394-1995 PHYs. However, use of multi-speed concatenation requires that the attached LLC be
P1394a compliant.
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
15
Page 16
TSB41LV06
ADDRESS
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
Table 2. Base Register Field Descriptions (Continued)
FIELDSIZETYPEDESCRIPTION
Page_Select3Rd/WrPage-select. This field selects the register page to use when accessing register addresses 8 through 15. This
field is reset to 0 by hardware reset and is unaffected by bus-reset.
Port_Select4Rd/WrPort-select. This field selects the port when accessing per-port status or control (e.g., when one of the port
status/control registers is accessed in page 0). Ports are numbered starting at 0. This field is reset to 0 by
hardware reset and is unaffected by bus-reset.
The Port Status page provides access to configuration and status information for each of the ports. The port
is selected by writing 0 to the Page_Select field and the desired port number to the Port_Select field in base
register 7. The configuration of the Port Status page registers is shown in Table 3 and corresponding field
descriptions given in Table 4. If the selected port is un-implemented, all registers in the Port Status page are
read as 0.
Table 4. Page 0 (Port Status) Register Field Descriptions
FIELDSIZETYPEDESCRIPTION
AStat2RdTPA line state. This field indicates the TPA line state of the selected port, encoded as follows:
Bstat2RdTPB line state. This field indicates the TPB line state of the selected port. This field has the same encoding as
the ASTAT field.
Ch1RdChild/parent status. A 1 indicates that the selected port is a child port. A 0 indicates that the selected port is the
parent port. A disconnected, disabled, or suspended port is reported as a child port. The Ch bit is invalid after a
bus–reset until tree-ID has completed.
Con1RdDebounced port connection status. This bit indicates that the selected port is connected. The connection must
be stable for the debounce time of approximately 341 ms for the Con bit to be set to 1. The Con bit is reset to 0 by
hardware reset and is unaffected by bus-reset.
NOTE: The Con bit indicates that the port is physically connected to a peer PHY , but the port is not necessarily
active.
Bias1RdDebounced incoming cable bias status. A 1 indicates that the selected port is detecting incoming cable bias.
The incoming cable bias must be stable for the debounce time of 52 µs for the Bias bit to be set to 1.
Dis1Rd/WrPort disabled control. If 1, the selected port is disabled. The Dis bit is reset to 0 by hardware reset (all ports are
enabled for normal operation following hardware reset). The Dis bit is not affected by bus-reset.
CodeLine State
11Z
011
100
00invalid
16
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 17
ADDRESS
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
Table 4. Page 0 (Port Status) Register Field Descriptions (Continued)
FIELDSIZETYPEDESCRIPTION
Peer_Speed3RdPort peer speed. This field indicates the highest speed capability of the peer PHY connected to the selected
PIE1Rd/WrPort event interrupt enable. When set to 1, a port event on the selected port will set the port event interrupt (PEI)
Fault1Rd/WrFault. This bit indicates that a resume-fault or suspend-fault has occurred on the selected port and that the port
port, encoded as follows:
CodePeer Speed
000S100
001S200
010S400
011–111invalid
The Peer_Speed field is invalid after a bus-reset until self-ID has completed.
NOTE: Peer speed codes higher than 010b (S400) are defined in P1394a. However, the TSB41LV06 is only
capable of detecting peer speeds up to S400.
bit and notify the link. This bit is reset to 0 by hardware reset and is unaffected by bus-reset.
is in the suspended state. A resume-fault occurs when a resuming port fails to detect incoming cable bias from
its attached peer. A suspend-fault occurs when a suspending port continues to detect incoming cable bias from
its attached peer. Writing 1 to this bit clears the Fault bit to 0. This bit is reset to 0 by hardware reset and is
unaffected by bus-reset.
The Vendor Identification page is used to identify the vendor/manufacturer and compliance level. The page is
selected by writing 1 to the Page_Select field in base register 7. The configuration of the Vendor Identification
page is shown in Table 5 and corresponding field descriptions given in Table 6.
Table 6. Page 1 (Vendor ID) Register Field Description
FIELDSIZETYPEDESCRIPTION
Compliance8RdCompliance level. For the TSB41LV06 this field is 01h, indicating compliance with the P1394a specification.
Vendor_ID
Product_ID24RdProduct identifier. For the TSB41LV06 this field is 46_xx_xxh (the MSB is at register address 1101b).
24RdManufacturer’s organizationally unique identifier (OUI). For the TSB41LV06 this field is 08_00_28h (Texas
Instruments) (the MSB is at register address 1010b).
The Vendor-Dependent page provides access to the special control features of the TSB41LV06, as well as
configuration and status information used in manufacturing test and debug. This page is selected by writing 7
to the Page_Select field
in base register 7. The configuration of the Vendor-Dependent page is shown in Table
7 and corresponding field descriptions given in Table 8.
1000NPAReservedLink_Speed
1001Reserved for test
1010Reserved for test
1011Reserved for test
1100Reserved for test
1101Reserved for test
1110Reserved for test
1111Reserved for test
Table 8. Page 7 (Vendor Dependent) Register Field Descriptions
FIELDSIZETYPEDESCRIPTION
NPA1Rd/WrNull-packet actions flag. This bit instructs the PHY to not clear fair and priority requests when a null packet is
received with arbitration acceleration enabled. If 1, then fair and priority requests are cleared only when a
packet of more than 8 bits is received; ACK packets (exactly 8 data bits), null packets (no data bits), and
malformed packets (less than 8 data bits) will not clear fair and priority requests. If 0, then fair and priority
requests are cleared when any non-ACK packet is received, including null-packets or malformed packets of
less than 8 bits. This bit is cleared to 0 by hardware reset and is unaffected by bus-reset.
Link_Speed2Rd/WrLink speed. This field indicates the top speed capability of the attached LLC. Encoding is as follows:
CodeSpeed
00S100
01S200
10S400
11illegal
This field is replicated in the sp field of the self-ID packet to indicate the speed capability of the node (PHY and
LLC in combination). However, this field does not affect the PHY speed capability indicated to peer PHYs
during self-ID; the TSB41L V06 PHY identifies itself as S400 capable to its peers regardless of the value in this
field. This field is set to 10b (S400) by hardware reset and is unaffected by bus-reset.
power-class programming
The PC0–PC2 pins are programmed to set the default value of the power-class indicated in the pwr field (bits
21–23) of the transmitted self-ID packet. Descriptions of the various power-classes are given in Table 9 The
default power-class value is loaded following a hardware reset, but is overriden by any value subsequently
loaded into the Pwr_Class field in register 4.
PC0–PC2DESCRIPTION
000Node does not need power and does not repeat power.
001Node is self-powered and provides a minimum of 15 W to the bus.
010Node is self-powered and provides a minimum of 30 W to the bus.
011Node is self-powered and provides a minimum of 45 W to the bus.
100Node may be powered from the bus for the PHY only using up to 3W and may also provide power to the bus. The amount of bus
power that it provides can be found in the configuration ROM.
101Node is powered from the bus and uses up to 3 W. An additional 2 W is needed to enable the link and higher layers of the node.
110Node is powered from the bus and uses up to 3W. An additional 3W is needed to enable the link.
111Node is powered from the bus and uses up to 3W. An additional 7W is needed to enable the link.
18
Table 9. Power-Class Description
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 19
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
TSB41LV06
Cable Port
CPS
TPBIASx
TPAx+
TPAx–
TPBx+
TPBx–
220 pF
(see Note A)
400 kΩ
1 µF
56 Ω56 Ω
56 Ω56 Ω
5 kΩ
Cable
Power
Pair
Cable
Pair
A
Cable
Pair
B
Outer Shield
Termination
NOTE A: The IEEE Std 1394-1995 calls for a 250 pF capacitor, which is a non-standard component value. A 220 pF capacitor is recommended.
Figure 4. TP Cable Connections
Outer Cable Shield
1 MΩ
Chassis Ground
0.001 µF0.01 µF
Figure 5. Compliant DC Isolated Outer Shield Termination
The TSB41L V06 is housed in a high performance, thermally enhanced, 100-pin PZP PowerP AD package. Use
of the PowerP AD package does not require any special considerations except to note that the PowerPAD, which
is an exposed die pad on the bottom of the device, is a metallic thermal and electrical conductor. Therefore, if
not implementing PowerPAD PCB features, the use of solder masks (or other assembly techniques) may be
required to prevent any inadvertent shorting by the exposed PowerP AD of connection etches or vias under the
package. The recommended option, however, is to not run any etches or signal vias under the device, but to
have only a grounded thermal land as explained below. Although the actual size of the exposed die pad may
vary, the minimum size required for the keepout area for the 100-pin PZP PowerPAD package is
12 mm × 12 mm.
It is recommended that there be a thermal land, which is an area of solder-tinned-copper, underneath the
PowerP AD package. The thermal land will vary in size depending on the PowerPAD package being used, the
PCB construction, and the amount of heat that needs to be removed. In addition, the thermal land may or may
not contain numerous thermal vias depending on PCB construction.
Other requirements for thermal lands and thermal vias are detailed in the TI application note
Thermally Enhanced Package Application Report
pages beginning at URL: http://www.ti.com.
Figure 9. Example of a Thermal Land for the TSB41LV06 PHY
For the TSB41LV06, this thermal land should be grounded to the low impedance ground plane of the device.
This improves not only thermal performance but also the electrical grounding of the device. It is also
recommended that the device ground pin landing pads be connected directly to the grounded thermal land. The
land size should be as large as possible without shorting device signal pins. The thermal land may be soldered
to the exposed PowerPAD using standard reflow soldering techniques.
, TI literature number SLMA002, available via the TI Web
PowerPAD
While the thermal land may be electrically floated and configured to remove heat to an external heat sink, it is
recommended that the thermal land be connected to the low impedance ground plane for the device. More
information may be obtained from the TI application note
PHY Layout
, TI literature number SLLA020.
using the TSB41LV06 with a non-P1394a link layer
The TSB41LV06 implements the PHY-LLC interface specified in the P1394a Supplement. This interface is
based upon the interface described in informative Annex J of IEEE Std 1394–1995, which is the interface used
in older TI PHY devices. The PHY-LLC interface specified in P1394a is completely compatible with the older
Annex J interface.
22
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 23
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
using the TSB41LV06 with a non-P1394a link layer (continued)
The P1394a Supplement includes enhancements to the Annex J interface that must be comprehended when
using the TSB41LV06 with a non-P1394a LLC device.
D
A new LLC service request was added which allows the LLC to temporarily enable and disable
asynchronous arbitration accelerations. If the LLC does not implement this new service request, the
arbitration enhancements should not be enabled (see the EAA bit in PHY register 5).
D
The capability to perform multispeed concatenation (the concatenation of packets of differing speeds) was
added in order to improve bus efficiency (primarily during isochronous transmission). If the LLC does not
support multispeed concatenation, multispeed concatenation should not be enabled in the PHY (see the
EMC bit in PHY register 5).
D
In order to accommodate the higher transmission speeds expected in future revisions of the standard,
P1394A extended the speed code in bus requests from 2 bits to 3 bits, increasing the length of the bus
request from 7 bits to 8 bits. The new speed codes were carefully selected so that new P1394a PHY and
LLC devices would be compatible, for speeds from S100 to S400, with legacy PHY and LLC devices that
use the 2-bit speed codes. The TSB41L V06 will correctly interpret both 7-bit bus requests (with 2-bit speed
codes) and 8-bit bus requests (with 3-bit speed codes). Moreover, if a 7-bit bus request is immediately
followed by another request (e.g., a register read or write request), the TSB41LV06 will correctly interpret
both requests. Although the TSB41L V06 will correctly interpret 8-bit bus requests, a request with a speed
code exceeding S400 will result in the TSB41LV06 transmitting a null packet (data-prefix followed by
data-end, with no data in the packet).
More explanation is included in the TI application note
Physical Layer Devices,
TI literature number SLL019.
IEEE 1394a Features Supported by TI TSB41LV0X
using the TSB41LV06 with a lower-speed link layer
Although the TSB41LV06 is an S400 capable PHY, it may be used with lower speed LLCs, such as the S200
capable TSB12L V31. In such a case, the LLC has fewer data terminals than the PHY, and some Dn terminals
on the TSB41LV06 will be unused. Unused Dn terminals should be pulled to ground through 10 kΩ resistors.
The TSB41LV06 transfers all received packet data to the LLC, even if the speed of the packet exceeds the
capability of the LLC to accept it. Some lower speed LLC designs do not properly ignore packet data in such
cases. On the rare occasions that the first 16 bits of partial data accepted by such a LLC match a node’s bus
and node ID, spurious header CRC or tcode errors may result.
During bus initialization following a bus-reset, each PHY transmits a self-ID packet that indicates, among other
information, the speed capability of the PHY. The bus manager (if one exists) builds a speed-map from the
collected self-ID packets. This speed-map gives the highest possible speed that can be used on the
node-to-node communication paths between every pair of nodes in the network.
In the case of a node consisting of a higher-speed PHY and a lower-speed LLC, the speed capability of the node
(PHY and LLC in combination) is that of the lower-speed LLC. A sophisticated bus manager may be able to
determine the LLC speed capability by reading the configuration ROM Bus_Info_Block, or by sending
asynchronous request packets at different speeds to the node and checking for an acknowledge; the
speed-map may then be adjusted accordingly. The speed-map should reflect that communication to such a
node must be done at the lower speed of the LLC, instead of the higher speed of the PHY . However , speed-map
entries for paths that merely pass through the node’s PHY, but do not terminate at that node, should not be
restricted by the lower speed of the LLC.
using the TSB41LV06 with a lower-speed link layer (continued)
T o assist in building an accurate speed-map, the TSB41L V06 has the capability of indicating a speed capability
other than S400 in its transmitted self-ID packet. This is controlled by the Link_Speed field in register 8 of the
Vendor-Dependent page (page 7). Setting the Link_Speed field af fects only the speed indicated in the self-ID
packet; it has no effect on the speed signaled to peer PHYs during self-ID. The TSB41L V06 identifies itself as
S400 capable to its peers regardless of the value in the Link_Speed field.
Generally, the Link_Speed field should not be changed from its power-on default value of S400 unless it is
determined that the speed-map (if one exists) is incorrect for path entries terminating in the local node. If the
speed-map is incorrect, it can be assumed that the bus manager has used only the self-ID packet information
to build the speed-map. In this case, the node may update the Link_Speed field to reflect the lower speed
capability of the LLC and then initiate another bus-reset to cause the speed-map to be rebuilt. Note that in this
scenario any speed-map entries for node-to-node communication paths that pass through the local node’s PHY
will be restricted by the lower speed.
In the case of a leaf node (which has only one active port) the Link_Speed field may be set to indicate the speed
of the LLC without first checking the speed–map. Changing the Link_Speed field in a leaf node can only affect
those paths that terminate at that node, since no other paths can pass through a leaf node. It can have no effect
on other paths in the speed-map. For hardware configurations which can only be a leaf node (all ports but one
are unimplemented), it is recommended that the Link_Speed field be updated immediately after power-on or
hardware reset.
power-up reset
T o ensure proper operation of the TSB41L V06 the RESET pin must be asserted low for a minimum of 2 ms from
the time that PHY power reaches the minimum required supply voltage. When using a passive capacitor on the
RESET
minimum value of 0.1 µF and also satisfies the following equation:
where C
Additionally , an approximately 120-kΩ resistor should be connected in parallel with the reset capacitor from the
RESET terminal to GND to ensure that the capacitor is discharged when PHY power is removed. An alternative
to the passive reset is to actively drive RESET low for the minimum reset time following power on.
pin to generate a power-on reset signal, the minimum reset time will be assured if the capacitor has a
= 0.0077 × T + 0.085
C
min
is the minimum capacitance on the RESET pin in µF , and T is the VDD ramp time, 10%–90%, in ms.
min
crystal selection
TI PHYs may use an external 24.576 MHz crystal connected between the XI and XO pins on the PHY to provide
the PHY clock. The following are some typical specifications for the crystals used with the Physical Layers from
TI. The clock resulting from the input from the crystal must be within the tolerance of ±100 parts per million for
the PHYs to function correctly. This is required by the 1394 standard. This frequency tolerance for the PHY
clocks on each node must be maintained over the variation introduced over production runs of boards and
environment the machines operate. Every board must have an SYSCLK (clock generated by the PHY) within
±100 ppm of 49.152 MHz to be compliant to the 1394 standard. If adjacent nodes are more than 200ppm away
from one another then long packets sent across the 1394 bus may be corrupted, with the final bits of the packet
being lost. TI PHYs are designed with a maximum of margin, but must still adhered to the limits imposed by 1394.
24
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 25
crystal selection (continued)
1. Crystal Mode of operation:
Fundamental
2. Frequency Tolerance at 25°C:
T otal variation specification for the complete circuit is 100ppm. The crystal is specified at less than 100 ppm.
It is currently recommended ours at ±30 ppm.
3. Frequency stability (over temperature):
T otal variation specification for the complete circuit is 100 ppm. The crystal is specified at less than 100 ppm.
It is currently recommended ours at ±30ppm.
The total variation must be kept below 100 ppm with some allowance for variation introduced by
variations in board builds and device tolerances. So the sum of the frequency tolerance and the
frequency stability must be less than 100 ppm. This can be traded between the two, for example
the frequency tolerance may be specified at 50 ppm and the temperature may be specified at
30 ppm to give a total of 80 ppm possible variation just due to the crystal. Aging of the crystal also
contributes to the net ppm.
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
APPLICATION INFORMATION
NOTE:
4. Load capacitance: [Parallel (pF)]
Parallel mode crystal circuits have been used since they should be matched to the onchip oscillator. Load
capacitance will be a function of the board layout and circuit. The total load capacitance (CL) will affect the
frequency the crystal oscillates at. Consult with a crystal vendor and iterate the design to get an SYSCLK
supplied by the PHY to less than 100 ppm from 49.152 MHz . It is recommended that a maximum of ±5%
tolerance load capacitors be used. For our OHCI + 41L V03 Evaluation Module (EVM) with a crystal specified
for 20pF loading, a value of 33 pF for each load capacitor (C9 = C10 below) was found to be appropriate
with the layout used for the board. The load specified for the crystal includes the load capacitors (C9, C10),
the loading of the PHY pins (C
C10) / (C9+C10)] + C
+ CBD. Representative values for C
PHY
), and the loading of the board itself (CBD). To summarize: CL =[ (C9 ×
PHY
are ~1 pF and for CBD are about 0.8 pF
PHY
per centimeter of board etch, a typical board can have from 3 pF to 6 pF or more. The capacitance of load
capacitors C9 and C10 combine as capacitors in series.
The layout of the crystal portion of the PHY circuit is important for getting the correct frequency from
the crystal, minimizing the noise introduced into the PHY Phase Lock Loop, and minimizing any
emissions from the circuit. The crystal and the two load capacitors should be considered a unit
during layout. The crystal and the load capacitors should be placed as close as possible to one
another while minimizing the loop area created by the combination of the three components.
Varying the size of the capacitors may help in this. Minimizing the loop area minimizes the effect
of the resonant current (Is) that flows in this resonant circuit. This layout unit (crystal and load
capacitors) should then be placed as close as possible to the PHY XI and XO pins to minimize etch
lengths.
C9
C10
X1
Figure 11. Recommended Crystal and Capacitor Layout for the TSB41LV06 PHY
It is strongly recommend that part of the verification process for the design be to measure the frequency of the
SYSCLK put out by the PHY . This should be done with a frequency counter with an accuracy of 6 digits or better .
If the SYSCLK is more than the crystal tolerance away from 49.152 MHz, the load capacitance of the crystal
may be varied to see if this brings it into line. If the frequency is too high add more load capacitance, if the
frequency is too low decrease load capacitance. Typically changes should be done to both load capacitors (C9
and C10 above) at the same time to the same value. It is suggested that a consultation with the crystal vendors
for a more detailed understanding of what is required. In order for a 1394 bus to operate correctly each SYSCLK
on each node on the bus must be within 200 ppm of the adjacent SYSCLK on the bus. The 1394 standard
requires this by specifying a center frequency of 49.152 MHz and a ±100 ppm tolerance around 49.152 MHz.
bus reset
To initiate a bus reset from software (SW) for a 1394-1995 PHY layer, the link layer uses the PHY chip access
register to write into PHY register 0001b. This changes the state of the initiate bus reset (IBR) bit. This bit is in
the same register as the gap count and root hold–off bit (RHB). Anytime the IBR bit is set, the gap count and
RHB are also set. The following is the recommended IBR sequence: read the PHY register 0001b, change only
the bits that need to be changed making sure to keep all other bits the same, and finally write a new value to
the PHY register 0001b. There is only one case in which a value other than 3Fh should ever be written into the
gap count field. This case occurs during the initiation of a bus reset immediately after a PHY configuration
packet. The PHY configuration packet is sent to set the gap counts of each node to the same value. In this case,
during the write to set the IBR bit, the gap count should be the same as the gap count written by the immediately
previous PHY configuration packet. This is required since after every two bus resets (unless a gap count register
write occurs between the bus resets) all gap counts are reset to the default value of 3Fh.
26
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 27
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
The TSB41LV06 is designed to operate with a LLC such as the Texas Instruments TSB12LV21, TSB12LV31,
TSB12L V41, TSB12LV01, or TSB12L V22. Details of operation for the T exas Instruments LLC devices are found
in the respective LLC data sheets. The following paragraphs describe the operation of the PHY -LLC interface.
The interface to the LLC consists of the SYSCLK, CTL0–CTL1, D0–D7, LREQ, LPS, C/LKON, and ISO
terminals on the TSB41LV06, as shown in Figure 12.
TSB41LV06
SYSCLK
CTL0–CTL1
LINK
LAYER
CONTROLLER
D0–D7
LREQ
LPS
C/LKON
ISO
ISO
ISO
Figure 12. PHY-LLC Interface
The SYSCLK terminal provides a 49.152 MHz interface clock. All control and data signals are synchronized to,
and sampled on, the rising edge of SYSCLK.
The CTL0 and CTL1 terminals form a bidirectional control bus, which controls the flow of information and data
between the TSB41LV06 and LLC.
The D0–D7 terminals form a bidirectional data bus, which is used to transfer status information, control
information, or packet data between the devices. The TSB41LV06 supports S100, S200, and S400 data
transfers over the D0–D7 data bus. In S100 operation only the D0 and D1 terminals are used; in S200 operation
only the D0–D3 terminals are used; and in S400 operation all D0–D7 terminals are used for data transfer. When
the TSB41LV06 is in control of the D0–D7 bus, unused Dn terminals are driven low during S100 and S200
operations. When the LLC is in control of the D0–D7 bus, unused Dn terminals are ignored by the TSB41L V06.
The LREQ terminal is controlled by the LLC to send serial service requests to the PHY in order to request access
to the serial-bus for packet transmission, read or write PHY registers, or control arbitration acceleration.
The LPS and C/LKON terminals are used for power management of the PHY and LLC. The LPS terminal
indicates the power status of the LLC, and may be used to reset the PHY -LLC interface or to disable SYSCLK.
The C/LKON terminal is used to send a wake-up notification to the LLC and to indicate an interrupt to the LLC
when either LPS is inactive or the PHY register L bit is zero.
The /ISO terminal is used to enable the output differentiation logic on the CTL0–CTL1 and D0–D7 terminals.
Output differentiation is required when an isolation barrier of the type described in Annex J of IEEE
Std 1394–1995 is implemented between the PHY and LLC.
The TSB41L V06 normally controls the CTL0–CTL1 and D0–D7 bidirectional buses. The LLC is allowed to drive
these buses only after the LLC has been granted permission to do so by the PHY.
There are four operations that may occur on the PHY–LLC interface: link service request, status transfer, data
transmit, and data receive. The LLC issues a service request to read or write a PHY register, to request the PHY
to gain control of the serial-bus in order to transmit a packet, or to control arbitration acceleration.
The PHY may initiate a status transfer either autonomously or in response to a register read request from the
LLC.
The PHY initiates a receive operation whenever a packet is received from the serial-bus.
The PHY initiates a transmit operation after winning control of the serial-bus following a bus-request by the LLC.
The transmit operation is initiated when the PHY grants control of the interface to the LLC.
The encoding of the CTL0–CTL1 bus is shown in Table10 and Table 11.
Table 10. CTL Encoding When PHY Has Control of the Bus
CTL0CTL1NAMEDESCRIPTION
00IdleNo activity (this is the default mode)
01StatusStatus information is being sent from the PHY to the LLC
10ReceiveAn incoming packet is being sent from the PHY to the LLC
11GrantThe LLC has been given control of the bus to send an outgoing packet
Table 11. CTL Encoding When LLC Has Control of the Bus
CTL0CTL0NAMEDESCRIPTION
00IdleThe LLC releases the bus (transmission has been completed)
01HoldThe LLC is holding the bus while data is being prepared for transmission, or indicating
10TransmitAn outgoing packet is being sent from the LLC to the PHY
11ReservedNone
that another packet is to be transmitted (concatenated) without arbitrating
LLC service request
T o request access to the bus, to read or write a PHY register, or to control arbitration acceleration, the LLC sends
a serial bit stream on the LREQ terminal as shown in Figure 13.
LR1
NOTE: Each cell represents one clock sample time, and n is the number of bits in the request stream.
Figure 13. LREQ Request Stream
The length of the stream will vary depending on the type of request as shown in Table 12.
Table 12. LLC Request Stream Bit Length
REQUEST TYPENUMBER OF BITS
Bus Request7 or 8
Read Register Request9
Write Register Request17
Acceleration Control Request6
LR2LR3LR (n–2)LR0LR (n–1)
28
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 29
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
LLC service request (continued)
Regardless of the type of request, a start-bit of 1 is required at the beginning of the stream, and a stop-bit of
0 is required at the end of the stream. The second through fourth bits of the request stream indicate the type
of the request. In the descriptions below, bit 0 is the most significant and is transmitted first in the request bit
stream. The LREQ terminal is normally low.
Encoding for the request type is shown in Table 13.
Table 13. Request Type Encoding
LR1–LR3NAMEDESCRIPTION
000ImmReqImmediate bus request. Upon detection of idle, the PHY takes control of the bus immediately without arbitration.
001IsoReqIsochronous bus request. Upon detection of idle, the PHY arbitrates for the bus without waiting for a subaction gap.
010PriReqPriority bus request. The PHY arbitrates for the bus after a subaction gap, ignores the fair protocol.
011FairReqFair bus request. The PHY arbitrates for the bus after a subaction gap, follows the fair protocol.
100RdRegThe PHY returns the specified register contents through a status transfer .
101WrRegWrite to the specified register.
110AccelCtlEnable or disable asynchronous arbitration acceleration.
111ReservedReserved
For a Bus Request the length of the LREQ bit stream is 7 or 8 bits as shown in Table 14.
Table 14. Bus Request
BIT(s)NAMEDESCRIPTION
0Start BitIndicates the beginning of the transfer (always 1).
1-3Request TypeIndicates the type of bus request. See T able 13.
4-6Request SpeedIndicates the speed at which the PHY will send the data for this request. See Table 15 for the encoding of this
7Stop BitIndicates the end of the transfer (always 0). If bit 6 is 0, this bit may be omitted.
field.
The 3-bit Request Speed field used in bus requests is shown in Table 15.
Table 15. Bus Request Speed Encoding
LR4–LR6DATA RATE
000S100
010S200
100S400
All OthersInvalid
NOTE:
The TSB41L V06 will accept a bus request with an invalid speed code and process the bus request
normally . However , during packet transmission for such a request, the TSB41L V06 will ignore any
data presented by the LLC and will transmit a null packet.
For a Read Register Request the length of the LREQ bit stream is 9 bits as shown in Table 16.
Table 16. LLC Read Register Request
BIT(s)NAMEDESCRIPTION
0Start BitIndicates the beginning of the transfer (always 1).
1-3Request TypeA 100 indicating this is a read register request.
4-7AddressIdentifies the address of the PHY register to be read.
8Stop BitIndicates the end of the transfer (always 0).
For a Write Register Request the Length of the LREQ data stream is 17 bits as shown in Table 17.
Table 17. Write Register Request
BIT(s)NAMEDESCRIPTION
0Start BitIndicates the beginning of the transfer (always 1).
1-3Request TypeA 101 indicating this is a write register request.
4-7AddressIdentifies the address of the PHY register to be written to.
8-15DataGives the data that is to be written to the specified register address.
16Stop BitIndicates the end of the transfer (always 0).
For an Acceleration Control Request the Length of the LREQ data stream is 6 bits as shown in Table 18.
Table 18. Acceleration Control Request
BIT(s)NAMEDESCRIPTION
0Start BitIndicates the beginning of the transfer (always 1).
1-3Request Type A 110 indicating this is an acceleration control request.
4ControlAsynchronous period arbitration acceleration is enabled if 1, and disabled if 0.
5Stop BitIndicates the end of the transfer (always 0).
For fair or priority access, the LLC sends the bus request (FairReq or PriReq) at least one clock after the
PHY -LLC interface becomes idle. If the CTL terminals are asserted to the Receive state (10b) by the PHY, then
any pending fair or priority request is lost (cleared). Additionally, the PHY ignores any fair or priority requests
if the Receive state is asserted while the LLC is sending the request. The LLC may then reissue the request
one clock after the next interface idle.
The cycle master node uses a priority bus request (PriReq) to send a cycle start message. After receiving or
transmitting a cycle start message, the LLC can issue an isochronous bus request (IsoReq). The PHY will clear
an isochronous request only when the serial bus has been won.
T o send an acknowledge packet, the LLC must issue an immediate bus request (ImmReq) during the reception
of the packet addressed to it. This is required in order to minimize the idle gap between the end of the received
packet and the start of the transmitted acknowledge packet. As soon as the receive packet ends, the PHY
immediately grants control of the bus to the LLC. The LLC sends an acknowledgment to the sender unless the
header CRC of the received packet is corrupted. In this case, the LLC does not transmit an acknowledge, but
instead cancels the transmit operation and releases the interface immediately; the LLC must not use this grant
to send another type of packet. After the interface is released the LLC may proceed with another request.
30
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 31
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
LLC service request (continued)
The LLC may make only one bus request at a time. Once the LLC issues any request for bus access (ImmReq,
IsoReq, FairReq, or PriReq), it cannot issue another bus request until the PHY indicates that the bus request
was lost (bus arbitration lost and another packet received), or won (bus arbitration won and the LLC granted
control). The PHY ignores new bus requests while a previous bus request is pending. All bus requests are
cleared upon a bus reset.
For write register requests, the PHY loads the specified data into the addressed register as soon as the request
transfer is complete. For read register requests, the PHY returns the contents of the addressed register to the
LLC at the next opportunity through a status transfer. If a received packet interrupts the status transfer , then the
PHY continues to attempt the transfer of the requested register until it is successful. A write or read register
request may be made at any time, including while a bus request is pending. Once a read register request is
made, the PHY ignores further read register requests until the register contents are successfully transferred to
the LLC. A bus reset does not clear a pending read register request.
The TSB41L V06 includes several arbitration acceleration enhancements, which allow the PHY to improve bus
performance and throughput by reducing the number and length of interpacket gaps. These enhancements
include autonomous (fly-by) isochronous packet concatenation, autonomous fair and priority packet
concatenation onto acknowledge packets, and accelerated fair and priority request arbitration following
acknowledge packets. The enhancements are enabled when the EAA bit in PHY register 5 is set.
The arbitration acceleration enhancements may interfere with the ability of the cycle master node to transmit
the cycle start message under certain circumstances. The acceleration control request is therefore provided
to allow the LLC to temporarily enable or disable the arbitration acceleration enhancements of the TSB41L V06
during the asynchronous period. The LLC typically disables the enhancements when its internal cycle counter
rolls over indicating that a cycle start message is imminent, and then re-enables the enhancements when it
receives a cycle start message. The acceleration control request may be made at any time, however, and is
immediately serviced by the PHY. Additionally, a bus reset or isochronous bus request will cause the
enhancements to be re-enabled, if the EAA bit is set.
status transfer
A status transfer is initiated by the PHY when there is status information to be transferred to the LLC. The PHY
waits until the interface is idle before starting the transfer. The transfer is initiated by the PHY asserting
(01b) on the CTL terminals, along with the first two bits of status information on the D[0:1] terminals. The PHY
maintains CTL =
by asserting something other than
status transfer completes. The PHY continues to attempt to complete the transfer until all status information has
been successfully transmitted. There is at least one idle cycle between consecutive status transfers.
The PHY normally sends just the first four bits of status to the LLC. These bits are status flags that are needed
by the LLC state machines. The PHY sends an entire 16-bit status packet to the LLC after a read register
request, or when the PHY has pertinent information to send to the LLC or transaction layers. The only defined
condition where the PHY automatically sends a register to the LLC is after self-ID, where the PHY sends the
physical–ID register that contains the new node address. All status transfers are either 4 or 16 bits unless
interrupted by a received packet. The status flags are considered to have been successfully transmitted to the
LLC immediately upon being sent, even if a received packet subsequently interrupts the status transfer. Register
contents are considered to have been successfully transmitted only when all 8 bits of the register have been
sent. A status transfer is retried after being interrupted only if any status flags remain to be sent, or if a register
transfer has not yet completed.
Status
for the duration of the status transfer. The PHY may prematurely end a status transfer
Status
on the CTL terminals. This occurs if a packet is received before the
The definition of the bits in the status transfer are shown in Figure 14 Table 19 and the timing is shown in
Figure 14.
Table 19. Status Bits
BIT(s)NAMEDESCRIPTION
0Arbitration Reset GapIndicates that the PHY has detected that the bus has been idle for an arbitration reset gap time (as defined in
the IEEE 1394–1995 standard). This bit is used by the LLC in the busy/retry state machine.
1Subaction GapIndicates that the PHY has detected that the bus has been idle for a subaction gap time (as defined in the
IEEE 1394–1995 standard). This bit is used by the LLC to detect the completion of an isochronous cycle.
2Bus ResetIndicates that the PHY has entered the bus reset state.
3InterruptIndicates that a PHY interrupt event has occurred. An interrupt event may be a configuration time-out,
cable-power voltage falling too low, a state time-out, or a port status change.
4–7AddressThis field holds the address of the PHY register whose contents are being transferred to the LLC.
8–15DataThis field holds the register contents.
SYSCLK
CTL0, CTL1
D0, D1
(a)
00
00S[14:15]S[0:1]
01
(b)
00
00
Figure 14. Status Transfer Timing
The sequence of events for a status transfer is as follows:
1. Status transfer initiated. The PHY indicates a status transfer by asserting status on the CTL lines along with
the status data on the D0 and D1 lines (only 2 bits of status are transferred per cycle). Normally (unless
interrupted by a receive operation), a status transfer will be either 2 or 8 cycles long. A 2-cycle (4 bit) transfer
occurs when only status information is to be sent. An 8-cycle (16 bit) transfer occurs when register data is
to be sent in addition to any status information.
2. Status transfer terminated. The PHY normally terminates a status transfer by asserting Idle on the CTL
lines. The PHY may also interrupt a status transfer at any cycle by asserting receive on the CTL lines to
begin a receive operation. The PHY shall assert at least one cycle of Idle between consecutive status
transfers. The PHY may also assert Grant on the CTL lines immediately following a complete status transfer.
receive
Whenever the PHY detects the data-prefix state on the serial bus, it initiates a receive operation by asserting
Receive on the CTL terminals and a logic 1 on each of the D terminals (data-on indication). The PHY indicates
the start of a packet by placing the speed code (encoded as shown in Table 5 on the D terminals, followed by
packet data. The PHY holds the CTL terminals in the receive state until the last symbol of the packet has been
transferred. The PHY indicates the end of packet data by asserting Idle on the CTL terminals. All received
packets are transferred to the LLC. Note that the speed code is part of the PHY -LLC protocol and is not included
in the calculation of CRC or any other data protection mechanisms.
32
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 33
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
receive (continued)
It is possible for the PHY to receive a null packet, which consists of the data-prefix state on the serial bus followed
by the data-end state, without any packet data. A null packet is transmitted whenever the packet speed exceeds
the capability of the receiving PHY , or whenever the LLC immediately releases the bus without transmitting any
data. In this case, the PHY will assert Receive on the CTL terminals with the data-on indication (all 1s) on the
D terminals, followed by Idle on the CTL terminals, without any speed code or data being transferred. In all
cases, the TSB41L V06 sends at least one data-on indication before sending the speed code or terminating the
receive operation.
The TSB41L V06 also transfers its own self-ID packet, transmitted during the self-ID phase of bus initialization,
to the LLC. This packet it transferred to the LLC just as any other received self-ID packet.
SYSCLK
(a)
CTL0, CTL1
D0–D7
NOTE B: SPD = Speed code, see Table 20 d0–dn = Packet data
00
01
(b)
XXdnd0SPD
FF (“data-on”)
(c)(d)
0010
(e)
00
Figure 15. Normal Packet Reception Timing
The sequence of events for a normal packet reception is as follows:
1. Receive operation initiated. The PHY indicates a receive operation by asserting receive on the CTL lines.
Normally, the interface is Idle when receive is asserted. However, the receive operation may interrupt a
status transfer operation that is in progress so that the CTL lines may change from status to receive without
an intervening Idle.
2. Data-on indication. The PHY may assert the data-on indication code on the D lines for zero or more cycles
preceding the speed-code.
3. Speed-code. The PHY indicates the speed of the received packet by asserting a speed-code on the D lines
for one cycle immediately preceding packet data. The link decodes the speed-code on the first receive cycle
for which the D lines are not the data-on code. If the speed-code is invalid, or indicates a speed higher that
that which the link is capable of handling, the link should ignore the subsequent data.
4. Receive data. Following the data-on indication (if any) and the speed-code, the PHY asserts packet data
on the D lines with receive on the CTL lines for the remainder of the receive operation.
5. Receive operation terminated. The PHY terminates the receive operation by asserting Idle on the CTL lines.
The PHY asserts at least one cycle of Idle following a receive operation.
The sequence of events for a null packet reception is as follows:
1. Receive operation initiated. The PHY indicates a receive operation by asserting Receive on the CTL lines.
Normally, the interface is Idle when Receive is asserted. However, the receive operation may interrupt a
status transfer operation that is in progress so that the CTL lines may change from Status to Receive without
an intervening Idle.
2. Data–on indication. The PHY asserts the data–on indication code on the D lines for one or more cycles.
3. Receive operation terminated. The PHY terminates the receive operation by asserting Idle on the CTL lines.
The PHY shall assert at least one cycle of Idle following a receive operation.
Table 20. Receive Speed Codes
D0–D7DATA RATE
00XX XXXXS100
0100 XXXXS200
0101 0000S400
1YYY YYYY“data–on” indication
NOTE: X = Output as 0 by PHY , ignored by LLC.
Y = Output as 1 by PHY , ignored by LLC
transmit
When the LLC issues a bus request through the LREQ terminal, the PHY arbitrates to gain control of the bus.
If the PHY wins arbitration for the serial bus, the PHY -LLC interface bus is granted to the LLC by asserting the
Grant state (11b) on the CTL terminals for one SYSCLK cycle, followed by Idle for one clock cycle. The LLC
then takes control of the bus by asserting either Idle (00b), hold (01b) or transmit (10b) on the CTL terminals.
Unless the LLC is immediately releasing the interface, the LLC may assert the Idle state for at most one clock
before it must assert either hold or transmit on the CTL terminals. The hold state is used by the LLC to retain
control of the bus while it prepares data for transmission. The LLC may assert hold for zero or more clock cycles
(i.e., the LLC need not assert hold before transmit). The PHY asserts data-prefix on the serial bus during this
time.
34
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 35
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
transmit (continued)
When the LLC is ready to send data, the LLC asserts transmit on the CTL terminals as well as sending the first
bits of packet data on the D lines. The transmit state is held on the CTL terminals until the last bits of data have
been sent. The LLC then asserts either Hold or Idle on the CTL terminals for one clock cycle, and then asserts
Idle for one additional cycle before releasing the interface bus and 3-stating the CTL and D terminals. The PHY
then regains control of the interface bus.
The hold state asserted at the end of packet transmission indicates to the PHY that the LLC requests to send
another packet (concatenated packet) without releasing the serial bus. The PHY responds to this concatenation
request by waiting the required minimum packet separation time and then asserting Grant as before. This
function may be used to send a unified response after sending an acknowledge, or to send consecutive
isochronous packets during a single isochronous period. Unless multispeed concatenation is enabled, all
packets transmitted during a single bus ownership must be of the same speed (since the speed of the packet
is set before the first packet). If multispeed concatenation is enabled (when the EMSC bit of PHY register 5 is
set), the LLC must specify the speed code of the next concatenated packet on the D terminals when it asserts
hold on the CTL terminals at the end of a packet. The encoding for this speed code is the same as the speed
code that precedes received packet data as given in Table 20.
After sending the last packet for the current bus ownership, the LLC releases the bus by asserting Idle on the
CTL terminals for two clock cycles. The PHY begins asserting idle on the CTL terminals one clock after sampling
idle from the link. Note that whenever the D and CTL terminals change direction between the PHY and the LLC,
there is an extra clock period allowed so that both sides of the interface can operate on registered versions of
the interface signals.
SYSCLK
(g)(e)(d)(c)(b)(a)
CTL0, CTL1
D0–D7
NOTE A: SPD = Speed code, see Table 20 d0–dn = Packet data
The sequence of events for a normal packet transmission is as follows:
1. Transmit operation initiated. The PHY asserts Grant on the CTL lines followed by Idle to hand over control
of the interface to the link so that the link may transmit a packet. The PHY releases control of the interface
(i.e., it 3-states the CTL and D outputs) following the Idle cycle.
2. Optional idle cycle. The link may assert at most one idle cycle preceding assertion of either hold or transmit.
This idle cycle is optional; the link is not required to assert Idle preceding either hold or transmit.
3. Optional hold cycles. The link may assert hold for up to 47 cycles preceding assertion of transmit. These
hold cycle(s) are optional; the link is not required to assert hold preceding transmit.
4. Transmit data. When data is ready to be transmitted, the link asserts transmit on the CTL lines along with
the data on the D lines.
5. Transmit operation terminated. The transmit operation is terminated by the link asserting hold or idle on the
CTL lines. The link asserts hold to indicate that the PHY is to retain control of the serial bus in order to
transmit a concatenated packet. The link asserts Idle to indicate that packet transmission is complete and
the PHY may release the serial bus. The link then asserts Idle for one more cycle following this cycle of hold
or idle before releasing the interface and returning control to the PHY.
6. Concatenated packet speed-code. If multispeed concatenation is enabled in the PHY, the link shall assert
a speed-code on the D lines when it asserts hold to terminate packet transmission. This speed-code
indicates the transmission speed for the concatenated packet that is to follow. The encoding for this
concatenated packet speed-code is the same as the encoding for the received packet speed-code (see
Table 20. The link may not concatenate an S100 packet onto any higher-speed packet.
7. After regaining control of the interface, the PHY shall assert at least one cycle of Idle before any subsequent
status transfer, receive operation, or transmit operation.
SYSCLK
(e)(d)(c)(b)(a)
CTL0, CTL1
D0–D7
000000
00
000011
PHY High-Impedance CTL and D outputs
01
00
Link controls CTL and D
00
Figure 18. Cancelled/Null packet Transmission
36
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Page 37
TSB41LV06
IEEE 1394a SIX-PORT CABLE TRANSCEIVER/ARBITER
SLLS289 – JANAURY1999
PRINCIPLES OF OPERATION
transmit (continued)
The sequence of events for a cancelled/null packet transmission is as follows:
1. Transmit operation initiated. PHY asserts Grant on the CTL lines followed by Idle to hand over control of
the interface to the link.
2. Optional idle cycle. The link may assert at most one Idle cycle preceding assertion of hold. This idle cycle
is optional; the link is not required to assert Idle preceding hold.
3. Optional hold cycles. The link may assert hold for up to 47 cycles preceding assertion of Idle. These hold
cycle(s) are optional; the link is not required to assert hold preceding idle.
4. Null transmit termination. The null transmit operation is terminated by the link asserting two cycles of Idle
on the CTL lines and then releasing the interface and returning control to the PHY. Note that the link may
assert idle for a total of 3 consecutive cycles if it asserts the optional first idle cycle but does not assert hold.
(It is recommended that the link assert 3 cycles of Idle to cancel a packet transmission if no hold cycles are
asserted. This guarantees that either the link or PHY controls the interface in all cycles.)
5. After regaining control of the interface, the PHY shall assert at least one cycle of idle before any subsequent
status transfer, receive operation, or transmit operation.
NOTES: A. All linear dimensions are in millimeters.
PowerPAD is a trademark of Texas Instruments Incorporated.
38
B. This drawing is subject to change without notice.
C. Body dimensions include mold flash or protrusions.
D. The package thermal performance may be enhanced by bonding the thermal pad to an external thermal plane. This pad is electrically
and thermally connected to the backside of the die and possibly selected leads.
E. Falls within JEDEC MS-026
POST OFFICE BOX 655303 • DALLAS, TEXAS 75265
Seating Plane
0,08
4146929/A 12/97
Page 39
IMPORTANT NOTICE
T exas Instruments and its subsidiaries (TI) reserve the right to make changes to their products or to discontinue
any product or service without notice, and advise customers to obtain the latest version of relevant information
to verify, before placing orders, that information being relied on is current and complete. All products are sold
subject to the terms and conditions of sale supplied at the time of order acknowledgement, including those
pertaining to warranty, patent infringement, and limitation of liability.
TI warrants performance of its semiconductor products to the specifications applicable at the time of sale in
accordance with TI’s standard warranty. Testing and other quality control techniques are utilized to the extent
TI deems necessary to support this warranty . Specific testing of all parameters of each device is not necessarily
performed, except those mandated by government requirements.
CERTAIN APPLICA TIONS USING SEMICONDUCTOR PRODUCTS MAY INVOL VE POTENTIAL RISKS OF
DEATH, PERSONAL INJURY, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE (“CRITICAL
APPLICATIONS”). TI SEMICONDUCTOR PRODUCTS ARE NOT DESIGNED, AUTHORIZED, OR
WARRANTED TO BE SUITABLE FOR USE IN LIFE-SUPPORT DEVICES OR SYSTEMS OR OTHER
CRITICAL APPLICA TIONS. INCLUSION OF TI PRODUCTS IN SUCH APPLICATIONS IS UNDERST OOD TO
BE FULLY AT THE CUSTOMER’S RISK.
In order to minimize risks associated with the customer’s applications, adequate design and operating
safeguards must be provided by the customer to minimize inherent or procedural hazards.
TI assumes no liability for applications assistance or customer product design. TI does not warrant or represent
that any license, either express or implied, is granted under any patent right, copyright, mask work right, or other
intellectual property right of TI covering or relating to any combination, machine, or process in which such
semiconductor products or services might be or are used. TI’s publication of information regarding any third
party’s products or services does not constitute TI’s approval, warranty or endorsement thereof.
Copyright 2000, Texas Instruments Incorporated
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.