TSB43AB23-EP [TI]
增强型产品 IEEE 1394A-2000 OHCI 物理层/链路层控制器;
| 型号： | TSB43AB23-EP |
| 厂家： | 
TEXAS INSTRUMENTS |
| 描述： | 增强型产品 IEEE 1394A-2000 OHCI 物理层/链路层控制器 通信 控制器 微控制器 微控制器和处理器 串行IO控制器 通信控制器 |
| 文件： | 总109页 (文件大小：627K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
ꢀ
ꢁ
ꢂ
ꢃ
ꢄ
ꢅ
ꢂ
ꢆ
ꢄ
ꢇꢈ ꢈ ꢈ ꢉ ꢄ ꢊꢃ ꢋꢌꢆ ꢍꢍꢍ ꢎ ꢏ ꢐꢇ ꢑꢏ ꢒ ꢓ ꢔꢕꢖꢗ ꢔꢋꢘꢙꢚ
ꢐ ꢛꢖ ꢜ ꢚꢛ ꢝ ꢝꢙ ꢚ
Data Manual
February 2003
1394 Host Controller Solutions
SLLS450A
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications,
enhancements, improvements, and other changes to its products and services at any time and to discontinue
any product or service without notice. Customers should obtain the latest relevant information before placing
orders and should verify that such information is current and complete. All products are sold subject to TI’s terms
and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its hardware products to the specifications applicable at the time of sale in
accordance with TI’s standard warranty. Testing and other quality control techniques are used to the extent TI
deems necessary to support this warranty. Except where mandated by government requirements, testing of all
parameters of each product is not necessarily performed.
TI assumes no liability for applications assistance or customer product design. Customers are responsible for
their products and applications using TI components. To minimize the risks associated with customer products
and applications, customers should provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right,
copyright, maskworkright, orotherTIintellectualpropertyrightrelatingtoanycombination, machine, orprocess
in which TI products or services are used. Information published by TI regarding third–party products or services
does not constitute a license from TI to use such products or services or a warranty or endorsement thereof.
Use of such information may require a license from a third party under the patents or other intellectual property
of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of information in TI data books or data sheets is permissible only if reproduction is without
alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction
of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for
such altered documentation.
Resale of TI products or services with statements different from or beyond the parameters stated by TI for that
product or service voids all express and any implied warranties for the associated TI product or service and
is an unfair and deceptive business practice. TI is not responsible or liable for any such statements.
Mailing Address:
Texas Instruments
Post Office Box 655303
Dallas, Texas 75265
Copyright 2003, Texas Instruments Incorporated
Contents
Section
Title
Page
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
1.1
1.2
1.3
1.4
1.5
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
2
3
Terminal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
TSB43AB23 1394 OHCI Controller Programming Model . . . . . . . . . . . . . . 3–1
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
PCI Configuration Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Vendor ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Device ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Command Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Class Code and Revision ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Latency Timer and Class Cache Line Size Register . . . . . . . . . . . . . . 3–6
Header Type and BIST Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
OHCI Base Address Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
3.10 TI Extension Base Address Register . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
3.11 Subsystem Identification Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
3.12 Power Management Capabilities Pointer Register . . . . . . . . . . . . . . . 3–9
3.13 Interrupt Line and Pin Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
3.14 MIN_GNT and MAX_LAT Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
3.15 OHCI Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11
3.16 Capability ID and Next Item Pointer Registers . . . . . . . . . . . . . . . . . . . 3–11
3.17 Power Management Capabilities Register . . . . . . . . . . . . . . . . . . . . . . 3–12
3.18 Power Management Control and Status Register . . . . . . . . . . . . . . . . 3–13
3.19 Power Management Extension Registers . . . . . . . . . . . . . . . . . . . . . . . 3–13
3.20 PCI PHY Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
3.21 Miscellaneous Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
3.22 Link Enhancement Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
3.23 Subsystem Access Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17
3.24 GPIO Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
OHCI Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
4
4.1
4.2
4.3
4.4
OHCI Version Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
GUID ROM Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Asynchronous Transmit Retries Register . . . . . . . . . . . . . . . . . . . . . . . 4–6
CSR Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
iii
4.5
4.6
4.7
4.8
4.9
CSR Compare Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
CSR Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Configuration ROM Header Register . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bus Identification Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bus Options Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
4.10 GUID High Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
4.11 GUID Low Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
4.12 Configuration ROM Mapping Register . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
4.13 Posted Write Address Low Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
4.14 Posted Write Address High Register . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
4.15 Vendor ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
4.16 Host Controller Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
4.17 Self-ID Buffer Pointer Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
4.18 Self-ID Count Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
4.19 Isochronous Receive Channel Mask High Register . . . . . . . . . . . . . . 4–16
4.20 Isochronous Receive Channel Mask Low Register . . . . . . . . . . . . . . . 4–17
4.21 Interrupt Event Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
4.22 Interrupt Mask Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
4.23 Isochronous Transmit Interrupt Event Register . . . . . . . . . . . . . . . . . . 4–22
4.24 Isochronous Transmit Interrupt Mask Register . . . . . . . . . . . . . . . . . . . 4–23
4.25 Isochronous Receive Interrupt Event Register . . . . . . . . . . . . . . . . . . . 4–23
4.26 Isochronous Receive Interrupt Mask Register . . . . . . . . . . . . . . . . . . . 4–24
4.27 Initial Bandwidth Available Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
4.28 Initial Channels Available High Register . . . . . . . . . . . . . . . . . . . . . . . . 4–25
4.29 Initial Channels Available Low Register . . . . . . . . . . . . . . . . . . . . . . . . . 4–25
4.30 Fairness Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
4.31 Link Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
4.32 Node Identification Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
4.33 PHY Layer Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
4.34 Isochronous Cycle Timer Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
4.35 Asynchronous Request Filter High Register . . . . . . . . . . . . . . . . . . . . . 4–31
4.36 Asynchronous Request Filter Low Register . . . . . . . . . . . . . . . . . . . . . 4–33
4.37 Physical Request Filter High Register . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
4.38 Physical Request Filter Low Register . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
4.39 Physical Upper Bound Register (Optional Register) . . . . . . . . . . . . . . 4–36
4.40 Asynchronous Context Control Register . . . . . . . . . . . . . . . . . . . . . . . . 4–37
4.41 Asynchronous Context Command Pointer Register . . . . . . . . . . . . . . 4–38
4.42 Isochronous Transmit Context Control Register . . . . . . . . . . . . . . . . . . 4–39
4.43 Isochronous Transmit Context Command Pointer Register . . . . . . . . 4–40
4.44 Isochronous Receive Context Control Register . . . . . . . . . . . . . . . . . . 4–40
4.45 Isochronous Receive Context Command Pointer Register . . . . . . . . 4–42
4.46 Isochronous Receive Context Match Register . . . . . . . . . . . . . . . . . . . 4–43
TI Extension Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
5
5.1
DV and MPEG2 Timestamp Enhancements . . . . . . . . . . . . . . . . . . . . . 5–1
iv
5.2
5.3
5.4
5.5
Isochronous Receive Digital Video Enhancements . . . . . . . . . . . . . . . 5–2
Isochronous Receive Digital Video Enhancements Register . . . . . . . 5–2
Link Enhancement Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Timestamp Offset Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
6
7
Serial EEPROM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
PHY Register Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
7.1
7.2
7.3
7.4
7.5
Base Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Port Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4
Vendor Identification Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Vendor-Dependent Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
Power-Class Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
8
9
Application Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
8.1
8.2
8.3
8.4
PHY Port Cable Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Crystal Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Bus Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
EMI Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
9.1
9.2
9.3
Absolute Maximum Ratings Over Operating Temperature Ranges . 9–1
Recommended Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Electrical Characteristics Over Recommended
Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
9.4
Electrical Characteristics Over Recommended Ranges of
Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
9.4.1
9.4.2
9.4.3
Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
9.5
9.6
9.7
9.8
Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Switching Characteristics for PHY Port Interface . . . . . . . . . . . . . . . . . 9–5
Operating, Timing, and Switching Characteristics of XI . . . . . . . . . . . 9–5
Switching Characteristics for PCI Interface . . . . . . . . . . . . . . . . . . . . . . 9–5
10 Mechanical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
v
List of Illustrations
Figure
2–1
2–2
3–1
8–1
8–2
8–3
8–4
8–5
9–1
Title
Page
PDT Package Terminal Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
PGE Package Terminal Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
TSB43AB23 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
TP Cable Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Typical Compliant DC Isolated Outer Shield Termination . . . . . . . . . . . . . 8–2
Non-DC Isolated Outer Shield Termination . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Load Capacitance for the TSB43AB23 PHY . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Recommended Crystal and Capacitor Layout . . . . . . . . . . . . . . . . . . . . . . . 8–3
Test Load Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
vi
List of Tables
Table
Title
Page
2–1
2–2
2–3
2–4
2–5
2–6
2–7
2–8
2–9
3–1
3–2
3–3
3–4
3–5
3–6
3–7
3–8
3–9
PDT Package Signals Sorted by Terminal Number . . . . . . . . . . . . . . . . . . 2–4
PGE Package Signals Sorted by Terminal Number . . . . . . . . . . . . . . . . . . 2–5
Signal Names Sorted Alphanumerically to Terminal Number . . . . . . . . . . 2–6
PCI System Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
PCI Address and Data Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
PCI Interface Control Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Miscellaneous Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Physical Layer Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Power Supply Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Bit Field Access Tag Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
PCI Configuration Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Command Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Status Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Class Code and Revision ID Register Description . . . . . . . . . . . . . . . . . . . 3–6
Latency Timer and Class Cache Line Size Register Description . . . . . . . 3–6
Header Type and BIST Register Description . . . . . . . . . . . . . . . . . . . . . . . . 3–7
OHCI Base Address Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
TI Base Address Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
3–10 Subsystem Identification Register Description . . . . . . . . . . . . . . . . . . . . . . 3–9
3–11 Interrupt Line and Pin Registers Description . . . . . . . . . . . . . . . . . . . . . . . . 3–10
3–12 MIN_GNT and MAX_LAT Register Description . . . . . . . . . . . . . . . . . . . . . 3–10
3–13 OHCI Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11
3–14 Capability ID and Next Item Pointer Registers Description . . . . . . . . . . . . 3–11
3–15 Power Management Capabilities Register Description . . . . . . . . . . . . . . . 3–12
3–16 Power Management Control and Status Register Description . . . . . . . . . 3–13
3–17 Power Management Extension Registers Description . . . . . . . . . . . . . . . . 3–13
3–18 PCI PHY Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
3–19 Miscellaneous Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
3–20 Link Enhancement Control Register Description . . . . . . . . . . . . . . . . . . . . 3–16
3–21 Subsystem Access Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17
3–22 General-Purpose Input/Output Control Register Description . . . . . . . . . . 3–18
4–1
4–2
4–3
4–4
4–5
4–6
OHCI Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
OHCI Version Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
GUID ROM Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Asynchronous Transmit Retries Register Description . . . . . . . . . . . . . . . . 4–6
CSR Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Configuration ROM Header Register Description . . . . . . . . . . . . . . . . . . . . 4–8
vii
4–7
4–8
4–9
Bus Options Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Configuration ROM Mapping Register Description . . . . . . . . . . . . . . . . . . . 4–11
Posted Write Address Low Register Description . . . . . . . . . . . . . . . . . . . . 4–11
4–10 Posted Write Address High Register Description . . . . . . . . . . . . . . . . . . . . 4–12
4–11 Host Controller Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . 4–13
4–12 Self-ID Count Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
4–13 Isochronous Receive Channel Mask High Register Description . . . . . . . 4–16
4–14 Isochronous Receive Channel Mask Low Register Description . . . . . . . . 4–17
4–15 Interrupt Event Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
4–16 Interrupt Mask Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
4–17 Isochronous Transmit Interrupt Event Register Description . . . . . . . . . . . 4–22
4–18 Isochronous Receive Interrupt Event Register Description . . . . . . . . . . . 4–23
4–19 Initial Bandwidth Available Register Description . . . . . . . . . . . . . . . . . . . . . 4–24
4–20 Initial Channels Available High Register Description . . . . . . . . . . . . . . . . . 4–25
4–21 Initial Channels Available Low Register Description . . . . . . . . . . . . . . . . . 4–25
4–22 Fairness Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
4–23 Link Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
4–24 Node Identification Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
4–25 PHY Control Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
4–26 Isochronous Cycle Timer Register Description . . . . . . . . . . . . . . . . . . . . . . 4–30
4–27 Asynchronous Request Filter High Register Description . . . . . . . . . . . . . 4–31
4–28 Asynchronous Request Filter Low Register Description . . . . . . . . . . . . . . 4–33
4–29 Physical Request Filter High Register Description . . . . . . . . . . . . . . . . . . . 4–34
4–30 Physical Request Filter Low Register Description . . . . . . . . . . . . . . . . . . . 4–36
4–31 Asynchronous Context Control Register Description . . . . . . . . . . . . . . . . . 4–37
4–32 Asynchronous Context Command Pointer Register Description . . . . . . . 4–38
4–33 Isochronous Transmit Context Control Register Description . . . . . . . . . . 4–39
4–34 Isochronous Receive Context Control Register Description . . . . . . . . . . . 4–40
4–35 Isochronous Receive Context Match Register Description . . . . . . . . . . . . 4–43
5–1
5–2
5–3
5–4
6–1
6–2
7–1
7–2
7–3
7–4
7–5
7–6
7–7
7–8
7–9
TI Extension Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Isochronous Receive Digital Video Enhancements Register Description 5–2
Link Enhancement Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Timestamp Offset Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Registers and Bits Loadable Through Serial EEPROM . . . . . . . . . . . . . . . 6–1
Serial EEPROM Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Base Register Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Base Register Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Page 0 (Port Status) Register Configuration . . . . . . . . . . . . . . . . . . . . . . . . 7–4
Page 0 (Port Status) Register Field Descriptions . . . . . . . . . . . . . . . . . . . . 7–4
Page 1 (Vendor ID) Register Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Page 1 (Vendor ID) Register Field Descriptions . . . . . . . . . . . . . . . . . . . . . 7–5
Page 7 (Vendor-Dependent) Register Configuration . . . . . . . . . . . . . . . . . 7–6
Page 7 (Vendor-Dependent) Register Field Descriptions . . . . . . . . . . . . . 7–6
Power Class Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
viii
1 Introduction
This chapter provides an overview of the Texas Instruments TSB43AB23 device and its features.
1.1 Description
The Texas Instruments TSB43AB23 device is an integrated 1394a-2000 OHCI PHY/link-layer controller (LLC) device
that is fully compliant with the PCI Local Bus Specification, the PCI Bus Power Management Interface Specification
(Revision 1.1), IEEE Std 1394-1995, IEEE Std 1394a-2000, and the 1394 Open Host Controller Interface
Specification (Release 1.1). It is capable of transferring data between the 33-MHz PCI bus and the 1394 bus at
100M bits/s, 200M bits/s, and 400M bits/s. The TSB43AB23 device provides three 1394 ports that have separate
cable bias (TPBIAS). The TSB43AB23 device also supports the IEEE Std 1394a-2000 power-down features for
battery-operated applications and arbitration enhancements.
As required by the 1394 Open Host Controller Interface Specification (OHCI) and IEEE Std 1394a-2000, internal
control registers are memory-mapped and nonprefetchable. The PCI configuration header is accessed through
configuration cycles specified by PCI, and it provides plug-and-play (PnP) compatibility. Furthermore, the
TSB43AB23 device is compliant with the PCI Bus Power Management Interface Specification as specified by the
PC 2001 Design Guide requirements. The TSB43AB23 device supports the D0, D1, D2, and D3 power states.
The TSB43AB23 design provides PCI bus master bursting, and it is capable of transferring a cacheline of data at
132M bytes/s after connection to the memory controller. Because PCI latency can be large, deep FIFOs are provided
to buffer the 1394 data.
The TSB43AB23 device provides physical write posting buffers and a highly-tuned physical data path for SBP-2
performance. The TSB43AB23 device also provides multiple isochronous contexts, multiple cacheline burst
transfers, and advanced internal arbitration.
An advanced CMOS process achieves low power consumption and allows the TSB43AB23 device to operate at PCI
clock rates up to 33 MHz.
The TSB43AB23 PHY-layer provides the digital and analog transceiver functions needed to implement a three-port
node in a cable-based 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 TSB43AB23 PHY-layer requires only an external 24.576-MHz crystal as a reference for the cable ports. 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 that control transmission of the outbound encoded strobe and data information. A 49.152-MHz clock
signal is supplied to the integrated LLC for synchronization and is used for resynchronization of the received data.
Data bits to be transmitted through the cable ports are received from the integrated LLC and are latched internally
in synchronization with the 49.152-MHz system clock. These bits are combined serially, encoded, and transmitted
at 98.304M, 196.608M, or 393.216M bits/s (referred to as S100, S200, or S400 speeds, respectively) as the outbound
data-strobe information stream. During transmission, the encoded data information is transmitted differentially on the
twisted-pair B (TPB) cable pair(s), and the encoded strobe information is transmitted differentially on the twisted-pair
A (TPA) cable pair(s).
During packet reception, the TPA 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 resynchronized to the local 49.152-MHz system clock
and sent to the integrated LLC. The received data is also transmitted (repeated) on the other active (connected) cable
ports.
1–1
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 TSB43AB23 device provides a 1.86-V nominal bias voltage at the TPBIAS terminal for port termination. The PHY
layer 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.0 µF.
The line drivers in the TSB43AB23 device operate in a high-impedance current mode and are designed to work with
external 112-Ω line-termination resistor networks in order to match the 110-Ω 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 TPA terminals is connected to its corresponding
TPBIAS voltage terminal. The midpoint of the pair of resistors that is directly connected to the TPB 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 and other internal operating currents. This current-setting resistor has a value of 6.34 kΩ ±1%.
When the power supply of the TSB43AB23 device is off and the twisted-pair cables are connected, the TSB43AB23
transmitter and receiver circuitry present a high impedance to the cable and do not load the TPBIAS voltage at the
other end of the cable.
When the device is in a low-power state (for example, D2 or D3) the TSB43AB23 device automatically enters a
low-power mode if all ports are inactive (disconnected, disabled, or suspended). In this low-power mode, the
TSB43AB23 device disables its internal clock generators and also disables various voltage and current reference
circuits, depending on the state of the ports (some reference circuitry must remain active in order to detect new cable
connections, disconnections, or incoming TPBIAS, for example). The lowest power consumption (the ultralow-power
sleep mode) is attained when all ports are either disconnected or disabled with the port interrupt enable bit cleared.
The TSB43AB23 device exits the low-power mode when bit 19 (LPS) in the host controller control register at OHCI
offset 50h/54h (see Section 4.16, Host Controller Control Register) is set to 1 or when a port event occurs which
requires that the TSB43AB23 device to become active in order to respond to the event or to notify the LLC of the event
(for example, incoming bias is detected on a suspended port, a disconnection is detected on a suspended port, or
a new connection is detected on a nondisabled port). When the TSB43AB23 device is in the low-power mode, the
internal 49.153-MHz clock becomes active (and the integrated PHY layer becomes operative) within 2 ms after bit 19
(LPS) in the host controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control
Register) is set to 1.
The TSB43AB23 device supports hardware enhancements to better support digital video (DV) and MPEG data
stream reception and transmission. These enhancements are enabled through the isochronous receive digital video
enhancements register at OHCI offset A88h (see Chapter 5, TI Extension Registers). The enhancements include
automatic timestamp insertion for transmitted DV and MPEG-formatted streams and common isochronous packet
(CIP) header stripping for received DV streams.
The CIP format is defined by the IEC 61883-1:1998 specification. The enhancements to the isochronous data
contexts are implemented as hardware support for the synchronization timestamp for both DV and MPEG CIP
formats. The TSB43AB23 device supports modification of the synchronization timestamp field to ensure that the
value inserted via software is not stale—that is, the value is less than the current cycle timer when the packet is
transmitted.
1–2
1.2 Features
The TSB43AB23 device supports the following features:
•
•
Fully compliant with 1394 Open Host Controller Interface Specification (Release 1.1)
†
Fully compliant with provisions of IEEE Std 1394-1995 for a high-performance serial bus and IEEE Std
1394a-2000
•
•
•
Fully interoperable with FireWire and i.LINK implementations of IEEE Std 1394
Compliant with Intel Mobile Power Guideline 2000
Full IEEE Std 1394a-2000 support includes: connection debounce, arbitrated short reset, multispeed
concatenation, arbitration acceleration, fly-by concatenation, and port disable/suspend/resume
•
Power-down features to conserve energy in battery-powered applications include: automatic device power
down during suspend, PCI power management for link-layer, and inactive ports powered down
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Ultralow-power sleep mode
Three IEEE Std 1394a-2000 fully compliant cable ports at 100M bits/s, 200M bits/s, and 400M bits/s
Cable ports monitor line conditions for active connection to remote node
Cable power presence monitoring
Separate cable bias (TPBIAS) for each port
1.8-V core logic with universal PCI interfaces compatible with 3.3-V and 5-V PCI signaling environments
Physical write posting of up to three outstanding transactions
PCI burst transfers and deep FIFOs to tolerate large host latency
PCI_CLKRUN protocol
External cycle timer control for customized synchronization
Extended resume signaling for compatibility with legacy DV components
PHY-link logic performs system initialization and arbitration functions
PHY-link encode and decode functions included for data-strobe bit level encoding
PHY-link incoming data resynchronized to local clock
Low-cost 24.576-MHz crystal provides transmit and receive data at 100M bits/s, 200M bits/s, and
400M bits/s
•
•
•
•
Node power class information signaling for system power management
Serial ROM interface supports 2-wire serial EEPROM devices
Two general-purpose I/Os
Register bits give software control of contender bit, power class bits, link active control bit, and IEEE Std
1394a-2000 features
•
•
•
•
Fabricated in advanced low-power CMOS process
Isochronous receive dual-buffer mode
Out-of-order pipelining for asynchronous transmit requests
Register access fail interrupt when the PHY SCLK is not active
†
Implements technology covered by one or more patents of Apple Computer, Incorporated and SGS Thompson, Limited.
1–3
•
•
•
PCI power-management D0, D1, D2, and D3 power states
Initial bandwidth available and initial channels available registers
PME support per 1394 Open Host Controller Interface Specification
1.3 Related Documents
•
•
•
•
•
•
•
•
•
•
1394 Open Host Controller Interface Specification (Release 1.1)
IEEE Standard for a High Performance Serial Bus (IEEE Std 1394-1995)
IEEE Standard for a High Performance Serial Bus—Amendment 1 (IEEE Std 1394a-2000)
PC Card Standard—Electrical Specification
PC 2001 Design Guide
PCI Bus Power Management Interface Specification (Revision 1.1)
PCI Local Bus Specification (Revision 2.2)
Mobile Power Guideline 2000
Serial Bus Protocol 2 (SBP-2)
IEC 61883-1:1998 Consumer Audio/Video Equipment Digital Interface Part 1: General
1.4 Trademarks
iOHCI-Lynx and TI are trademarks of Texas Instruments.
Other trademarks are the property of their respective owners.
1.5 Ordering Information
ORDERING NUMBER
TSB43AB23PDT
NAME
VOLTAGE
3.3 V
PACKAGE
PDT
iOHCI-Lynx
iOHCI-Lynx
TSB43AB23PGE
3.3 V
PGE
1–4
2 Terminal Descriptions
This section provides the terminal descriptions for the TSB43AB23 device. Figure 2–2 shows the signal assigned to
each terminal in the package. Table 2–1 and Table 2–3 provide a cross-reference between each terminal number and
the signal name on that terminal. Table 2–1 is arranged in terminal number order, and Table 2–3 lists signals in
alphabetical order.
2–1
PDT PACKAGE
(TOP VIEW)
TPBIAS2
TPA2+
TPA2–
1
2
3
4
5
6
7
8
DGND
PCI_C/BE3
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
V
DDP
AV
TPB2+
PCI_IDSEL
PCI_AD23
PCI_AD22
DD
TPB2–
AV
AGND
DV
DD
DD
PCI_AD21
PCI_AD20
PCI_AD19
PCI_AD18
DGND
9
TPBIAS1
TPA1+
TPA1–
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
AV
DD
AGND
TPB1+
TPB1–
PCI_AD17
PCI_AD16
PCI_C/BE2
TSB43AB23
AV
V
DDP
DD
AGND
TPBIAS0
TPA0+
TPA0–
AGND
TPB0+
TPB0–
AGND
PCI_FRAME
PCI_IRDY
DV
DD
PCI_TRDY
PCI_DEVSEL
PCI_STOP
DGND
PCI_PERR
PCI_SERR
PCI_PAR
AV
AGND
DD
AV
CPS
DV
DD
DD
PCI_C/BE1
PCI_AD15
PHY_TEST_MA
CNA
DGND
30
31
32
V
DDP
PCI_AD14
DGND
DV
DD
Figure 2–1. PDT Package Terminal Assignments
2–2
PGE PACKAGE
(TOP VIEW)
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
56
55
54
NC
NC
NC
109
NC
110
111
112
113
114
AGND
PC0
AV
PC1
DD
R1
PC2
R0
REG18
SDA
FILTER0
FILTER1
115
116
SCL
PLLV
117
118
GPIO2/TEST0
GPIO3/TEST1
DD
PLLGND
XI
119
120
121
122
DV
DD
XO
CYCLEIN
CYCLEOUT
PCI_RST
PCI_AD0
DGND
REG_EN
PCI_CLKRUN
PCI_INTA
G_RST
123
124
DV
125
126
PCI_AD1
PCI_AD2
PCI_AD3
PCI_AD4
DD
PCI_PCLK
TSB43AB23
DGND
127
128
129
130
PCI_GNT
PCI_REQ
53
52
V
DDP
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
V
PCI_AD5
PCI_AD6
DGND
DDP
131
132
PCI_PME
PCI_AD31
DGND
133
134
PCI_AD7
PCI_C/BE0
PCI_AD30
PCI_AD29
PCI_AD28
135
136
137
DV
DD
PCI_AD8
PCI_AD9
PCI_AD10
DGND
DV
DD
PCI_AD27
PCI_AD26
REG18
PCI_AD25
PCI_AD24
NC
138
139
140
PCI_AD11
PCI_AD12
PCI_AD13
NC
141
142
143
144
NC
NC
Figure 2–2. PGE Package Terminal Assignments
2–3
Table 2–1. PDT Package Signals Sorted by Terminal Number
NO.
1
TERMINAL NAME
DGND
NO.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
TERMINAL NAME
PCI_AD13
PCI_AD12
PCI_AD11
DGND
NO.
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
TERMINAL NAME
DV
NO.
97
TERMINAL NAME
AGND
DD
2
PCI_C/BE3
DGND
CNA
98
AV
DD
3
V
DDP
99
R1
4
PCI_IDSEL
PCI_AD23
PCI_AD22
PHY_TEST_MA
CPS
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
R0
5
PCI_AD10
PCI_AD9
FILTER0
FILTER1
6
AV
DD
7
DV
PCI_AD8
AGND
AV
PLLV
DD
DD
8
PCI_AD21
PCI_AD20
PCI_AD19
PCI_AD18
DGND
DV
PLL
GND
DD
DD
9
PCI_C/BE0
PCI_AD7
DGND
AGND
TPB0–
TPB0+
AGND
XI
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
XO
REG_EN
PCI_CLKRUN
PCI_INTA
G_RST
PCI_AD6
PCI_AD5
PCI_AD17
PCI_AD16
PCI_C/BE2
TPA0–
TPA0+
TPBIAS0
AGND
V
DDP
PCI_AD4
PCI_AD3
PCI_AD2
PCI_AD1
DGND
DV
DD
V
DDP
PCI_PCLK
DGND
PCI_FRAME
PCI_IRDY
AV
DD
TPB1–
TPB1+
AGND
PCI_GNT
PCI_REQ
DV
DD
PCI_TRDY
PCI_DEVSEL
PCI_STOP
DGND
PCI_AD0
PCI_RST
CYCLEOUT
CYCLEIN
V
DDP
AV
DD
PCI_PME
PCI_AD31
DGND
TPA1–
TPA1+
PCI_PERR
PCI_SERR
PCI_PAR
DV
TPBIAS1
AGND
PCI_AD30
PCI_AD29
PCI_AD28
DD
GPIO3/TEST1
GPIO2/TEST0
SCL
AV
DD
DV
TPB2–
DV
DD
DD
PCI_C/BE1
PCI_AD15
SDA
TPB2+
PCI_AD27
PCI_AD26
REG18
REG18
PC2
AV
DD
V
DDP
TPA2–
TPA2+
PCI_AD14
DGND
PC1
PCI_AD25
PCI_AD24
PC0
TPBIAS2
2–4
Table 2–2. PGE Package Signals Sorted by Terminal Number
NO.
1
TERMINAL NAME
NO.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
TERMINAL NAME
NC
NO.
73
TERMINAL NAME
NO.
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
TERMINAL NAME
NC
NC
NC
NC
NC
NC
2
NC
74
3
DGND
PCI_C/BE3
PCI_AD13
PCI_AD12
PCI_AD11
DGND
75
DV
AGND
DD
4
76
DGND
CNA
AV
DD
5
V
DDP
77
R1
6
PCI_IDSEL
PCI_AD23
PCI_AD22
78
PHY_TEST_MA
CPS
R0
7
PCI_AD10
PCI_AD9
PCI_AD8
79
FILTER0
FILTER1
8
80
AV
DD
9
DV
81
AGND
AV
PLLV
DD
DD
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
PCI_AD21
PCI_AD20
PCI_AD19
PCI_AD18
DGND
DV
82
PLLGND
XI
DD
DD
PCI_C/BE0
PCI_AD7
DGND
83
AGND
TPB0–
TPB0+
AGND
84
XO
85
REG_EN
PCI_CLKRUN
PCI_INTA
G_RST
PCI_AD6
PCI_AD5
86
PCI_AD17
PCI_AD16
PCI_C/BE2
87
TPA0–
TPA0+
TPBIAS0
AGND
V
DDP
88
PCI_AD4
PCI_AD3
PCI_AD2
PCI_AD1
DGND
89
DV
DD
V
DDP
90
PCI_PCLK
DGND
PCI_FRAME
PCI_RDY
91
AV
DD
92
TPB1–
TPB1+
AGND
PCI_GNT
PCI_REQ
DV
93
DD
PCI_TRDY
PCI_DEVSEL
PCI_STOP
DGND
PCI_AD0
PCI_RST
CYCLEOUT
CYCLEIN
94
V
DDP
95
AV
DD
PCI_PME
PCI_AD31
DGND
96
TPA1–
TPA1+
97
PCI_PERR
PCI_SERR
PCI_PAR
DV
98
TPBIAS1
AGND
PCI_AD30
PCI_AD29
PCI_AD28
DD
GPIO3/TEST1
GPIO2/TEST0
SCL
99
100
101
102
103
104
105
AV
DD
DV
TPB2–
DV
DD
DD
PCI_C/BE1
PCI_AD15
SDA
TPB2+
PCI_AD27
PCI_AD26
REG18
REG18
PC2
AV
DD
V
DDP
TPA2–
TPA2+
TPBIAS2
NC
PCI_AD14
DGND
NC
PC1
PCI_AD25
34
35
36
70
71
72
PC0
NC
106
107
108
142
143
144
PCI_AD24
NC
NC
NC
NC
NC
2–5
Table 2–3. Signal Names Sorted Alphanumerically to Terminal Number
TERMINAL
NAME
PDT PGE
TERMINAL
NAME
PDT PGE-
TERMINAL
NAME
PDT PGE-
TERMINAL
NAME
PDT PGE-
NO.
71
73
76
80
84
89
97
70
72
81
85
90
93
98
67
69
55
54
1
NO.
81
83
86
90
94
99
111
80
82
91
95
100
103
112
77
79
61
60
3
NO.
56
65
111
123
101
102
58
57
110
52
50
49
48
47
45
44
42
39
38
37
35
34
33
31
29
14
13
11
NO.
62
75
125
137
115
116
64
63
124
58
56
55
54
53
51
50
48
45
44
43
41
40
39
33
31
16
15
13
12
11
NO.
NO.
NO.
NO.
AGND
AGND
AGND
AGND
AGND
AGND
AGND
DV
DV
DV
DV
PCI_AD23
PCI_AD24
PCI_AD25
PCI_AD26
PCI_AD27
PCI_AD28
PCI_AD29
PCI_AD30
PCI_AD31
PCI_C/BE0
PCI_C/BE1
PCI_C/BE2
PCI_C/BE3
PCI_CLKRUN
PCI_DEVSEL
PCI_FRAME
PCI_GNT
PCI_IDSEL
PCI_INTA
PCI_IRDY
PCI_PAR
5
7
PHY_TEST_MA
68
78
DD
DD
DD
DD
128
127
125
124
122
121
120
118
41
142
141
139
138
136
135
134
132
47
PLL
GND
104
103
61
118
117
67
PLLV
DD
REG18
REG18
REG_EN
R1
FILTER0
FILTER1
126
107
99
140
121
113
114
65
GPIO2/TEST0
GPIO3/TEST1
G_RST
AV
AV
AV
AV
AV
AV
AV
R0
100
59
DD
DD
DD
DD
DD
DD
DD
SCL
PCI_AD0
PCI_AD1
PCI_AD2
PCI_AD3
PCI_AD4
PCI_AD5
PCI_AD6
PCI_AD7
PCI_AD8
PCI_AD9
PCI_AD10
PCI_AD11
PCI_AD12
PCI_AD13
PCI_AD14
PCI_AD15
PCI_AD16
PCI_AD17
PCI_AD18
PCI_AD19
PCI_AD20
PCI_AD21
PCI_AD22
SDA
60
66
28
30
TPA0–
TPA0+
TPA1–
TPA1+
TPA2–
TPA2+
TPBIAS0
TPBIAS1
TPBIAS2
TPB0–
TPB0+
TPB1–
TPB1+
TPB2–
TPB2+
77
87
15
17
78
88
2
4
86
96
108
21
122
23
87
97
CNA
CPS
94
104
105
89
17
19
95
CYCLEIN
CYCLEOUT
DGND
DGND
DGND
DGND
DGND
DGND
DGND
DGND
DGND
DGND
114
4
128
6
79
88
98
109
18
123
20
96
106
84
12
23
32
36
43
51
66
113
119
7
14
25
34
42
49
57
76
127
133
9
74
26
28
75
85
PCI_PCLK
PCI_PERR
PCI_PME
PCI_REQ
PCI_RST
PCI_SERR
PCI_STOP
PCI_TRDY
PC0
112
24
126
26
82
92
83
93
117
115
53
131
129
59
91
101
102
5
92
V
V
V
V
V
3
DDP
DDP
DDP
DDP
25
27
16
18
22
24
30
32
DV
DV
DV
DV
10
9
20
22
46
52
DD
DD
DD
DD
19
27
40
21
29
46
64
70
116
105
106
130
119
120
DDP
XI
8
10
8
PC1
63
69
6
PC2
62
68
XO
2–6
The terminals are grouped in tables by functionality, such as PCI system function and power supply function (see
Table 2–4 through Table 2–9). The terminal numbers are also listed for convenient reference.
Table 2–4. PCI System Terminals
TERMINAL
NAME
PDT PGE I/O
DESCRIPTION
NO.
NO.
Global power reset. This reset brings all of the TSB43AB23 internal registers to their default states,
including those registers not reset by PCI_RST. When G_RST is asserted, the device is completely
nonfunctional, placing all output buffers in a high impedance state.
When implementing wake capabilities from the 1394 host controller, it is necessary to implement two
resets to the TSB43AB23 device. G_RST is designed to be a one-time power-on reset, and PCI_RST
must be connected to the PCI bus RST. G_RST must be asserted for a minimum of 2 ms.
G_RST
110
124
I
PCI bus clock. Provides timing for all transactions on the PCI bus. All PCI signals are sampled at the
rising edge of PCI_CLK.
PCI_PCLK
PCI_INTA
112
109
126
123
I
Interrupt signal. This output indicates interrupts from the TSB43AB23 device to the host. This terminal
is implemented as open-drain.
O
PCI reset. When this bus reset is asserted, the TSB43AB23 device places all output buffers in a
high-impedancestate and resets all internal registers except device power management context- and
vendor-specific bits initialized by host power-on software. When PCI_RST is asserted, the device is
completely nonfunctional. Connect this terminal to PCI bus RST.
PCI_RST
53
59
I
Table 2–5. PCI Address and Data Terminals
TERMINAL
NAME
PDT PGE
I/O
DESCRIPTION
NO.
NO.
PCI_AD31
PCI_AD30
PCI_AD29
PCI_AD28
PCI_AD27
PCI_AD26
PCI_AD25
PCI_AD24
PCI_AD23
PCI_AD22
PCI_AD21
PCI_AD20
PCI_AD19
PCI_AD18
PCI_AD17
PCI_AD16
PCI_AD15
PCI_AD14
PCI_AD13
PCI_AD12
PCI_AD11
PCI_AD10
PCI_AD9
PCI_AD8
PCI_AD7
PCI_AD6
PCI_AD5
PCI_AD4
PCI_AD3
PCI_AD2
PCI_AD1
PCI_AD0
118
120
121
122
124
125
127
128
5
6
8
9
10
11
13
14
29
31
33
34
35
37
38
39
42
44
45
47
48
49
50
52
132
134
135
136
138
139
141
142
7
8
10
11
12
13
15
16
31
33
39
40
41
43
44
45
48
50
51
53
54
55
56
58
PCI address/data bus. These signals make up the multiplexed PCI address and data bus on the PCI
interface. During the address phase of a PCI cycle, AD31–AD0 contain a 32-bit address or other
destination information. During the data phase, AD31–AD0 contain data.
I/O
2–7
Table 2–6. PCI Interface Control Terminals
TERMINAL
NAME PDT PGE
I/O
DESCRIPTION
NO.
NO.
Clock run. This terminal provides clock control through the CLKRUN protocol. This terminal is
implementedas open-drain and must be pulled low through a 10-kΩ nominal resistor for designs where
CLKRUN is not implemented. For mobile applications where CLKRUN is implemented, the pullup
resistor is typically provided by the system central resource.
PCI_CLKRUN
108
122
I/O
PCI_C/BE0
PCI_C/BE1
PCI_C/BE2
PCI_C/BE3
41
28
15
2
47
30
17
4
PCI bus commands and byte enables. The command and byte enable signals are multiplexed on the
same PCI terminals. During the address phase of a bus cycle, PCI_C/BE3–PCI_C/BE0 define the bus
command. During the data phase, this 4-bit bus is used for byte enables.
I/O
PCI device select. The TSB43AB23 device asserts this signal to claim a PCI cycle as the target device.
As a PCI initiator, the TSB43AB23 device monitors this signal until a target responds. If no target
responds before time-out occurs, the TSB43AB23 device terminates the cycle with an initiator abort.
PCI_DEVSEL
PCI_FRAME
21
17
23
19
I/O
I/O
PCI cycle frame. This signal is driven by the initiator of a PCI bus cycle. PCI_FRAME is asserted to
indicate that a bus transaction is beginning, and data transfers continue while this signal is asserted.
When PCI_FRAME is deasserted, the PCI bus transaction is in the final data phase.
PCI bus grant. This signal is driven by the PCI bus arbiter to grant the TSB43AB23 device access to
the PCI bus after the current data transaction has completed. This signal may or may not follow a PCI
bus request, depending upon the PCI bus parking algorithm.
PCI_GNT
PCI_IDSEL
PCI_IRDY
114
4
128
6
I
I
Initialization device select. PCI_IDSEL selects the TSB43AB23 device during configuration space
accesses. PCI_IDSEL can be connected to 1 of the upper 21 PCI address lines on the PCI bus.
PCI initiator ready. PCI_IRDY indicates the ability of the PCI bus initiator to complete the current data
phase of the transaction. A data phase is completed upon a rising edge of PCI_CLK where both
PCI_IRDY and PCI_TRDY are asserted.
18
20
I/O
PCI parity. In all PCI bus read and write cycles, the TSB43AB23 device calculates even parity across
the PCI_AD and PCI_C/BE buses. As an initiator during PCI cycles, the TSB43AB23 device outputs
this parity indicator with a one-PCI_CLK delay. As a target during PCI cycles, the calculated parity is
compared to the initiator parity indicator; a miscompare can result in a parity error assertion
(PCI_PERR).
PCI_PAR
26
24
28
26
I/O
I/O
PCI parity error indicator. This signal is driven by a PCI device to indicate that calculated parity does
not match PCI_PAR when bit 6 (PERR_ENB) is set to 1 in the command register at offset 04h in the
PCI configuration space (see Section 3.4, Command Register).
PCI_PERR
Power management event. This terminal indicates wake events to the host and is implemented as an
open-drain output.
PCI_PME
PCI_REQ
117
115
131
129
O
O
PCI bus request. Asserted by the TSB43AB23 device to request access to the bus as an initiator. The
host arbiter asserts PCI_GNT when the TSB43AB23 device has been granted access to the bus.
PCI system error. When bit 8 (SERR_ENB) in the command register at offset 04h in the PCI
configuration space (see Section 3.4, Command Register) is set to 1, the output is pulsed, indicating
an address parity error has occurred. The TSB43AB23 device need not be the target of the PCI cycle
to assert this signal. This terminal is implemented as open-drain.
PCI_SERR
25
27
O
PCI cycle stop signal. This signal is driven by a PCI target to request the initiator to stop the current PCI
bus transaction. This signal is used for target disconnects, and is commonly asserted by target devices
which do not support burst data transfers.
PCI_STOP
PCI_TRDY
22
20
24
22
I/O
I/O
PCI target ready. PCI_TRDY indicates the ability of the PCI bus target to complete the current data
phase of the transaction. A data phase is completed upon a rising edge of PCI_CLK where both
PCI_IRDY and PCI_TRDY are asserted.
2–8
Table 2–7. Miscellaneous Terminals
TERMINAL
NAME PDT PGE
I/O
DESCRIPTION
NO.
NO.
The CYCLEIN terminal allows an external 8-kHz clock to be used as a cycle timer for synchronization
with other system devices.
CYCLEIN
55
61
I/O
I/O
If this terminal is not implemented, it must be pulled high to DV
DD
through a pullup resistor.
The CYCLEOUT terminal provides an 8-kHz cycle timer synchronization signal. If CYCLEOUT is not
implemented, this terminal must be pulled down to ground through a pulldown resistor.
CYCLEOUT
54
60
Regulator enable. This terminal must be tied to ground to enable the internal voltage regulator. When
using a single 3.3-V supply, this terminal must be tied to ground to enable the internal voltage regulator.
REG_EN
107
121
I
Whenusingadual1.8-V/3.3-Vsupplytoprovidepowertothedevice, REG_ENmustbepulledtoDV
to disable the internal voltage regulator.
DD
General-purpose I/O [2]. This terminal defaults as an input and if it is not implemented, it is
recommended that it be pulled low to ground with a 220-Ω resistor.
GPIO2/TEST0
GPIO3/TEST1
58
57
64
63
I/O
I/O
General-purpose I/O [3]. This terminal defaults as an input and if it is not implemented, it is
recommended that it be pulled low to ground with a 220-Ω resistor.
Serial clock. This terminal provides the serial clock signaling and is implemented as open-drain. For
normal operation (a ROM is implemented in the design), this terminal must be pulled high to the ROM
SCL
SDA
59
60
65
66
I/O
I/O
DV
with a 2.7-kΩ resistor. Otherwise, it must be pulled low to ground with a 220-Ω resistor.
DD
Serial data. At PCI_RST, the SDA signal is sampled to determine if a two-wire serial ROM is present.
If the serial ROM is detected, this terminal provides the serial data signaling.
This terminal is implemented as open-drain, and for normal operation (a ROM is implemented in the
design), this terminal must be pulled high to the ROM DV
be pulled low to ground with a 220-Ω resistor.
with a 2.7-kΩ resistor. Otherwise, it must
DD
2–9
Table 2–8. Physical Layer Terminals
TERMINAL
TYPE
I/O
DESCRIPTION
NAME
PDT
NO.
PGE
NO.
Cable not active. This terminal is asserted high when there are no ports receiving incoming
bias voltage. If not used, this terminal must be strapped either to DV or to GND through
DD
a resistor. To enable the CNA terminal, the BIOS must set bit 7 (CNAOUT) of the PCI PHY
control register at offset ECh in the PCI configuration space (see Section 3.20, PCI PHY
Control Register). If an EEPROM is implemented and CNA functionality is needed, bit 7 of
byte offset 16h in the serial EEPROM must be set. This sets the bit in the PCI configuration
space at power up via the EEPROM.
CNA
67
69
77
79
CMOS
I/O
Cable power status input. This terminal is normally connected to cable power through a
400-kΩ resistor. This circuit drives an internal comparator that detects the presence of cable
CPS
CMOS
CMOS
I
power. If CPS does not detect cable power, this terminal must be pulled to AV
.
DD
PLL filter terminals. These terminals are connected to an external capacitance to form a
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.
FILTER0
FILTER1
101
102
115
116
I/O
PC0
PC1
PC2
64
63
62
70
69
68
Power class programming inputs. On hardware reset, these inputs set the default value of
the power class indicated during self-ID. Programming is done by tying these terminals high
or low.
CMOS
Bias
I
Current-setting resistor terminals. These terminals are connected to an external resistance
to set the internal operating currents and cable driver output currents. A resistance of
6.34 kΩ ±1% is required to meet the IEEE Std 1394-1995 output voltage limits.
R0
R1
100
99
114
113
–
TPA0+
TPA0–
78
77
88
87
Cable
Cable
Cable
Cable
Cable
Cable
I/O
I/O
I/O
I/O
I/O
I/O
Twisted-pair cable A differential signal terminals. Board trace lengths from each pair of
positive and negative differential signal pins must be matched and as short as possible to
the external load resistors and to the cable connector.
TPA1+
TPA1–
87
86
97
96
TPA2+
TPA2–
95
94
105
104
TPB0+
TPB0–
75
74
85
84
Twisted-pair cable B differential signal terminals. Board trace lengths from each pair of
positive and negative differential signal pins must be matched and as short as possible to
the external load resistors and to the cable connector.
TPB1+
TPB1–
83
82
93
92
TPB2+
TPB2–
92
91
102
101
Twisted-pair bias output. This provides the 1.86-V nominal bias voltage needed 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.
TPBIAS0
TPBIAS1
TPBIAS2
79
88
96
89
98
106
Cable
I/O
Crystaloscillatorinputs. Thesepinsconnecttoa24.576-MHzparallelresonantfundamental
mode crystal. The optimum values for the external shunt capacitors are dependent on the
specifications of the crystal used (see Section 8.2, Crystal Selection). Terminal 5 has an
internal 10-kΩ (nominal value) pulldown resistor. An external clock input can be connected
to the XI terminal. When using an external clock input, the XO terminal must be left
unconnected. Refer to Section 9.7 for the operating characteristics of the XI terminal.
XI
XO
105
106
119
120
Crystal
–
2–10
Table 2–9. Power Supply Terminals
TERMINAL
PDT
NO.
PGE
NO.
TYPE
I/O
DESCRIPTION
NAME
AGND
71, 73, 76, 80, 81, 83, 86, 90,
84, 89, 97 94, 99, 111
Analog circuit ground terminals. These terminals must be tied together
to the low-impedance circuit board ground plane.
Supply
–
Analog circuit power terminals. A parallel combination of high
frequency decoupling capacitors near each terminal is suggested,
such as 0.1 µF and 0.001 µF. Lower frequency 10-µF filtering
capacitors are also recommended. These supply terminals are
70, 72, 81, 85, 80, 82, 91, 95,
AV
DD
Supply
–
90, 93, 98
100, 103, 112
separated from PLLV
and DV
internal to the device to provide
DD
DD
noise isolation. They must be tied at a low-impedance point on the
circuit board.
1, 12, 23, 32,
36, 43, 51, 66, 42, 49, 57, 76, Supply
3, 14, 25, 34,
Digital circuit ground terminals. These terminals must be tied together
to the low-impedance circuit board ground plane.
DGND
–
–
113, 119
127, 133
Digitalcircuit power terminals. A parallel combination of high frequency
decoupling capacitors near each DV
0.1 µF and 0.001 µF. Lower frequency 10-µF filtering capacitors are
terminal is suggested, such as
DD
7, 19, 27, 40,
56, 65, 111,
123
9, 21, 29, 46,
62, 75, 125,
137
DV
Supply
DD
also recommended. These supply terminals are separated from
PLLV
andAV internaltothedevicetoprovidenoiseisolation.They
DD
DD
must be tied at a low-impedance point on the circuit board.
Test control input. This input is used in the manufacturing test of the
PHY_TEST_MA
68
78
–
–
–
TSB43AB23device.Fornormaluse,theterminalmustbetiedtoDV
DD
.
PLL circuit ground terminal. This terminal must be tied to the
low-impedance circuit board ground plane.
PLL
GND
104
118
Supply
PLL circuit power terminal. A parallel combination of high frequency
decoupling capacitors near the terminal is suggested, such as 0.1 µF
and 0.001 µF. Lower frequency 10-µF filtering capacitors are also
PLLV
DD
103
117
Supply
–
recommended.ThissupplyterminalisseparatedfromDV
andAV
DD
DD
internal to the device to provide noise isolation. It must be tied to a
low-impedance point on the circuit board.
REG18. 1.8-V power supply for the device core. The internal voltage
regulator provides 1.8 V from DV . When the internal regulator is
DD
disabled(REG_ENishigh),theREG18terminalscanbeusedtosupply
an external 1.8-V supply to the TSB43AB23 core. It is recommended
that 0.1-µF bypass capacitors be used and placed close to these
terminals.
REG18
61, 126
67, 140
Supply
Supply
–
–
PCI signaling clamp voltage power input. PCI signals are clamped per
the PCI Local Bus Specification. In addition, if a 5-V ROM is used, the
3, 16, 30, 46,
116
5, 18, 32, 52,
130
V
DDP
V
DDP
must be connected to 5 V.
2–11
3 TSB43AB23 1394 OHCI Controller Programming Model
This section describes the internal PCI configuration registers used to program the TSB43AB23 1394 open host
controller interface. All registers are detailed in the same format: a brief description for each register is followed by
the register offset and a bit table describing the reset state for each register.
A bit description table, typically included when the register contains bits of more than one type or purpose, indicates
bit field names, a detailed field description, and field access tags which appear in the type column. Table 3–1
describes the field access tags.
Table 3–1. Bit Field Access Tag Descriptions
ACCESS TAG
NAME
Read
Write
Set
MEANING
Field can be read by software.
R
W
S
Field can be written by software to any value.
Field can be set by a write of 1. Writes of 0 have no effect.
Field can be cleared by a write of 1. Writes of 0 have no effect.
Field can be autonomously updated by the TSB43AB23 device.
C
U
Clear
Update
Figure 3–1 shows a simplified block diagram of the TSB43AB23 device.
3–1
Serial
ROM
PCI
Target
SM
Internal
Registers
OHCI PCI Power
Mgmt and CLKRUN
GPIOs
Isochronous
Transmit
Contexts
Misc
Interface
Asynchronous
Transmit
Contexts
Transmit
FIFO
Physical DMA
and Response
Link
Transmit
Resp
Time-out
Receive
Acknowledge
PCI
Host
Bus
Interface
PHY
Register
Access
and
Status
Monitor
Central
Arbiter
and
Cycle Start
Generator and
Cycle Monitor
CRC
PCI
Initiator
SM
Synthesized
Bus Reset
Request
Filters
Link
Receive
General
Request Receive
PHY/
Link
Interface
Asynchronous
Response
Receive
Receive
FIFO
Isochronous
Receive
Contexts
Received Data
Cable Port 0
Cable Port 1
Cable Port 2
Decoder/Retimer
Arbitration
and Control
State Machine
Logic
Crystal
Oscillator,
PLL System,
and Clock
Generator
Bias Voltage
and
Current Generator
Transmit Data
Encoder
Figure 3–1. TSB43AB23 Block Diagram
3–2
3.1 PCI Configuration Registers
The TSB43AB23 device is a single-function PCI device. The configuration header is compliant with the PCI Local Bus
Specification as a standard header. Table 3–2 illustrates the PCI configuration header that includes both the
predefined portion of the configuration space and the user-definable registers.
Table 3–2. PCI Configuration Register Map
REGISTER NAME
OFFSET
00h
Device ID
Status
Vendor ID
Command
04h
Class code
Header type
OHCI base address
Revision ID
08h
BIST
Latency timer
Cache line size
0Ch
10h
TI extension base address
Reserved
14h
18h–2Bh
2Ch
Subsystem ID
Subsystem vendor ID
Reserved
30h
PCI power
management
34h
Reserved
capabilities pointer
Reserved
38h
3Ch
Maximum latency Minimum grant
Interrupt pin
Interrupt line
Capability ID
OHCI control
40h
Power management capabilities
PM data PMCSR_BSE
Reserved
Next item pointer
44h
Power management control and status
48h
4Ch–EBh
ECh
F0h
PCI PHY control
Miscellaneous configuration
Link enhancement control
F4h
Subsystem device ID alias
Subsystem vendor ID alias
Reserved
F8h
GPIO3
GPIO2
FCh
3.2 Vendor ID Register
The vendor ID register contains a value allocated by the PCI SIG and identifies the manufacturer of the PCI device.
The vendor ID assigned to Texas Instruments is 104Ch.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Vendor ID
R
0
R
0
R
0
R
1
R
0
R
0
R
0
R
0
R
0
R
1
R
0
R
0
R
1
R
1
R
0
R
0
Register:
Offset:
Type:
Vendor ID
00h
Read-only
104Ch
Default:
3–3
3.3 Device ID Register
The device ID register contains a value assigned to the TSB43AB23 device by Texas Instruments. The device
identification for the TSB43AB23 device is 8024h.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Device ID
R
1
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
R
0
R
0
R
1
R
0
R
0
Register:
Offset:
Type:
Device ID
02h
Read-only
8024h
Default:
3.4 Command Register
The command register provides control over the TSB43AB23 interface to the PCI bus. All bit functions adhere to the
definitions in the PCI Local Bus Specification, as seen in the following bit descriptions. See Table 3–3 for a complete
description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Command
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R
0
R/W
0
R
0
R/W
0
R
0
R/W
0
R/W
0
R
0
Register:
Offset:
Type:
Command
04h
Read/Write, Read-only
0000h
Default:
Table 3–3. Command Register Description
BIT
15–10
9
FIELD NAME
RSVD
TYPE
DESCRIPTION
R
R
Reserved. Bits 15–10 return 0s when read.
FBB_ENB
Fast back-to-back enable. The TSB43AB23 device does not generate fast back-to-back transactions;
therefore, bit 9 returns 0 when read.
8
7
6
5
4
SERR_ENB
STEP_ENB
PERR_ENB
VGA_ENB
MWI_ENB
R/W
R
PCI_SERR enable. When bit 8 is set to 1, the TSB43AB23 PCI_SERR driver is enabled. PCI_SERR
can be asserted after detecting an address parity error on the PCI bus.
Address/data stepping control. The TSB43AB23 device does not support address/data stepping;
therefore, bit 7 is hardwired to 0.
R/W
R
Parity error enable. When bit 6 is set to 1, the TSB43AB23 device is enabled to drive PCI_PERR
response to parity errors through the PCI_PERR signal.
VGApalettesnoopenable. TheTSB43AB23devicedoesnotfeatureVGApalettesnooping;therefore,
bit 5 returns 0 when read.
R/W
Memory write and invalidate enable. When bit 4 is set to 1, the TSB43AB23 device is enabled to
generate MWI PCI bus commands. If this bit is cleared, the TSB43AB23 device generates memory
write commands instead.
3
2
1
0
SPECIAL
MASTER_ENB
MEMORY_ENB
IO_ENB
R
Special cycle enable. The TSB43AB23 function does not respond to special cycle transactions;
therefore, bit 3 returns 0 when read.
R/W
R/W
R
Bus master enable. When bit 2 is set to 1, the TSB43AB23 device is enabled to initiate cycles on the
PCI bus.
Memory response enable. Setting bit 1 to 1 enables the TSB43AB23 device to respond to memory
cycles on the PCI bus. This bit must be set to access OHCI registers.
I/O space enable. The TSB43AB23 device does not implement any I/O-mapped functionality;
therefore, bit 0 returns 0 when read.
3–4
3.5 Status Register
The status register provides status over the TSB43AB23 interface to the PCI bus. All bit functions adhere to the
definitions in the PCI Local Bus Specification, as seen in the following bit descriptions. See Table 3–4 for a complete
description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Status
RCU RCU RCU RCU RCU
R
0
R
1
RCU
0
R
0
R
0
R
0
R
1
R
0
R
0
R
0
R
0
0
0
0
0
0
Register:
Offset:
Type:
Status
06h
Read/Clear/Update, Read-only
0210h
Default:
Table 3–4. Status Register Description
BIT
15
FIELD NAME
PAR_ERR
TYPE
RCU
RCU
DESCRIPTION
Detected parity error. Bit 15 is set to 1 when either an address parity or data parity error is detected.
14
SYS_ERR
Signaled system error. Bit 14 is set to 1 when PCI_SERR is enabled and the TSB43AB23 device has
signaled a system error to the host.
13
12
MABORT
TABORT_REC
TABORT_SIG
PCI_SPEED
RCU
RCU
RCU
R
Received master abort. Bit 13 is set to 1 when a cycle initiated by the TSB43AB23 device on the PCI
bus has been terminated by a master abort.
Received target abort. Bit 12 is set to 1 when a cycle initiated by the TSB43AB23 device on the PCI
bus was terminated by a target abort.
11
Signaled target abort. Bit 11 is set to 1 by the TSB43AB23 device when it terminates a transaction on
the PCI bus with a target abort.
10–9
DEVSEL timing. Bits 10 and 9 encode the timing of PCI_DEVSEL and are hardwired to 01b, indicating
that the TSB43AB23 device asserts this signal at a medium speed on nonconfiguration cycle
accesses.
8
DATAPAR
RCU
Data parity error detected. Bit 8 is set to 1 when the following conditions have been met:
a. PCI_PERR was asserted by any PCI device including the TSB43AB23 device.
b. The TSB43AB23 device was the bus master during the data parity error.
c. Bit 6 (PERR_EN) in the command register at offset 04h in the PCI configuration space
(see Section 3.4, Command Register) is set to 1.
7
6
FBB_CAP
UDF
R
R
R
R
R
Fast back-to-back capable. The TSB43AB23 device cannot accept fast back-to-back transactions;
therefore, bit 7 is hardwired to 0.
User-definable features (UDF) supported. The TSB43AB23 device does not support the UDF;
therefore, bit 6 is hardwired to 0.
5
66MHZ
CAPLIST
RSVD
66-MHz capable. The TSB43AB23 device operates at a maximum PCI_CLK frequency of 33 MHz;
therefore, bit 5 is hardwired to 0.
4
Capabilities list. Bit 4 returns 1 when read, indicating that capabilities additional to standard PCI are
implemented. The linked list of PCI power-management capabilities is implemented in this function.
3–0
Reserved. Bits 3–0 return 0s when read.
3–5
3.6 Class Code and Revision ID Register
The class code and revision ID register categorizes the TSB43AB23 device as a serial bus controller (0Ch),
controlling an IEEE 1394 bus (00h), with an OHCI programming model (10h). Furthermore, the TI chip revision is
indicated in the least significant byte. See Table 3–5 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Class code and revision ID
R
0
R
0
R
0
R
0
R
1
R
1
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Class code and revision ID
R
0
R
0
R
0
R
1
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Class code and revision ID
08h
Read-only
0C00 1000h
Default:
Table 3–5. Class Code and Revision ID Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–24
BASECLASS
R
Base class. This field returns 0Ch when read, which broadly classifies the function as a serial bus
controller.
23–16
15–8
7–0
SUBCLASS
PGMIF
R
R
R
Subclass. This field returns 00h when read, which specifically classifies the function as controlling an
IEEE 1394 serial bus.
Programminginterface. This field returns 10h when read, which indicates that the programming model
is compliant with the 1394 Open Host Controller Interface Specification.
CHIPREV
Silicon revision. This field returns 00h when read, which indicates the silicon revision of the
TSB43AB23 device.
3.7 Latency Timer and Class Cache Line Size Register
The latency timer and class cache line size register is programmed by host BIOS to indicate system cache line size
and the latency timer associated with theTSB43AB23device. SeeTable 3–6 for a complete description of the register
contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Latency timer and class cache line size
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Latency timer and class cache line size
0Ch
Read/Write
0000h
Default:
Table 3–6. Latency Timer and Class Cache Line Size Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–8
LATENCY_TIMER
R/W
PCI latency timer. The value in this register specifies the latency timer for the TSB43AB23 device, in
unitsofPCIclockcycles. WhentheTSB43AB23deviceisaPCIbusinitiatorandassertsPCI_FRAME,
the latency timer begins counting from zero. If the latency timer expires before the TSB43AB23
transaction has terminated, the TSB43AB23 device terminates the transaction when its PCI_GNT is
deasserted.
7–0
CACHELINE_SZ
R/W
Cache line size. This value is used by the TSB43AB23 device during memory write and invalidate,
memory-read line, and memory-read multiple transactions.
3–6
3.8 Header Type and BIST Register
The header type and built-in self-test (BIST) register indicates the TSB43AB23 PCI header type and no built-in
self-test. See Table 3–7 for a complete description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Header type and BIST
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Header type and BIST
0Eh
Read-only
0000h
Default:
Table 3–7. Header Type and BIST Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–8
BIST
R
Built-in self-test. The TSB43AB23 device does not include a BIST; therefore, this field returns 00h when
read.
7–0
HEADER_TYPE
R
PCI header type. The TSB43AB23 device includes the standard PCI header, which is communicated
by returning 00h when this field is read.
3.9 OHCI Base Address Register
The OHCI base address register is programmed with a base address referencing the memory-mapped OHCI control.
When BIOS writes all 1s to this register, the value read back is FFFF F800h, indicating that at least 2K bytes of
memory address space are required for the OHCI registers. See Table 3–8 for a complete description of the register
contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
OHCI base address
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
OHCI base address
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
OHCI base address
10h
Read/Write, Read-only
0000 0000h
Default:
Table 3–8. OHCI Base Address Register Description
BIT
31–11
10–4
FIELD NAME
OHCIREG_PTR
OHCI_SZ
TYPE
DESCRIPTION
R/W
R
OHCI register pointer. This field specifies the upper 21 bits of the 32-bit OHCI base address register.
OHCI register size. This field returns 0s when read, indicating that the OHCI registers require a
2K-byte region of memory.
3
2–1
0
OHCI_PF
OHCI_MEMTYPE
OHCI_MEM
R
R
R
OHCI register prefetch. Bit 3 returns 0 when read, indicating that the OHCI registers are
nonprefetchable.
OHCI memory type. This field returns 0s when read, indicating that the OHCI base address register
is 32 bits wide and mapping can be done anywhere in the 32-bit memory space.
OHCI memory indicator. Bit 0 returns 0 when read, indicating that the OHCI registers are mapped
into system memory space.
3–7
3.10 TI Extension Base Address Register
The TI extension base address register is programmed with a base address referencing the memory-mapped TI
extension registers. When BIOS writes all 1s to this register, the value read back is FFFF C000h, indicating that at
least 16K bytes of memory address space are required for the TI registers. See Table 3–9 for a complete description
of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
TI extension base address
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
TI extension base address
R/W
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
TI extension base address
14h
Read/Write, Read-only
0000 0000h
Default:
Table 3–9. TI Base Address Register Description
BIT
31–14
13–4
FIELD NAME
TIREG_PTR
TI_SZ
TYPE
DESCRIPTION
R/W
R
TI register pointer. This field specifies the upper 18 bits of the 32-bit TI base address register.
TI register size. This field returns 0s when read, indicating that the TI registers require a 16K-byte
region of memory.
3
TI_PF
R
R
TI register prefetch. Bit 3 returns 0 when read, indicating that the TI registers are nonprefetchable.
2–1
TI_MEMTYPE
TI memory type. This field returns 0s when read, indicating that the TI base address register is 32 bits
wide and mapping can be done anywhere in the 32-bit memory space.
0
TI_MEM
R
TImemoryindicator.Bit0returns0whenread,indicatingthattheTIregistersaremappedintosystem
memory space.
3–8
3.11 Subsystem Identification Register
The subsystem identification register is used for system and option card identification purposes. This register can
be initialized from the serial EEPROM or programmed via the subsystem access register at offset F8h in the PCI
configuration space (see Section 3.23, Subsystem Access Register). See Table 3–10 for a complete description of
the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Subsystem identification
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Subsystem identification
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
Register:
Offset:
Type:
Subsystem identification
2Ch
Read/Update
0000 0000h
Default:
Table 3–10. Subsystem Identification Register Description
BIT
31–16
15–0
FIELD NAME
OHCI_SSID
OHCI_SSVID
TYPE
RU
DESCRIPTION
Subsystem device ID. This field indicates the subsystem device ID.
Subsystem vendor ID. This field indicates the subsystem vendor ID.
RU
3.12 Power Management Capabilities Pointer Register
The power management capabilities pointer register provides a pointer into the PCI configuration header where the
power-management register block resides. The TSB43AB23 configuration header doublewords at offsets 44h and
48h provide the power-management registers. This register is read-only and returns 44h when read.
Bit
7
6
5
4
3
2
1
0
Name
Type
Default
Power management capabilities pointer
R
0
R
1
R
0
R
0
R
0
R
1
R
0
R
0
Register:
Offset:
Type:
Power management capabilities pointer
34h
Read-only
44h
Default:
3–9
3.13 Interrupt Line and Pin Register
The interrupt line and pin register communicates interrupt line routing information. See Table 3–11 for a complete
description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Interrupt line and pin
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Interrupt line and pin
3Ch
Read/Write
0100h
Default:
Table 3–11. Interrupt Line and Pin Registers Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–8
INTR_PIN
R
Interrupt pin. This field returns 01h when read, indicating that the TSB43AB23 PCI function signals
interrupts on the PCI_INTA terminal.
7–0
INTR_LINE
R/W
Interrupt line. This field is programmed by the system and indicates to software which interrupt line the
TSB43AB23 PCI_INTA is connected to.
3.14 MIN_GNT and MAX_LAT Register
TheMIN_GNTandMAX_LATregistercommunicatestothesystemthedesiredsettingofbits15–8inthelatencytimer
and class cache line size register at offset 0Ch in the PCI configuration space (see Section 3.7, Latency Timer and
Class Cache Line Size Register). If a serial EEPROM is detected, the contents of this register are loaded through
the serial EEPROM interface after a G_RST. If no serial EEPROM is detected, this register returns a default value
that corresponds to the MAX_LAT = 4, MIN_GNT = 2. See Table 3–12 for a complete description of the register
contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
MIN_GNT and MAX_LAT
RU
0
RU
0
RU
0
RU
0
RU
0
RU
1
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
1
RU
0
Register:
Offset:
Type:
MIN_GNT and MAX_LAT
3Eh
Read/Update
0402h
Default:
Table 3–12. MIN_GNT and MAX_LAT Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–8
MAX_LAT
RU
RU
Maximum latency. The contents of this field may be used by host BIOS to assign an arbitration priority level
to the TSB43AB23 device. The default for this register indicates that the TSB43AB23 device may need to
access the PCI bus as often as every 0.25 µs; thus, an extremely high priority level is requested. The
contents of this field may also be loaded through the serial EEPROM.
7–0
MIN_GNT
Minimumgrant. The contents of this field may be used by host BIOS to assign a latency timer register value
to the TSB43AB23 device. The default for this register indicates that the TSB43AB23 device may need to
sustain burst transfers for nearly 64 µs and thus request a large value be programmed in bits 15–8 of the
TSB43AB23 latency timer and class cache line size register at offset 0Ch in the PCI configuration space
(see Section 3.7, Latency Timer and Class Cache Line Size Register).
3–10
3.15 OHCI Control Register
The PCI OHCI control register is defined by the 1394 Open Host Controller Interface Specification and provides a
bit for big endian PCI support. See Table 3–13 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
OHCI control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
OHCI control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
Register:
Offset:
Type:
OHCI control
40h
Read/Write, read-only
0000 0000h
Default:
Table 3–13. OHCI Control Register Description
BIT
31–1
0
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bits 31–1 return 0s when read.
GLOBAL_SWAP
R/W
When bit 0 is set to 1, all quadlets read from and written to the PCI interface are byte-swapped (big
endian).
3.16 Capability ID and Next Item Pointer Registers
The capability ID and next item pointer register identifies the linked-list capability item and provides a pointer to the
next capability item. See Table 3–14 for a complete description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Capability ID and next item pointer
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
Register:
Offset:
Type:
Capability ID and next item pointer
44h
Read-only
0001h
Default:
Table 3–14. Capability ID and Next Item Pointer Registers Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–8
NEXT_ITEM
R
Next item pointer. The TSB43AB23 device supports only one additional capability that is
communicated to the system through the extended capabilities list; therefore, this field returns 00h
when read.
7–0
CAPABILITY_ID
R
Capabilityidentification. This field returns 01h when read, which is the unique ID assigned by the PCI
SIG for PCI power-management capability.
3–11
3.17 Power Management Capabilities Register
ThepowermanagementcapabilitiesregisterindicatesthecapabilitiesoftheTSB43AB23devicerelatedtoPCIpower
management. See Table 3–15 for a complete description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Power management capabilities
RU
0
R
1
R
1
R
1
R
1
R
1
R
1
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
R
0
Register:
Offset:
Type:
Power management capabilities
46h
Read/Update, Read-only
7E02h
Default:
Table 3–15. Power Management Capabilities Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15
PME_D3COLD
RU
PCI_PME support from D3 . This bit can be set to 1 or cleared to 0 via bit 15 (PME_D3COLD) in
cold
themiscellaneousconfigurationregisteratoffsetF0hinthePCIconfigurationspace(seeSection3.21,
MiscellaneousConfigurationRegister). The miscellaneous configuration register is loaded from ROM.
When this bit is set to 1, it indicates that the TSB43AB23 device is capable of generating a PCI_PME
wake event from D3
. This bit state is dependent upon the TSB43AB23 V implementation and
cold
AUX
may be configured by using bit 15 (PME_D3COLD) in the miscellaneous configuration register (see
Section 3.21).
14–11
PME_SUPPORT
D2_SUPPORT
R
R
PCI_PME support. This 4-bit field indicates the power states from which the TSB43AB23 device may
assert PCI_PME. This field returns a value of 1111b by default, indicating that PCI_PME may be
asserted from the D3 , D2, D1, and D0 power states.
hot
10
D2 support. Bit 10 is hardwired to 1, indicating that the TSB43AB23 device supports the D2 power
state.
9
D1_SUPPORT
R
R
D1 support. Bit 9 is hardwired to 1, indicating that the TSB43AB23 device supports the D1 power state.
8–6
AUX_CURRENT
Auxiliary current. This 3-bit field reports the 3.3-V auxiliary current requirements. When bit 15
AUX
(PME_D3COLD) is cleared, this field returns 000b; otherwise, it returns 001b.
000b = Self-powered
001b = 55 mA (3.3-V
AUX
maximum current required)
5
DSI
R
Device-specific initialization. This bit returns 0 when read, indicating that the TSB43AB23 device does
not require special initialization beyond the standard PCI configuration header before a generic class
driver is able to use it.
4
3
RSVD
R
R
Reserved. Bit 4 returns 0 when read.
PME_CLK
PCI_PME clock. This bit returns 0 when read, indicating that no host bus clock is required for the
TSB43AB23 device to generate PCI_PME.
2–0
PM_VERSION
R
Power-managementversion. Thisfieldreturns010bwhenread, indicatingthattheTSB43AB23device
is compatible with the registers described in the PCI Bus Power Management Interface Specification
(Revision 1.1).
3–12
3.18 Power Management Control and Status Register
The power management control and status register implements the control and status of the PCI power management
function. This register is not affected by the internally generated reset caused by the transition from the D3 to D0
hot
state. See Table 3–16 for a complete description of the register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Power management control and status
RWC
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R/W
0
Register:
Offset:
Type:
Power management control and status
48h
Read/Clear, Read/Write, Read-only
0000h
Default:
Table 3–16. Power Management Control and Status Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15
PME_STS
RWC
Bit 15 is set to 1 when the TSB43AB23 device normally asserts the PCI_PME signal independent of
the state of bit 8 (PME_ENB). This bit is cleared by a writeback of 1, which also clears the PCI_PME
signal driven by the TSB43AB23 device. Writing a 0 to this bit has no effect.
14–13
12–9
8
DATA_SCALE
DATA_SELECT
PME_ENB
R
R
This field returns 0s, because the data register is not implemented.
This field returns 0s, because the data register is not implemented.
R/W
When bit 8 is set to 1, PME assertion is enabled. When bit 8 is cleared, PME assertion is disabled. This
bit defaults to 0 if the function does not support PME generation from D3
. If the function supports
cold
PME from D3 , this bit is sticky and must be explicitly cleared by the operating system each time
cold
it is initially loaded.
7–2
1–0
RSVD
R
Reserved. Bits 7–2 return 0s when read.
PWR_STATE
R/W
Power state. This 2-bit field sets the TSB43AB23 device power state and is encoded as follows:
00 = Current power state is D0.
01 = Current power state is D1.
10 = Current power state is D2.
11 = Current power state is D3.
3.19 Power Management Extension Registers
The power management extension register provides extended power-management features not applicable to the
TSB43AB23 device; thus, it is read-only and returns 0 when read. See Table 3–17 for a complete description of the
register contents.
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Power management extension
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Power management extension
4Ah
Read-only
0000h
Default:
Table 3–17. Power Management Extension Registers Description
BIT
FIELD NAME
TYPE
DESCRIPTION
15–0
RSVD
R
Reserved. Bits 15–0 return 0s when read.
3–13
3.20 PCI PHY Control Register
The PCI PHY control register provides a method for enabling the PHY CNA output. See Table 3–18 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
PCI PHY control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
PCI PHY control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R
0
R
0
R
0
R/W
1
R
0
R
0
R
0
Register:
Offset:
Type:
PCI PHY control
ECh
Read/Write, read-only
0000 0008h
Default:
Table 3–18. PCI PHY Control Register
BIT
31–8
7
FIELD NAME
TYPE
R
DESCRIPTION
Reserved. Bits 31–8 return 0s when read.
RSVD
CNAOUT
R/W
When bit 7 is set to 1, the PHY CNA output is routed to terminal 96. When implementing a serial
EEPROM, this bit can be set by programming bit 7 of offset 16h in the EEPROM to 1.
6–4
RSVD
RSVD
R
R
Reserved. Bits 6–4 return 0s when read. These bits are affected when implementing a serial
EEPROM; thus, bits 6–4 at EEPROM byte offset 16h must be programmed to 0.
3
Reserved. Bit 3 defaults to 1 to indicate compliance with IEEE Std 1394a-2000. If a serial
EEPROM is implemented, bit 3 at EEPROM byte offset 16h must be set to 1. See Table 6–2,
Serial EEPROM Map.
2–0
RSVD
R
Reserved. Bits 2–0 return 0s when read. These bits are affected when implementing a serial
EEPROM; thus, bits 2–0 at EEPROM byte offset 16h must be programmed to 0.
3–14
3.21 Miscellaneous Configuration Register
The miscellaneous configuration register provides miscellaneous PCI-related configuration. See Table 3–19 for a
complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Miscellaneous configuration
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Miscellaneous configuration
R/W
0
R
0
R/W
0
R
0
R
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Miscellaneous configuration
F0h
Read/Write, read-only
0000 0000h
Default:
Table 3–19. Miscellaneous Configuration Register
BIT
31–16
15
FIELD NAME
TYPE
R
DESCRIPTION
Reserved. Bits 31–16 return 0s when read.
PCI_PME support from D3 . This bit programs bit 15 (PME_D3COLD) in the power
RSVD
PME_D3COLD
R/W
cold
management capabilities register at offset 46h in the PCI configuration space (see Section 3.17,
Power Management Capabilities Register).
14–5
RSVD
R
Reserved. Bits 14–5 return 0s when read.
4
DIS_TGT_ABT
R/W
Bit 4 defaults to 0, which provides iOHCI-Lynx compatible target abort signaling. When this bit
is set to 1, it enables the no-target-abort mode, in which the TSB43AB23 device returns
indeterminate data instead of signaling target abort.
The TSB43AB23 LLC is divided into the PCI_CLK and SCLK domains. If software tries to access
registers in the link that are not active because the SCLK is disabled, a target abort is issued by
the link. On some systems, this can cause a problem resulting in a fatal system error. Enabling
this bit allows the link to respond to these types of requests by returning FFh.
It is recommended that this bit be set to 1.
3
2
1
0
GP2IIC
R/W
R/W
R/W
R/W
When bit 3 is set to 1, the GPIO3 and GPIO2 signals are internally routed to the SCL and SDA,
respectively. The GPIO3 and GPIO2 terminals are also placed in the high-impedance state.
DISABLE_SCLKGATE
DISABLE_PCIGATE
KEEP_PCLK
When bit 2 is set to 1, the internal SCLK runs identically with the chip input. This is a test feature
only and must be cleared to 0 (all applications).
Whenbit1issetto1, theinternalPCIclockrunsidenticallywiththechipinput. Thisisatestfeature
only and must be cleared to 0 (all applications).
When bit 0 is set to 1, the PCI clock is always kept running through the PCI_CLKRUN protocol.
When this bit is cleared, the PCI clock can be stopped using PCI_CLKRUN.
3–15
3.22 Link Enhancement Control Register
The link enhancement control register implements TI proprietary bits that are initialized by software or by a serial
EEPROM, if present. After these bits are set to 1, their functionality is enabled only if bit 22 (aPhyEnhanceEnable)
in the host controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register) is
set to 1. See Table 3–20 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Link enhancement control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Link enhancement control
R/W
0
R
0
R/W
0
R/W
1
R
0
R/W
0
R
0
R/W
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R
0
Register:
Offset:
Type:
Link enhancement control
F4h
Read/Write, read-only
0000 1000h
Default:
Table 3–20. Link Enhancement Control Register Description
BIT
31–16
15
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bits 31–16 return 0s when read.
dis_at_pipeline
RSVD
R/W
R
Disable AT pipelining. When bit 15 is set to 1, out-of-order AT pipelining is disabled.
Reserved.
14
13–12
atx_thresh
R/W
This field sets the initial AT threshold value, which is used until the AT FIFO is underrun. When the
TSB43AB23 device retries the packet, it uses a 2K-byte threshold, resulting in a store-and-forward
operation.
00 = Threshold ~ 2K bytes resulting in a store-and-forward operation
01 = Threshold ~ 1.7K bytes (default)
10 = Threshold ~ 1K bytes
11 = Threshold ~ 512 bytes
These bits fine-tune the asynchronous transmit threshold. For most applications the 1.7K-byte
threshold is optimal. Changing this value may increase or decrease the 1394 latency depending on
the average PCI bus latency.
Setting the AT threshold to 1.7K, 1K, or 512 bytes results in data being transmitted at these thresholds
or when an entire packet has been checked into the FIFO. If the packet to be transmitted is larger than
the AT threshold, the remaining data must be received before the AT FIFO is emptied; otherwise, an
underrun condition occurs, resulting in a packet error at the receiving node. As a result, the link then
commences store-and-forward operation. Wait until it has the complete packet in the FIFO before
retransmitting it on the second attempt to ensure delivery.
An AT threshold of 2K results in store-and-forward operation, which means that asynchronous data
will not be transmitted until an end-of-packet token is received. Restated, setting the AT threshold to
2K results in only complete packets being transmitted.
Note that this device always uses store-and-forward when the asynchronous transmit retries register
at OHCI offset 08h (see Section 4.3, Asynchronous Transmit Retries Register) is cleared.
11
10
RSVD
R
Reserved. Bit 11 returns 0 when read.
enab_mpeg_ts
R/W
Enable MPEG CIP timestamp enhancement. When bit 9 is set to 1, the enhancement is enabled for
MPEG CIP transmit streams (FMT = 20h).
9
8
RSVD
R
Reserved. Bit 9 returns 0 when read.
enab_dv_ts
R/W
Enable DV CIP timestamp enhancement. When bit 8 is set to 1, the enhancement is enabled for DV
CIP transmit streams (FMT = 00h).
7
enab_unfair
R/W
Enable asynchronous priority requests. iOHCI-Lynx compatible. Setting bit 7 to 1 enables the link
to respond to requests with priority arbitration. It is recommended that this bit be set to 1.
3–16
Table 3–20. Link Enhancement Control Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
6
RSVD
R
This bit is not assigned in the TSB43AB23 follow-on products, because this bit location loaded by the
serial EEPROM from the enhancements field corresponds to bit 23 (programPhyEnable) in the host
controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register).
5–2
RSVD
R
Reserved. Bits 5–2 return 0s when read.
1
enab_accel
R/W
Enable acceleration enhancements. iOHCI-Lynx compatible. When bit 1 is set to 1, the PHY layer
is notified that the link supports the IEEE Std 1394a-2000 acceleration enhancements, that is,
ack-accelerated, fly-by concatenation, etc. It is recommended that this bit be set to 1.
0
RSVD
R
Reserved. Bit 0 returns 0 when read.
3.23 Subsystem Access Register
Write access to the subsystem access register updates the subsystem identification registers identically to
iOHCI-Lynx . The system ID value written to this register may also be read back from this register. See Table 3–21
for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Subsystem access
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Subsystem access
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Subsystem access
F8h
Read/Write
0000 0000h
Default:
Table 3–21. Subsystem Access Register Description
BIT
31–16
15–0
FIELD NAME
SUBDEV_ID
SUBVEN_ID
TYPE
DESCRIPTION
R/W
R/W
Subsystem device ID alias. This field indicates the subsystem device ID.
Subsystem vendor ID alias. This field indicates the subsystem vendor ID.
3–17
3.24 GPIO Control Register
The GPIO control register has the control and status bits for the GPIO2 and GPIO3 ports. See Table 3–22 for a
complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
GPIO control
RWU R/W
R/W
0
R
0
R/W
0
R/W
0
R
0
R
0
R
0
9
R
0
6
R/W
0
R/W
0
R
0
3
R
0
2
R
0
1
RWU
0
0
0
15
14
13
12
11
10
8
7
5
4
0
Name
Type
Default
GPIO control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
GPIO control
FCh
Read/Write/Update, read/write, read-only
0000 0000h
Default:
Table 3–22. General-Purpose Input/Output Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
INT_3EN
R/W
When bit 31 is set to 1, a TSB43AB23 general-purpose interrupt event occurs on a level change of the
GPIO3 input. This event can generate an interrupt, with mask and event status reported through the
interrupt mask register at OHCI offset 88h/8Ch (see Section 4.22, Interrupt Mask Register) and
interrupt event register at OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register).
30
29
28
RSVD
R
Reserved. Bit 30 returns 0 when read.
GPIO_INV3
GPIO_ENB3
R/W
R/W
GPIO3 polarity invert. When bit 29 is set to 1, the polarity of GPIO3 is inverted.
GPIO3 enable control. When bit 28 is set to 1, the output is enabled. Otherwise, the output is high
impedance.
27–25
RSVD
R
Reserved. Bits 27–25 return 0s when read.
24
GPIO_DATA3
RWU
GPIO3 data. Reads from bit 24 return the logical value of the input to GPIO3. Writes to this bit update
the value to drive to GPIO3 when output is enabled.
23
INT_2EN
R/W
When bit 23 is set to 1, a TSB43AB23 general-purpose interrupt event occurs on a level change of the
GPIO2 input. This event can generate an interrupt, with mask and event status reported through the
interrupt mask register at OHCI offset 88h/8Ch (see Section 4.22, Interrupt Mask Register) and
interrupt event register at OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register).
22
21
20
RSVD
R
Reserved. Bit 22 returns 0 when read.
GPIO_INV2
GPIO_ENB2
R/W
R/W
GPIO2 polarity invert. When bit 21 is set to 1, the polarity of GPIO2 is inverted.
GPIO2 enable control. When bit 20 is set to 1, the output is enabled. Otherwise, the output is high
impedance.
19–17
RSVD
R
Reserved. Bits 19–17 return 0s when read.
16
GPIO_DATA2
RWU
GPIO2 data. Reads from bit 16 return the logical value of the input to GPIO2. Writes to this bit update
the value to drive to GPIO2 when the output is enabled.
15–0
RSVD
R
Reserved. Bits 15–0 return 0s when read.
3–18
4 OHCI Registers
The OHCI registers defined by the 1394 Open Host Controller Interface Specification are memory-mapped into a
2K-byte region of memory pointed to by the OHCI base address register at offset 10h in PCI configuration space (see
Section 3.9, OHCI Base Address Register). These registers are the primary interface for controlling the TSB43AB23
IEEE 1394 link function.
This section provides the register interface and bit descriptions. Several set/clear register pairs in this programming
model are implemented to solve various issues with typical read-modify-write control registers. There are two
addresses for a set/clear register: RegisterSet and RegisterClear. See Table 4–1 for a register listing. A 1 bit written
to RegisterSet causes the corresponding bit in the set/clear register to be set to 1; a 0 bit leaves the corresponding
bit unaffected. A 1 bit written to RegisterClear causes the corresponding bit in the set/clear register to be cleared;
a 0 bit leaves the corresponding bit in the set/clear register unaffected.
Typically, a read from either RegisterSet or RegisterClear returns the contents of the set or clear register, respectively.
However, sometimes reading the RegisterClear provides a masked version of the set or clear register. The interrupt
event register is an example of this behavior.
Table 4–1. OHCI Register Map
DMA CONTEXT
REGISTER NAME
OHCI version
ABBREVIATION
Version
OFFSET
00h
—
GUID ROM
GUID_ROM
ATRetries
04h
Asynchronous transmit retries
CSR data
08h
CSRData
0Ch
CSR compare
CSRCompareData
CSRControl
ConfigROMhdr
BusID
10h
CSR control
14h
Configuration ROM header
Bus identification
Bus options
18h
1Ch
BusOptions
GUIDHi
20h
GUID high
24h
GUID low
GUIDLo
28h
Reserved
—
2Ch–30h
34h
Configuration ROM mapping
Posted write address low
Posted write address high
Vendor ID
ConfigROMmap
PostedWriteAddressLo
PostedWriteAddressHi
VendorID
38h
3Ch
40h
Reserved
—
44h–4Ch
50h
HCControlSet
HCControlClr
—
Host controller control
Reserved
54h
58h–5Ch
4–1
Table 4–1. OHCI Register Map (Continued)
DMA CONTEXT
REGISTER NAME
ABBREVIATION
OFFSET
60h
Self-ID
Reserved
—
Self-ID buffer pointer
Self-ID count
SelfIDBuffer
64h
SelfIDCount
68h
Reserved
—
6Ch
—
IRChannelMaskHiSet
IRChannelMaskHiClear
IRChannelMaskLoSet
IRChannelMaskLoClear
IntEventSet
70h
Isochronous receive channel mask high
Isochronous receive channel mask low
Interrupt event
74h
78h
7Ch
80h
IntEventClear
84h
IntMaskSet
88h
Interrupt mask
IntMaskClear
8Ch
IsoXmitIntEventSet
IsoXmitIntEventClear
IsoXmitIntMaskSet
IsoXmitIntMaskClear
IsoRecvIntEventSet
IsoRecvIntEventClear
IsoRecvIntMaskSet
IsoRecvIntMaskClear
InitialBandwidthAvailable
InitialChannelsAvailableHi
InitialChannelsAvailableLo
—
90h
Isochronous transmit interrupt event
Isochronous transmit interrupt mask
Isochronous receive interrupt event
Isochronous receive interrupt mask
94h
98h
9Ch
—
A0h
A4h
A8h
ACh
B0h
Initial bandwidth available
Initial channels available high
Initial channels available low
Reserved
B4h
B8h
BCh–D8h
DCh
E0h
Fairness control
FairnessControl
LinkControlSet
Link control
LinkControlClear
NodeID
E4h
Node identification
PHY layer control
Isochronous cycle timer
Reserved
E8h
PhyControl
ECh
F0h
Isocyctimer
—
F4h–FCh
100h
104h
108h
10Ch
110h
114h
118h
11Ch
120h
124h–17Ch
AsyncRequestFilterHiSet
AsyncRequestFilterHiClear
AsyncRequestFilterLoSet
AsyncRequestFilterLoClear
PhysicalRequestFilterHiSet
PhysicalRequestFilterHiClear
PhysicalRequestFilterLoSet
PhysicalRequestFilterLoClear
PhysicalUpperBound
—
Asynchronous request filter high
Asynchronous request filter low
Physical request filter high
Physical request filter low
Physical upper bound
Reserved
4–2
Table 4–1. OHCI Register Map (Continued)
DMA CONTEXT
REGISTER NAME
ABBREVIATION
OFFSET
180h
ContextControlSet
Asynchronous context control
ContextControlClear
184h
Asynchronous
Request Transmit
[ ATRQ ]
Reserved
—
188h
Asynchronous context command pointer
Reserved
CommandPtr
18Ch
—
190h–19Ch
1A0h
ContextControlSet
Asynchronous context control
ContextControlClear
1A4h
Asynchronous
Response Transmit
[ ATRS ]
Reserved
—
1A8h
Asynchronous context command pointer
Reserved
CommandPtr
1ACh
—
1B0h–1BCh
1C0h
ContextControlSet
Asynchronous context control
ContextControlClear
1C4h
Asynchronous
Request Receive
[ ARRQ ]
Reserved
—
1C8h
Asynchronous context command pointer
Reserved
CommandPtr
1CCh
—
1D0h–1DCh
1E0h
ContextControlSet
Asynchronous context control
ContextControlClear
1E4h
Asynchronous
Response Receive
[ ARRS ]
Reserved
—
1E8h
Asynchronous context command pointer
Reserved
CommandPtr
1ECh
—
1F0h–1FCh
200h + 16*n
204h + 16*n
208h + 16*n
ContextControlSet
ContextControlClear
—
Isochronous transmit context control
Reserved
Isochronous
Transmit Context n
n = 0, 1, 2, 3, …, 7
Isochronous transmit context command
pointer
CommandPtr
20Ch + 16*n
Reserved
—
210h–3FCh
400h + 32*n
404h + 32*n
408h + 32*n
ContextControlSet
ContextControlClear
—
Isochronous receive context control
Reserved
Isochronous
Receive Context n
n = 0, 1, 2, 3
Isochronous receive context command
pointer
CommandPtr
ContextMatch
40Ch + 32*n
410h + 32*n
Isochronous receive context match
4–3
4.1 OHCI Version Register
The OHCI version register indicates the OHCI version support and whether or not the serial EEPROM is present. See
Table 4–2 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
OHCI version
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
X
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
1
0
15
14
13
12
11
10
Name
Type
Default
OHCI version
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
OHCI version
00h
Read-only
0X01 0010h
Default:
Table 4–2. OHCI Version Register Description
BIT
31–25
24
FIELD NAME
RSVD
TYPE
DESCRIPTION
R
R
Reserved. Bits 31–25 return 0s when read.
GUID_ROM
The TSB43AB23 device sets bit 24 to 1 if the serial EEPROM is detected. If the serial EEPROM is
present, the Bus_Info_Block is automatically loaded on system (hardware) reset.
23–16
version
R
Major version of the OHCI. The TSB43AB23 device is compliant with the 1394 Open Host Controller
Interface Specification (Revision 1.1); thus, this field reads 01h.
15–8
7–0
RSVD
R
R
Reserved. Bits 15–8 return 0s when read.
revision
Minor version of the OHCI. The TSB43AB23 device is compliant with the 1394 Open Host Controller
Interface Specification (Revision 1.1); thus, this field reads 10h.
4–4
4.2 GUID ROM Register
The GUID ROM register accesses the serial EEPROM, and is only applicable if bit 24 (GUID_ROM) in the OHCI
version register at OHCI offset 00h (see Section 4.1, OHCI Version Register) is set to 1. See Table 4–3 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
GUID ROM
RSU
0
R
0
R
0
R
0
R
0
R
0
RSU
R
0
8
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
0
15
14
13
12
11
10
9
7
6
5
4
3
2
1
0
Name
Type
Default
GUID ROM
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
GUID ROM
04h
Read/Set/Update, read/update, read-only
00XX 0000h
Default:
Table 4–3. GUID ROM Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
addrReset
RSU
Softwaresetsbit31to1toresettheGUIDROMaddressto0. WhentheTSB43AB23devicecompletes
the reset, it clears this bit. The TSB43AB23 device does not automatically fill bits 23–16 (rdData field)
th
with the 0 byte.
30–26
RSVD
rdStart
R
Reserved. Bits 30–26 return 0s when read.
25
RSU
A read of the currently addressed byte is started when bit 25 is set to 1. This bit is automatically cleared
when the TSB43AB23 device completes the read of the currently addressed GUID ROM byte.
24
RSVD
rdData
R
RU
R
Reserved. Bit 24 returns 0 when read.
23–16
15–8
7–0
This field contains the data read from the GUID ROM.
Reserved. Bits 15–8 return 0s when read.
RSVD
miniROM
R
The miniROM field defaults to 0 indicating that no mini-ROM is implemented. If bit 5 of EEPROM offset
6h is set to 1, this field returns 20h indicating that valid mini-ROM data begins at offset 20h of the GUID
ROM.
4–5
4.3 Asynchronous Transmit Retries Register
The asynchronous transmit retries register indicates the number of times the TSB43AB23 device attempts a retry
for asynchronous DMA request transmit and for asynchronous physical and DMA response transmit. See Table 4–4
for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Asynchronous transmit retries
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Asynchronous transmit retries
R
0
R
0
R
0
R
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Asynchronous transmit retries
08h
Read/Write, read-only
0000 0000h
Default:
Table 4–4. Asynchronous Transmit Retries Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–29
secondLimit
R
The second limit field returns 0s when read, because outbound dual-phase retry is not
implemented.
28–16
15–12
11–8
cycleLimit
RSVD
R
R
The cycle limit field returns 0s when read, because outbound dual-phase retry is not implemented.
Reserved. Bits 15–12 return 0s when read.
maxPhysRespRetries
R/W
This field tells the physical response unit how many times to attempt to retry the transmit operation
for the response packet when a busy acknowledge or ack_data_error is received from the target
node.
7–4
3–0
maxATRespRetries
maxATReqRetries
R/W
R/W
This field tells the asynchronous transmit response unit how many times to attempt to retry the
transmit operation for the response packet when a busy acknowledge or ack_data_error is
received from the target node.
This field tells the asynchronous transmit DMA request unit how many times to attempt to retry the
transmit operation for the response packet when a busy acknowledge or ack_data_error is
received from the target node.
4.4 CSR Data Register
The CSR data register accesses the bus management CSR registers from the host through compare-swap
operations. This register contains the data to be stored in a CSR if the compare is successful.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
CSR data
R
X
R
X
R
X
R
X
R
X
R
X
R
X
9
R
X
8
R
X
7
R
X
6
R
X
5
R
X
4
R
X
3
R
X
2
R
X
1
R
X
0
15
14
13
12
11
10
Name
Type
Default
CSR data
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
Register:
Offset:
Type:
CSR data
0Ch
Read-only
XXXX XXXXh
Default:
4–6
4.5 CSR Compare Register
The CSR compare register accesses the bus management CSR registers from the host through compare-swap
operations. This register contains the data to be compared with the existing value of the CSR resource.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
CSR compare
R
X
R
X
R
X
R
X
R
X
R
X
R
X
9
R
X
8
R
X
7
R
X
6
R
X
5
R
X
4
R
X
3
R
X
2
R
X
1
R
X
0
15
14
13
12
11
10
Name
Type
Default
CSR compare
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
Register:
Offset:
Type:
CSR compare
10h
Read-only
XXXX XXXXh
Default:
4.6 CSR Control Register
The CSR control register accesses the bus management CSR registers from the host through compare-swap
operations. This register controls the compare-swap operation and selects the CSR resource. See Table 4–5 for a
complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
CSR control
RU
1
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
CSR control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
X
R/W
X
Register:
Offset:
Type:
CSR control
14h
Read/Write, Read/Update, Read-only
8000 000Xh
Default:
Table 4–5. CSR Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
csrDone
RU
Bit 31 is set to 1 by the TSB43AB23 device when a compare-swap operation is complete. It is cleared
whenever this register is written.
30–2
1–0
RSVD
csrSel
R
Reserved. Bits 30–2 return 0s when read.
R/W
This field selects the CSR resource as follows:
00 = BUS_MANAGER_ID
01 = BANDWIDTH_AVAILABLE
10 = CHANNELS_AVAILABLE_HI
11 = CHANNELS_AVAILABLE_LO
4–7
4.7 Configuration ROM Header Register
The configuration ROM header register externally maps to the first quadlet of the 1394 configuration ROM, offset
FFFF F000 0400h. See Table 4–6 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Configuration ROM header
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Configuration ROM header
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
Register:
Offset:
Type:
Configuration ROM header
18h
Read/Write
Default:
0000 XXXXh
Table 4–6. Configuration ROM Header Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–24
info_length
R/W
IEEE 1394 bus-management field. Must be valid when bit 17 (linkEnable) in the host controller control
register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register) is set to 1.
23–16
15–0
crc_length
R/W
R/W
IEEE 1394 bus-management field. Must be valid when bit 17 (linkEnable) in the host controller control
register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register) is set to 1.
rom_crc_value
IEEE 1394 bus-management field. Must be valid at any time bit 17 (linkEnable) in the host controller
control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register) is set to
1. The reset value is undefined if no serial EEPROM is present. If a serial EEPROM is present, this
field is loaded from the serial EEPROM.
4.8 Bus Identification Register
The bus identification register externally maps to the first quadlet in the Bus_Info_Block and contains the constant
3133 3934h, which is the ASCII value of 1394.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Bus identification
R
0
R
0
R
1
R
1
R
0
R
0
R
0
9
R
1
8
R
0
7
R
0
6
R
1
5
R
1
4
R
0
3
R
0
2
R
1
1
R
1
0
15
14
13
12
11
10
Name
Type
Default
Bus identification
R
0
R
0
R
1
R
1
R
1
R
0
R
0
R
1
R
0
R
0
R
1
R
1
R
0
R
1
R
0
R
0
Register:
Offset:
Type:
Bus identification
1Ch
Read-only
Default:
3133 3934h
4–8
4.9 Bus Options Register
The bus options register externally maps to the second quadlet of the Bus_Info_Block. See Table 4–7 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Bus options
R/W
X
R/W
X
R/W
X
R/W
X
R/W
0
R
0
R
0
9
R
0
8
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
15
14
13
12
11
10
7
6
5
4
3
2
1
0
Name
Type
Default
Bus options
R/W
1
R/W
0
R/W
1
R/W
0
R
0
R
0
R
0
R
0
R/W
X
R/W
X
R
0
R
0
R
0
R
0
R
1
R
0
Register:
Offset:
Type:
Bus options
20h
Read/Write, read-only
X0XX A0X2h
Default:
Table 4–7. Bus Options Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
irmc
R/W
Isochronousresource-manager capable. IEEE 1394 bus-management field. Must be valid when bit 17
(linkEnable) in the host controller control register at OHCI offset 50h/54h (see Section 4.16, Host
Controller Control Register) is set to 1.
30
29
28
27
cmc
isc
R/W
R/W
R/W
R/W
Cycle master capable. IEEE 1394 bus-management field. Must be valid when bit 17 (linkEnable) in the
host controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control
Register) is set to 1.
Isochronous support capable. IEEE 1394 bus-management field. Must be valid when bit 17
(linkEnable) in the host controller control register at OHCI offset 50h/54h (see Section 4.16, Host
Controller Control Register) is set to 1.
bmc
pmc
Bus manager capable. IEEE 1394 bus-management field. Must be valid when bit 17 (linkEnable) in
the host controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control
Register) is set to 1.
Power-managementcapable. IEEE 1394 bus-management field. When bit 27 is set to 1, this indicates
that the node is power-management capable. Must be valid when bit 17 (linkEnable) in the host
controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register)
is set to 1.
26–24
23–16
RSVD
R
Reserved. Bits 26–24 return 0s when read.
cyc_clk_acc
R/W
Cycle master clock accuracy, in parts per million. IEEE 1394 bus-management field. Must be valid
whenbit17(linkEnable)inthehostcontrollercontrolregisteratOHCIoffset 50h/54h (see Section 4.16,
Host Controller Control Register) is set to 1.
15–12
max_rec
R/W
Maximum request. IEEE 1394 bus-management field. Hardware initializes this field to indicate the
maximum number of bytes in a block request packet that is supported by the implementation. This
value, max_rec_bytes, must be 512 or greater, and is calculated by 2^(max_rec + 1). Software may
change this field; however, this field must be valid at any time bit 17 (linkEnable) in the host controller
control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control Register) is set to
1. A received block write request packet with a length greater than max_rec_bytes may generate an
ack_type_error. This field is not affected by a software reset, and defaults to value indicating
2048 bytes on a system (hardware) reset.
11–8
7–6
RSVD
g
R
Reserved. Bits 11–8 return 0s when read.
R/W
Generation counter. This field is incremented if any portion of the configuration ROM has been
incremented since the prior bus reset.
5–3
2–0
RSVD
R
R
Reserved. Bits 5–3 return 0s when read.
Lnk_spd
Link speed. This field returns 010, indicating that the link speeds of 100M bits/s, 200M bits/s, and
400M bits/s are supported.
4–9
4.10 GUID High Register
The GUID high register represents the upper quadlet in a 64-bit global unique ID (GUID) which maps to the third
quadlet in the Bus_Info_Block. This register contains node_vendor_ID and chip_ID_hi fields. This register initializes
to 0s on a system (hardware) reset, which is an illegal GUID value. If a serial EEPROM is detected, the contents of
this register are loaded through the serial EEPROM interface after a G_RST. At that point, the contents of this register
cannot be changed. If no serial EEPROM is detected, the contents of this register are loaded by the BIOS after a
PCI_RST. At that point, the contents of this register cannot be changed.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
GUID high
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
GUID high
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
GUID high
24h
Read-only
0000 0000h
Default:
4.11 GUID Low Register
The GUID low register represents the lower quadlet in a 64-bit global unique ID (GUID) which maps to chip_ID_lo
in the Bus_Info_Block. This register initializes to 0s on a system (hardware) reset and behaves identical to the GUID
high register at OHCI offset 24h (see Section 4.10, GUID High Register).
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
GUID low
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
GUID low
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
GUID low
28h
Read-only
0000 0000h
Default:
4–10
4.12 Configuration ROM Mapping Register
The configuration ROM mapping register contains the start address within system memory that maps to the start
address of 1394 configuration ROM for this node. See Table 4–8 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Configuration ROM mapping
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Configuration ROM mapping
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Configuration ROM mapping
34h
Read/Write
0000 0000h
Default:
Table 4–8. Configuration ROM Mapping Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–10
configROMaddr
R/W
If a quadlet read request to 1394 offset FFFF F000 0400h through offset FFFF F000 07FFh is
received, the low-order 10 bits of the offset are added to this register to determine the host memory
address of the read request.
9–0
RSVD
R
Reserved. Bits 9–0 return 0s when read.
4.13 Posted Write Address Low Register
The posted write address low register communicates error information if a write request is posted and an error occurs
while the posted data packet is being written. See Table 4–9 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Posted write address low
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Posted write address low
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
Register:
Offset:
Type:
Posted write address low
38h
Read/Update
XXXX XXXXh
Default:
Table 4–9. Posted Write Address Low Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
The lower 32 bits of the 1394 destination offset of the write request that failed.
31–0
offsetLo
RU
4–11
4.14 Posted Write Address High Register
Thepostedwriteaddresshighregistercommunicateserrorinformationifawriterequestispostedandanerroroccurs
while writing the posted data packet. See Table 4–10 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Posted write address high
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Posted write address high
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
Register:
Offset:
Type:
Posted write address high
3Ch
Read/Update
Default:
XXXX XXXXh
Table 4–10. Posted Write Address High Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–16
sourceID
RU
This field is the 10-bit bus number (bits 31–22) and 6-bit node number (bits 21–16) of the node that
issued the write request that failed.
15–0
offsetHi
RU
The upper 16 bits of the 1394 destination offset of the write request that failed.
4.15 Vendor ID Register
The vendor ID register holds the company ID of an organization that specifies any vendor-unique registers. The
TSB43AB23 device implements Texas Instruments unique behavior with regards to OHCI. Thus, this register is
read-only and returns 0108 0028h when read.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Vendor ID
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
1
8
R
0
7
R
0
6
R
0
5
R
0
4
R
1
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Vendor ID
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
1
R
0
R
1
R
0
R
0
R
0
Register:
Offset:
Type:
Vendor ID
40h
Read-only
0108 0028h
Default:
4–12
4.16 Host Controller Control Register
Thehostcontrollercontrolset/clearregisterpairprovidesflagsforcontrollingtheTSB43AB23device. SeeTable 4–11
for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Host controller control
RSU
0
RSC
X
RSC
0
R
0
R
0
R
0
R
0
9
R
0
8
R
1
7
RSC
R
0
5
R
0
4
RSC
RSC
X
RSC RSCU
0
0
0
0
15
14
13
12
11
10
6
3
2
1
0
Name
Type
Default
Host controller control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Host controller control
50h
54h
set register
clear register
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read/clear, read-only
X08X 0000h
Table 4–11. Host Controller Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
BIBimage Valid
RSU
Whenbit31issetto1, theTSB43AB23physicalresponseunitisenabledtorespondtoblockread
requests to host configuration ROM and to the mechanism for atomically updating configuration
ROM. Software creates a valid image of the bus_info_block in host configuration ROM before
setting this bit.
When this bit is cleared, the TSB43AB23 device returns ack_type_error on block read requests
to host configuration ROM. Also, when this bit is cleared and a 1394 bus reset occurs, the
configuration ROM mapping register at OHCI offset 34h (see Section 4.12, Configuration ROM
Mapping Register), configuration ROM header register at OHCI offset 18h (see Section 4.7,
Configuration ROM Header Register), and bus options register at OHCI offset 20h (see
Section 4.9, Bus Options Register) are not updated.
Software can set this bit only when bit 17 (linkEnable) is 0. Once bit 31 is set to 1, it can be cleared
by a system (hardware) reset, a software reset, or if a fetch error occurs when the TSB43AB23
device loads bus_info_block registers from host memory.
30
29
noByteSwapData
AckTardyEnable
RSC
RSC
Bit 30 controls whether physical accesses to locations outside the TSB43AB23 device itself, as
well as any other DMA data accesses are byte swapped.
Bit 29 controls the acknowledgement of ack_tardy. When bit 29 is set to 1, ack_tardy may be
returned as an acknowledgment to accesses from the 1394 bus to the TSB43AB23 device,
including accesses to the bus_info_block. The TSB43AB23 device returns ack_tardy to all other
asynchronouspackets addressed to the TSB43AB23 node. When the TSB43AB23 device sends
ack_tardy, bit 27 (ack_tardy) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, InterruptEventRegister) is set to 1 to indicate the attempted asynchronous access.
Softwareensuresthatbit27(ack_tardy)intheinterrupteventregisteris0.Softwarealsounmasks
wake-up interrupt events such as bit 19 (phy) and bit 27 (ack_tardy) in the interrupt event register
before placing the TSB43AB23 device into the D1 power mode.
Software must not set this bit if the TSB43AB23 node is the 1394 bus manager.
28–24
RSVD
R
R
Reserved. Bits 28–24 return 0s when read.
23
programPhyEnable
Bit23informsupper-levelsoftwarethatlower-levelsoftwarehasconsistentlyconfiguredtheIEEE
1394a-2000 enhancements in the link and PHY layers. When this bit is 1, generic software such
as the OHCI driver is responsible for configuring IEEE 1394a-2000 enhancements in the PHY
layer and bit 22 (aPhyEnhanceEnable). When this bit is 0, the generic software may not modify
the IEEE 1394a-2000 enhancements in the PHY layer and cannot interpret the setting of bit 22
(aPhyEnhanceEnable). This bit is initialized from serial EEPROM. This bit defaults to 1.
4–13
Table 4–11. Host Controller Control Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
22
aPhyEnhanceEnable
RSC
When bits 23 (programPhyEnable) and 17 (linkEnable) are 1, the OHCI driver can set bit 22 to
1 to use all IEEE 1394a-2000 enhancements. When bit 23 (programPhyEnable) is cleared to 0,
the software does not change PHY enhancements or this bit.
21–20
RSVD
LPS
R
Reserved. Bits 21 and 20 return 0s when read.
19
RSC
Bit 19 controls the link power status. Software must set this bit to 1 to permit the link-PHY
communication. A 0 prevents link-PHY communication.
The OHCI-link is divided into two clock domains (PCI_CLK and PHY_SCLK). If software tries to
access any register in the PHY_SCLK domain while the PHY_SCLK is disabled, a target abort
is issued by the link. This problem can be avoided by setting bit 4 (DIS_TGT_ABT) to 1 in the
miscellaneous configuration register at offset F0h in the PCI configuration space (see
Section 3.21, Miscellaneous Configuration Register). This allows the link to respond to these
types of request by returning all Fs (hex).
OHCI registers at offsets DCh–F0h and 100h–11Ch are in the PHY_SCLK domain.
After setting LPS, software must wait approximately 10 ms before attempting to access any of
the OHCI registers. This gives the PHY_SCLK time to stabilize.
18
17
postedWriteEnable
linkEnable
RSC
RSC
Bit 18 enables (1) or disables (0) posted writes. Software changes this bit only when bit 17
(linkEnable) is 0.
Bit 17 is cleared to 0 by either a system (hardware) or software reset. Software must set this bit
to 1 when the system is ready to begin operation and then force a bus reset. This bit is necessary
to keep other nodes from sending transactions before the local system is ready. When this bit is
cleared, the TSB43AB23 device is logically and immediately disconnected from the 1394 bus, no
packets are received or processed, nor are packets transmitted.
16
SoftReset
RSVD
RSCU When bit 16 is set to 1, all TSB43AB23 states are reset, all FIFOs are flushed, and all OHCI
registers are set to their system (hardware) reset values, unless otherwise specified. PCI
registersarenotaffectedbythisbit. Thisbitremainssetto1whilethesoftwareresetisinprogress
and reverts back to 0 when the reset has completed.
15–0
R
Reserved. Bits 15–0 return 0s when read.
4.17 Self-ID Buffer Pointer Register
The self-ID buffer pointer register points to the 2K-byte aligned base address of the buffer in host memory where the
self-ID packets are stored during bus initialization. Bits 31–11 are read/write accessible. Bits 10–0 are reserved, and
return 0s when read.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Self-ID buffer pointer
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Self-ID buffer pointer
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Self-ID buffer pointer
64h
Read/Write, read-only
XXXX XX00h
Default:
4–14
4.18 Self-ID Count Register
The self-ID count register keeps a count of the number of times the bus self-ID process has occurred, flags self-ID
packet errors, and keeps a count of the self-ID data in the self-ID buffer. See Table 4–12 for a complete description
of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Self-ID count
RU
X
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
15
14
13
12
11
10
7
6
5
4
3
2
1
0
Name
Type
Default
Self-ID count
R
0
R
0
R
0
R
0
R
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
R
0
R
0
Register:
Offset:
Type:
Self-ID count
68h
Read/Update, read-only
X0XX 0000h
Default:
Table 4–12. Self-ID Count Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
selfIDError
RU
When bit 31 is set to 1, an error was detected during the most recent self-ID packet reception. The
contents of the self-ID buffer are undefined. This bit is cleared after a self-ID reception in which no
errors are detected. Note that an error can be a hardware error or a host bus write error.
30–24
23–16
RSVD
R
Reserved. Bits 30–24 return 0s when read.
selfIDGeneration
RU
The value in this field increments each time a bus reset is detected. This field rolls over to 0 after
reaching 255.
15–11
10–2
RSVD
R
Reserved. Bits 15–11 return 0s when read.
selfIDSize
RU
This fieldindicates the number of quadlets that havebeen writtenintothe self-ID buffer forthe current
bits 23–16 (selfIDGeneration field). This includes the header quadlet and the self-ID data. This field
is cleared to 0s when the self-ID reception begins.
1–0
RSVD
R
Reserved. Bits 1 and 0 return 0s when read.
4–15
4.19 Isochronous Receive Channel Mask High Register
The isochronous receive channel mask high set/clear register enables packet receives from the upper 32
isochronous data channels. A read from either the set register or clear register returns the content of the isochronous
receive channel mask high register. See Table 4–13 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive channel mask high
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Isochronous receive channel mask high
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous receive channel mask high
70h
74h
set register
clear register
Type:
Default:
Read/Set/Clear
XXXX XXXXh
Table 4–13. Isochronous Receive Channel Mask High Register Description
BIT
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
FIELD NAME
isoChannel63
isoChannel62
isoChannel61
isoChannel60
isoChannel59
isoChannel58
isoChannel57
isoChannel56
isoChannel55
isoChannel54
isoChannel53
isoChannel52
isoChannel51
isoChannel50
isoChannel49
isoChannel48
isoChannel47
isoChannel46
isoChannel45
isoChannel44
isoChannel43
isoChannel42
isoChannel41
isoChannel40
isoChannel39
TYPE
DESCRIPTION
RSC Whenbit 31 issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber63.
RSC Whenbit30issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber62.
RSC Whenbit29issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber61.
RSC Whenbit28issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber60.
RSC Whenbit27issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber59.
RSC Whenbit26issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber58.
RSC Whenbit25issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber57.
RSC Whenbit24issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber56.
RSC Whenbit23issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber55.
RSC Whenbit22issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber54.
RSC Whenbit21issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber53.
RSC Whenbit20issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber52.
RSC Whenbit19issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber51.
RSC Whenbit18issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber50.
RSC Whenbit17issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber49.
RSC Whenbit16issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber48.
RSC Whenbit15issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber47.
RSC Whenbit14issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber46.
RSC Whenbit13issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber45.
RSC Whenbit12issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber44.
RSC When bit 11 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 43.
RSC Whenbit10issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber42.
RSC When bit 9 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 41.
RSC When bit 8 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 40.
RSC When bit 7 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 39.
8
7
4–16
Table 4–13. Isochronous Receive Channel Mask High Register Description (Continued)
BIT
6
FIELD NAME
isoChannel38
isoChannel37
isoChannel36
isoChannel35
isoChannel34
isoChannel33
isoChannel32
TYPE
RSC
RSC
RSC
RSC
RSC
RSC
RSC
DESCRIPTION
Whenbit6issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber38.
Whenbit5issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber37.
Whenbit4issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber36.
Whenbit3issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber35.
Whenbit2issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber34.
Whenbit1issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber33.
Whenbit0issetto1,theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber32.
5
4
3
2
1
0
4.20 Isochronous Receive Channel Mask Low Register
The isochronous receive channel mask low set/clear register enables packet receives from the lower 32 isochronous
data channels. See Table 4–14 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive channel mask low
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Isochronous receive channel mask low
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous receive channel mask low
78h
7Ch
set register
clear register
Type:
Default:
Read/Set/Clear
XXXX XXXXh
Table 4–14. Isochronous Receive Channel Mask Low Register Description
BIT
31
FIELD NAME
isoChannel31
isoChannel30
isoChanneln
isoChannel1
isoChannel0
TYPE
DESCRIPTION
RSC Whenbit 31 issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber31.
RSC Whenbit30issetto1, theTSB43AB23deviceisenabledtoreceivefromisochronouschannelnumber30.
RSC Bits 29 through 2 (isoChanneln, where n = 29, 28, 27, …, 2) follow the same pattern as bits 31 and 30.
RSC When bit 1 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 1.
RSC When bit 0 is set to 1, the TSB43AB23 device is enabled to receive from isochronous channel number 0.
30
29–2
1
0
4–17
4.21 Interrupt Event Register
The interrupt event set/clear register reflects the state of the various TSB43AB23 interrupt sources. The interrupt bits
are set to 1 by an asserting edge of the corresponding interrupt signal or by writing a 1 in the corresponding bit in the
set register. The only mechanism to clear a bit in this register is to write a 1 to the corresponding bit in the clear register.
This register is fully compliant with the 1394OpenHostControllerInterfaceSpecification, andtheTSB43AB23device
adds a vendor-specific interrupt function to bit 30. When the interrupt event register is read, the return value is the
bit-wise AND function of the interrupt event and interrupt mask registers. See Table 4–15 for a complete description
of the register contents.
Bit
31
30
29
28
27
26
25
24
Interrupt event
RSCU RSCU RSCU RSCU RSCU RSCU RSCU RSCU RSCU RSCU RSCU RSCU
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
R
0
RSC RSC
R
0
X
0
0
X
X
X
X
X
X
X
X
0
X
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Interrupt event
RSCU
0
R
0
R
0
R
0
R
0
R
0
RSCU RSCU
RU
X
RU
X
RSCU RSCU RSCU RSCU RSCU RSCU
X
X
X
X
X
X
X
X
Register:
Offset:
Interrupt event
80h
84h
set register
clear register [returns the content of the interrupt event register bit-wise ANDed with
the interrupt mask register when read]
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read/update, read-only
XXXX 0XXXh
Table 4–15. Interrupt Event Register Description
BIT
31
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bit 31 returns 0 when read.
30
vendorSpecific
RSC
This vendor-specific interrupt event is reported when either of the general-purpose interrupts are
asserted. The general-purpose interrupts are enabled by setting the corresponding bits INT_3EN
and INT_2EN (bits 31 and 23, respectively) to 1 in the GPIO control register at offset FCh in the PCI
configuration space (see Section 3.24, GPIO Control Register).
29
28
27
SoftInterrupt
RSVD
RSC
R
Bit 29 is used by software to generate a TSB43AB23 interrupt for its own use.
Reserved. Bit 28 returns 0 when read.
ack_tardy
RSCU Bit 27 is set to 1 when bit 29 (AckTardyEnable) in the host controller control register at OHCI offset
50h/54h (see Section 4.16, Host Controller Control Register) is set to 1 and any of the following
conditions occur:
a. Data is present in a receive FIFO that is to be delivered to the host.
b. The physical response unit is busy processing requests or sending responses.
c. The TSB43AB23 device sent an ack_tardy acknowledgment.
26
25
phyRegRcvd
cycleTooLong
RSCU The TSB43AB23 device has received a PHY register data byte which can be read from bits 23–16
in the PHY layer control register at OHCI offset ECh (see Section 4.33, PHY Layer Control Register).
RSCU If bit 21 (cycleMaster) in the link control register at OHCI offset E0h/E4h (see Section 4.31, Link
Control Register) is set to 1, this indicates that over 125 µs has elapsed between the start of sending
a cycle start packet and the end of a subaction gap. Bit 21 (cycleMaster) in the link control register
is cleared by this event.
24
23
unrecoverableError RSCU This event occurs when the TSB43AB23 device encounters any error that forces it to stop operations
on any or all of its subunits, for example, when a DMA context sets its dead bit to 1. While bit 24 is
set to 1, all normal interrupts for the context(s) that caused this interrupt are blocked from being set
to 1.
cycleInconsistent
RSCU A cycle start was received that had values for the cycleSeconds and cycleCount fields that are
different from the values in bits 31–25 (cycleSeconds field) and bits 24–12 (cycleCount field) in the
isochronous cycle timer register at OHCI offset F0h (see Section 4.34, Isochronous Cycle Timer
Register).
4–18
Table 4–15. Interrupt Event Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
22
cycleLost
RSCU A lost cycle is indicated when no cycle_start packet is sent or received between two successive
cycleSynch events. A lost cycle can be predicted when a cycle_start packet does not immediately
follow the first subaction gap after the cycleSynch event or if an arbitration reset gap is detected after
a cycleSynch event without an intervening cycle start. Bit 22 may be set to 1 either when a lost cycle
occurs or when logic predicts that one will occur.
th
21
20
cycle64Seconds
cycleSynch
RSCU Indicates that the 7 bit of the cycle second counter has changed.
RSCU Indicates that a new isochronous cycle has started. Bit 20 is set to 1 when the low-order bit of the
cycle count toggles.
19
18
phy
RSCU Indicates that the PHY layer requests an interrupt through a status transfer.
regAccessFail
RSCU Indicates that a TSB43AB23 register access has failed due to a missing SCLK clock signal from the
PHY layer. When a register access fails, bit 18 is set to 1 before the next register access.
17
16
busReset
RSCU Indicates that the PHY layer has entered bus reset mode.
selfIDcomplete
RSCU A self-ID packet stream has been received. It is generated at the end of the bus initialization process.
Bit 16 is turned off simultaneously when bit 17 (busReset) is turned on.
15
selfIDcomplete2
RSCU Secondaryindicationoftheendofaself-IDpacketstream. Bit15issetto1bytheTSB43AB23device
when it sets bit 16 (selfIDcomplete), and retains the state, independent of bit 17 (busReset).
14–10
RSVD
R
Reserved. Bits 14–10 return 0s when read.
9
lockRespErr
RSCU Indicates that the TSB43AB23 device sent a lock response for a lock request to a serial bus register,
but did not receive an ack_complete.
8
7
postedWriteErr
isochRx
RSCU Indicates that a host bus error occurred while the TSB43AB23 device was trying to write a 1394 write
request, which had already been given an ack_complete, into system memory.
RU
RU
Isochronous receive DMA interrupt. Indicates that one or more isochronous receive contexts have
generated an interrupt. This is not a latched event; it is the logical OR of all bits in the isochronous
receive interrupt event register at OHCI offset A0h/A4h (see Section 4.25, Isochronous Receive
Interrupt Event Register) and isochronous receive interrupt mask register at OHCI offset A8h/ACh
(see Section 4.26, Isochronous Receive Interrupt Mask Register). The isochronous receive interrupt
event register indicates which contexts have been interrupted.
6
isochTx
Isochronous transmit DMA interrupt. Indicates that one or more isochronous transmit contexts have
generated an interrupt. This is not a latched event; it is the logical OR of all bits in the isochronous
transmit interrupt event register at OHCI offset 90h/94h (see Section 4.23, Isochronous Transmit
Interrupt Event Register) and isochronous transmit interrupt mask register at OHCI offset 98h/9Ch
(see Section 4.24, Isochronous Transmit Interrupt Mask Register). The isochronous transmit
interrupt event register indicates which contexts have been interrupted.
5
4
3
2
1
0
RSPkt
RQPkt
RSCU Indicates that a packet was sent to an asynchronous receive response context buffer and the
descriptor xferStatus and resCount fields have been updated.
RSCU Indicates that a packet was sent to an asynchronous receive request context buffer and the
descriptor xferStatus and resCount fields have been updated.
ARRS
RSCU Asynchronous receive response DMA interrupt. Bit 3 is conditionally set to 1 upon completion of an
ARRS DMA context command descriptor.
ARRQ
RSCU Asynchronous receive request DMA interrupt. Bit 2 is conditionally set to 1 upon completion of an
ARRQ DMA context command descriptor.
respTxComplete
reqTxComplete
RSCU Asynchronous response transmit DMA interrupt. Bit 1 is conditionally set to 1 upon completion of an
ATRS DMA command.
RSCU Asynchronous request transmit DMA interrupt. Bit 0 is conditionally set to 1 upon completion of an
ATRQ DMA command.
4–19
4.22 Interrupt Mask Register
The interrupt mask set/clear register enables the various TSB43AB23 interrupt sources. Reads from either the set
register or the clear register always return the contents of the interrupt mask register. In all cases except
masterIntEnable (bit 31) and vendorSpecific (bit 30), the enables for each interrupt event align with the interrupt event
register bits detailed in Table 4–15.
This register is fully compliant with the 1394 Open Host Controller Interface Specification and the TSB43AB23 device
adds an interrupt function to bit 30. See Table 4–16 for a complete description of bits 31 and 30.
Bit
31
30
29
28
27
26
25
24
Interrupt mask
RSC RSC RSC RSC RSC RSC RSC RSC RSC RSC RSC RSC
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
RSCU RSC RSC
R
0
X
X
0
0
X
X
X
X
X
X
X
X
0
X
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Interrupt mask
RSC RSC RSC RSC RSC RSC RSC RSC RSC RSC
RSC
0
R
0
R
0
R
0
R
0
R
0
X
X
X
X
X
X
X
X
X
X
Register:
Offset:
Interrupt mask
88h
8Ch
set register
clear register
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read/update, read-only
XXXX 0XXXh
Table 4–16. Interrupt Mask Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
masterIntEnable
RSCU Master interrupt enable. If bit 31 is set to 1, external interrupts are generated in accordance with the
interrupt mask register. If this bit is cleared, external interrupts are not generated regardless of the
interrupt mask register settings.
30
29
VendorSpecific
SoftInterrupt
RSC When this bit and bit 30 (vendorSpecific) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this vendor-specific interrupt mask enables
interrupt generation.
RSC When this bit and bit 29 (SoftInterrupt) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this soft-interrupt mask enables interrupt
generation.
28
27
RSVD
R
Reserved. Bit 28 returns 0 when read.
ack_tardy
RSC When this bit and bit 27 (ack_tardy) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this acknowledge-tardy interrupt mask enables
interrupt generation.
26
25
24
23
22
phyRegRcvd
cycleTooLong
unrecoverableError
cycleInconsistent
cycleLost
RSC When this bit and bit 26 (phyRegRcvd) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this PHY-register interrupt mask enables interrupt
generation.
RSC When this bit and bit 25 (cycleTooLong) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, InterruptEventRegister)aresetto1, thiscycle-too-longinterruptmaskenablesinterrupt
generation.
RSC Whenthisbitandbit24(unrecoverableError)intheinterrupteventregisteratOHCIoffset80h/84h(see
Section 4.21, Interrupt Event Register) are set to 1, this unrecoverable-error interrupt mask enables
interrupt generation.
RSC When this bit and bit 23 (cycleInconsistent) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this inconsistent-cycle interrupt mask enables
interrupt generation.
RSC When this bit and bit 22 (cycleLost) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this lost-cycle interrupt mask enables interrupt
generation.
4–20
Table 4–16. Interrupt Mask Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
21
cycle64Seconds
RSC When this bit and bit 21 (cycle64Seconds) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this 64-second-cycle interrupt mask enables
interrupt generation.
20
19
18
17
16
15
cycleSynch
phy
RSC When this bit and bit 20 (cycleSynch) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this isochronous-cycle interrupt mask enables
interrupt generation.
RSC When this bit and bit 19 (phy) in the interrupt event register at OHCI offset 80h/84h (see Section 4.21,
Interrupt Event Register) are set to 1, this PHY-status-transfer interrupt mask enables interrupt
generation.
regAccessFail
busReset
RSC When this bit and bit 18 (regAccessFail) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this register-access-failed interrupt mask enables
interrupt generation.
RSC When this bit and bit 17 (busReset) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this bus-reset interrupt mask enables interrupt
generation.
selfIDcomplete
selfIDcomplete2
RSC When this bit and bit 16 (selfIDcomplete) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this self-ID-complete interrupt mask enables
interrupt generation.
RSC When this bit and bit 15 (selfIDcomplete2) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this second-self-ID-complete interrupt mask
enables interrupt generation.
14–10
RSVD
R
Reserved. Bits 14–10 return 0s when read.
9
lockRespErr
RSC When this bit and bit 9 (lockRespErr) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this lock-response-error interrupt mask enables
interrupt generation.
8
7
6
5
4
3
2
1
0
postedWriteErr
isochRx
RSC When this bit and bit 8 (postedWriteErr) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this posted-write-error interrupt mask enables
interrupt generation.
RSC When this bit and bit 7 (isochRx) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this isochronous-receive-DMA interrupt mask
enables interrupt generation.
isochTx
RSC When this bit and bit 6 (isochTx) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this isochronous-transmit-DMA interrupt mask
enables interrupt generation.
RSPkt
RSC Whenthis bit and bit 5 (RSPkt) in the interrupt event register at OHCI offset 80h/84h (see Section 4.21,
Interrupt Event Register) are set to 1, this receive-response-packet interrupt mask enables interrupt
generation.
RQPkt
RSC Whenthis bit and bit 4 (RQPkt)intheinterrupteventregisteratOHCIoffset 80h/84h (see Section 4.21,
Interrupt Event Register) are set to 1, this receive-request-packet interrupt mask enables interrupt
generation.
ARRS
RSC When this bit and bit 3 (ARRS) in the interrupt event register at OHCI offset 80h/84h (see Section 4.21,
Interrupt Event Register) are set to 1, this asynchronous-receive-response-DMA interrupt mask
enables interrupt generation.
ARRQ
RSC Whenthis bit and bit 2 (ARRQ) in the interrupt event register at OHCI offset 80h/84h (see Section 4.21,
InterruptEventRegister) are setto1, thisasynchronous-receive-request-DMAinterruptmaskenables
interrupt generation.
respTxComplete
reqTxComplete
RSC When this bit and bit 1 (respTxComplete) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this response-transmit-complete interrupt mask
enables interrupt generation.
RSC When this bit and bit 0 (reqTxComplete) in the interrupt event register at OHCI offset 80h/84h (see
Section 4.21, Interrupt Event Register) are set to 1, this request-transmit-complete interrupt mask
enables interrupt generation.
4–21
4.23 Isochronous Transmit Interrupt Event Register
The isochronous transmit interrupt event set/clear register reflects the interrupt state of the isochronous transmit
contexts. An interrupt is generated on behalf of an isochronous transmit context if an OUTPUT_LAST* command
completes and its interrupt bits are set to 1. Upon determining that the isochTx (bit 6) interrupt has occurred in the
interrupt event register at OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register), software can check this
register to determine which context(s) caused the interrupt. The interrupt bits are set to 1 by an asserting edge of the
corresponding interrupt signal, or by writing a 1 in the corresponding bit in the set register. The only mechanism to
clear a bit in this register is to write a 1 to the corresponding bit in the clear register. See Table 4–17 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous transmit interrupt event
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Isochronous transmit interrupt event
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous transmit interrupt event
90h
94h
set register
clear register [returns the contents of the isochronous transmit interrupt event
register bit-wise ANDed with the isochronous transmit interrupt mask register
when read]
Type:
Default:
Read/Set/Clear, read-only
0000 00XXh
Table 4–17. Isochronous Transmit Interrupt Event Register Description
BIT
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
31–8
Reserved. Bits 31–8 return 0s when read.
7
6
5
4
3
2
1
0
isoXmit7
isoXmit6
isoXmit5
isoXmit4
isoXmit3
isoXmit2
isoXmit1
isoXmit0
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
Isochronous transmit channel 7 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 6 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 5 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 4 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 3 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 2 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 1 caused the interrupt event register bit 6 (isochTx) interrupt.
Isochronous transmit channel 0 caused the interrupt event register bit 6 (isochTx) interrupt.
4–22
4.24 Isochronous Transmit Interrupt Mask Register
The isochronous transmit interrupt mask set/clear register enables the isochTx interrupt source on a per-channel
basis. Reads from either the set register or the clear register always return the contents of the isochronous transmit
interrupt mask register. In all cases the enables for each interrupt event align with the isochronous transmit interrupt
event register bits detailed in Table 4–17.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous transmit interrupt mask
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Isochronous transmit interrupt mask
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous transmit interrupt mask
98h
9Ch
set register
clear register
Type:
Default:
Read/Set/Clear, read-only
0000 00XXh
4.25 Isochronous Receive Interrupt Event Register
The isochronous receive interrupt event set/clear register reflects the interrupt state of the isochronous receive
contexts. An interrupt is generated on behalf of an isochronous receive context if an INPUT_* command completes
and its interrupt bits are set to 1. Upon determining that the isochRx (bit 7) interrupt in the interrupt event register at
OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register) has occurred, software can check this register to
determine which context(s) caused the interrupt. The interrupt bits are set to 1 by an asserting edge of the
corresponding interrupt signal or by writing a 1 in the corresponding bit in the set register. The only mechanism to
clear a bit in this register is to write a 1 to the corresponding bit in the clear register. See Table 4–18 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive interrupt event
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Isochronous receive interrupt event
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous receive interrupt event
A0h
A4h
set register
clear register [returns the contents of isochronous receive interrupt event register
bit-wise ANDed with the isochronous receive mask register when read]
Type:
Default:
Read/Set/Clear, read-only
0000 000Xh
Table 4–18. Isochronous Receive Interrupt Event Register Description
BIT
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
31–4
Reserved. Bits 31–4 return 0s when read.
3
2
1
0
isoRecv3
isoRecv2
isoRecv1
isoRecv0
RSC
RSC
RSC
RSC
Isochronous receive channel 3 caused the interrupt event register bit 7 (isochRx) interrupt.
Isochronous receive channel 2 caused the interrupt event register bit 7 (isochRx) interrupt.
Isochronous receive channel 1 caused the interrupt event register bit 7 (isochRx) interrupt.
Isochronous receive channel 0 caused the interrupt event register bit 7 (isochRx) interrupt.
4–23
4.26 Isochronous Receive Interrupt Mask Register
The isochronous receive interrupt mask set/clear register enables the isochRx interrupt source on a per-channel
basis. Reads from either the set register or the clear register always return the contents of the isochronous receive
interrupt mask register. In all cases the enables for each interrupt event align with the isochronous receive interrupt
event register bits detailed in Table 4–18.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive interrupt mask
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Isochronous receive interrupt mask
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
RSC
X
RSC
X
RSC
X
RSC
X
Register:
Offset:
Isochronous receive interrupt mask
A8h
ACh
set register
clear register
Type:
Default:
Read/Set/Clear, read-only
0000 000Xh
4.27 Initial Bandwidth Available Register
The initial bandwidth available register value is loaded into the corresponding bus management CSR register on a
system (hardware) or software reset. See Table 4–19 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Initial bandwidth available
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Initial bandwidth available
R
0
R
0
R
0
R/W
1
R/W
0
R/W
0
R/W
1
R/W
1
R/W
0
R/W
0
R/W
1
R/W
1
R/W
0
R/W
0
R/W
1
R/W
1
Register:
Offset:
Type:
Initial bandwidth available
B0h
Read-only, read/write
0000 1333h
Default:
Table 4–19. Initial Bandwidth Available Register Description
BIT
31–13
12–0
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bits 31–13 return 0s when read.
InitBWAvailable
R/W
This field is reset to 1333h on a system (hardware) or software reset, and is not affected by a 1394
bus reset. The value of this field is loaded into the BANDWIDTH_AVAILABLE CSR register upon
a G_RST, PCI_RST, or a 1394 bus reset.
4–24
4.28 Initial Channels Available High Register
The initial channels available high register value is loaded into the corresponding bus management CSR register on
a system (hardware) or software reset. See Table 4–20 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Initial channels available high
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Initial channels available high
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
Register:
Offset:
Type:
Initial channels available high
B4h
Read/Write
FFFF FFFFh
Default:
Table 4–20. Initial Channels Available High Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–0
InitChanAvailHi
R/W
This field is reset to FFFF_FFFFh on a system (hardware) or software reset, and is not affected by
a 1394 bus reset. The value of this field is loaded into the CHANNELS_AVAILABLE_HI CSR
register upon a G_RST, PCI_RST, or a 1394 bus reset.
4.29 Initial Channels Available Low Register
The initial channels available low register value is loaded into the corresponding bus management CSR register on
a system (hardware) or software reset. See Table 4–21 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Initial channels available low
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Initial channels available low
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
R/W
1
Register:
Offset:
Type:
Initial channels available low
B8h
Read/Write
FFFF FFFFh
Default:
Table 4–21. Initial Channels Available Low Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31–0
InitChanAvailLo
R/W
This field is reset to FFFF_FFFFh on a system (hardware) or software reset, and is not affected by
a 1394 bus reset. The value of this field is loaded into the CHANNELS_AVAILABLE_LO CSR
register upon a G_RST, PCI_RST, or a 1394 bus reset.
4–25
4.30 Fairness Control Register
The fairness control register provides a mechanism by which software can direct the host controller to transmit
multiple asynchronous requests during a fairness interval. See Table 4–22 for a complete description of the register
contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Fairness control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Fairness control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Fairness control
DCh
Read-only
0000 0000h
Default:
Table 4–22. Fairness Control Register Description
BIT
31–8
7–0
FIELD NAME
RSVD
TYPE
DESCRIPTION
Reserved. Bits 31–8 return 0s when read.
R
pri_req
R/W
This field specifies the maximum number of priority arbitration requests for asynchronous request
packets that the link is permitted to make of the PHY layer during a fairness interval.
4–26
4.31 Link Control Register
The link control set/clear register provides the control flags that enable and configure the link core protocol portions
of the TSB43AB23 device. It contains controls for the receiver and cycle timer. See Table 4–23 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Link control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
RSC RSCU RSC
R
0
3
R
0
2
R
0
1
R
0
0
X
X
X
15
14
13
12
11
10
6
5
4
Name
Type
Default
Link control
R
0
R
0
R
0
R
0
R
0
RSC
X
RSC
X
R
0
R
0
RS
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Link control
E0h
E4h
set register
clear register
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read-only
00X0 0X00h
Table 4–23. Link Control Register Description
BIT
31–23
22
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bits 31–23 return 0s when read.
cycleSource
RSC
When bit 22 is set to 1, the cycle timer uses an external source (CYCLEIN) to determine when to roll
over the cycle timer. When this bit is cleared, the cycle timer rolls over when the timer reaches
3072 cycles of the 24.576-MHz clock (125 µs).
21
cycleMaster
RSCU When bit 21 is set to 1, the TSB43AB23 device is root and it generates a cycle start packet every time
the cycle timer rolls over, based on the setting of bit 22 (cycleSource). When bit 21 is cleared, the
iOHCI-Lynx accepts received cycle start packets to maintain synchronization with the node which
is sending them. Bit 21 is automatically cleared when bit 25 (cycleTooLong) in the interrupt event
register at OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register) is set to 1. Bit 21 cannot
be set to 1 until bit 25 (cycleTooLong) is cleared.
20
CycleTimerEnable
RSC
When bit 20 is set to 1, the cycle timer offset counts cycles of the 24.576-MHz clock and rolls over
at the appropriate time, based on the settings of the above bits. When this bit is cleared, the cycle
timer offset does not count.
19–11
RSVD
R
Reserved. Bits 19–11 return 0s when read.
10
RcvPhyPkt
RSC
When bit 10 is set to 1, the receiver accepts incoming PHY packets into the AR request context if
the AR request context is enabled. This bit does not control receipt of self-identification packets.
9
RcvSelfID
RSC
When bit 9 is set to 1, the receiver accepts incoming self-identification packets. Before setting this
bit to 1, software must ensure that the self-ID buffer pointer register contains a valid address.
8–7
RSVD
R
Reserved. Bits 8 and 7 return 0s when read.
6
tag1SyncFilterLock
RS
When bit 6 is set to 1, bit 6 (tag1SyncFilter) in the isochronous receive context match register (see
Section 4.46, Isochronous Receive Context Match Register) is set to 1 for all isochronous receive
contexts. When bit 6 is cleared, bit 6 (tag1SyncFilter) in the isochronous receive context match
register has read/write access. This bit is cleared when G_RST is asserted.
5–0
RSVD
R
Reserved. Bits 5–0 return 0s when read.
4–27
4.32 Node Identification Register
The node identification register contains the address of the node on which the iOHCI-Lynx chip resides and
indicates the valid node number status. The 16-bit combination of the busNumber field (bits 15–6) and the
NodeNumber field (bits 5–0) is referred to as the node ID. See Table 4–24 for a complete description of the register
contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Node identification
RU
0
RU
0
R
0
R
0
RU
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Node identification
RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
1
1
1
1
1
1
1
1
1
1
Register:
Offset:
Type:
Node identification
E8h
Read/Write/Update, read/update, read-only
0000 FFXXh
Default:
Table 4–24. Node Identification Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
iDValid
RU
Bit 31 indicates whether or not the TSB43AB23 device has a valid node number. It is cleared when a
1394 bus reset is detected and set to 1 when the TSB43AB23 device receives a new node number
from its PHY layer.
30
root
RSVD
RU
R
Bit 30 is set to 1 during the bus reset process if the attached PHY layer is root.
Reserved. Bits 29 and 28 return 0s when read.
29–28
27
CPS
RU
R
Bit 27 is set to 1 if the PHY layer is reporting that cable power status is OK.
Reserved. Bits 26–16 return 0s when read.
26–16
15–6
RSVD
busNumber
RWU
This field identifies the specific 1394 bus the TSB43AB23 device belongs to when multiple
1394-compatible buses are connected via a bridge.
5–0
NodeNumber
RU
This field is the physical node number established by the PHY layer during self-identification. It is
automaticallyset to the value received from the PHY layer after the self-identification phase. If the PHY
layersetsthenodeNumberto63, softwaremustnotsetbit15(run)intheasynchronouscontextcontrol
register (see Section 4.40, Asynchronous Context Control Register) for either of the AT DMA contexts.
4–28
4.33 PHY Layer Control Register
The PHY layer control register reads from or writes to a PHY register. See Table 4–25 for a complete description of
the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
PHY layer control
RU
0
R
0
R
0
R
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
RU
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
PHY layer control
RWU RWU
R
0
R
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
0
Register:
Offset:
Type:
PHY layer control
ECh
Read/Write/Update, Read/Write, Read/Update, Read-only
0000 0000h
Default:
Table 4–25. PHY Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
rdDone
RU
Bit 31 is cleared to 0 by the TSB43AB23 device when either bit 15 (rdReg) or bit 14 (wrReg) is set to
1. This bit is set to 1 when a register transfer is received from the PHY layer.
30–28
27–24
23–16
15
RSVD
rdAddr
rdData
rdReg
R
Reserved. Bits 30–28 return 0s when read.
RU
This field is the address of the register most recently received from the PHY layer.
This field is the contents of a PHY register that has been read.
RU
RWU
Bit 15 is set to 1 by software to initiate a read request to a PHY register and is cleared by hardware
when the request has been sent. Bits 14 (wrReg) and 15 (rdReg) must not both be set to 1
simultaneously.
14
wrReg
RWU
Bit 14 is set to 1 by software to initiate a write request to a PHY register and is cleared by hardware
when the request has been sent. Bits 14 (wrReg) and 15 (rdReg) must not both be set to 1
simultaneously.
13–12
11–8
7–0
RSVD
regAddr
wrData
R
Reserved. Bits 13 and 12 return 0s when read.
R/W
R/W
This field is the address of the PHY register to be written or read.
This field is the data to be written to a PHY register and is ignored for reads.
4–29
4.34 Isochronous Cycle Timer Register
The isochronous cycle timer register indicates the current cycle number and offset. When the TSB43AB23 device
is cycle master, this register is transmitted with the cycle start message. When the TSB43AB23 device is not cycle
master, this register is loaded with the data field in an incoming cycle start. In the event that the cycle start message
is not received, the fields can continue incrementing on their own (if programmed) to maintain a local time reference.
See Table 4–26 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
Isochronous cycle timer
RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Isochronous cycle timer
RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Register:
Offset:
Type:
Isochronous cycle timer
F0h
Read/Write/Update
XXXX XXXXh
Default:
Table 4–26. Isochronous Cycle Timer Register Description
BIT
FIELD NAME
cycleSeconds
cycleCount
TYPE
RWU
RWU
RWU
DESCRIPTION
31–25
24–12
11–0
This field counts seconds [rollovers from bits 24–12 (cycleCount field)] modulo 128.
This field counts cycles [rollovers from bits 11–0 (cycleOffset field)] modulo 8000.
cycleOffset
This field counts 24.576-MHz clocks modulo 3072, that is, 125 µs. If an external 8-kHz clock
configuration is being used, this field must be cleared to 0s at each tick of the external clock.
4–30
4.35 Asynchronous Request Filter High Register
The asynchronous request filter high set/clear register enables asynchronous receive requests on a per-node basis,
and handles the upper node IDs. When a packet is destined for either the physical request context or the ARRQ
context, thesourcenodeIDisexamined. IfthebitcorrespondingtothenodeIDisnotsetto1inthisregister, thepacket
is not acknowledged and the request is not queued. The node ID comparison is done if the source node is on the same
bus as the TSB43AB23 device. Nonlocal bus-sourced packets are not acknowledged unless bit 31 in this register
is set to 1. See Table 4–27 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Asynchronous request filter high
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Asynchronous request filter high
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
Register:
Offset:
Asynchronous request filter high
100h set register
104h clear register
Read/Set/Clear
Type:
Default:
0000 0000h
Table 4–27. Asynchronous Request Filter High Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
asynReqAllBuses
asynReqResource62
asynReqResource61
asynReqResource60
asynReqResource59
asynReqResource58
asynReqResource57
asynReqResource56
asynReqResource55
asynReqResource54
asynReqResource53
asynReqResource52
asynReqResource51
RSC
If bit 31 is set to 1, all asynchronous requests received by the TSB43AB23 device from nonlocal
bus nodes are accepted.
30
29
28
27
26
25
24
23
22
21
20
19
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
If bit 30 is set to 1 for local bus node number 62, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 29 is set to 1 for local bus node number 61, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 28 is set to 1 for local bus node number 60, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 27 is set to 1 for local bus node number 59, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 26 is set to 1 for local bus node number 58, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 25 is set to 1 for local bus node number 57, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 24 is set to 1 for local bus node number 56, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 23 is set to 1 for local bus node number 55, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 22 is set to 1 for local bus node number 54, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 21 is set to 1 for local bus node number 53, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 20 is set to 1 for local bus node number 52, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 19 is set to 1 for local bus node number 51, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
4–31
Table 4–27. Asynchronous Request Filter High Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
18
asynReqResource50
RSC
If bit 18 is set to 1 for local bus node number 50, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
17
16
15
14
13
12
11
10
9
asynReqResource49
asynReqResource48
asynReqResource47
asynReqResource46
asynReqResource45
asynReqResource44
asynReqResource43
asynReqResource42
asynReqResource41
asynReqResource40
asynReqResource39
asynReqResource38
asynReqResource37
asynReqResource36
asynReqResource35
asynReqResource34
asynReqResource33
asynReqResource32
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
If bit 17 is set to 1 for local bus node number 49, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 16 is set to 1 for local bus node number 48, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 15 is set to 1 for local bus node number 47, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 14 is set to 1 for local bus node number 46, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 13 is set to 1 for local bus node number 45, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 12 is set to 1 for local bus node number 44, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 11 is set to 1 for local bus node number 43, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 10 is set to 1 for local bus node number 42, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
If bit 9 is set to 1 for local busnodenumber41, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
8
If bit 8 is set to 1 for local busnodenumber40, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
7
If bit 7 is set to 1 for local busnodenumber39, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
6
If bit 6 is set to 1 for local busnodenumber38, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
5
If bit 5 is set to 1 for local busnodenumber37, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
4
If bit 4 is set to 1 for local busnodenumber36, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
3
If bit 3 is set to 1 for local busnodenumber35, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
2
If bit 2 is set to 1 for local busnodenumber34, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
1
If bit 1 is set to 1 for local busnodenumber33, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
0
If bit 0 is set to 1 for local busnodenumber32, asynchronousrequestsreceivedbytheTSB43AB23
device from that node are accepted.
4–32
4.36 Asynchronous Request Filter Low Register
The asynchronous request filter low set/clear register enables asynchronous receive requests on a per-node basis,
and handles the lower node IDs. Other than filtering different node IDs, this register behaves identically to the
asynchronous request filter high register. See Table 4–28 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Asynchronous request filter low
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Asynchronous request filter low
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
Register:
Offset:
Asynchronous request filter low
108h set register
10Ch clear register
Read/Set/Clear
Type:
Default:
0000 0000h
Table 4–28. Asynchronous Request Filter Low Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
asynReqResource31
asynReqResource30
asynReqResourcen
asynReqResource1
asynReqResource0
RSC
If bit 31 is set to 1 for local bus node number 31, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
30
29–2
1
RSC
RSC
RSC
RSC
If bit 30 is set to 1 for local bus node number 30, asynchronous requests received by the
TSB43AB23 device from that node are accepted.
Bits 29 through 2 (asynReqResourcen, where n = 29, 28, 27, …, 2) follow the same pattern as
bits 31 and 30.
If bit 1 is set to 1 for local bus node number 1, asynchronous requests received by the TSB43AB23
device from that node are accepted.
0
If bit 0 is set to 1 for local bus node number 0, asynchronous requests received by the TSB43AB23
device from that node are accepted.
4–33
4.37 Physical Request Filter High Register
The physical request filter high set/clear register enables physical receive requests on a per-node basis, and handles
the upper node IDs. When a packet is destined for the physical request context, and the node ID has been compared
against the ARRQ registers, then the comparison is done again with this register. If the bit corresponding to the node
ID is not set to 1 in this register, the request is handled by the ARRQ context instead of the physical request context.
The node ID comparison is done if the source node is on the same bus as the TSB43AB23 device. Nonlocal
bus-sourced packets are not acknowledged unless bit 31 in this register is set to 1. See Table 4–29 for a complete
description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Physical request filter high
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Physical request filter high
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
Register:
Offset:
Physical request filter high
110h set register
114h clear register
Read/Set/Clear
Type:
Default:
0000 0000h
Table 4–29. Physical Request Filter High Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
physReqAllBusses
physReqResource62
physReqResource61
physReqResource60
physReqResource59
physReqResource58
physReqResource57
physReqResource56
physReqResource55
physReqResource54
physReqResource53
physReqResource52
physReqResource51
RSC
If bit 31 is set to 1, all asynchronous requests received by the TSB43AB23 device from nonlocal
bus nodes are accepted. Bit 31 is not cleared by a PCI_RST.
30
29
28
27
26
25
24
23
22
21
20
19
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
If bit 30 is set to 1 for local bus node number 62, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 29 is set to 1 for local bus node number 61, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 28 is set to 1 for local bus node number 60, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 27 is set to 1 for local bus node number 59, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 26 is set to 1 for local bus node number 58, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 25 is set to 1 for local bus node number 57, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 24 is set to 1 for local bus node number 56, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 23 is set to 1 for local bus node number 55, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 22 is set to 1 for local bus node number 54, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 21 is set to 1 for local bus node number 53, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 20 is set to 1 for local bus node number 52, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 19 is set to 1 for local bus node number 51, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
4–34
Table 4–29. Physical Request Filter High Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
18
physReqResource50
RSC
If bit 18 is set to 1 for local bus node number 50, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
17
16
15
14
13
12
11
10
9
physReqResource49
physReqResource48
physReqResource47
physReqResource46
physReqResource45
physReqResource44
physReqResource43
physReqResource42
physReqResource41
physReqResource40
physReqResource39
physReqResource38
physReqResource37
physReqResource36
physReqResource35
physReqResource34
physReqResource33
physReqResource32
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
If bit 17 is set to 1 for local bus node number 49, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 16 is set to 1 for local bus node number 48, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 15 is set to 1 for local bus node number 47, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 14 is set to 1 for local bus node number 46, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 13 is set to 1 for local bus node number 45, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 12 is set to 1 for local bus node number 44, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 11 is set to 1 for local bus node number 43, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 10 is set to 1 for local bus node number 42, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
If bit 9 is set to 1 for local bus node number 41, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
8
If bit 8 is set to 1 for local bus node number 40, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
7
If bit 7 is set to 1 for local bus node number 39, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
6
If bit 6 is set to 1 for local bus node number 38, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
5
If bit 5 is set to 1 for local bus node number 37, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
4
If bit 4 is set to 1 for local bus node number 36, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
3
If bit 3 is set to 1 for local bus node number 35, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
2
If bit 2 is set to 1 for local bus node number 34, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
1
If bit 1 is set to 1 for local bus node number 33, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
0
If bit 0 is set to 1 for local bus node number 32, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
4–35
4.38 Physical Request Filter Low Register
The physical request filter low set/clear register enables physical receive requests on a per-node basis, and handles
the lower node IDs. When a packet is destined for the physical request context and the node ID has been compared
against the asynchronous request filter registers, then the node ID comparison is done again with this register. If the
bit corresponding to the node ID is not set to 1 in this register, the request is handled by the asynchronous request
context instead of the physical request context. See Table 4–30 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Physical request filter low
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
RSC
0
0
0
0
0
0
0
0
0
0
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Physical request filter low
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
RSC
0
Register:
Offset:
Physical request filter low
118h set register
11Ch clear register
Read/Set/Clear
Type:
Default:
0000 0000h
Table 4–30. Physical Request Filter Low Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
physReqResource31
physReqResource30
physReqResourcen
physReqResource1
physReqResource0
RSC
If bit 31 is set to 1 for local bus node number 31, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
30
29–2
1
RSC
RSC
RSC
RSC
If bit 30 is set to 1 for local bus node number 30, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
Bits 29 through 2 (physReqResourcen, where n = 29, 28, 27, …, 2) follow the same pattern as
bits 31 and 30.
If bit 1 is set to 1 for local bus node number 1, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
0
If bit 0 is set to 1 for local bus node number 0, physical requests received by the TSB43AB23
device from that node are handled through the physical request context.
4.39 Physical Upper Bound Register (Optional Register)
The physical upper bound register is an optional register and is not implemented. This register returns all 0s when
read.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Physical upper bound
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Physical upper bound
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
Register:
Offset:
Type:
Physical upper bound
120h
Read-only
Default:
0000 0000h
4–36
4.40 Asynchronous Context Control Register
The asynchronous context control set/clear register controls the state and indicates status of the DMA context. See
Table 4–31 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Asynchronous context control
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Asynchronous context control
RSCU
0
R
0
R
0
RSU
X
RU
0
RU
0
R
0
R
0
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
Register:
Offset:
Asynchronous context control
180h set register [ATRQ]
184h clear register [ATRQ]
1A0h set register [ATRS]
1A4h clear register [ATRS]
1C0h set register [ARRQ]
1C4h clear register [ARRQ]
1E0h set register [ARRS]
1E4h clear register [ARRS]
Type:
Default:
Read/Set/Clear/Update, read/set/update, read/update, read-only
0000 X0XXh
Table 4–31. Asynchronous Context Control Register Description
BIT
31–16
15
FIELD NAME
RSVD
TYPE
DESCRIPTION
Reserved. Bits 31–16 return 0s when read.
R
run
RSCU Bit 15 is set to 1 by software to enable descriptor processing for the context and cleared by software
to stop descriptor processing. The TSB43AB23 device changes this bit only on a system (hardware)
or software reset.
14–13
RSVD
wake
R
Reserved. Bits 14 and 13 return 0s when read.
12
RSU
Softwaresets bit 12 to 1 to cause the TSB43AB23 device to continue or resume descriptor processing.
The TSB43AB23 device clears this bit on every descriptor fetch.
11
dead
RU
The TSB43AB23 device sets bit 11 to 1 when it encounters a fatal error, and clears the bit when
software clears bit 15 (run). Asynchronous contexts supporting out-of-order pipelining provide unique
ContextControl.dead functionality. See Section 7.7 in the 1394 Open Host Controller Interface
Specification (Revision 1.1) for more information.
10
active
RSVD
spd
RU
R
The TSB43AB23 device sets bit 10 to 1 when it is processing descriptors.
Reserved. Bits 9 and 8 return 0s when read.
9–8
7–5
RU
This field indicates the speed at which a packet was received or transmitted and only contains
meaningful information for receive contexts. This field is encoded as:
000 = 100M bits/sec
001 = 200M bits/sec
010 = 400M bits/sec
All other values are reserved.
4–0
eventcode
RU
This field holds the acknowledge sent by the link core for this packet or an internally generated error
code if the packet was not transferred successfully.
4–37
4.41 Asynchronous Context Command Pointer Register
The asynchronous context command pointer register contains a pointer to the address of the first descriptor block
that the TSB43AB23 device accesses when software enables the context by setting bit 15 (run) in the asynchronous
context control register (see Section 4.40, Asynchronous Context Control Register) to 1. See Table 4–32 for a
complete description of the register contents.
Bit
31
30
29
28
27
26
Asynchronous context command pointer
RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Asynchronous context command pointer
RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU RWU
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Register:
Offset:
Asynchronous context command pointer
18Ch [ATRQ]
1ACh [ATRS]
1CCh [ARRQ]
1ECh [ARRS]
Type:
Default:
Read/Write/Update
XXXX XXXXh
Table 4–32. Asynchronous Context Command Pointer Register Description
BIT
31–4
3–0
FIELD NAME
descriptorAddress
Z
TYPE
RWU
RWU
DESCRIPTION
Contains the upper 28 bits of the address of a 16-byte aligned descriptor block.
Indicates the number of contiguous descriptors at the address pointed to by the descriptor address.
If Z is 0, it indicates that the descriptorAddress field (bits 31–4) is not valid.
4–38
4.42 Isochronous Transmit Context Control Register
The isochronous transmit context control set/clear register controls options, state, and status for the isochronous
transmit DMA contexts. The n value in the following register addresses indicates the context number (n = 0, 1, 2, 3,
…, 7). See Table 4–33 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous transmit context control
RSCU RSC
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC RSC
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
RSC
X
X
X
X
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Isochronous transmit context control
RSC
0
R
0
R
0
RSU
X
RU
0
RU
0
R
0
R
0
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
Register:
Offset:
Isochronous transmit context control
200h + (16 * n)
204h + (16 * n)
set register
clear register
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read/set/update, read/update, read-only
XXXX X0XXh
Table 4–33. Isochronous Transmit Context Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
cycleMatchEnable
RSCU When bit 31 is set to 1, processing occurs such that the packet described by the context first
descriptor block is transmitted in the cycle whose number is specified in the cycleMatch field
(bits 30–16). The cycleMatch field (bits 30–16) must match the low-order two bits of cycleSeconds
and the 13-bit cycleCount field in the cycle start packet that is sent or received immediately before
isochronous transmission begins. Since the isochronous transmit DMA controller may work ahead,
the processing of the first descriptor block may begin slightly in advance of the actual cycle in which
the first packet is transmitted.
The effects of this bit, however, are impacted by the values of other bits in this register and are
explained in the 1394 Open Host Controller Interface Specification. Once the context has become
active, hardware clears this bit.
30–16
cycleMatch
RSC
RSC
This field contains a 15-bit value, corresponding to the low-order two bits of the isochronous cycle
timer register at OHCI offset F0h (see Section 4.34, Isochronous Cycle Timer Register)
cycleSeconds field (bits 31–25) and the cycleCount field (bits 24–12). If bit 31 (cycleMatchEnable)
is set to 1, this isochronous transmit DMA context becomes enabled for transmits when the low-order
two bits of the isochronous cycle timer register at OHCI offset F0h cycleSeconds field (bits 31–25)
and the cycleCount field (bits 24–12) value equal this field (cycleMatch) value.
15
run
Bit 15 is set to 1 by software to enable descriptor processing for the context and cleared by software
to stop descriptor processing. The TSB43AB23 device changes this bit only on a system (hardware)
or software reset.
14–13
RSVD
wake
R
Reserved. Bits 14 and 13 return 0s when read.
12
RSU
Software sets bit 12 to 1 to cause the TSB43AB23 device to continue or resume descriptor
processing. The TSB43AB23 device clears this bit on every descriptor fetch.
11
dead
RU
The TSB43AB23 device sets bit 11 to 1 when it encounters a fatal error, and clears the bit when
software clears bit 15 (run) to 0.
10
active
RSVD
RU
R
The TSB43AB23 device sets bit 10 to 1 when it is processing descriptors.
Reserved. Bits 9 and 8 return 0s when read.
9–8
7–5
4–0
spd
RU
RU
This field in not meaningful for isochronous transmit contexts.
event code
FollowinganOUTPUT_LAST*command, theerrorcodeisindicatedinthisfield. Possiblevaluesare:
ack_complete, evt_descriptor_read, evt_data_read, and evt_unknown.
†
On an overflow for each running context, the isochronous transmit DMA supports up to 7 cycle skips, when the following are true:
1. Bit 11 (dead) in either the isochronous transmit or receive context control register is set to 1.
2. Bits 4–0 (eventcode field) in either the isochronous transmit or receive context control register is set to evt_timeout.
3. Bit 24 (unrecoverableError) in the interrupt event register at OHCI offset 80h/84h (see Section 4.21, Interrupt Event Register) is set to 1.
4–39
4.43 Isochronous Transmit Context Command Pointer Register
The isochronous transmit context command pointer register contains a pointer to the address of the first descriptor
block that the TSB43AB23 device accesses when software enables an isochronous transmit context by setting bit 15
(run) in the isochronous transmit context control register (see Section 4.42, Isochronous Transmit Context Control
Register) to 1. The isochronous transmit DMA context command pointer can be read when a context is active. The
n value in the following register addresses indicates the context number (n = 0, 1, 2, 3, …, 7).
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous transmit context command pointer
R
X
R
X
R
X
R
X
R
X
R
X
R
X
9
R
X
8
R
X
7
R
X
6
R
X
5
R
X
4
R
X
3
R
X
2
R
X
1
R
X
0
15
14
13
12
11
10
Name
Type
Default
Isochronous transmit context command pointer
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
Register:
Offset:
Type:
Isochronous transmit context command pointer
20Ch + (16 * n)
Read-only
Default:
XXXX XXXXh
4.44 Isochronous Receive Context Control Register
The isochronous receive context control set/clear register controls options, state, and status for the isochronous
receive DMA contexts. The n value in the following register addresses indicates the context number (n = 0, 1, 2, 3).
See Table 4–34 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive context control
RSC
X
RSC RSCU RSC RSC
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
X
X
X
X
15
14
13
12
11
10
Name
Type
Default
Isochronous receive context control
RSCU
0
R
0
R
0
RSU
X
RU
0
RU
0
R
0
R
0
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
RU
X
Register:
Offset:
Isochronous receive context control
400h + (32 * n)
404h + (32 * n)
set register
clear register
Type:
Default:
Read/Set/Clear/Update, read/set/clear, read/set/update, read/update, read-only
XX00 X0XXh
Table 4–34. Isochronous Receive Context Control Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
bufferFill
RSC
When bit 31 is set to 1, received packets are placed back-to-back to completely fill each receive
buffer. When this bit is cleared, each received packet is placed in a single buffer. If bit 28
(multiChanMode) is set to 1, this bit must also be set to 1. The value of this bit must not be changed
while bit 10 (active) or bit 15 (run) is set to 1.
30
isochHeader
RSC
When bit 30 is set to 1, received isochronous packets include the complete 4-byte isochronous
packet header seen by the link layer. The end of the packet is marked with a xferStatus in the first
doublet, and a 16-bit timeStamp indicating the time of the most recently received (or sent) cycleStart
packet.
When this bit is cleared, the packet header is stripped from received isochronous packets. The
packet header, if received, immediately precedes the packet payload. The value of this bit must not
be changed while bit 10 (active) or bit 15 (run) is set to 1.
4–40
Table 4–34. Isochronous Receive Context Control Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
29
cycleMatchEnable
RSCU Whenbit29issetto1andthe13-bitcycleMatch field (bits 24–12) in the isochronous receive context
matchregister(SeeSection4.46, IsochronousReceiveContextMatchRegister)matchesthe13-bit
cycleCount field in the cycleStart packet, the context begins running. The effects of this bit, however,
are impacted by the values of other bits in this register. Once the context has become active,
hardware clears this bit. The value of this bit must not be changed while bit 10 (active) or bit 15 (run)
is set to 1.
28
multiChanMode
RSC
When bit 28 is set to 1, the corresponding isochronous receive DMA context receives packets for
all isochronous channels enabled in the isochronous receive channel mask high register at OHCI
offset 70h/74h (see Section 4.19, Isochronous Receive Channel Mask High Register) and
isochronous receive channel mask low register at OHCI offset 78h/7Ch (see Section 4.20,
Isochronous Receive Channel Mask Low Register). The isochronous channel number specified in
the isochronous receive context match register (see Section 4.46, Isochronous Receive Context
Match Register) is ignored.
When this bit is cleared, the isochronous receive DMA context receives packets for the single
channel specified in the isochronous receive context match register (see Section 4.46, Isochronous
Receive Context Match Register). Only one isochronous receive DMA context may use the
isochronous receive channel mask registers (see Sections 4.19, Isochronous Receive Channel
Mask High Register, and 4.20, Isochronous Receive Channel Mask Low Register). If more than one
isochronous receive context control register has this bit set, the results are undefined. The value of
this bit must not be changed while bit 10 (active) or bit 15 (run) is set to 1.
27
dualBufferMode
RSC
When bit 27 is set to 1, receive packets are separated into first and second payload and streamed
independentlyto the firstBuffer series and secondBuffer series as described in Section 10.2.3 in the
1394 Open Host Controller Interface Specification. Also, when bit 27 is set to 1, both bits 28
(multiChanMode) and 31 (bufferFill) are cleared to 0. The value of this bit does not change when
either bit 10 (active) or bit 15 (run) is set to 1.
26–16
RSVD
run
R
Reserved. Bits 26–16 return 0s when read.
15
RSCU Bit 15 is set to 1 by software to enable descriptor processing for the context and cleared by software
to stop descriptor processing. The TSB43AB23 device changes this bit only on a system (hardware)
or software reset.
14–13
RSVD
wake
R
Reserved. Bits 14 and 13 return 0s when read.
12
RSU
Software sets bit 12 to 1 to cause the TSB43AB23 device to continue or resume descriptor
processing. The TSB43AB23 device clears this bit on every descriptor fetch.
11
dead
RU
The TSB43AB23 device sets bit 11 to 1 when it encounters a fatal error, and clears the bit when
software clears bit 15 (run).
10
active
RSVD
spd
RU
R
The TSB43AB23 device sets bit 10 to 1 when it is processing descriptors.
Reserved. Bits 9 and 8 return 0s when read.
9–8
7–5
RU
This field indicates the speed at which the packet was received.
000 = 100M bits/sec
001 = 200M bits/sec
010 = 400M bits/sec
All other values are reserved.
4–0
event code
RU
For bufferFill mode, possible values are: ack_complete, evt_descriptor_read, evt_data_write, and
evt_unknown. Packets with data errors (either dataLength mismatches or dataCRC errors) and
packets for which a FIFO overrun occurred are backed out. For packet-per-buffer mode, possible
values are: ack_complete, ack_data_error, evt_long_packet, evt_overrun, evt_descriptor_read,
evt_data_write, and evt_unknown.
4–41
4.45 Isochronous Receive Context Command Pointer Register
The isochronous receive context command pointer register contains a pointer to the address of the first descriptor
block that the TSB43AB23 device accesses when software enables an isochronous receive context by setting bit 15
(run) in the isochronous receive context control register (see Section 4.44, Isochronous Receive Context Control
Register) to 1. The n value in the following register addresses indicates the context number (n = 0, 1, 2, 3).
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive context command pointer
R
X
R
X
R
X
R
X
R
X
R
X
R
X
9
R
X
8
R
X
7
R
X
6
R
X
5
R
X
4
R
X
3
R
X
2
R
X
1
R
X
0
15
14
13
12
11
10
Name
Type
Default
Isochronous receive context command pointer
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
R
X
Register:
Offset:
Type:
Isochronous receive context command pointer
40Ch + (32 * n)
Read-only
Default:
XXXX XXXXh
4–42
4.46 Isochronous Receive Context Match Register
The isochronous receive context match register starts an isochronous receive context running on a specified cycle
number, filters incoming isochronous packets based on tag values, and waits for packets with a specified
synchronous value. The n value in the following register addresses indicates the context number (n = 0, 1, 2, 3). See
Table 4–35 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive context match
R/W
X
R/W
X
R/W
X
R/W
X
R
0
R/W
0
R/W
0
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Name
Type
Default
Isochronous receive context match
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R
0
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
R/W
X
Register:
Offset:
Type:
Isochronous receive context match
410Ch + (32 * n)
Read/Write, Read-only
XXXX XXXXh
Default:
Table 4–35. Isochronous Receive Context Match Register Description
BIT
31
FIELD NAME
tag3
TYPE
R/W
R/W
R/W
R/W
R
DESCRIPTION
If bit 31 is set to 1, this context matches on isochronous receive packets with a tag field of 11b.
If bit 30 is set to 1, this context matches on isochronous receive packets with a tag field of 10b.
If bit 29 is set to 1, this context matches on isochronous receive packets with a tag field of 01b.
If bit 28 is set to 1, this context matches on isochronous receive packets with a tag field of 00b.
Reserved. Bit 27 returns 0 when read.
30
tag2
29
tag1
28
tag0
27
RSVD
26–12
cycleMatch
R/W
Thisfieldcontainsa15-bitvaluecorrespondingtothetwolow-orderbitsofcycleSecondsandthe13-bit
cycleCount field in the cycleStart packet. If cycleMatchEnable (bit 29) in the isochronous receive
context control register (see Section 4.44, Isochronous Receive Context Control Register) is set to 1,
this context is enabled for receives when the two low-order bits of the isochronous cycle timer register
at OHCI offset F0h (see Section 4.34, Isochronous Cycle Timer Register) cycleSeconds field
(bits 31–25) and cycleCount field (bits 24–12) value equal this field (cycleMatch) value.
11–8
sync
R/W
This 4-bit field is compared to the sync field of each isochronous packet for this channel when the
command descriptor w field is set to 11b.
7
6
RSVD
R
Reserved. Bit 7 returns 0 when read.
tag1SyncFilter
R/W
If bit 6 and bit 29 (tag1) are set to 1, packets with tag 01b are accepted into the context if the two most
significant bits of the packet sync field are 00b. Packets with tag values other than 01b are filtered
according to bit 28 (tag0), bit 30 (tag2), and bit 31 (tag3) without any additional restrictions.
If this bit is cleared, this context matches on isochronous receive packets as specified in bits 28–31
(tag0–tag3) with no additional restrictions.
5–0
channelNumber
R/W
This 6-bit field indicates the isochronous channel number for which this isochronous receive DMA
context accepts packets.
4–43
5 TI Extension Registers
The TI extension base address register provides a method of accessing memory-mapped TI extension registers. See
Section 3.10, TI Extension Base Address Register, for register bit field details. See Table 5–1 for the TI extension
register listing.
Table 5–1. TI Extension Register Map
REGISTER NAME
OFFSET
00h–A7Fh
A80h
Reserved
Isochronous Receive DV Enhancement Set
Isochronous Receive DV Enhancement Clear
Link Enhancement Control Set
A84h
A88h
Link Enhancement Control Clear
A8Ch
A90h
Isochronous Transmit Context 0 Timestamp Offset
Isochronous Transmit Context 1 Timestamp Offset
Isochronous Transmit Context 2 Timestamp Offset
Isochronous Transmit Context 3 Timestamp Offset
Isochronous Transmit Context 4 Timestamp Offset
Isochronous Transmit Context 5 Timestamp Offset
Isochronous Transmit Context 6 Timestamp Offset
Isochronous Transmit Context 7 Timestamp Offset
A94h
A98h
A9Ch
AA0h
AA4h
AA8h
AA8h
5.1 DV and MPEG2 Timestamp Enhancements
The DV timestamp enhancements are enabled by bit 8 (enab_dv_ts) in the link enhancement control register located
at PCI offset F4h and are aliased in TI extension register space at offset A88h (set) and A8Ch (clear).
The DV and MPEG transmit enhancements are enabled separately by bits in the link enhancement control register
located in PCI configuration space at PCI offset F4h. The link enhancement control register is also aliased as a
set/clear register in TI extension space at offset A88h (set) and A8Ch (clear).
Bit 8 (enab_dv_ts) of the link enhancement control register enables DV timestamp support. When enabled, the link
calculates a timestamp based on the cycle timer and the timestamp offset register and substitutes it in the SYT field
of the CIP once per DV frame.
Bit 10 (enab_mpeg_ts) of the link enhancement control register enables MPEG timestamp support. Two MPEG time
stamp modes are supported. The default mode calculates an initial delta that is added to the calculated timestamp
in addition to a user-defined offset. The initial offset is calculated as the difference in the intended transmit cycle count
and the cycle count field of the timestamp in the first TSP of the MPEG2 stream. The use of the initial delta can be
controlled by bit 31 (DisableInitialOffset) in the timestamp offset register (see Section 5.5, Timestamp Offset
Register).
The MPEG2 timestamp enhancements are enabled by bit 10 (enab_mpeg_ts) in the link enhancement control
register located at PCI offset F4h and aliased in TI extension register space at offset A88h (set) and A8Ch (clear).
When bit 10 (enab_mpeg_ts) is set to 1, the hardware applies the timestamp enhancements to isochronous transmit
packets that have the tag field equal to 01b in the isochronous packet header and a FMT field equal to 10h.
5–1
5.2 Isochronous Receive Digital Video Enhancements
The DV frame synchronous and branch enhancement provides a mechanism in buffer-fill mode to synchronize 1394
DV data that is received in the correct order to DV frame-sized data buffers described by several INPUT_MORE
descriptors (see 1394 Open Host Controller Interface Specification, Revision 1.1). This is accomplished by waiting
for the start-of-frame packet in a DV stream before transferring the received isochronous stream into the memory
buffer described by the INPUT_MORE descriptors. This can improve the DV capture application performance by
reducing the amount of processing overhead required to strip the CIP header and copy the received packets into
frame-sized buffers.
The start of a DV frame is represented in the 1394 packet as a 16-bit pattern of 1FX7h (first byte 1Fh and second
byte X7h) received as the first two bytes of the third quadlet in a DV isochronous packet.
5.3 Isochronous Receive Digital Video Enhancements Register
The isochronous receive digital video enhancements register enables the DV enhancements in the TSB43AB23
device. The bits in this register may only be modified when both the active (bit 10) and run (bit 15) bits of the
corresponding context control register are 0. See Table 5–2 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Isochronous receive digital video enhancements
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Isochronous receive digital video enhancements
R
0
R
0
RSC
0
RSC
0
R
0
R
0
RSC
0
RSC
0
R
0
R
0
RSC
0
RSC
0
R
0
R
0
RSC
0
RSC
0
Register:
Offset:
Isochronous receive digital video enhancements
A80h
A84h
set register
clear register
Type:
Default:
Read/Set/Clear, read-only
0000 0000h
Table 5–2. Isochronous Receive Digital Video Enhancements Register Description
BIT
31–14
13
FIELD NAME
RSVD
TYPE
R
DESCRIPTION
Reserved. Bits 31–14 return 0s when read.
DV_Branch3
RSC
When bit 13 is set to 1, the isochronous receive context 3 synchronizes reception to the DV frame start
tag in bufferfill mode if input_more.b = 01b, and jumps to the descriptor pointed to by frameBranch if
a DV frame start tag is received out of place. This bit is only interpreted when bit 12 (CIP_Strip3) is
set to 1 and bit 30 (isochHeader) in the isochronous receive context control register at OHCI offset
460h/464h (see Section 4.44, Isochronous Receive Context Control Register) is cleared to 0.
12
CIP_Strip3
RSC
When bit 12 is set to 1, the isochronous receive context 3 strips the first two quadlets of payload. This
bit is only interpreted when bit 30 (isochHeader) in the isochronous receive context control register at
OHCI offset 460h/464h (see Section 4.44, Isochronous Receive Context Control Register) is cleared
to 0.
11–10
RSVD
R
Reserved. Bits 11 and 10 return 0s when read.
9
DV_Branch2
RSC
When bit 9 is set to 1, the isochronous receive context 2 synchronizes reception to the DV frame start
tag in bufferfill mode if input_more.b = 01b, and jumps to the descriptor pointed to by frameBranch if
a DV frame start tag is received out of place. This bit is only interpreted when bit 8 (CIP_Strip2) is set
to 1 and bit 30 (isochHeader) in the isochronous receive context control register at OHCI offset
440h/444h (see Section 4.44, Isochronous Receive Context Control Register) is cleared to 0.
5–2
Table 5–2. Isochronous Receive Digital Video Enhancements Register Description (Continued)
BIT
FIELD NAME
TYPE
DESCRIPTION
8
CIP_Strip2
RSC
When bit 8 is set to 1, the isochronous receive context 2 strips the first two quadlets of payload. This
bit is only interpreted when bit 30 (isochHeader) in the isochronous receive context control register at
OHCI offset 440h/444h (see Section 4.44, Isochronous Receive Context Control Register) is cleared
to 0.
7–6
RSVD
R
Reserved. Bits 7 and 6 return 0s when read.
5
DV_Branch1
RSC
When bit 5 is set to 1, the isochronous receive context 1 synchronizes reception to the DV frame start
tag in bufferfill mode if input_more.b = 01b, and jumps to the descriptor pointed to by frameBranch if
a DV frame start tag is received out of place. This bit is only interpreted when bit 4 (CIP_Strip1) is set
to 1 and bit 30 (isochHeader) in the isochronous receive context control register at OHCI offset
420h/424h (see Section 4.44, Isochronous Receive Context Control Register) is cleared to 0.
4
CIP_Strip1
RSC
When bit 4 is set to 1, the isochronous receive context 1 strips the first two quadlets of payload. This
bit is only interpreted when bit 30 (isochHeader) in the isochronous receive context control register at
OHCI offset 420h/424h (see Section 4.44, Isochronous Receive Context Control Register) is cleared
to 0.
3–2
RSVD
R
Reserved. Bits 3 and 2 return 0s when read.
1
DV_Branch0
RSC
When bit 1 is set to 1, the isochronous receive context 0 synchronizes reception to the DV frame start
tag in bufferfill mode if input_more.b = 01b and jumps to the descriptor pointed to by frameBranch if
a DV frame start tag is received out of place. This bit is only interpreted when bit 0 (CIP_Strip0) is set
to 1 and bit 30 (isochHeader) in the isochronous receive context control register at OHCI offset
400h/404h (see Section 4.44, Isochronous Receive Context Control Register) is cleared to 0.
0
CIP_Strip0
RSC
When bit 0 is set to 1, the isochronous receive context 0 strips the first two quadlets of payload. This
bit is only interpreted when bit 30 (isochHeader) in the isochronous receive context control register at
OHCI offset 400h/404h (see Section 4.44, Isochronous Receive Context Control Register) is cleared
to 0.
5–3
5.4 Link Enhancement Register
This register is a memory-mapped set/clear register that is an alias of the link enhancement control register at PCI
offset F4h. These bits may be initialized by software. Some of the bits may also be initialized by a serial EEPROM,
if one is present, as noted in the bit descriptions below. If the bits are to be initialized by software, the bits must be
initialized prior to setting bit 19 (LPS) in the host controller control register at OHCI offset 50h/54h (see Section 4.16,
Host Controller Control Register). See Table 5–3 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Link enhancement
R
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R
0
8
R
0
7
R
0
6
R
0
5
R
0
4
R
0
3
R
0
2
R
0
1
R
0
0
15
14
13
12
11
10
Name
Type
Default
Link enhancement
RSC
0
R
0
RSC
0
RSC
1
R
0
RSC
0
R
0
RSC
0
RSC
0
R
0
R
0
R
0
R
0
R
0
RSC
0
R
0
Register:
Offset:
Link enhancement
A88h
A8Ch
set register
clear register
Type:
Default:
Read/Set/Clear, read-only
0000 0000h
Table 5–3. Link Enhancement Register Description
BIT
31–16
15
FIELD NAME
RSVD
TYPE
DESCRIPTION
Reserved. Bits 31–16 return 0s when read.
R
dis_at_pipeline
RSVD
RSC
R
Disable AT pipelining. When bit 15 is set to 1, out-of-order AT pipelining is disabled.
Reserved.
14
13–12
atx_thresh
RSC
This field sets the initial AT threshold value, which is used until the AT FIFO is underrun. When the
TSB43AB23 device retries the packet, it uses a 2K-byte threshold, resulting in a store-and-forward
operation.
00 = Threshold ~ 2K bytes resulting in a store-and-forward operation
01 = Threshold ~ 1.7K bytes (default)
10 = Threshold ~ 1K bytes
11 = Threshold ~ 512 bytes
These bits fine-tune the asynchronous transmit threshold. For most applications the 1.7K-byte
threshold is optimal. Changing this value may increase or decrease the 1394 latency depending on
the average PCI bus latency.
SettingtheATthresholdto1.7K, 1K, or512bytesresultsindatabeingtransmittedatthesethresholds
or when an entire packet has been checked into the FIFO. If the packet to be transmitted is larger
thantheATthreshold, theremainingdatamustbereceivedbeforetheATFIFOisemptied;otherwise,
an underrun condition occurs, resulting in a packet error at the receiving node. As a result, the link
then commences store-and-forward operation. Wait until it has the complete packet in the FIFO
before retransmitting it on the second attempt, to ensure delivery.
An AT threshold of 2K results in store-and-forward operation, which means that asynchronous data
will not be transmitted until an end-of-packet token is received. Restated, setting the AT threshold
to 2K results in only complete packets being transmitted.
Notethat this device always uses store-and-forward when the asynchronous transmit retries register
at OHCI offset 08h (see Section 4.3, Asynchronous Transmit Retries Register) is cleared.
11
10
RSVD
R
Reserved. Bit 11 returns 0 when read.
enab_mpeg_ts
RSC
Enable MPEG timestamp enhancements. When bit 10 is set to 1, the enhancement is enabled for
MPEG transmit streams (FMT = 20h).
9
8
RSVD
R
Reserved. Bit 9 returns 0 when read.
enab_dv_ts
RSC
Enable DV CIP timestamp enhancement. When bit 8 is set to 1, the enhancement is enabled for DV
CIP transmit streams (FMT = 00h).
5–4
Table 5–3. Link Enhancement Register Description (Continued)
7
6
enab_unfair
RSVD
RSC
Enable asynchronous priority requests. iOHCI-Lynx compatible. Setting bit 7 to 1 enables the link
to respond to requests with priority arbitration. It is recommended that this bit be set to 1.
R
This bit is not assigned in the TSB43AB23 follow-on products, since this bit location loaded by the
serial EEPROM from the enhancements field corresponds to bit 23 (programPhyEnable) in the host
controller control register at OHCI offset 50h/54h (see Section 4.16, Host Controller Control
Register).
5–2
RSVD
R
Reserved. Bits 5–2 return 0s when read.
1
enab_accel
RSC
Enable acceleration enhancements. iOHCI-Lynx compatible. When bit 1 is set to 1, the PHY layer
is notified that the link supports the IEEE Std 1394a-2000 acceleration enhancements, that is,
ack-accelerated, fly-by concatenation, etc. It is recommended that this bit be set to 1.
0
RSVD
R
Reserved. Bit 0 returns 0 when read.
5.5 Timestamp Offset Register
The value of this register is added as an offset to the cycle timer value when using the MPEG, DV, and CIP
enhancements. A timestamp offset register is implemented per isochronous transmit context. The n value following
the offset indicates the context number (n = 0, 1, 2, 3, …, 7). These registers are programmed by software as
appropriate. See Table 5–4 for a complete description of the register contents.
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Name
Type
Default
Bit
Timestamp offset
R/W
0
R
0
R
0
R
0
R
0
R
0
R
0
9
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
15
14
13
12
11
10
8
7
6
5
4
3
2
1
0
Name
Type
Default
Timestamp offset
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
Register:
Offset:
Type:
Timestamp offset
A90h + (4*n)
Read/Write, read-only
0000 0000h
Default:
Table 5–4. Timestamp Offset Register Description
BIT
FIELD NAME
TYPE
DESCRIPTION
31
DisableInitialOffset
R/W
Bit 31 disables the use of the initial timestamp offset when the MPEG2 enhancements are enabled.
A value of 0 indicates the use of the initial offset, a value of 1 indicates that the initial offset must not
be applied to the calculated timestamp. This bit has no meaning for the DV timestamp
enhancements.
30–25
24–12
RSVD
R
Reserved. Bits 30–25 return 0s when read.
CycleCount
R/W
This field adds an offset to the cycle count field in the timestamp when the DV or MPEG2
enhancements are enabled. The cycle count field is incremented modulo 8000; therefore, values in
this field must be limited between 0 and 7999.
11–0
CycleOffset
R/W
This field adds an offset to the cycle offset field in the timestamp when the DV or MPEG2
enhancements are enabled. The cycle offset field is incremented modulo 3072; therefore, values in
this field must be limited between 0 and 3071.
5–5
6 Serial EEPROM Interface
The TSB43AB23 device provides a serial bus interface to initialize the GUID registers and a few PCI configuration
registers through a serial EEPROM. The TSB43AB23 device communicates with the serial EEPROM via the 2-wire
serial interface.
After power up the serial interface initializes the locations listed in Table 6–1. While the TSB43AB23 device accesses
the serial EEPROM, all incoming PCI slave accesses are terminated with retry status. Table 6–2 shows the serial
EEPROM memory map required for initializing the TSB43AB23 registers.
NOTE: If an EEPROM is implemented in the design, byte offsets 00h–16h must be
programmed. An unprogrammed EEPROM defaults to all 1s, which can adversely impact
device operation.
Table 6–1. Registers and Bits Loadable Through Serial EEPROM
OHCI/PCI
CONFIGURATION
OFFSET
REGISTER BITS
LOADED
FROM EEPROM
EEPROM BYTE OFFSET
REGISTER NAME
00h
PCI register (3Eh)
PCI register (2Dh)
PCI register (2Ch)
OHCI register (50h)
PCI register (F4h)
OHCI register (04h)
OHCI register (24h)
OHCI register (28h)
PCI register (F4h)
PCI register (F0h)
PCI register (ECh)
PCI maximum latency, PCI minimum grant
Vendor identification
Subsystem identification
Host controller control
Link enhancement control
GUID ROM
15–0
15–0
15–0
23
01h
03h
05h (bit 6)
05h
7, 6, 1
7–0
06h
07h–0Ah
0Bh–0Eh
10h
GUID high
31–0
31–0
15–12
15, 4
7–0
GUID low
Link enhancement control
†
Miscellaneous configuration
11h–12h
16h
‡
PCI PHY control
†
Bits 2–0 at EEPROM byte offset 11h must be programmed to 000b to ensure proper functioning. By default, unprogrammed EEPROM
bits are 1.
Bits 6–4 and 2–0 at EEPROM byte offset 16h must be programmed to 0 to ensure proper functioning. Bit 3 must be programmed to 1.
If CNA functionality is desired on terminal 96, bit 7 must be programmed to 1; otherwise, bit 7 can be programmed to 0.
‡
6–1
Table 6–2. Serial EEPROM Map
EEPROM
BYTE
BYTE DESCRIPTION
ADDRESS
00
01
02
03
04
PCI maximum latency (0h)
PCI_minimum grant (0h)
PCI vendor ID
PCI vendor ID (msbyte)
PCI subsystem ID (lsbyte)
PCI subsystem ID (msbyte)
[5–3]
[7]
[6]
[2]
[1]
[0]
RSVD
†
Link_enhancement
HCControl.
RSVD
RSVD
Link_enhancement
Control.enab_accel
05
Control.enab_unfair ProgramPhy
Enable
[7–6]
RSVD
Mini
ROM
[4–3]
RSVD
06
address
07
08
09
0A
0B
0C
0D
0E
0F
GUID high (lsbyte 0)
GUID high (byte 1)
GUID high (byte 2)
GUID high (msbyte 3)
GUID low (lsbyte 0)
GUID low (byte 1)
GUID low (byte 2)
GUID low (msbyte 3)
Checksum
[15]
dis_at_pipeline
[14]
RSVD
[13–12]
ATX threshold
[11–8]
RSVD
‡
10
[7–5]
RSVD
[4]
Disable
Target
Abort
[3–0]
RSVD
§
11
[15]
PME D3 Cold
[14–8]
RSVD
12
13
[7–0]
RSVD
[7–0]
RSVD
14
15
RSVD
[7]
[6–4]
RSVD
[3]
RSVD
[2–0]
RSVD
¶
16
CNA OUT Enable
17–1F
RSVD
†
‡
§
Bit 2 at EEPROM byte offset 05h must be programmed to 0b.
Bit 14 must be programmed to 0 for normal operation.
Bits 2–0 at EEPROM byte offset 11h must be programmed to 000b to ensure proper functioning. By default, unprogrammed EEPROM bits are
1.
Bits 6–4 and 2–0 at EEPROM byte offset 16h must be programmed to 0 to ensure proper functioning. Bit 3 must be programmed to 1. If CNA
functionality is desired on terminal 96, bit 7 must be programmed to 1; otherwise, bit 7 can be programmed to 0.
¶
6–2
7 PHY Register Configuration
There are 16 accessible internal registers in the TSB43AB23 device. The configuration of the registers at addresses
0h through 7h (the base registers) is fixed, whereas the configuration of the registers at addresses 8h through Fh (the
paged registers) is dependent upon which one of eight pages, numbered 0h through 7h, is currently selected. The
selected page is set in base register 7h.
7.1 Base Registers
Table 7–1 shows the configuration of the base registers, and Table 7–2 shows the corresponding field descriptions.
The base register field definitions are unaffected by the selected page number.
A reserved register or register field (marked as reserved in the following register configuration tables) is read as 0,
but is subject to future usage. All registers in address pages 2 through 6 are reserved.
Table 7–1. Base Register Configuration
BIT POSITION
ADDRESS
0
1
2
3
4
5
6
7
0000
0001
0010
0011
0100
0101
0110
0111
Physical ID
R
CPS
RHB
IBR
Extended (111b)
Max_Speed (010b)
C
Gap_Count
Reserved
Reserved
Jitter (000b)
Pwr_fail
Total_Ports (0011b)
Delay (0000b)
LCtrl
Pwr_Class
Watchdog
ISBR
Loop
Timeout
Port_event Enab_accel Enab_multi
Port_Select
Reserved
Reserved
Page_Select
7–1
Table 7–2. Base Register Field Descriptions
FIELD
SIZE TYPE
DESCRIPTION
Physical ID
6
1
1
R
R
R
This field contains the physical address ID of this node determined during self-ID. The physical ID is invalid
after a bus reset until self-ID has completed as indicated by an unsolicited register-0 status transfer.
R
Root. This bit indicates that this node is the root node. The R bit is cleared to 0 by bus reset and is set to 1
during tree-ID if this node becomes root.
CPS
Cable-power-status. This bit indicates the state of the CPS input terminal. The CPS terminal is normally tied
to serial bus cable power through a 400-kΩ resistor. A 0 in this bit indicates that the cable power voltage has
dropped below its threshold for ensured reliable operation.
RHB
IBR
1
1
R/W
R/W
Root-holdoff bit. This bit instructs the PHY layer to attempt to become root after the next bus reset. The RHB
bit is cleared to 0 by a system (hardware) reset and is unaffected by a bus reset.
Initiate bus reset. This bit instructs the PHY layer to initiate a long (166 µs) bus reset at the next opportunity.
Any receive or transmit operation in progress when this bit is set will complete before the bus reset is
initiated. The IBR bit is cleared to 0 after a system (hardware) reset or a bus reset.
Gap_Count
6
R/W
Arbitration gap count. This value sets the subaction (fair) gap, arb-reset gap, and arb-delay times. The gap
count can be set either by a write to the register, or by reception or transmission of a PHY_CONFIG packet.
The gap count is reset to 3Fh by system (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).
Extended
3
4
R
R
Extended register definition. For the TSB43AB23 device, this field is 111b, indicating that the extended
register set is implemented.
Total_Ports
Numberof ports. This field indicates the number of ports implemented in the PHY layer. For the TSB43AB23
device this field is 3.
Max_Speed
Delay
3
4
R
R
PHY speed capability. For the TSB43AB23 PHY layer this field is 010b, indicating S400 speed capability.
PHYrepeaterdatadelay. ThisfieldindicatestheworstcaserepeaterdatadelayofthePHYlayer, expressed
as 144+(delay × 20) ns. For the TSB43AB23 device this field is 0.
LCtrl
1
R/W
Link-active status control. This bit controls the active status of the LLC as indicated during self-ID. The
logicalANDofthisbitandtheLPSactivestatusisreplicatedintheLfield(bit9)oftheself-IDpacket.TheLLC
is considered active only if both the LPS input is active and the LCtrl bit is set.
TheLCtrl bit providesasoftwarecontrollablemeanstoindicatetheLLCactive/statusinlieuofusingtheLPS
input.
The LCtrl bit is set to 1 by a system (hardware) reset and is unaffected by a bus reset.
NOTE: The state of the PHY-LLCinterfaceiscontrolledsolelybytheLPSinput, regardlessofthestateofthe
LCtrl bit. If the PHY-LLC interface is operational as determined by the LPS input being active, received
packetsandstatusinformationcontinuestobepresentedontheinterface,andanyrequestsindicatedonthe
LREQ input are processed, even if the LCtrl bit is cleared to 0.
C
1
3
3
R/W
R
Contender status. This bit indicates that this node is a contender for the bus or isochronous resource
manager. This bit is replicated in the c field (bit 20) of the self-ID packet.
Jitter
PHY repeater jitter. This field indicates the worst case difference between the fastest and slowest repeater
data delay, expressed as (Jitter+1) × 20 ns. For the TSB43AB23 device, this field is 0.
Pwr_Class
R/W
Node power class. This field indicates this node power consumption and source characteristics and is
replicated in the pwr field (bits 21–23) of the self-ID packet. This field is reset to the state specified by the
PC0–PC2 input terminals upon a system (hardware) reset and is unaffected by a bus reset. See Table 7–9.
Watchdog
1
R/W
Watchdog enable. This bit, if set to 1, enables the port event interrupt (Port_event) bit to be set whenever
resumeoperationsbeginonanyport. Thisbitisclearedto0bysystem(hardware)resetandisunaffectedby
bus reset.
7–2
Table 7–2. Base Register Field Descriptions (Continued)
FIELD
ISBR
SIZE TYPE
DESCRIPTION
1
R/W
Initiate short arbitrated bus reset. This bit, if set to 1, instructs the PHY layer to initiate a short (1.3 µs)
arbitrated bus reset at the next opportunity. This bit is cleared to 0 by a bus reset.
NOTE: Legacy IEEE Std 1394-1995 compliant PHY layers can not be capable of performing short bus
resets. Therefore, initiation of a short bus reset in a network that contains such a legacy device results in a
long bus reset being performed.
Loop
1
R/W
Loop detect. This bit is set to 1 when the arbitration controller times out during tree-ID start and may indicate
that the bus is configured in a loop. This bit is cleared to 0 by system (hardware) reset or by writing a 1 to this
register bit.
If the Loop and Watchdog bits are both set and the LLC is or becomes inactive, the PHY layer activates the
LLC to service the interrupt.
NOTE: If the network is configured in a loop, only those nodes which are part of the loop generate a
configuration-timeoutinterrupt. Allothernodesinsteadtimeoutwaitingforthetree-IDand/orself-IDprocess
to complete and then generate a state time-out interrupt and bus-reset.
Pwr_fail
1
R/W
Cable power failure detect. This bit is set to 1 whenever the CPS input transitions from high to low indicating
that cable power may be too low for reliable operation. This bit is cleared to 0 by system (hardware) reset or
by writing a 1 to this register bit.
Timeout
1
1
R/W
R/W
State time-out interrupt. This bit indicates that a state time-out has occurred (which also causes a bus reset
to occur). This bit is cleared to 0 by system (hardware) reset or by writing a 1 to this register bit.
Port_event
Porteventdetect. Thisbitissetto1uponachangeinthebias(unlessdisabled)connected, disabled, orfault
bits for any port for which the port interrupt enable (Int_enable) bit is set. Additionally, if the Watchdog bit is
set, the Port_event bit is set to 1 at the start of resume operations on any port. This bit is cleared to 0 by
system (hardware) reset or by writing a 1 to this register bit.
Enab_accel
Enab_multi
1
1
R/W
R/W
Enableacceleratedarbitration. ThisbitenablesthePHYlayertoperformthevariousarbitrationacceleration
enhancements defined in IEEE Std 1394a-2000 (ACK-accelerated arbitration, asynchronous fly-by
concatenation, and isochronous fly-by concatenation). This bit is cleared to 0 by system (hardware) reset
and is unaffected by bus reset.
Enable multispeed concatenated packets. This bit enables the PHY layer to transmit concatenated packets
of differing speeds in accordance with the protocols defined in IEEE Std 1394a-2000. This bit is cleared to 0
by system (hardware) reset and is unaffected by bus reset.
Page_Select
Port_Select
3
4
R/W
R/W
Page_Select. This field selects the register page to use when accessing register addresses 8 through 15.
This field is cleared to 0 by a system (hardware) reset and is unaffected by bus reset.
Port_Select. This field selects the port when accessing per-port status or control (for example, when one of
theport status/control registers is accessed in page 0). Ports are numbered starting at 0. This field is cleared
to 0 by system (hardware) reset and is unaffected by bus reset.
7–3
7.2 Port Status Register
Theportstatuspageprovidesaccesstoconfigurationandstatusinformationforeachoftheports. Theportisselected
by writing 0 to the Page_Select field and the desired port number to the Port_Select field in base register 7. Table 7–3
shows the configuration of the port status page registers and Table 7–4 shows the corresponding field descriptions.
If the selected port is not implemented, all registers in the port status page are read as 0.
Table 7–3. Page 0 (Port Status) Register Configuration
BIT POSITION
ADDRESS
1000
0
1
2
3
4
5
6
7
AStat
Peer_Speed
BStat
Int_enable
Ch
Con
Bias
Dis
1001
Fault
Reserved
1010
Reserved
1011
Reserved
Reserved
Reserved
Reserved
Reserved
1100
1101
1110
1111
Table 7–4. Page 0 (Port Status) Register Field Descriptions
FIELD
AStat
SIZE TYPE
DESCRIPTION
2
R
TPA line state. This field indicates the TPA line state of the selected port, encoded as follows:
Code
11
Arb Value
Z
10
01
0
1
00
invalid
BStat
Ch
2
1
R
R
TPBlinestate. ThisfieldindicatestheTPBlinestateoftheselectedport. Thisfieldhasthesameencodingas
the AStat field.
Child/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.
Con
1
R
Debounced 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
cleared to 0 by system (hardware) reset and is unaffected by bus reset.
NOTE: The Con bit indicates that the port is physically connected to a peer PHY device, but the port is not
necessarily active.
Bias
Dis
1
1
R
Debouncedincoming 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.
R/W
Port disabled control. If the Dis bit is set to 1, the selected port is disabled. The Dis bit is cleared to 0 by
system (hardware) reset (all ports are enabled for normal operation following system (hardware) reset). The
Dis bit is not affected by bus reset.
Peer_Speed
3
R
Port peer speed. This field indicates the highest speed capability of the peer PHY device connected to the
selected port, encoded as follows:
Code
000
Peer Speed
S100
001
S200
010
S400
011–111
invalid
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 IEEE Std 1394a-2000. However, the
TSB43AB23 device is only capable of detecting peer speeds up to S400.
7–4
Table 7–4. Page 0 (Port Status) Register Field Descriptions (Continued)
FIELD
SIZE TYPE
DESCRIPTION
Int_enable
1
R/W
Port event interrupt enable. When the Int_enable bit is set to 1, a port event on the selected port sets the port
event interrupt (Port_event) bit and notifies the link. This bit is cleared to 0 by a system (hardware) reset and
is unaffected by bus reset.
Fault
1
R/W
Fault. This bit indicates that a resume-fault or suspend-fault has occurred on the selected port, and that the
port 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 cleared to 0 by system
(hardware) reset and is unaffected by bus reset.
7.3 Vendor Identification Register
The vendor identification page identifies the vendor/manufacturer and compliance level. The page is selected by
writing 1 to the Page_Select field in base register 7. Table 7–5 shows the configuration of the vendor identification
page, and Table 7–6 shows the corresponding field descriptions.
Table 7–5. Page 1 (Vendor ID) Register Configuration
BIT POSITION
ADDRESS
1000
0
1
2
3
4
5
6
7
Compliance
Reserved
1001
1010
Vendor_ID[0]
Vendor_ID[1]
Vendor_ID[2]
Product_ID[0]
Product_ID[1]
Product_ID[2]
1011
1100
1101
1110
1111
Table 7–6. Page 1 (Vendor ID) Register Field Descriptions
FIELD
SIZE TYPE
DESCRIPTION
Compliance
8
R
R
R
Compliance level. For the TSB43AB23 device this field is 01h, indicating compliance with IEEE Std
1394a-2000.
Vendor_ID
Product_ID
24
24
Manufacturer’s organizationally unique identifier (OUI). For the TSB43AB23 device this field is 08 0028h
(Texas Instruments) (the MSB is at register address 1010b).
Product identifier. For the TSB43AB23 device this field is 42 4499h (the MSB is at register address 1101b).
7–5
7.4 Vendor-Dependent Register
The vendor-dependent page provides access to the special control features of the TSB43AB23 device, as well as
to 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. Table 7–7 shows the configuration of the vendor-dependent page, and
Table 7–8 shows the corresponding field descriptions.
Table 7–7. Page 7 (Vendor-Dependent) Register Configuration
BIT POSITION
ADDRESS
1000
0
1
2
3
4
5
6
7
NPA
Reserved
Link_Speed
1001
Reserved for test
Reserved for test
Reserved for test
Reserved for test
Reserved for test
Reserved for test
Reserved for test
1010
1011
1100
1101
1110
1111
Table 7–8. Page 7 (Vendor-Dependent) Register Field Descriptions
FIELD
SIZE TYPE
DESCRIPTION
NPA
1
R/W
Null-packet actions flag. This bit instructs the PHY layer to not clear fair and priority requests when a null
packet is received with arbitration acceleration enabled. If this bit is set to 1, 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
(nodatabits), andmalformedpackets(lessthan8databits)donotclearfairandpriorityrequests. Ifthisbitis
cleared to 0, 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 system (hardware) reset and is
unaffected by bus reset.
Link_Speed
2
R/W
Link speed. This field indicates the top speed capability of the attached LLC. Encoding is as follows:
Code
00
01
10
11
Speed
S100
S200
S400
illegal
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 TSB43AB23 PHY layer identifies itself as S400 capable to its peers regardless of
the value in this field. This field is set to 10b (S400) by system (hardware) reset and is unaffected by bus
reset.
7–6
7.5 Power-Class Programming
The PC0–PC2 terminals 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. Table 7–9 shows the descriptions of the various power classes. The
default power-class value is loaded following a system (hardware) reset, but is overridden by any value subsequently
loaded into the Pwr_Class field in register 4.
Table 7–9. Power Class Descriptions
PC0–PC2
000
DESCRIPTION
Node does not need power and does not repeat power.
001
Node is self-powered and provides a minimum of 15 W to the bus.
010
Node is self-powered and provides a minimum of 30 W to the bus.
011
Node is self-powered and provides a minimum of 45 W to the bus.
100
Node may be powered from the bus and is using up to 3 W. No additional power is needed to enable the link.
Reserved
101
110
Node is powered from the bus and uses up to 3 W. An additional 3 W is needed to enable the link.
Node is powered from the bus and uses up to 3 W. An additional 7 W is needed to enable the link.
111
7–7
8 Application Information
8.1 PHY Port Cable Connection
TSB43AB23
CPS
400 kΩ
Cable
Power
Pair
1 µF
TPBIAS
56 Ω
56 Ω
TPA+
Cable
Pair
A
TPA–
Cable Port
TPB+
Cable
Pair
B
TPB–
56 Ω
56 Ω
5 kΩ
220 pF
(see Note A)
Outer Shield
Termination
NOTE A: IEEE Std 1394-1995 calls for a 250-pF capacitor, which is a nonstandard component value. A 220-pF capacitor is recommended.
Figure 8–1. TP Cable Connections
8–1
Outer Cable Shield
1 MΩ
0.01 µF
0.001µF
Chassis Ground
Figure 8–2. Typical Compliant DC Isolated Outer Shield Termination
Outer Cable Shield
Chassis Ground
Figure 8–3. Non-DC Isolated Outer Shield Termination
8.2 Crystal Selection
The TSB43AB23 device is designed to use an external 24.576-MHz crystal connected between the XI and XO pins
to provide the reference for an internal oscillator circuit. This oscillator in turn drives a PLL circuit that generates the
various clocks required for transmission and resynchronization of data at the S100 through S400 media data rates.
A variation of less than ±100 ppm from nominal for the media data rates is required by IEEE Std 1394-1995. Adjacent
PHYs may therefore have a difference of up to 200 ppm from each other in their internal clocks, and PHY devices
must be able to compensate for this difference over the maximum packet length. Large clock variations may cause
resynchronization overflows or underflows, resulting in corrupted packet data.
The following are some typical specifications for crystals used with the PHYs from TI in order to achieve the required
frequency accuracy and stability:
•
•
Crystal mode of operation: Fundamental
Frequency tolerance @ 25°C: Total frequency variation for the complete circuit is ±100 ppm. A crystal with
±30 ppm frequency tolerance is recommended for adequate margin.
•
Frequency stability (over temperature and age): A crystal with ±30 ppm frequency stability is recommended
for adequate margin.
NOTE: The total frequency variation must be kept below ±100 ppm from nominal with some
allowance for error introduced by board and device variations. Trade-offs between frequency
tolerance and stability may be made as long as the total frequency variation is less than
±100 ppm. For example, the frequency tolerance of the crystal may be specified at 50 ppm and
the temperature tolerance may be specified at 30 ppm to give a total of 80 ppm possible
variation due to the crystal alone. Crystal aging also contributes to the frequency variation.
•
Load capacitance: For parallel resonant mode crystal circuits, the frequency of oscillation is dependent
upon the load capacitance specified for the crystal. Total load capacitance (C ) is a function of not only the
L
discrete load capacitors, but also board layout and circuit. It is recommended that load capacitors with a
maximum of ±5% tolerance be used.
8–2
For example, load capacitors (C9 and C10 in Figure 8–4) of 16 pF each were appropriate for the layout of the
TSB43AB23 evaluation module (EVM), which uses a crystal specified for 12-pF loading. The load specified for the
crystal includes the load capacitors (C9 and C10), the loading of the PHY pins (C
), and the loading of the board
PHY
itself(C ).ThevalueofC
istypicallyabout1pF,andC istypically0.8pFpercentimeterofboardetch;atypical
BD
PHY
BD
board can have 3 pF to 6 pF or more. The load capacitors C9 and C10 combine as capacitors in series so that the
total load capacitance is:
C9 C10
C9 ) C10
C
+
) C
) C
L
PHY
BD
C9
X1
X0
X1
C
+ C
BD
PHY
24.576 MHz
I
S
C10
Figure 8–4. Load Capacitance for the TSB43AB23 PHY
The layout of the crystal portion of the PHY circuit is important for obtaining the correct frequency, minimizing noise
introduced into the PHY phase-lock loop, and minimizing any emissions from the circuit. The crystal and two load
capacitors must be considered as a unit during layout. The crystal and the load capacitors must 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) must then be placed as
close as possible to the PHY X1 and X0 pins to minimize etch lengths, as shown in Figure 8–5.
C9
C10
X1
For more details on crystal selection, see application report SLLA051 available from the TI website:
http://www.ti.com/sc/1394.
Figure 8–5. Recommended Crystal and Capacitor Layout
8.3 Bus Reset
In the TSB43AB23 device, the initiate bus reset (IBR) bit may be set to 1 in order to initiate a bus reset and initialization
sequence. The IBR bit is located in PHY register 1, along with the root-holdoff bit (RHB) and Gap_Count field, as
required by IEEE Std 1394a-2000. Therefore, whenever the IBR bit is written, the RHB and Gap_Count are also
written.
The RHB and Gap_Count may also be updated by PHY-config packets. The TSB43AB23 device is IEEE 1394a-2000
compliant, and therefore both the reception and transmission of PHY-config packets cause the RHB and Gap_Count
to be loaded, unlike older IEEE 1394-1995 compliant PHY devices which decode only received PHY-config packets.
The gap-count is set to the maximum value of 63 after 2 consecutive bus resets without an intervening write to the
Gap_Count, either by a write to PHY register 1 or by a PHY-config packet. This mechanism allows a PHY-config
8–3
packet to be transmitted and then a bus reset initiated so as to verify that all nodes on the bus have updated their
RHBs and Gap_Count values, without having the Gap_Count set back to 63 by the bus reset. The subsequent
connection of a new node to the bus, which initiates a bus reset, then causes the Gap_Count of each node to be set
to 63. Note, however, that if a subsequent bus reset is instead initiated by a write to register 1 to set the IBR bit, all
other nodes on the bus have their Gap_Count values set to 63, while this node Gap_Count remains set to the value
just loaded by the write to PHY register 1.
Therefore, in order to maintain consistent gap-counts throughout the bus, the following rules apply to the use of the
IBR bit, RHB, and Gap_Count in PHY register 1:
•
Following the transmission of a PHY-config packet, a bus reset must be initiated in order to verify that all
nodes have correctly updated their RHBs and Gap_Count values and to ensure that a subsequent new
connection to the bus causes the Gap_Count to be set to 63 on all nodes in the bus. If this bus reset is
initiated by setting the IBR bit to 1, the RHB and Gap_Count field must also be loaded with the correct values
consistent with the just transmitted PHY-config packet. In the TSB43AB23 device, the RHB and Gap_Count
are updated to their correct values upon the transmission of the PHY-config packet, so these values may
first be read from register 1 and then rewritten.
•
•
Other than to initiate the bus reset, which must follow the transmission of a PHY-config packet, whenever
the IBR bit is set to 1 in order to initiate a bus reset, the Gap_Count value must also be set to 63 so as to
be consistent with other nodes on the bus, and the RHB must be maintained with its current value.
The PHY register 1 must not be written to except to set the IBR bit. The RHB and Gap_Count must not be
written without also setting the IBR bit to 1.
8.4 EMI Guidelines
For electromagnetic interference (EMI) guidelines and recommendations send a request via e-mail to
1394–EMI@list.ti.com.
8–4
9 Electrical Characteristics
†
9.1 Absolute Maximum Ratings Over Operating Temperature Ranges
Supply voltage range: REG18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.2 V to 2.2 V
AV
DV
PLLV
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.3 V to 4.0 V
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.3 V to 4.0 V
DD
DD
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.3 V to 4.0 V
DD
V
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.5 V to 5.5 V
DDP
Input voltage range for PCI, V , PHY, and Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . –0.5 to V
+ 0.5 V
+ 0.5 V
I
DD
DD
Output voltage range for PCI, V , PHY, and Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . –0.5 to V
O
Input clamp current, I (V < 0 or V > V ) (see Note 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ±20 mA
IK
OK
I
I
DD
Output clamp current, I
(V < 0 or V > V ) (see Note 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ±20 mA
O O DD
Electrostatic discharge (see Note 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HBM: 2 kV
Continuous total power dissipation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . See Dissipation Rating Table
Operating free-air temperature, T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0°C to 70°C
A
Storage temperature range, T
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –65°C to 150°C
stg
Lead temperature 1,6 mm (1/16 inch) from cage for 10 seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260°C
†
Stresses beyond those listed under absolute maximum ratings may cause permanent damage to the device. These are stress ratings only, and
functionaloperationofthedeviceattheseoranyotherconditionsbeyondthoseindicatedunderrecommendedoperatingconditionsisnotimplied.
Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
NOTES: 1. Applies to external input and bidirectional buffers. For 5-V tolerant use V > V
. For PCI use V > V
DDI
.
I
I
DDP
. For PCI use V > V .
DDP
2. Applies to external output and bidirectional buffers. For 5-V tolerant use V > V
O
DDI
O
3. HBM is human body model, MM is machine model.
DISSIPATION RATING TABLE
§
T
≤ 25°C
DERATING FACTOR
T = 70°C
A
POWER RATING
A
PACKAGE
POWER RATING
ABOVE T = 25°C
A
‡
§
PDT
1.116 W
0.013 W/°C
0.009 W/°C
0.563 W
PDT
0.967 W
0.523 W
‡
§
Standard JEDEC high-K board
Standard JEDEC low-K board
9–1
9.2 Recommended Operating Conditions
TEST
CONDITION
MIN
1.6
NOM
MAX
2.0
UNIT
REG18
1.8
3.3
3.3
3
V
V
V
V
V
Core voltage, AV
DD
3
3
3.6
3.6
3.6
Core voltage, DV
DD
Core voltage, PLLV
2.7
0
DD
Output voltage, V
TTL and LVCMOS terminals
DV
O
DD
3.6
V
V
= 3.3 V
= 5 V
3
3.3
5
PCI I/O clamping voltage,
DDP
V
V
DDP
4.5
5.5
DDP
3.3 V
0.475V
V
DDP
DDP
2
PCI
5 V
V
DDP
†
PC(0–2)
0.7DV
0.6DV
DV
DV
V
High-level input voltage, V
DD
DD
DD
IH
G_RST
DD
2
‡
Miscellaneous
V
DDP
PCI
3.3 V
5 V
0
0
0
0
0
0
0
0
0
0.325V
DDP
PCI
0.8
†
PC(0–2)
G_RST
0.2DV
V
V
Low-level input voltage, V
DD
DD
IL
0.3DV
‡
‡
‡
Miscellaneous
0.8
DDP
DDP
PCI
3.3 V
3.3 V
V
V
Input voltage, V
I
Miscellaneous
PCI
DV
DV
DD
DD
§
Output voltage, V
V
O
Miscellaneous
Input transition time
(t and t ), t
PCI
0
6
ns
r
f
t
Operating free-air
temperature, T
Rθ = 70.82°C/W, T = 70°C
99.3
°C
JA
A
A
Output current, I
TPBIAS outputs
–5.6
1.3
260
mA
O
Cable inputs, during data reception
Cable inputs, during arbitration
118
168
Differential input voltage, V
ID
mV
V
265
TPB cable inputs, source power node
TPB cable inputs, nonsource power node
128-PDT high-K JEDEC board
0.4706
0.4706
2.515
Common-mode input voltage,
¶
V
IC
2.015
119.2
136.9
Rθ = 74.6°C/W, T = 70°C, Pd = 0.6 W
JA
A
Maximum junction
temperature, T
J
°C
ms
ns
128-PDT low-K JEDEC board
Rθ = 101.3°C/W, T = 70°C, Pd = 0.6 W
JA
A
Power-up reset time, t
Receive input jitter
G_RST input
2
pu
TPA, TPB cable inputs, S100 operation
TPA, TPB cable inputs, S200 operation
TPA, TPB cable inputs, S400 operation
±1.08
±0.5
±0.315
†
Applies to external inputs and bidirectional buffers without hysteresis.
Miscellaneous terminals are: GPIO2 (90), GPIO3 (89), SDA (92), SCL (91).
Applies to external output buffers.
‡
§
¶
For a node that does not source power; see Section 4.2.2.2 in IEEE Std 1394a-2000.
9–2
Recommended Operating Conditions (Continued)
TEST
CONDITION
MIN
NOM
MAX
UNIT
Between TPA and TPB cable inputs, S100 operation
Between TPA and TPB cable inputs, S200 operation
Between TPA and TPB cable inputs, S400 operation
±0.8
±0.55
±0.5
Receive input
skew
ns
9.3 Electrical Characteristics Over Recommended Operating Conditions
(unless otherwise noted)
TEST
CONDITIONS
PARAMETER
OPERATION
MIN
MAX
UNIT
I
I
I
I
I
I
= –0.5 mA
= –2 mA
= –4 mA
= 1.5 mA
= 6 mA
0.9DV
DD
OH
OH
OH
OL
OL
OL
PCI
2.4
V
V
High-level output voltage
V
OH
‡
‡
Miscellaneous
DV
–0.6
DD
0.1DV
DD
PCI
0.55
0.5
Low-level output voltage
V
OL
Miscellaneous
Output pins
Input pins
= 4 mA
I
I
3-state output high-impedance
Low-level input current
3.6 V
3.6 V
3.6 V
3.6 V
3.6 V
V
= DV
or GND
±20
±20
µA
µA
OZ
O
DD
V = GND
I
IL
†
I/O pins
V = GND
±20
I
†
PCI
V = DV
±20
I
DD
DD
I
IH
High-level input current
µA
†
Others
V = DV
±20
I
†
‡
For I/O terminals, input leakage (I and I ) includes I
IL IH
of the disabled output.
OZ
Miscellaneous terminals are: GPIO2 (90), GPIO3 (89), SDA (92), SCL (91).
9–3
9.4 Electrical Characteristics Over Recommended Ranges of Operating Conditions
(unless otherwise noted)
9.4.1 Device
PARAMETER
TEST CONDITIONS
See Note 4
MIN
TYP
158
128
69.8
MAX
UNIT
Supply current (internal voltage regulator enabled,
REG_EN = L)
See Note 5
See Note 6
Ports disabled
I
mA
DD
Supply current—ultralow power mode (internal voltage
regulator enabled, REG_EN = L)
I
I
V
T
A
= 1.8 V (internal)
3
mA
DD(ULP)
DD
= 25°C
Ports disabled
= 1.8 V (external)
Supply current—ultralow power mode (internal voltage
regulator disabled, REG_EN = H, REG18 = 1.8 V)
V
50
µA
DD(ULP)
DD
T
= 25°C
A
†
†
V
V
Power status threshold, CPS input
400-kΩ resistor
4.7
7.5
V
V
TH
TPBIAS output voltage
At rated I current
1.665
2.015
O
O
I
Input current (PC0–PC2 inputs)
V
= 3.6 V
5
–20
–20
µA
I
DD
V = 1.5 V
–90
–90
I
I
Pullup current (G_RST input)
µA
IRST
V = 0 V
I
†
Measured at cable power side of resistor.
NOTES: 4. Transmit data (transmit on all ports full isochronous payload of 84 µs, S400, data value of CCCC CCCCh).
5. Repeatdata(receiveononeport, transmitonothertwoports, fullisochronouspayloadof84µs, S400, data value of CCCC CCCCh),
= 3.3 V, T = 25°C
V
DD
A
6. Idle (receive cycle start on one port, transmit cycle start on other two ports), V
= 3.3 V, T = 25°C
DD
A
9.4.2 Driver
PARAMETER
Differential output voltage
TEST CONDITIONS
56 Ω, see Figure 9–1
MIN
MAX
UNIT
mV
mA
mA
mA
mV
V
172
265
OD
‡
§
§
‡
I
I
I
Driver difference current, TPA+, TPA–, TPB+, TPB–
Common-mode speed signaling current, TPB+, TPB–
Common-mode speed signaling current, TPB+, TPB–
Off state differential voltage
Drivers enabled, speed signaling off
S200 speed signaling enabled
S400 speed signaling enabled
Drivers disabled, see Figure 9–1
–1.05
–4.84
–12.4
1.05
–2.53
–8.10
DIFF
§
§
SP200
SP400
V
OFF
20
‡
§
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.
TPAx+
TPBx+
56 Ω
TPAx–
TPBx–
Figure 9–1. Test Load Diagram
9–4
9.4.3 Receiver
PARAMETER
TEST CONDITIONS
Drivers disabled
MIN
TYP
MAX
UNIT
kΩ
pF
4
7
Z
Z
Differential impedance
ID
4
20
kΩ
pF
Common-mode impedance
Drivers disabled
IC
24
30
V
V
V
V
Receiver input threshold voltage
Drivers disabled
Drivers disabled
Drivers disabled
Drivers disabled
–30
0.6
mV
V
TH-R
Cable bias detect threshold, TPBx cable inputs
Positive arbitration comparator threshold voltage
Negative arbitration comparator threshold voltage
1.0
168
–89
TH-CB
+
89
mV
mV
TH
TH
–
–168
TPBIAS–TPA common mode
voltage, drivers disabled
V
Speed signal threshold
Speed signal threshold
49
131
396
mV
mV
TH–SP200
TH–SP400
TPBIAS–TPA common mode
voltage, drivers disabled
V
314
9.5 Thermal Characteristics
PARAMETER
TEST CONDITIONS
MIN
TYP
MAX
74.6
UNIT
°C/W
°C/W
°C/W
128-PDT
128-PDT
128-PDT
Rθ
Rθ
Rθ
high-K board
low-K board
JA,
JA,
JC
101.3
18.7
Board mounted, no air flow, JEDEC test board
9.6 Switching Characteristics for PHY Port Interface
PARAMETER
TEST CONDITIONS
MIN
TYP
MAX
±0.15
±0.10
1.2
UNIT
ns
Jitter, transmit
Skew, transmit
Between TPA and TPB
Between TPA and TPB
ns
t
t
TP differential rise time, transmit
TP differential fall time, transmit
10% to 90%, at 1394 connector
90% to 10%, at 1394 connector
0.5
0.5
ns
r
1.2
ns
f
9.7 Operating, Timing, and Switching Characteristics of XI
PARAMETER
MIN
TYP
MAX
UNIT
V
DD
V
IH
V
IL
3.0
3.3
3.6 V (PLLV
V
)
DD
High-level input voltage
Low-level input voltage
Input clock frequency
Input clock frequency tolerance
Input slew rate
0.63V
DD
0.33V
V
DD
24.576
MHz
PPM
V/ns
<100
4
0.2
Input clock duty cycle
40%
60%
†
9.8 Switching Characteristics for PCI Interface
PARAMETER
MEASURED
–50% to 50%
–50% to 50%
–50% to 50%
MIN
7
TYP
MAX
UNIT
t
t
t
Setup time before PCLK
Hold time before PCLK
ns
ns
ns
su
0
h
Delay time, PCLK to data valid
2
11
val
†
These parameters are ensured by design.
9–5
10 Mechanical Information
The TSB43AB23 device is packaged in a 128-terminal PDT package. The following shows the mechanical
dimensions for the PDT package.
PDT (S-PQFP-G128)
PLASTIC QUAD FLATPACK
0,23
0,13
M
0,40
96
0,05
65
64
97
33
128
0,13 NOM
1
32
12,40 TYP
Gage Plane
14,05
SQ
13,95
0,25
16,10
SQ
0,05 MIN
15,90
0°–ā5°
1,05
0,95
0,75
0,45
Seating Plane
0,08
1,20 MAX
4087726/A 11/95
NOTES: A. All linear dimensions are in millimeters.
B. This drawing is subject to change without notice.
C. Falls within JEDEC MO-136
10–1
PGE (S-PQFP-G144)
PLASTIC QUAD FLATPACK
108
73
109
72
0,27
0,17
M
0,08
0,50
0,13 NOM
144
37
1
36
Gage Plane
17,50 TYP
20,20
SQ
19,80
0,25
0,05 MIN
22,20
SQ
0°–ā7°
21,80
0,75
0,45
1,45
1,35
Seating Plane
0,08
1,60 MAX
4040147/C 10/96
NOTES: A. All linear dimensions are in millimeters.
B. This drawing is subject to change without notice.
C. Falls within JEDEC MS-026
10–2
相关型号：
TSB43AB23IPDTEP
Enhanced Product Ieee 1394A-2000 Ohci Phy/Link Layer Controller 128-TQFP -40 to 85
TI
©2020 ICPDF网 联系我们和版权申明