Datasheet
Table Of Contents
- 1 Introduction
- Table of Contents
- 2 Pin Descriptions
- 3 Configuration
- 4 Interfaces
- 5 Architecture
- 6 Reset and Power Down Operation
- 7 Design Guidelines
- 8 Register Block
- 8.1 Register Definition
- 8.1.1 Basic Mode Control Register (BMCR)
- 8.1.2 Basic Mode Status Register (BMSR)
- 8.1.3 PHY Identifier Register #1 (PHYIDR1)
- 8.1.4 PHY Identifier Register #2 (PHYIDR2)
- 8.1.5 Auto-Negotiation Advertisement Register (ANAR)
- 8.1.6 Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page)
- 8.1.7 Auto-Negotiate Expansion Register (ANER)
- 8.1.8 Auto-Negotiate Next Page Transmit Register (ANNPTR)
- 8.1.9 Auto-Negotiation Link Partner Ability Next Page Register (ANLNPTR)
- 8.2 Register Control Register (REGCR)
- 8.3 Address or Data Register (ADDAR)
- 8.4 Extended Registers
- 8.4.1 PHY Control Register (PHYCR)
- 8.4.2 PHY Status Register (PHYSR)
- 8.4.3 MII Interrupt Mask Register (MINTMR)
- 8.4.4 MII Interrupt Status Register (MINTSR)
- 8.4.5 MII Interrupt Control Register (MINTCR)
- 8.4.6 Receiver Error Counter Register (RECR)
- 8.4.7 BIST Control Register (BISCR)
- 8.4.8 BIST STATUS Register (BISSR)
- 8.4.9 BIST Byte Count Register (BISBCR)
- 8.4.10 BIST Error Count Register (BISECR)
- 8.4.11 BIST Packet Length Register (BISPLR)
- 8.4.12 BIST Inter Packet Gap Register (BISIPGR)
- 8.4.13 LED Direct Control Register (LEDCR)
- 8.4.14 Power Down Register (PDR)
- 8.4.15 False Carrier Sense Counter Register (FCSCR)
- 8.4.16 RX Channel Control Register (RXCCR)
- 8.5 Cable Diagnostic Registers
- 8.5.1 Cable Diagnostic Registers (CDCR)
- 8.5.2 Cable Diagnostic Status Register (CDSR)
- 8.5.3 Cable Diagnostic Results Register (CDRR)
- 8.5.4 TDR State Machine Enable (TDRSMR)
- 8.5.5 TDR Pattern Amplitude Register (TDRPAR)
- 8.5.6 TDR Manual Pulse Register (TDRMPR)
- 8.5.7 TDR Channel Silence Register (TDRCSR)
- 8.5.8 TDR Control Register (TDRCR)
- 8.5.9 TDR Clock Cycles Register (TDRLCR)
- 8.5.10 TDR Low Threshold Register (TDRLT1)
- 8.5.11 TDR Low Threshold Register (TDRLT2)
- 8.5.12 TDR Low Threshold Register (TDRLT3)
- 8.5.13 TDR Low Threshold Register (TDRLT4)
- 8.5.14 TDR High Threshold Register (TDRHT1)
- 8.5.15 TDR High Threshold Register (TDRHT2)
- 8.5.16 TDR High Threshold Register (TDRHT3)
- 8.5.17 TDR High Threshold Register (TDRHT4)
- 8.5.18 TDR Pattern Control Register 1 (TDRLCR1)
- 8.5.19 TDR Pattern Control Register 2 (TDRLCR2)
- 8.5.20 DSA Configuration Register 1 (DSACR1)
- 8.5.21 DSA Configuration Register 2 (DSACR2)
- 8.5.22 DSA Start Frequency (DSASFR)
- 8.5.23 DSA Frequency Control (DSAFCR)
- 8.5.24 DSA Output Control (DSAOCR)
- 8.5.25 RAM Control 1 (RAMCR1)
- 8.5.26 RAM Control 2 (RAMCR2)
- 8.5.27 RAM Data Out (RAMDR)
- 8.5.28 CD Pre Test Configuration Control 1 (CDPTC1R)
- 8.5.29 CD Pre Test Configuration Control 2 (CDPTC2R)
- 8.5.30 LPF Bypass (LPFBR)
- 8.1 Register Definition
- 9 Electrical Specifications
- 10 Appendix A: Digital Spectrum Analyzer (DSA) Output
- Revision History

TLK100
SLLS931B–AUGUST 2009–REVISED DECEMBER 2009
www.ti.com
5.2.10 Signal Detect
The signal detect function of the TLK100 is incorporated to meet the specifications mandated by the
ANSIFDDI TP-PMD Standard as well as the IEEE 802.3 100BASE-TX Standard for both voltage
thresholds and timing parameters.
The energy-detector module provides signal-strength indication in various scenarios. Because it is based
on an IIR filter, this robust energy detector has excellent reaction time and reliability. The filter output is
compared to predefined thresholds in order to decide the presence or absence of an incoming signal.
The energy detector also implements hysteresis to avoid jittering in the signal-detect indication. In addition
it has fully-programmable thresholds and listening-time periods, enabling shortening of the reaction time if
required.
5.2.11 Bad SSD Detection
A Bad Start of Stream Delimiter (Bad SSD) is any transition from consecutive idle code-groups to non-idle
code-groups which is not prefixed by the code-group pair /J/K. If this condition is detected, the TLK100
asserts MII_RX_ERR presents MII_RXD[3:0] = 1110 to the MII for the cycles that correspond to received
5B code-groups until at least two IDLE code groups are detected. In addition, the FCSCR register (0x42h)
is incremented by one for every error in the nibble.
When at least two IDLE code groups are detected, RX_ER and MII_CRS become de-asserted.
5.3 10M Squelch
The squelch feature determines when valid data is present on the differential receive inputs. The TLK100
implements a squelch to prevent impulse noise on the receive inputs from being mistaken for a valid
signal. Squelch operation is independent of the 10BASE-T operating mode. The squelch circuitry employs
a combination of amplitude and timing measurements (as specified in the IEEE 802.3 10BASE-T
standard) to determine the validity of data on the twisted-pair inputs.
The signal at the start of a packet is checked by the squelch, and any pulses not exceeding the squelch
level (either positive or negative, depending upon polarity) are rejected. When this first squelch level is
exceeded correctly, the opposite squelch level must then be exceeded no earlier than 50ns. Finally, the
signal must again exceed the original squelch level no earlier than 50ns to qualify as a valid input
waveform, and not be rejected. This checking procedure results in the typical loss of three preamble bits
at the beginning of each packet. When the transmitter is operating, five consecutive transitions are
checked before indicating that valid data is present. At this time, the squelch circuitry is reset.
5.3.1 Collision Detection
When in Half-Duplex mode, a 10BASE-T collision is detected when receive and transmit channels are
active simultaneously. Collisions are reported by the MII_COL signal on the MII.
The MII_COL signal remains set for the duration of the collision. If the PHY is receiving when a collision is
detected, it is reported immediately (through the MII_COL pin).
5.3.2 Carrier Sense
Carrier Sense (MII_CRS) may be asserted due to receive activity after valid data is detected via the
squelch function. For 10Mb/s Half Duplex operation, MII_CRS is asserted during either packet
transmission or reception. For 10Mb/s Full Duplex operation, MII_CRS is asserted only during receive
activity.
MII_CRS is de-asserted following an end-of-packet.
30 Architecture Copyright © 2009, Texas Instruments Incorporated
Submit Documentation Feedback
Product Folder Link(s): TLK100