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.
CERT AIN APPLICATIONS USING SEMICONDUCTOR PRODUCTS MA Y INVOLVE 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.
B.3.1 Transmitting DV Data from Bulky Data Interface, Headers Auto-Inserted B–4
B.3.2 Transmitting Fully Formatted Data Fully Formatted with 1394 Isochronous,
TSB12LV42PZDVLynx3.3 V – 5 V Tolerant I/O’sUp to 200 Mbits/s100 pin PQFP
1–3
1.5TSB12LV42 Terminal Functions
I/O
DESCRIPTION
TERMINAL
NAMENO.
ADR0 – ADR850, 51, 52,
53 54, 55,
56, 58 59
BCLK66IHost bus clock
BDI_FR94IFrame pulse input. The frame pulse input signal for PAL is 25 Hz and for
BDIBUSY(STAT3)31OBDIF is busy or status output 3. STAT3 is programmable at DIAG register
BDICLK91IBulky data I/O clock. This terminal operates at up to 40 MHz.
BDIEN93IBDIO bus enable. If BDIEN is low, accesses to BDIO-bus are ignored.
BDIF2 – BDIF0100, 99,
20, 19
BDOAVAIL(STAT2)30OBulky data output available or status output 2. STAT2 is programmable at
BDOCLK16IBulky data output clock. The bulky data output clock operates at up to
BDOEN49IBDO bus enable. If BDOEN is low, accesses to BDO-bus are ignored.
BDOF2 – BDOF047, 46, 45OBDIF format bus for BDO Port. BDOF2 is the MSB.
CNTNDR11I/OContender . The CNTNDR tells the Link when the local node is a contender
CS186IChip select. CS1 needs to be low when the device is to be selected for reads
CTL0, CTL140, 39I/OControl 0 and control 1 of the Phy-Link control bus. CTL0 and CTL1 indicate
CYCLEIN33ICycle In. CYCLEIN is an optional external 8-kHz clock used as the cycle
D0 – D338, 37, 36,35I/OData 0 – 3 of the Phy-Link data bus. Data is expected on D0 – D1 for 100
DATA0 – DATA1580, 78, 76,
74 71, 69,
64, 62 79,
77, 75, 73
70, 68, 63,
61
IMP/MC address lines. ADR0 is the MSB.
NTSC is 29.97 Hz at 50% duty cycle.
(reg 30h).
I/OBDIF format bus for BDIO port. BDIF2 is MSB.
I/OBDIF I/O data lines. BDIO7 – BDIO0 are high-speed I/O data lines for the
BDIF bus. They are primarily used for audio/data/video applications. These
lines can also be configured for input only. BDIO7 is the MSB.
OBDIF output data lines. BDO7 – BDO0 are data lines for high-speed output
on the BDIF bus for audio/data/video applications. These lines are
compliant with several standard interfaces. BDO7 is the MSB.
DIAG register (reg 30h).
40 MHz.
for IRM. This terminal can also be driven by the Link. The default status of
this terminal is input.
and writes.
the four operations that can occur in this interface.
clock. It should only be used when attached to the cycle master node. It is
enabled by the cycle source bit and should be tied high when not used.
Mbits/s and D0 – D3 for 200 Mbits/s. Data0 is the MSB.
I/OData 0 – 15 of MC/MP host processor. Some of the DATAx terminals have
second functions depending on the status of the MCSEL terminals. DATA0
is the MSB.
1–4
1.5TSB12LV42 Terminal Functions (Continued)
I/O
DESCRIPTION
TERMINAL
NAMENO.
GND10, 23, 34, 48
INT89OInterrupt. INT is used to notify the host that an interrupt has occurred.
ISOLAT(STAT1)29I/OIsolation or status output 1. ISOLA T is sampled during hardware reset to
LPS/STAT092OLink power status or status output 0. LPS is used to drive the LPS input to
LREQ44OLink request. LREQ is a DVLynx output that makes bus request and
MCCTL0/182, 83IControl lines for bus access. MCCTL0 and MCCTL1 function depends
MCSEL0/184, 85ISelect lines for MP/MC. MCSEL0 and MCSEL1 are selection lines for
NC18ONo connect
RDY88OReady line. When high, RDY indicates the end of an MP/MC access.
RESET96IReset (active low). RESET is the asynchronous power on reset to the
SCLK42ISystem clock. SCLK is a 49.152-MHz clock from the Phy. This terminal
TEST112ITest pin should be tied to VCC.
TEST213ITest should be tied to GND.
TEST314ITest pin should be tied to VCC.
TEST428ITest pin should be tied to GND.
V
CC
VCC5V15, 41, 65, 905-V ±5% power supplies for 5V tolerant I/O terminals. These terminals
60, 72, 87, 97
5, 17, 32, 43
57, 67, 81
Ground
This terminal can be active low or active high depending on the status of
the INTPOL bit in IOCR register. It is high-impedance when no interrupt
is pending.
determine if isolation is present. When this terminal is high, this indicates
NO isolation is being used. STA T1 is driven as an output after hardware
reset and used as a status output. STAT1 is programmable in the DIAG
register (reg 30h)
the Phy. This signal indicates that the LLC is powered up and active. This
output toggles at 1/32 of BCLK or SYSCLK depending on the
microprocessor used. STA T0 is used to MUX out internal signals. ST AT0
is programmable in the DIAG register (reg 30h).
accesses the Phy layer.
on MP/MC type being used.
the MP/MC-type being used. These terminals have an impact on the
function MCTRL,ADR, RDY and DA TA terminals.
device.
generates the 24.576-MHz clock (NCLK).
3.3 V (3 V – 3.6 V) supply voltage
can be tied to 3.3 V if no 5 V devices interface to the TSB12LV42.
The bulky data interface (BDIF) enables the TSB12L V42 to provide sustained data rates up to 160 Mbits/s.
The bulky data FIFO supports DV compressed data as defined by the Blue Book standard for digital video,
asynchronous, and isochronous data for both transmit and receive.
2.2Bulky Data FIFO
The bulky data FIFO is where the BDIF buffers the transmit or receive data. The bulky data FIFO is
partitioned into six logical divisions. Each of these logical FIFO sizes are programmable on four quadlet
boundaries. These six FIFOs are:
•Bulky DV transmit FIFO (BDTX)
•Bulky DV receive FIFO (BDRX)
•Bulky asynchronous transmit FIFO (BATX)
2–1
•Bulky asynchronous receive FIFO (BARX)
•Bulky isochronous transmit FIFO (BITX)
•Bulky isochronous receive FIFO (BIRX)
The following sections give functional descriptions to these logical FIFOs. See Section 4.1,
Interface
, for more detail on using this FIFO to transmit/receive data.
Bulky Data
2.2.1Bulky DV Transmit FIFO (BDTX)
The BDTX FIFO is used to transmit DV data according to the Blue Book standard. Data is typically written
to this FIFO for the BDIF or microcontroller interface in quadlets (four bytes). The TSB12LV42 can be
configured to automatically insert 1394 isochronous headers, CIP (or common isochronous packet)
headers, and H0 DIF blocks. The TSB12L V42 can also be configured to automatically insert empty packets
to smooth out the bursty data rates. This is necessary to accommodate receiving nodes whose FIFO’s are
sized to receive evenly distributed data.
2.2.2Bulky DV Receive FIFO (BDRX)
The BDRX FIFO is typically used to store DV data received from the link layer core and then forward it on
to a high speed application via the BDIF . Only isochronous port 0 of the link layer core can access the BDRX
FIFO.
2.2.3Bulky Asynchronous Transmit FIFO (BATX)
The BATX FIFO is typically used to transmit asynchronous data packets from high-speed applications.
Either the BDI or the microcontroller can load data into this FIFO.
2.2.4Bulky Asynchronous Receive FIFO (BARX)
The BARX FIFO is typically used to store received asynchronous data packets to be forwarded to a
high-speed application via the BDIF. The microcontroller can also read data from the BARX FIFO one
quadlet at a time. This FIFO is the default location for self-IDs.
2.2.5Bulky Isochronous Transmit FIFO (BITX)
The BITX FIFO is typically used to transmit isochronous data packets from high-speed applications. Data
can be loaded into the FIFO by either the BDIF or by the microcontroller one quadlet at a time.
2.2.6Bulky Isochronous Receive FIFO (BIRX)
The BIRX FIFO is typically used for receiving isochronous data and forwarding it to a high-speed application
via the BDIF . Data can also be forwarded to the microcontroller interface one quadlet at a time. Isochronous
ports 1 through 7 have access to this FIFO. Each port can be programmed to filter incoming packets
according to the isochronous channel and/or isochronous header T AG value.
2.3DV Transmit and Receive Control
The DVLynx transmit and receive circuitry controls automatic insertion of the common isochronous packet
(CIP) header information as defined by the IEC 61883 standard. This circuitry also controls the automatic
insertion of the H0 DIF block header as defined by the Blue Book standard for SD-DVCR. The transmit
circuitry also includes automatic timestamp insertion. The TSB12LV42 has an empty packet insertion
function that will automatically insert a number of empty packets within a frame. These empty packets
smooth out bursty data so that it is easier to handle for the receiving node, whose FIFOs are designed for
evenly distributed data.
2–2
2.4Microprocessor/Microcontroller Interface
The microprocessor/microcontroller interface (MP/MC) is used as the host controller port. It is designed to
work with several standard MP/MCs including Motorola 68000, Intel 8051, and ARM processors. The
interface supports both 8-bit and 16-bit wide data busses as well as both little endian and big endian
microcontrollers. This interface has two basic modes of operation: handshake Mode and blind access mode.
See Section 4.2,
Microprocessor Interface
, for more details.
2.5Control FIFO
The control FIFO is partitioned into three logical FIFOs. The size of each of these logical FIFOs is
programmable on quadlet boundaries. These three FIFOs are called:
•Asynchronous control transmit FIFO (ACTX)
•Asynchronous control receive FIFO (ACRX)
•Broadcast write receive FIFO (BWRX)
2.5.1Asynchronous Control Transmit FIFO (ACTX)
The ACTX FIFO is typically used to transmit small asynchronous control packets sent by the
microprocessor/microcontroller. The ACTX FIFO can also be used to support asynchronous traffic at very
low data rates. Asynchronous packets are written into the FIFO and transmitted using the ACRXF , ACTXC,
and ACTXCU registers. See Section 3.3.1,
concerning the ACTX.
Transmitting Asynchronous Control Packets
2.5.2Asynchronous Control Receive FIFO (ACRX)
The ACRX FIFO is typically used to receive asynchronous control packets other than self-ID packets.
Regular asynchronous control packets are usually received to the ACRX FIFO. This FIFO is accessible by
the microcontroller port through the ACRX register. See Section 3.4.1,
for more details concerning the ACRX.
Receiving Asynchronous Packets
, for more details
,
2.5.3Broadcast Write Receive FIFO (BWRX)
The BWRX FIFO is typically used to receive asynchronous broadcast write request packets. See
Section 3.4.1,
Receiving Asynchronous Packets
, for more detail concerning the BWRX.
2.6Physical Layer
The physical layer interface provides phy-level services to the transmitter and receiver. This includes
gaining access to the serial bus, sending packets, receiving packets, and sending/receiving acknowledges.
The TSB12LV42 supports Texas Instruments bus-holder circuitry on the Phy-link interface terminals. By
using the internal bus holders, the user avoids the need for the complex Annex J isolation method. The bus
holders are enabled by connecting the ISOLA T
terminal to ground.
2.7Configuration Register (CFR)
The TSB12L V42 is configured for various modes of operation using CFRs. These registers are accessed
via the host microprocessor/microcontroller. The CFR space is 512 bytes, thus the need for a 9-bit address
bus. All CFRs are 32-bits wide. Since the microcontroller interface is either 8 or 16-bits wide, it must perform
a byte stacking/unstacking operation internally on the incoming (write) or outgoing (read) microcontroller
data. Chapter 5 gives a map of all the registers and detailed descriptions of all the register bits.
2–3
2–4
3 Functional Description and Data Formats
3.1Overview
The TSB12L V42 is a 1394 interface for high-speed audio, video, and data applications at up to 200 Mb/s.
For these high-speed applications a bulky data interface (BDIF) has been implemented that supports long
term data rates up to 60 Mb/s. Burst data rates, however, can go up to 160 Mb/s.
The TSB12L V42 contains two FIFOs that are a 256-byte control FIFO (Control FIFO) and an 8K-byte BDIF
FIFO. These two FIFOs are further subdivided into smaller logical FIFOs.
Bulky data is usually buffered in the BDIF FIFO. The BDIF FIFO supports DV, asynchronous, and
isochronous formatted traffic for receive and transmit.
Asynchronous packets (for 1394 bus control/status) are usually written to or read from the Control FIFO.
For lower data rates the Control FIFO can also be used to buffer asynchronous application data. Based on
destination address, received asynchronous request packets may be steered into either the Control FIFO
or the BDIF FIFO.
A separate self-ID-FIFO allows faster BUS setup and reduces software complexity . The 256-Byte Control
FIFO (Control FIFO) is partitioned into three logical FIFOs. The size of these three logical FIFOs is
programmable on quadlet boundaries. These FIFOs are called:
1.Asynchronous control transmit (ACTX) FIFO
2.Asynchronous control receive (ACRX) FIFO
3.Broadcast write receive (BWRX) FIFO.
The 8K-Byte BDIF FIFO is partitioned into six logical FIFOs. The size of these FIFOs is programmable on
four quadlet (hexlet) boundaries. These FIFOs are called:
1.BDIF DV transmit (BDTX) FIFO
2.BDIF DV receive (BDRX) FIFO
3.BDIF asynchronous transmit (BATX) FIFO
4.BDIF asynchronous receive (BARX) FIFO
5.BDIF isochronous transmit (BITX) FIFO
6.BDIF isochronous receive (BIRX ) FIFO
The Control and BDIF FIFOs are structured are as follows:
8K-Byte BDIF FIFO Structure
256-Byte Control
FIFO Structure
00h
FFh
ACTX
ACRX
BWRX
0000h
1FFFh
DV TX Buffer
DV RX Buffer
Async TX Buffer
Async RX Buffer
Isoch TX Buffer
Isoch RX Buffer
The TSB12L V42 (with built-in programmable Endianness) interfaces directly to most microprocessors and
microcontrollers.
3–1
3.2DV on 1394 Overview
3.2.1DV interface
NCLK
820020 Clocks
250 Source Packets NTSC
BDI_Fr
NTSCPAL
3280 Clks for 249 SPs
3300 Clks for Last SP
983040 Clocks
300 Source Packets PAL
3277 Clks for 299 SPs
3217 Clks for Last SP
Figure 3–1. Example of a Source Packet Transmit Event
A source packet (SP) event occurs 250 times in 1 NTSC frame or 300 times in 1 PAL frame. NCLK is an
internal 24.576-MHz clock derived from the 49.152-MHz SCLK. The first BDI_FR pulse starts the source
packet counter used to generate the empty packet insertion algorithm. The TSB12L V42 provides automatic
empty packet insertion on transmit to evenly distribute the 250/300 source packets within a frame. Turning
off the appropriate bit in the MDCR Register can turn off this feature. In one NTSC frame, there are 820020.0
NCLKs and therefore 3280.08 NCLKs per source packet. That is equivalent to 249 source packets of 3280
NCLKs and one source packet of 3300 NCLKs. For NTSC a SP event is signaled every 3280 clocks for the
first 249 SP event and the last SP event is signaled after 3300 clocks following the 249th event. This yields
a 33.367-ms frame rate (40.69 ((3280 × 249) + 3300)). For PAL the time for 1 frame is 40.00 ms
(40.69 ((3277 × 299) + 3217)).
Cycle synchronous (CS) events occurs every 125 µs ( this is the isochronous cycle base rate). During each
isochronous cycle a complete SP is transmitted or an empty packet (EP) is transmitted. If two contiguous
CS events occur without an SP event occurring, then an empty packet is forced in the current isochronous
cycle regardless if a complete source packet is available in the FIFO. If a SP event occurs between two CS
events but a complete source packet is not available in the FIFO, then an empty packet is transmitted in the
current isochronous cycle.
NCLK
BDI_Fr
CLK_cntr
SPevent
Valid
001 00232800010023300001 002
Figure 3–2. Source Packet Transmit Event Timing
NOTE: BDI_Fr has already been synchronized with NCLK.
3–2
3.2.2DV Bandwidth on IEEE1394
Table 3–1. DV Bandwidth on IEEE 1394
MAX SP-BW
(Mbits/s)
30.723220/500
†
SP-BW: Source package bandwidth (based on 480 byte DV).
‡
1394-BW: Overall bandwidth of 1394 bus on physical medium (includes 4-byte 1394
packet transmit header, 4-byte packet header CRC, 8-byte CIP header, actual
payload, and 4-byte payload CRC. This bandwidth should be allocated by the DV
transfer initiator.
NOTES: A. SD-DVCR 525-50 System is identical to 525-60 system except the number of source packets is 300
B. H0 = Header DIF block
SCi = Subcode DIF block (i = 0, 1)
VAi = VAUX DIF block i (i = 0, 1, 2)
Vi = Video DIF block (i = 0 – 134)
Ai = Audio DIF block (i = 0 – 8)
Figure 3–4. DIF Block H0
The H0 DIF block is inserted into the first 80 bytes every 25th packet. The TSB12LV42 gives the system
designer the option to automatically insert the 80 byte DIF block before transmit. The value of the H0 header
DIF block is programmable via internal registers 1A4h and 1A8h.
Figure 3–5 shows the H0 header DIF block. Bytes 0–7 can be inserted by the link core or can be provided
by the application with the data.
The TSB12LV42 has an option to automatically insert CIP headers and timestamps during transmission.
The CIP headers, or common isochronous packet headers, follow the format of the IEC 61883-2 standard
for transmitting SD-DVCR data over 1394. The values of the CIP headers are programmable in registers
1CCh and 1D0h. The TSB12L V42 also has the option to automatically calculate and insert timestamp values
into the CIP1 header. The timestamp is inserted either into the first transmitted packet in the next
isochronous cycle (register F0h, bit 1 1 INTSSP=0) or into the first full data packet of the next frame (register
F0h, bit 1 1 INTSSP=1).
Data_Length
T ag Channel Tcode Sy
Header_CRC
Data Field
Data_CRC
Length field is either 488 bytes (DV-Source Packet) or 8 bytes (empty packet).
00000525–60 System
00001ReservedReserved
000101125–60 System1250–50 System
0001 1
11111
†
525-60 system: The 525-line system with a frame frequency of 29.97 Hz
625-50 system: The 625-line system with a frame frequency of 25.00 Hz
SD-DVCR:Standard-definition digital-video cassette recorder
FMT
50/60
STYPE
rsvSYT
Figure 3–8. CIP Header Format
01
†
.
.
.
ReservedReserved
625–50 System
†
3.3Transmit Operation
The functional description for transmission is shown in the following sections. The transmit format describes
the expected organization of data presented to the TSB12L V42 at the host-bus interface.
3.3.1Transmitting Asynchronous Control Packets
Asynchronous control packets are typically transmitted by the microprocessor (host) using the
Asynchronous Control Transmit FIFO (ACTX). This FIFO is part of the 256 bytes Control FIFO. It is
configurable in register 44h (Asynchronous Control Data Transmit FIFO Status). The ACTX FIFO can also
be used for asynchronous data traffic at low data rates.
For transmit, the 1394 asynchronous headers and the data are loaded into the ACTX by the microprocessor.
The microprocessor has access to the ACTX FIFO through registers 80h – 8Ch. The asynchronous header
must fit the format described in Section 3.6,
TSB12LV42)
3–6
.
Asynchronous Transmit Data Formats (Host Bus to
Loading...
+ 145 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.