SLLSEE3D August 2013 – April 2016 TLK105L , TLK106L
PRODUCTION DATA.
This section includes information on the various configuration options available with the TLK10xL. The configuration options described below include:
|
|
Bootstrap configuration is a convenient way to configure the TLK10xL into specific modes of operation. Some of the functional pins are used as configuration inputs. The logic states of these pins are sampled during reset and are used to configure the device into specific modes of operation. The table below describes bootstrap configuration.
A 2.2kΩ resistor is used for pull-down or pull-up to change the default configuration. If the default option is desired, then there is no need for external pull-up or pull down resistors. Because these pins may have alternate functions after reset is deasserted, they must not be connected directly to VCC or GND.
PIN | TYPE | |||||||
---|---|---|---|---|---|---|---|---|
NAME | NO. | DESCRIPTION | ||||||
PHYAD0 (COL) PHYAD1 (RXD_0) PHYAD2 (RXD_1) PHYAD3 (RXD_2) PHYAD4 (RXD_3) |
29 30 31 32 1 |
S, O, PD / PU | PHY Address [4:0]: The TLK10xL provides five PHY address pins, the states of which are latched into an internal register at system hardware reset. The TLK10xL supports PHY Address values 0 (<00000>) through 31 (<11111>). PHYAD[4:1] pins have weak internal pull-down resistors, and PHYAD[0] has weak internal pull-up resistor, setting the default PHYAD if no external resistors are connected. | |||||
AN_0 (LED_LINK) |
17 | S, O, PU |
AN_0: FD-HD config. FD = pull up. The default wake-up is auto negotiation enable 100BT. |
|||||
LED_CFG (CRS) | 27 | S, O, PU | LED Configuration: This option selects the operation mode of the LED LINK pin. Default is Mode 1. All modes are also configurable via register access. See PHY Control Register (PHYCR), Address 0x0019. | |||||
AMDIX_EN (RX_ER) | 28 | S, O, PU | Auto-MDIX Enable: This option sets the Auto-MDIX mode. By default, it enables Auto-MDIX. An external pull-down resistor disables Auto-MDIX mode. | |||||
MII_MODE (RX_DV) | 26 | S, O, PD | MII Mode Select: This option selects the operating mode of the MAC data interface. This pin has a weak internal pull-down, and it defaults to normal MII operation mode. An external pull-up causes the device to operate in RMII mode. |
The TLK10xL provides best-in-class flexibility of power supplies.
If a single 3.3V power supply is desired, the TLK10xL internal regulator provides the necessary core supply voltages. Ceramic capacitors of 10µf and 0.1µf should be placed close to the PFBOUT (pin 15) which is the output of the internal regulator. The PFBOUT pin should be connected to the PFBIN1 and PFBIN2 on the board. A small capacitor of 0.1µF should be placed close to the PFBIN1 (pin 13) and PFBIN2 (pin 24). To operate in this mode, connect the TLK10xL supply pins as shown in Figure 5-1.
When a 1.55V external power rail is available, the TLK10xL can be configured as shown in Figure 5-2. PFBOUT (pin 15) is left floating. The 1.55V external supply is connected to PFBIN1 (pin 13) and PFBIN2 (pin 24). Furthermore, to lower the power consumption, the internal regulator should be powered down by writing ‘1’ to bit 15 of the VRCR register (0x00d0h).
When operating with dual supplies, follow these guidelines:
The TLK10xL digital IO pins can operate with a variable supply voltage. While the primary applications will use 3.3V, VDD_IO can also operate on 2.5V, and for MII mode only, VDD_IO of 1.8V can be used as well. For more details, see Section 4.6.
The following IO or output pins are in hi-Z state when RESET is active (Low).
PIN NAME | TYPE | INTERNAL PU/PD | PIN NAME | TYPE | Internal PU/PD | |
---|---|---|---|---|---|---|
TXD_3 | IO | PD | COL (MLED(1)) | IO | PU | |
TX_EN | IO | PD | RXD_0 | IO | PD | |
INT/PWDN | IO | PU | RXD_1 | IO | PD | |
LED_LINK (MLED(1)) | IO | PU | RXD_2 | IO | PD | |
MDIO | IO | RXD_3 | IO | PD | ||
RX_DV | IO | PD | TX_CLK | O | ||
CRS | IO | PU | RX_CLK | O | ||
RX_ER | IO | PU |
The TLK10xL device auto-negotiates to operate in 10Base-T or 100Base-TX. With Auto-Negotiation enabled, the TLK10xL negotiates with the link partner to determine the speed and duplex mode. If the link partner cannot Auto-Negotiate, the TLK10xL device enters parallel-detect mode to determine the speed of the link partner. Parallel-detect mode uses fixed half-duplex mode.
The TLK10xL supports four different Ethernet protocols (10Mbs Half-Duplex, 10Mbs Full-Duplex, 100Mbs Half-Duplex, and 100Mbs Full-Duplex). Auto-Negotiation selects the highest performance protocol based on the advertised ability of the Link Partner. Control the Auto-Negotiation function within the TLK10xL by internal register access according to the IEEE specification.
Alternatively, control the HD-FD functionality by configuring the AN_0 pins. The state of AN_0 selects full or half duplex mode, both in Auto-negotiation or force 100/10 mode as given in Table 5-2. The state of AN_0 upon power-up/reset, determines the state of bits [8:5] of the ANAR register (0x04h).
Auto-Negotiation advertises ANEN, 100BT by default. Full-Duplex or Half-Duplex configuration is available through the AN_0 bit. Internal register access configures the device for a specific mode.
AN_0 | FORCED MODE |
---|---|
0 | 10Base-T, Half-Duplex 100Base-TX, Half-Duplex |
1 | 10Base-T, Half or Full-Duplex 100Base-TX, Half or Full-Duplex |
Internal register access controls the Auto-Negotiation function, as defined by the IEEE 802.3u specification. For further detail regarding Auto-Negotiation, see Clause 28 of the IEEE 802.3u specification.
The TLK10xL device automatically determines whether or not it needs to cross over between pairs, eliminating the requirement for an external crossover cable. If the TLK10xL interoperates with a device that implements MDI/MDIX crossover, a random algorithm as described in IEEE 802.3 determines which device performs the crossover.
Auto-MDIX is enabled by default and can be configured via pin strap, control register CR1 (0x09h), bit 14 or via register PHYCR (0x19h), bit 15.
The crossover can be manually forced through bit 14 of the PHYCR (0x19h) register. Neither Auto-Negotiation nor Auto-MDIX is required to be enabled in forcing crossover of the MDI pairs.
Auto-MDIX can be used in the forced 100Base-TX mode. Because in modern networks all the nodes are 100Base-TX, having the Auto-MDIX working in the forced 100Base-TX mode resolves the link faster without the need for the long Auto-Negotiation period.
The TLK10xL can be put into MII-Isolate mode by writing bit 10 of the BMCR register.
When in the MII-Isolate mode, the TLK10xL ignores packet data present at the TXD[3:0], TX_EN inputs, and presents a high impedance on the TX_CLK, RX_CLK, RX_DV, RX_ER, RXD[3:0], COL, and CRS outputs. When in isolate mode, the TLK10xL continues to respond to all management transactions.
When in isolate mode, the PMD output pair does not transmit packet data, but continues to source 100Base-TX scrambled idles or 10Base-T normal link pulses. The TLK10xL can auto-negotiate or parallel detect on the receive signal at the PMD input pair. A valid link can be established for the receiver even when the TLK10xL is in Isolate mode.
The 5 PHY address inputs pins are shared with the RXD[3:0] pins and COL pin as shown in Table 5-3.
PIN Number | PHYAD FUNCTION | RXD FUNCTION |
---|---|---|
29 | PHYAD0 | COL |
30 | PHYAD1 | RXD_0 |
31 | PHYAD2 | RXD_1 |
32 | PHYAD3 | RXD_2 |
1 | PHYAD4 | RXD_3 |
Each TLK10xL or port sharing an MDIO bus in a system must have a unique physical address. With 5 address input pins, the TLK10xL can support PHY Address values 0 (<00000>) through 31 (<11111>). The address-pin states are latched into an internal register at device power-up and hardware reset. Because all the PHYAD[4:0] pins have weak internal pull-down/up resistors, the default setting for the PHY address is 00001 (0x01h).
See Figure 5-3 for an example of a PHYAD connection to external components. In this example, the PHYAD configuration results in address 00011 (0x03h).
By default, the TLK10xL supports one light emitting diode (LED) - LINK_LED, pin 17. In addition, the TLK10xL supports by register access a multi-configurable LED (MLED). The MLED is not activated by default, but by register access it can be routed through either pin 17 (allowing more configuration options for pin 17), or pin 29 supporting two simultaneous LEDs (LED_LINK on pin 17 & MLED on pin 29). When MLED is routed to the COL pin (pin 29) the COL functionality is disabled. REG 0x0025 (MLEDCR Register) controls the MLED routing and configurations. The different MLED modes are configured by bits [6:3] as described in Table 5-4.
(BIT 6:3) |
MODE | (BIT 6:3) | MODE | |
---|---|---|---|---|
0x0 | Link OK | 0x6 | LED Speed: High for 10 Base TX | |
0x1 | RX/TX Activity | 0x7 | Full Duplex | |
0x2 | TX Activity | 0x8 | Link OK / Blink on TX/RX Activity | |
0x3 | RX Activity | 0x9 | Active stretch signal | |
0x4 | Collision | 0xA | MI_LINK (100BT+FD) | |
0x5 | LED Speed: High for 100 Base TX |
As mentioned before, by default the TLK10xL is pin compatible to the TLK105, and the default LED output is LED_LINk on pin 17. The LED can be controlled by configuration pin and internal register bits. Bit 5 of the PHY Control register (PHYCR) selects the LED mode as described in Table 5-5.
MODE | LED_CFG[0] (BIT 5) or (PIN 27) |
LED_LINK |
---|---|---|
1 | 1 | ON for Good Link OFF for No Link |
2 | 0 | ON for Good Link BLINK for Activity |
The LED_LINK pin in Mode 1 indicates the link status of the port. The LED is OFF when no link is present. In Mode 2 it is ON to indicate that the link is good; BLINK indicates that activity is present on either transmit or receive channel. Bits 10:9 of the LEDCR register (0x18) control the blink rate. The default blink rate is 5Hz. Enabling Enhanced LED Link via the CR2 register (0x0A) bit 4 overrides the LED blinking functionality of the PHYCR register (0x0019) bit 5. The Link LED will not blink for activity when Enhanced LED Link is enabled.
See Figure 5-4 for an example of AN0 connections to external components. In this example, the AN0 configuration results in Full-Duplex advertised.
The TLK10xL provides several options for Loopback that test and verify various functional blocks within the PHY. Enabling loopback mode allows in-circuit testing of the TLK10xL digital and analog data path. Generally, the TLK10xL may be configured to one of the Near-end loopback modes or to the Far-end (reverse) loopback.
Near-end loopback provides the ability to loop the transmitted data back to the receiver via the digital or analog circuitry. The point at which the signal is looped back is selected using loopback control bits with several options being provided. Figure 5-5 shows the PHY near-end loopback functionality.
The Near-end Loopback mode is selected by setting the respective bit in the BIST Control Register (BISCR), MII register address 0x0016. MII loopback can be selected by using the BMCR register at address 0x0000, bit [14].
The Near-end Loopback can be selected according to the following:
Table 5-6 describes the available operational modes for each loop mode:
LOOP MODE | MII | PCS INPUT | PCS OUTPUT | DIGITAL | ANALOG(1) | EXTERNAL |
---|---|---|---|---|---|---|
Operational Setting | Force/ANEG 100/10 | Force 100/10 | Force 100 | Force 100 | Force 10/100 ANEG 10 | Force/ANEG 100/10 |
Operational MAC int. | MII Only | MII or RMII | MII or RMII | MII or RMII | MII or RMII | MII or RMII |
While in MII Loopback mode, there is no link indication, but packets propagate back to the MAC. While in MII Loopback mode the data is looped back, and can also be transmitted onto the media. For transmitting data during MII loopback in 100BT only please use bit [6] in the BISCR Register address 0x0016. For proper operation in Analog Loopback mode, attach 100Ω terminations to the RJ45 connector. External Loopback can be performed while working in normal mode (Bits 3:0 of the BISCR register are asserted to 0, and on the RJ45 connector, pin 1 is connected to pin 3 and pin 2 is connected to pin 6). To maintain the desired operating mode, Auto-Negotiation should be disabled before selecting Loopback mode. This constraint does not apply for external-loopback mode. For selected loopback Delay propagation timing please see Section 4.9.21.
Far-end (Reverse) loopback is a special test mode to allow testing the PHY from the link-partner side. In this mode, data that is received from the link partner passes through the PHY's receiver, looped back on the MII and transmitted back to the link partner. Figure 5-6 shows Far-end loopback functionality.
The Reverse Loopback mode is selected by setting bit 4 in the BIST Control Register (BISCR), MII register address 0x0016.
While in Reverse Loopback mode the data is looped back and also transmitted onto the MAC Interface and all data signals that come from the MAC are ignored.
Table 5-7 describes the operating modes for Far-End Loopback.
OPERATIONAL MAC INT. | MII MODE | RMII MODE |
---|---|---|
Operational Setting | Force/ANEG 10/100 | Force/ANEG 10 |
The device incorporates an internal PRBS Built-in Self Test (BIST) circuit to accommodate in-circuit testing or diagnostics. The BIST circuit can be used to test the integrity of the transmit and receive data paths. The BIST can be performed using both internal loopback (digital or analog) or external loopback using a cable fixture. The BIST simulates pseudo-random data transfer scenarios in format of real packets and Inter-Packet Gap (IPG) on the lines. The BIST allows full control of the packet lengths and of the IPG.
The BIST is implemented with independent transmit and receive paths, with the transmit block generating a continuous stream of a pseudo-random sequence. The device generates a 15-bit pseudo-random sequence for the BIST. The received data is compared to the generated pseudo-random data by the BIST Linear Feedback Shift Register (LFSR) to determine the BIST pass/fail status. The number of error bytes that the PRBS checker received is stored in the BICSR1 register (0x001Bh). The status of whether the PRBS checker is locked to the incoming receive bit stream, whether the PRBS has lost sync, and whether the packet generator is busy, can be read from the BISCR register (0x0016h). While the lock and sync indications are required to identify the beginning of proper data reception, for any link failures or data corruption, the best indication is the contents of the the error counter in the BICSR1 register (0x001Bh).
The PRBS test can be put in a continuous mode or single mode by using bit 14 of the BISCR register (0x0016h). In continuous mode, when one of the PRBS counters reaches the maximum value, the counter starts counting from zero again. In single mode, when the PRBS counter reaches its maximum value, the PRBS checker stops counting.
The device allows the user to control the length of the PRBS packet. By programming the BICSR2 register (0x001Ch) one can set the length of the PRBS packet. There is also an option to generate a single-packet transmission of two types, 64 and 1518 bytes, through register bit 13 of the BISCR register (0x0016h). The single generated packet is composed of a constant data.
With the vast deployment of Ethernet devices, the need for reliable, comprehensive and user-friendly cable diagnostic tool is more important than ever. The wide variety of cables, topologies, and connectors deployed results in the need to non-intrusively identify and report cable faults. The TI cable-diagnostic unit provides extensive information about cable integrity.
The TLK10xL offers the following capabilities in its Cable Diagnostic tools kit:
The TLK10xL uses Time Domain Reflectometry (TDR) to determine the quality of the cables, connectors, and terminations in addition to estimating the cable length. Some of the possible problems that can be diagnosed include opens, shorts, cable impedance mismatch, bad connectors, termination mismatches, cross faults, cross shorts and any other discontinuities along the cable.
The TLK10xL transmits a test pulse of known amplitude (1V or 2.5V) down each of the two pairs of an attached cable. The transmitted signal continues down the cable and reflects from each cable imperfection, fault, bad connector, and from the end of the cable itself. After the pulse transmission the TLK10xL measures the return time and amplitude of all these reflected pulses. This technique enables measuring the distance and magnitude (impedance) of non-terminated cables (open or short), discontinuities (bad connectors), and improperly-terminated cables with ±1m accuracy.
The TLK10xL also uses data averaging to reduce noise and improve accuracy. The TLK10xL can record up to five reflections within the tested pair. If more than 5 reflections are recorded, the TLK10xL saves the first 5 of them. If a cross fault is detected, the TDR saves the first location of the cross fault and up to 4 reflections in the tested channel. The TLK10xL TDR can measure cables up to 200m in length.
For all TDR measurements, the transformation between time of arrival and physical distance is done by the external host using minor computations (such as multiplication, addition and lookup tables). The host must know the expected propagation delay of the cable, which depends, among other things, on the cable category (for example, CAT5, CAT5e, or CAT6).
TDR measurement is allowed in the TLK10xL in the following scenarios:
The TLK10xL also supports Active Link Cable Diagnostic (ALCD). The ALCD offers a passive method to estimate the cable length during active link. The ALCD uses passive digital signal processing based on adapted data, thus enabling measurement of cable length with an active link partner.
The ALCD Cable length measurement accuracy is ±5m for the pair used in the Rx path (due to the passive nature of the test, only the receive path is measured).
The TLK10xL Fast Ethernet transceiver is a physical layer core for Ethernet 100Base-TX and 10Base-T applications. The TLK10xL contains all the active circuitry required to implement the physical layer functions to transmit and receive data on standard CAT 3 and 5 unshielded twisted pair. The core supports the IEEE 802.3 Standard Fast Media Independent Interface (MII), as well as the Reduced Media Independent Interface (RMII), for direct connection to a MAC/Switch port.
The TLK10xL uses mixed signal processing to perform equalization, data recovery and error correction to achieve robust and low power operation over the existing CAT 5 twisted pair wiring. The TLK10xL architecture not only meets the requirements of IEEE802.3, but maintains a high level of margin over the IEEE requirements for NEXT, Alien and External noise.
In 100Base-TX, the MAC feeds the 100Mbps transmit data in 4-bit wide nibbles through the MII interface. The data is encoded into 5-bit code groups, encapsulated with control code symbols and serialized. The control-code symbols indicate the start and end of the frame and code other information such as transmit errors. When no data is available from the MAC, IDLE symbols are constantly transmitted. The serialized bit stream is fed into a scrambler. The scrambled data stream passes through an NRZI encoder and then through an MLT3 encoder. Finally, it is fed to the DAC and transmitted through one of the twisted pairs of the cable.
According to IEEE 802.3:
“If TX_EN is de-asserted on an odd nibble boundary, PHY should extend TX_EN by one TX_CLK cycle and behave as if TX_ER were asserted during that cycle”.
The TLK10xL supports Error Forwarding in MII transmission from the MAC to the PHY. Error forwarding allows adding information to the frame to be used as an error code between the 2 MACs. The error code informs the receiving MAC on the link partner side of the reason for the error from the transmitting side. If the MAC transmits an odd number of nibbles, an additional error nibble is added to the transmitted frame just before the end of the transmission.To turn off Transmit Error Forwarding, write to bit 1 of register CR2 (0x000A). If Error Forwarding is disabled, delivered packets contain either odd or even numbers of nibbles.
In Figure 5-8, Error Code Forwarding functionality is illustrated. The wave diagram demonstrates MAC’s transmitted signals in one side and MAC’s reception signals on link partner side.
The transmit data that is received from the MAC first passes through the 4-Bit to 5-Bit encoder. This block encodes 4-bit nibble into 5-bit code-groups according to the Table 5-8. Each 4-bit data nibble is mapped to 16 of the 32 possible code-groups. The remaining 16 code-groups are either used for control information or they are considered as not valid.
The code-group encoder substitutes the first 8-bits of the MAC preamble with a J/K code-group pair (11000 10001) upon transmission. The code-group encoder continues to replace subsequent 4-bit preamble and data nibbles with corresponding 5-bit code-groups. At the end of the transmit packet, upon the de-assertion of Transmit Enable signal from the MAC, the code-group encoder adds the T/R code-group pair (01101 00111) indicating the end of the frame.
After the T/R code-group pair, the code-group encoder continuously adds IDLEs into the transmit data stream until the next transmit packet is detected.
4-BIT CODE | SYMBOL | 5-BIT CODE | RECEIVER INTERPRETATION |
---|---|---|---|
0000 | 0 | 11110 | Data |
0001 | 1 | 01001 | |
0010 | 2 | 10100 | |
0011 | 3 | 10101 | |
0100 | 4 | 01010 | |
0101 | 5 | 01011 | |
0110 | 6 | 01110 | |
0111 | 7 | 01111 | |
1000 | 8 | 10010 | |
1001 | 9 | 10011 | |
1010 | A | 10110 | |
1011 | B | 10111 | |
1100 | C | 11010 | |
1101 | D | 11011 | |
1110 | E | 11100 | |
1111 | F | 11101 | |
IDLE AND CONTROL CODES | |||
DESCRIPTION | Symbol(1) | 5-Bit Code | |
Inter-Packet IDLE | I | 11111 | IDLE |
First nibble of SSD | J | 11000 | First nibble of SSD, translated to "0101" following /I/ (IDLE), else RX_ER asserted high |
Second nibble of SSD | K | 10001 | Second nibble of SSD, translated to "0101" following /J/, else RX_ER asserted high |
First nibble of ESD | T | 01101 | First nibble of ESD, causes de-assertion of CRS if followed by /R/, else assertion of RX_ER |
Second nibble of ESD | R | 00111 | Second nibble of ESD, causes de-assertion of CRS if following /T/, else assertion of RX_ER |
Transmit Error Symbol | H | 00100 | RX_ER |
Invalid Symbol | V | 00000 | INVALID
RX_ER asserted high If during RX_DV |
V | 00001 | ||
V | 00010 | ||
V | 00011 | ||
V | 00101 | ||
V | 00110 | ||
V | 01000 | ||
V | 01100 |
The purpose of the scrambler is to flatten the power spectrum of the transmitted signal, thus reduce EMI. The scrambler seed is generated with reference to the PHY address so that multiple PHYs that reside within the system will not use the same scrambler sequence.
To comply with the TP-PMD standard for 100Base-TX transmission over CAT-5 unshielded twisted pair cable, the scrambled data must be NRZI encoded. The serial binary data stream output from the NRZI encoder is further encoded to MLT-3. MLT-3 is a tri-level code where a change in the logic level represents a code bit '1' and the logic output remaining at the same level represents a code bit '0'.
The multipurpose programmable transmit Digital to Analog Converter (DAC) receives digital coded symbols and generates filtered analog symbols to be transmitted on the line. In 100B-TX the DAC applies a low-pass shaping filter to minimize EMI. The DAC is designed to improve the return loss requirements and enable the use of low-cost transformers.
Digital pulse-shape filtering is also applied in order to conform to the pulse masks defined by standard and to reduce EMI and high frequency signal harmonics.
In 100B-TX, the ADC sampled data is passed to an adaptive equalizer. The adaptive equalizer drives the received symbols to the MLT3 decoder. The decoded NRZ symbols are transferred to the descrambler block for descrambling and deserialization.
The Receiver Analog Front End (AFE) resides in front of the 100B-TX receiver. The AFE consists of an Analog to Digital Converter (ADC), receive filters and a Programmable Gain Amplifier (PGA).
The ADC samples the input signal at the 125MHz clock recovered by the timing loop and feeds the data into the adaptive equalizer. The ADC is designed to optimize the SNR performance at the receiver input while maintaining high power-supply rejection ratio and low power consumption. There is only one ADC in the TLK10xL, which receives the analog input data from the relevant cable pair, according to MDI-MDIX resolution.
The PGA, digitally controlled by the adaptive equalizer, fully uses the dynamic range of the ADC by adjusting the incoming-signal amplitude. Generally, the PGA attenuates short-cable strong signals and amplifies long-cable weak signals.
The adaptive equalizer removes Inter-Symbol Interference (ISI) from the received signal introduced by the channel and analog Tx/Rx filters. The TLK10xL includes both Feed Forward Equalization (FFE) and Decision Feedback Equalization (DFE). The combination of both adaptive modules with the adaptive gain control results in a powerful equalizer that can eliminate ISI and compensate for cable attenuation for longer-reach cables. In addition, the Equalizer includes a Shift Gear Step mechanism to provide fast convergence on the one hand and small residual-adaptive noise in steady state on the other hand.
The DC offset of the transmitted signal is shifted down or up based on the polarity of the transmitted data because the MLT-3 data is coupled onto the CAT 5 cable through a transformer that is high-pass in nature. This phenomenon is called Baseline wander. To prevent corruption of the received data because of this phenomenon, the receiver corrects the baseline wander and can receive the ANSI TP-PMD-defined "killer packet" with no bit errors.
The TLK10xL decodes the MLT-3 information from the Digital Adaptive Equalizer block to binary NRZI data. The NRZI-to-NRZ decoder is used to present NRZ-formatted data to the descrambler.
The descrambler is used to descramble the received NRZ data. The data is further deserialized and the parallelized data is aligned to 5-bit code-groups and mapped into 4-bit nibbles. At initialization, the 100B-TX descrambler uses the IDLE-symbols sequence to lock on the far-end scrambler state. During that time, neither data transmission nor reception is enabled. After the far-end scrambler state is recovered, the descrambler constantly monitors the data and checks whether it still synchronized. If, for any reason, synchronization is lost, the descrambler tries to re-acquire synchronization using the IDLE symbols.
The code-group decoder functions as a look up table that translates incoming 5-bit code-groups into 4-bit nibbles. The code-group decoder first detects the Start of Stream Delimiter (SSD) /J/K/ code-group pair preceded by IDLE code-groups at the start of a packet. Once the code group alignment is determined, it is stored and used until the next start-of-frame. The decoder replaces the /J/K/ with the MAC preamble. Specifically, the /J/K/ 10-bit code-group pair is replaced by the nibble pair (0101 0101). All subsequent 5-bit code-groups are converted to the corresponding 4-bit nibbles for the duration of the entire packet. This conversion ceases upon the detection of the /T/R/ code-group pair denoting the End-of-Stream Delimiter (ESD) or with the reception of a minimum of two IDLE code-groups.
The receiver must lock on the far-end transmitter clock in order to sample the data at the optimum timing. The timing loop recovers the far-end clock frequency and offset from the received data samples and tracks instantaneous phase drifts caused by timing jitter.
The TLK10xL has a robust adaptive-timing loop (Tloop) mechanism that is responsible for tracking the Far-End TX clock and adjusting the AFE sampling point to the incoming signal. The Tloop implements an advanced tracking mechanism that when combined with different available phases, always keeps track of the optimized sampling point for the data, and thus offers a robust RX path,tolerant to both PPM and Jitter. The TLK10xL is capable of dealing with PPM and jitter at levels far higher than those defined by the standard.
In 10B-T the digital phase lock loop (DPLL) function recovers the far-end link-partner clock from the received Manchester signal. The DPLL is able to combat clock jitter of up to ±18ns and frequency drifts of ±500ppm between the local PHY clock and the far-end clock. The DPLL feeds the decoder with a decoded serial bit stream.
The integrated analog Phase-Locked Loop (PLL) provides the clocks to the analog and digital sections of the PHY. The PLL is driven by an external reference clock (sourced at the XI,XO pins with a crystal oscillator, or at XI with an external reference clock).
The TLK10xL implements the link monitor State Machine (SM) as defined by the IEEE 802.3 100Base-TX Standard. In addition, the TLK10xL enables several add-ons to the link monitor SM activated by configuration bits. The new add-ons include the recovery state which enables the PHY to attempt recovery in the event of a temporary energy-loss situation before entering the LINK_FAIL state, thus restarting the whole link establishment procedure. This sequence allows significant reduction of the recovery time in scenarios where the link loss is temporal.
In addition, the link monitor SM enables moving to the LINK_DOWN state based on descrambler synchronization failure and not only on Signal_Status indication, which shortens the drop-link down time. These add-ons are supplementary to the IEEE standard and are bypassed by default.
The signal detect function of the TLK10xL 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 signal-detect indication. In addition it has fully-programmable thresholds and listening-time periods, enabling shortening of the reaction time if required.
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 TLK10xL asserts RX_ER, and presents 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 (0x14h) is incremented by one for every error in the nibble.
When at least two IDLE code groups are detected, RX_ER and CRS are de-asserted.
In 10B-T, after the far-end clock is recovered, the received Manchester symbols pass to the Manchester decoder. The serial decoded bit stream is aligned to the start of the frame, de-serialized to 4-bit wide nibbles and sent to the MAC through the MII.
The squelch feature determines when valid data is present on the differential receive inputs. The TLK10xL 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.
When in Half-Duplex mode, a 10Base-T collision is detected when receive and transmit channels are active simultaneously. Collisions are reported by the COL signal on the MII.
The 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 COL pin).
Carrier Sense (CRS) may be asserted due to receive activity after valid data is detected via the squelch function. For 10Mb/s Half Duplex operation, CRS is asserted during either packet transmission or reception. For 10Mb/s Full Duplex operation, CRS is asserted only during receive activity.
CRS is de-asserted following an end-of-packet.
Jabber is a condition in which a station transmits for a period of time longer than the maximum permissible packet length, usually due to a fault condition. The jabber function monitors the TLK10xL output and disables the transmitter if it attempts to transmit a packet of longer than legal size. A jabber timer monitors the transmitter and disables the transmission if the transmitter is active for approximately 100ms.
When disabled by the Jabber function, the transmitter stays disabled for the entire time that the ENDEC module's internal transmit enable is asserted. This signal must be de-asserted for approximately 500ms (the unjab time) before the Jabber function re-enables the transmit outputs.
The Jabber function is only available and active in 10Base-T mode.
Swapping the wires within the twisted pair causes polarity errors. Wrong polarity affects the 10B-T PHYs. The 100B-TX is immune to polarity problems because it uses MLT3 encoding. The 10B-T automatically detects reversed polarity according to the received link pulses or data. Note that the default transmit link pulse polarity for the TLK10xL is reversed.
External 10Base-T filters are not required when using the TLK10xL, because the required signal conditioning is integrated into the device. Only isolation transformers and impedance matching resistors are required for the 10Base-T transmit and receive interface. The internal transmit filtering ensures that all the harmonics in the transmit signal are attenuated by at least 30dB.
The TLK10xL has two basic 10Base-T operational modes:
The auto-negotiation function, described in detail in IEEE802.3 chapter 28, provides the means to exchange information between two devices and automatically configure both of them to take maximum advantage of their abilities.
Auto negotiation uses the 10B-T link pulses to encapsulate the transmitted data in a sequence of pulses, also referred to as a Fast Link Pulses (FLP) burst. The FLP Burst consists of a series of closely spaced 10B-T link integrity test pulses that form an alternating clock/data sequence. Extraction of the data bits from the FLP Burst yields a Link Code Word that identifies the operational modes supported by the remote device, as well as some information used for the auto negotiation function’s handshake mechanism.
The information exchanged between the devices during the auto-negotiation process consists of the devices' abilities such as duplex support and speed. This information allows higher levels of the network (MAC) to send to the other link partner vendor-specific data (via the Next Page mechanism, see below), and provides the mechanism for both parties to agree on the highest performance mode of operation.
When auto negotiation has started, the TLK10xL transmits FLP on one twisted pair and listens on the other, thus trying to find out whether the other link partner supports the auto negotiation function as well. The decision on what pair to transmit/listen depends on the MDI/MDI-X state. If the other link partner activates auto negotiation, then the two parties begin to exchange their information. If the other link partner is a legacy PHY or does not activate the auto negotiation, then the TLK10xL uses the parallel detection function, as described in IEEE802.3 chapters 40 and 28, to determine 10B-T or 100B-TX operation modes.
The TLK10xL initiates the auto negotiation function if one of the following events have happened:
The auto-negotiation function is also initiated when the auto-negotiation enable bit is set in register BMCR (0x0000h) bit 12 and one of the following events has happened:
To disable the auto-negotiation function during operation, clear register BMCR (0x0000h) bit 12. During operation, setting/resetting this register does not affect the TLK10xL operation. For the changes to take place, issue a restart command through register BMCR (0x0000h) bit 9.
The TLK10xL supports the optional feature of the transmission and reception of auto-negotiation additional (vendor specific) next pages.
If next pages are needed, the user must set register ANAR(0x0004h) bit 15 to '1'. The next pages are then sent and received through registers ANNPTR(0x0007h) and ANLNPTR(0x0008h), respectively. The user must poll register ANER(0x0006h) bit 1 to check whether a new page has been received, and then read register ANLNPTR for the received next page's content. Only after register ANLNPTR is read may the user write to register ANNPTR the next page to be transmitted. After register ANNPTR is written, new next pages overwrite the contents of register ANLNPTR.
If register ANAR(0x0004h) bit 15 is set, then the next page sequence is controlled by the user, meaning that the auto-negotiation function always waits for register ANNPTR to be written before transmitting the next page.
If additional user-defined next pages are transmitted and the link partner has more next pages to send, it is the user's responsibility to keep writing null pages (of value 0x2001) to register ANNPTR until the link partner notifies that it has sent its last page (by setting bit 15 of its transmitted next page to zero).
The TLK10xL includes advanced link-down capabilities that support various real-time applications. The link-down mechanism of the TLK10xL is configurable and includes enhanced modes that allow extremely fast reaction times to link-drops.
As described in Figure 5-9, the TLK10xL link loss mechanism is based on a time window search period, in which the signal behavior is monitored. The T1 window is set by default to reduce typical link-drops to less than 1ms.
The TLK10xL supports enhanced modes that shorten the window called Fast Link Down mode. In this mode, which can be configured in Control Register 3 (CR3), address 0x000B, bits 3:0, the T1 window is shortened significantly, in most cases less than 10µs. In this period of time there are several criteria allowed to generate link loss event and drop the link:
The Fast Link Down functionality allows the use of each of these options separately or in any combination. Note that since this mode enables extremely quick reaction time, it is more exposed to temporary bad link-quality scenarios.
The TLK10xLsupports an IEEE 1588 indication pulse at the SFD (start frame delimiter) for the RX and TX paths in 100BT mode. The pulse can be delivered to various pins as configured by register 0x3e. The pulse indicates the actual time the symbol is presented on the lines (for TX), or the first bit where the /J/ symbol is received (RX). Exact timing of the pulse can be adjusted using register 0x3f. Each increment of phase value is an 8ns step.
space
In the register definitions under the ‘Default’ heading, the following definitions hold true:
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | 100Base-T4 | 0, RO/P | 100Base-T4 Capable: | |
This protocol is not available. Always 0 = Device does not perform 100Base-T4 mode. | ||||
14 | 100Base-TX Full Duplex | 1, RO/P | 100Base-TX Full Duplex Capable: | |
1 = | Device able to perform 100Base-TX in full duplex mode | |||
0 = | Device not able to perform 100Base-TX in full duplex mode | |||
13 | 100Base-TX Half Duplex | 1, RO/P | 100Base-TX Half Duplex Capable: | |
1 = | Device able to perform 100Base-TX in half duplex mode | |||
0 = | Device not able to perform 100Base-TX in half duplex mode | |||
12 | 10Base-T Full Duplex |
1, RO/P | 10Base-T Full Duplex Capable: | |
1 = | Device able to perform 10Base-T in full duplex mode | |||
0 = | Device not able to perform 10Base-T in full duplex mode | |||
11 | 10Base-T Half Duplex | 1, RO/P | 10Base-T Half Duplex Capable: | |
1 = | Device able to perform 10Base-T in half duplex mode | |||
0 = | Device not able to perform 10Base-T in half duplex mode | |||
10:7 | RESERVED | 0, RO | RESERVED: Write as 0, read as 0 | |
6 | MF Preamble Suppression | 1, RO/P | Preamble suppression Capable: | |
1 = | Device able to perform management transaction with preamble suppressed, 32-bits of preamble needed only once after reset, invalid opcode or invalid turnaround. | |||
0 = | Device will not perform management transaction with preambles suppressed | |||
5 | Auto-Negotiation Complete | 0, RO | Auto-Negotiation Complete: | |
1 = | Auto-Negotiation process complete | |||
0 = | Auto-Negotiation process not complete (either still in process, disabled, or reset) | |||
4 | Remote Fault | 0, RO/LH | Remote Fault: | |
1 = | Remote Fault condition detected (cleared on read or by reset). Fault criteria: Far End Fault Indication or notification from Link Partner of Remote Fault. | |||
0 = | No remote fault condition detected | |||
3 | Auto-Negotiation Ability | 1, RO/P | Auto Negotiation Ability: | |
1 = | Device is able to perform Auto-Negotiation | |||
0 = | Device is not able to perform Auto-Negotiation | |||
2 | Link Status | 0, RO/LL | Link Status: | |
1 = | Valid link established (for either 10 or 100Mbs operation) | |||
0 = | Link not established | |||
1 | Jabber Detect | 0, RO/LH | Jabber Detect: This bit only has meaning in 10Mbs mode. | |
1 = | Jabber condition detected | |||
0 = | No Jabber. condition detected | |||
This bit is implemented with a latching function, such that the occurrence of a jabber condition causes it to set until it is cleared by a read to this register by the management interface or by a reset. | ||||
0 | Extended Capability | 1, RO/P | Extended Capability: | |
1 = | Extended register capabilities | |||
0 = | Basic register set capabilities only |
The PHY Identifier Registers 1 and 2 together form a unique identifier for the TLK10xL. The identifier consists of a concatenation of the Organizationally Unique Identifier (OUI), the vendor's model number and the model revision number. A PHY may return a value of zero in each of the 32 bits of the PHY Identifier if desired. The PHY Identifier is intended to support network management. The Texas Instruments IEEE-assigned OUI is 080028h, implemented as Reg 0x2 [15:0] = OUI[21:6] = 2000(h) and Reg 0x3 [15:10] = OUI[5:0] = A(h).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:0 | OUI_MSB | 0010 0000 0000 0000, RO/P |
OUI[21:6] = 2000(h): The most significant two bits of the OUI are ignored (the IEEE standard refers to these as bits 1 and 2). |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:10 | OUI_LSB | 1010 00, RO/P | OUI[5:0] = 28(h) |
9:4 | VNDR_MDL | 10 0001, RO/P | Vendor Model Number:
The six bits of vendor model number are mapped from bits 9 to 4 (most significant bit to bit 9). |
3:0 | MDL_REV | 0010, RO/P | Model Revision Number:
Four bits of the vendor model revision number are mapped from bits 3 to 0 (most significant bit to bit 3). This field is incremented for all major device changes. |
This register contains the advertised abilities of this device as they are transmitted to its link partner during Auto-Negotiation.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | NP | 0, RW | Next Page Indication: | |
0 = | Next Page Transfer not desired | |||
1 = | Next Page Transfer desired | |||
14 | RESERVED | 0, RO/P | RESERVED by IEEE: Writes ignored, Read as 0 | |
13 | RF | 0, RW | Remote Fault: | |
1 = | Advertises that this device has detected a Remote Fault | |||
0 = | No Remote Fault detected | |||
12 | RESERVED | 0, RW | RESERVED for Future IEEE use: Write as 0, Read as 0 | |
11 | ASM_DIR | 0, RW | Asymmetric PAUSE Support for Full Duplex Links: The ASM_DIR bit indicates that asymmetric PAUSE is supported. | |
1 = | Asymmetric PAUSE implemented. Advertise that the DTE/MAC has implemented both the optional MAC control sublayer and the pause function as specified in clause 31 and annex 31B of IEEE802.3u. | |||
0 = | Asymmetric PAUSE not implemented | |||
Encoding and resolution of PAUSE bits is defined in IEEE 802.3 Annex 28B, Tables 28B-2 and 28B-3, respectively. Pause resolution status is reported in PHYCR[13:12]. | ||||
10 | PAUSE | 0, RW | PAUSE Support for Full Duplex Links: The PAUSE bit indicates that the device is capable of providing the symmetric PAUSE functions as defined in Annex 31B. | |
1 = | MAC PAUSE implemented. Advertise that the DTE (MAC) has implemented both the optional MAC control sub-layer and the pause function as specified in clause 31 and annex 31B of 802.3u. | |||
0 = | MAC PAUSE not implemented | |||
Encoding and resolution of PAUSE bits is defined in IEEE 802.3 Annex 28B, Tables 28B-2 and 28B-3, respectively. Pause resolution status is reported in PHYCR[13:12]. | ||||
9 | 100B-T4 | 0, RO/P | 100Base-T4 Support: | |
1 = | 100Base-T4 is supported by the local device | |||
0 = | 100Base-T4 not supported | |||
8 | 100B-TX_FD | 1, RW | 100Base-TX Full Duplex Support: | |
1 = | 100Base-TX Full Duplex is supported by the local device | |||
0 = | 100Base-TX Full Duplex not supported | |||
7 | 100B-TX | 1, RW | 100Base-TX Support: | |
1 = | 100Base-TX is supported by the local device | |||
0 = | 100Base-TX not supported | |||
6 | 10B-T_FD | 1, RW | 10Base-T Full Duplex Support: | |
1 = | 10Base-T Full Duplex is supported by the local device | |||
0 = | 10Base-T Full Duplex not supported | |||
5 | 10B-T | 1, RW | 10Base-T Support: | |
1 = | 10Base-T is supported by the local device | |||
0 = | 10Base-T not supported | |||
4:0 | Selector | 0 0001, RW | Protocol Selection Bits:
These bits contain the binary encoded protocol selector supported by this port. <00001> indicates that this device supports IEEE 802.3u. |
This register contains the advertised abilities of the Link Partner as received during Auto-Negotiation. The content changes after the successful auto-negotiation if Next-pages are supported.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | NP | 0, RO | Next Page Indication: | |
0 = | Link Partner does not desire Next Page Transfer | |||
1 = | Link Partner desires Next Page Transfer | |||
14 | ACK | 0, RO | Acknowledge: | |
1 = | Link Partner acknowledges reception of the ability data word | |||
0 = | Not acknowledged. The Auto-Negotiation state machine will automatically control the this bit based on the incoming FLP bursts. | |||
13 | RF | 0, RO | Remote Fault: | |
1 = | Remote Fault indicated by Link Partner | |||
0 = | No Remote Fault indicated by Link Partner | |||
12 | RESERVED | 0, RO | RESERVED for Future IEEE use: Write as 0, read as 0 | |
11 | ASM_DIR | 0, RO | ASYMMETRIC PAUSE: | |
1 = | Asymmetric pause is supported by the Link Partner | |||
0 = | Asymmetric pause is not supported by the Link Partner | |||
10 | PAUSE | 0, RO | PAUSE: | |
1 = | Pause function is supported by the Link Partner | |||
0 = | Pause function is not supported by the Link Partner | |||
9 | 100B-T4 | 0, RO | 100Base-T4 Support: | |
1 = | 100Base-T4 is supported by the Link Partner | |||
0 = | 100Base-T4 is not supported by the Link Partner | |||
8 | 100B-TX_FD | 0, RO | 100Base-TX Full Duplex Support: | |
1 = | 100Base-TX Full Duplex is supported by the Link Partner | |||
0 = | 100Base-TX Full Duplex is not supported by the Link Partner | |||
7 | 100B-TX | 0, RO | 100Base-TX Support: | |
1 = | 100Base-TX is supported by the Link Partner | |||
0 = | 100Base-TX is not supported by the Link Partner | |||
6 | 10B-T_FD | 0, RO | 10Base-T Full Duplex Support: | |
1 = | 10Base-T Full Duplex is supported by the Link Partner | |||
0 = | 10Base-T Full Duplex is not supported by the Link Partner | |||
5 | 10B-T | 0, RO | 10Base-T Support: | |
1 = | 10Base-T is supported by the Link Partner | |||
0 = | 10Base-T is not supported by the Link Partner | |||
4:0 | Selector | 0 0000, RO | Protocol Selection Bits:
Link Partner’s binary encoded protocol selector. |
This register contains additional Local Device and Link Partner status information.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15:5 | RESERVED | 0, RO | RESERVED: Writes ignored, Read as 0. | |
4 | 0, RO | Parallel Detection Fault: | ||
1 = | Fault detected via the Parallel Detection function | |||
0 = | No fault detected | |||
3 | LP_NP_ABLE | 0, RO | Link Partner Next Page Able: | |
1 = | Link Partner does support Next Page | |||
0 = | Link Partner does not support Next Page | |||
2 | NP_ABLE | 1, RO/P | Next Page Able: | |
1 = | Indicates local device is able to send additional Next Pages | |||
0 = | Indicates local device is not able to send additional Next Pages | |||
1 | PAGE_RX | 0, RO/COR | Link Code Word Page Received: | |
1 = | Link Code Word has been received, cleared on a read | |||
0 = | Link Code Word has not been received | |||
0 | LP_AN_ABLE | 0, RO | Link Partner Auto-Negotiation Able: | |
1 = | indicates that the Link Partner supports Auto-Negotiation | |||
0 = | indicates that the Link Partner does not support Auto-Negotiation |
This register contains the next page information sent by this device to its Link Partner during Auto-Negotiation.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | NP | 0, RW | Next Page Indication: | |
0 = | No other Next Page Transfer desired | |||
1 = | Another Next Page desired | |||
14 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0 | |
13 | MP | 1, RW | Message Page: | |
1 = | Message Page | |||
0 = | Unformatted Page | |||
12 | ACK2 | 0, RW | Acknowledge2: | |
1 = | Will comply with message | |||
0 = | Cannot comply with message | |||
Acknowledge2 is used by the next page function to indicate that Local Device has the ability to comply with the message received. | ||||
11 | TOG_TX | 0, RO | Toggle: | |
1 = | Value of toggle bit in previously transmitted Link Code Word was 0 | |||
0 = | Value of toggle bit in previously transmitted Link Code Word was 1 | |||
Toggle is used by the Arbitration function within Auto-Negotiation to synchronize with the Link Partner during Next Page exchange. This bit always takes the opposite value of the Toggle bit in the previously exchanged Link Code Word. | ||||
10:0 | CODE | 000 0000 0001, RW |
This field represents the code field of the next page transmission. If the MP bit is set (bit 13 of this register), then the code is interpreted as a Message Page, as defined in annex 28C of IEEE 802.3u. Otherwise, the code is interpreted as an Unformatted Page, and the interpretation is application specific. The default value of the CODE represents a Null Page as defined in Annex 28C of IEEE 802.3u. |
This register contains the next page information sent by this device to its Link Partner during Auto-Negotiation.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | NP | 0, RO | Next Page Indication: | |
1 = | No other Next Page Transfer desired | |||
0 = | Another Next Page desired | |||
14 | ACK | 0, RO | Acknowledge: | |
1 = | Link Partner acknowledges reception of the ability data word | |||
0 = | Not acknowledged | |||
The Auto-Negotiation state machine automatically controls this bit based on the incoming FLP bursts. Software should not attempt to write to this bit. | ||||
13 | MP | 1, RO | Message Page: | |
1 = | Message Page | |||
0 = | Unformatted Page | |||
12 | ACK2 | 0, RO | Acknowledge2: | |
1 = | Link Partner has the ability to comply to next-page message | |||
0 = | Link Partner cannot comply to next-page message | |||
Acknowledge2 is used by the next page function to indicate that Local Device has the ability to comply with the message received. | ||||
11 | Toggle | 0, RO | Toggle: | |
1 = | Value of toggle bit in previously transmitted Link Code Word was 0 | |||
0 = | Value of toggle bit in previously transmitted Link Code Word was 1 | |||
Toggle is used by the Arbitration function within Auto-Negotiation to synchronize with the Link Partner during Next Page exchange. This bit always takes the opposite value of the Toggle bit in the previously exchanged Link Code Word. | ||||
10:0 | CODE | 000 0000 0001, RO | Code:
This field represents the code field of the next page transmission. If the MP bit is set (bit 13 of this register), then the code is interpreted as a Message Page, as defined in annex 28C of IEEE 802.3u. Otherwise, the code is interpreted as an Unformatted Page, and the interpretation is application specific. The default value of the CODE represents a Null Page as defined in Annex 28C of IEEE 802.3u. |
BIT | BIT NAME | DEFAULT | DESCRIPTION | ||||
---|---|---|---|---|---|---|---|
15:10 | RESERVED | 1, RW | RESERVED | ||||
9 | RMII Enhanced Mode | 0, RW | RMII Enhanced Mode: | ||||
1 = | Enable RMII Enhanced Mode | ||||||
0 = | RMII operates in normal mode | ||||||
In normal mode, If the line is not idle CRS_DV goes high. As soon as the False Carrier is detected, RX_ER is asserted and RXD is set to “2”. This situation remains for the duration of the receive event. While in enhanced mode, CRS_DV is disqualified and de-asserted when the False Carrier detected. This status also remains for the duration of the receive event. In addition in normal mode, the start of the packet is intact. Each symbol error is indicated by setting RX_ER high. The data on RXD is replaced with “1” starting with the first symbol error. While in enhanced mode, the CRS_DV is de-asserted with the first symbol error. | |||||||
8 | TDR AUTORUN | 0, RW | TDR Auto Run at link down: | ||||
1 = | Enable execution of TDR procedure after link down event | ||||||
0 = | Disable automatic execution of TDR | ||||||
7 | Link Loss Recovery | 0, RW | Link Loss Recovery: | ||||
1 = | Enable Link Loss Recovery mechanism. This mode allow recovery from short interference and continue to hold the link up for period of additional few mSec till the short interference will gone and the signal is OK. | ||||||
0 = | Normal Link Loss operation. Link status will go down approximately 250µs from signal loss. | ||||||
6 | Fast Auto MDI-X | 0, RW | Fast Auto MDI/MDIX: | ||||
1 = | Enable Fast Auto MDI/MDIX mode | ||||||
0 = | Normal Auto MDI/MDIX mode. | ||||||
If both link partners are configured to work in Force 100Base-TX mode (Auto-Negotiation is disabled), this mode enables Automatic MDI/MDIX resolution in a short time. | |||||||
5 | Robust Auto MDI-X | 0, RW | Robust Auto MDI-X : | ||||
1 = | Enable Robust Auto MDI/MDIX resolution | ||||||
0 = | Normal Auto MDI/MDIX mode | ||||||
If link partners are configured to operational modes that are not supported by normal Auto MDI/MDIX mode (like Auto-Neg versus Force 100Base-TX or Force 100Base-TX versus Force 100Base-TX), this Robust Auto MDI/MDIX mode allows MDI/MDIX resolution and prevents deadlock. | |||||||
4 | Fast AN En | 0, RW | Fast AN En: | ||||
1 = | Enable Fast Auto-Negotiation mode – The PHY auto-negotiates using Timer setting according to Fast AN Sel bits (bits 3:2 this register) | ||||||
0 = | Disable Fast Auto-Negotiation mode – The PHY auto-negotiates using normal Timer setting | ||||||
Adjusting these bits reduces the time it takes to Auto-negotiate between two PHYs. Note: When using this option care must be taken to maintain proper operation of the system. While shortening these timer intervals may not cause problems in normal operation, there are certain situations where this may lead to problems. | |||||||
3:2 | Fast AN Sel | 0, RW | Fast Auto-Negotiation Select bits: | ||||
Fast AN Select | Break Link Timer | Link Fail Inhibit Timer | Auto-Neg Wait Timer | ||||
<00> | 80 | 50 | 35 | ||||
<01> | 120 | 75 | 50 | ||||
<10> | 240 | 150 | 100 | ||||
<11> | NA | NA | NA | ||||
Adjusting these bits reduces the time it takes to Auto-negotiate between two PHYs. In Fast AN mode, both PHYs should be configured to the same configuration. These 2 bits define the duration for each state of the Auto Negotiation process according to the table above. The new duration time must be enabled by setting “Fast AN En” - bit 4 of this register. Note: Using this mode in cases where both link partners are not configured to the same Fast Auto-negotiation configuration might produce scenarios with unexpected behavior. | |||||||
1 | Fast RXDV Detection | 0, RW | Fast RXDV Detection: | ||||
1 = | Enable assertion high of RX_DV on receive packet due to detection of /J/ symbol only. If a consecutive /K/ does not appear, RX_ER is generated. | ||||||
0 = | Disable Fast RX_DV detection. The PHY operates in normal mode - RX_DV assertion after detection of /J/K/. | ||||||
0 | RESERVED | 1, RW | RESERVED |
REGCR (0x000D) and ADDAR (0x000E) allow read/write access to the extended register set (addresses above 0x001F) using indirect addressing.
This register is the MDIO Manageable MMD access control. In general, register REGCR (4:0) is the device address DEVAD that directs any accesses of the ADDAR (0x000E) register to the appropriate MMD. REGCR also contains selection bits for auto increment of the data register. This register contains the device address to be written to access the extended registers. Write 0x1F into bits 4:0 of this register. REGCR also contains selection bits (15:14) for the address auto-increment mode of ADDAR.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:14 | Function | 0, RW | 00 = Address 01 = Data, no post increment 10 = Data, post increment on read and write 11 = Data, post increment on write only |
13:5 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
4:0 | DEVAD | 0, RW | Device Address: In general, these bits [4:0] are the device address DEVAD that directs any accesses of ADDAR register (0x000E) to the appropriate MMD. Specifically, the TLK10xL uses the vendor specific DEVAD [4:0] = “11111” for accesses. All accesses through registers REGCR and ADDAR should use this DEVAD. Transactions with other DEVAD are ignored. |
This register is the address/data MMD register. ADDAR is used in conjunction with REGCR register (0x000D) to provide the access by indirect read/write mechanism to the extended register set.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:0 | Addr/data | 0, RW | If REGCR register 15:14 = 00, holds the MMD DEVAD's address register, otherwise holds the MMD DEVAD's data register |
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15:9 | RESERVED | 0, RO | RESERVED | |
8:4 | Fast Link Down Status[4:0] | 0, RO, LH | Status Registers that latch high each time a given Fast Link Down mode is activated and causes a link drop (assuming this criterion was enabled): | |
Bit 4 | Descrambler Loss Sync | |||
Bit 3 | RX Errors | |||
Bit 2 | MLT3 Errors | |||
Bit 1 | SNR level | |||
Bit 0 | Signal/Energy Lost | |||
3:0 | RESERVED | 0, RO | RESERVED |
This register provides quick access to commonly accessed PHY control status and general information.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. | |
14 | MDI-X Mode | 0,RO | MDI-X mode as reported by the Auto-Negotiation state machine: | |
1 = | MDI pairs swapped (Receive on TPTD pair, Transmit on TPRD pair) | |||
0 = | MDI pairs normal (Receive on TRD pair, Transmit on TPTD pair) | |||
This bit will be affected by the settings of the AMDIX_EN and FORCE_MDIX bits in the PHYCR register. When MDIX is enabled, but not forced, this bit will update dynamically as the Auto-MDIX algorithm swaps between MDI and MDI-X configurations. | ||||
13 | Receive Error Latch | 0,RO/LH | Receive Error Latch: | |
1 = | Receive error event has occurred since last read of RXERCNT register (0x0015) | |||
0 = | No receive error event has occurred | |||
This bit will be cleared upon a read of the RECR register | ||||
12 | Polarity Status | 0,RO | Polarity Status: | |
1 = | Inverted Polarity detected | |||
0 = | Correct Polarity detected | |||
This bit is a duplication of bit 4 in the 10BTSCR register (0x001A). This bit will be cleared upon a read of the 10BTSCR register, but not upon a read of the PHYSTS register. | ||||
11 | False Carrier Sense Latch | 0,RO/LH | False Carrier Sense Latch: | |
1 = | False Carrier event has occurred since last read of FCSCR register (0x0014) | |||
0 = | No False Carrier event has occurred | |||
This bit will be cleared upon a read of the FCSR register. | ||||
10 | Signal Detect | 0,RO/LL | Signal Detect: | |
Active high 100Base-TX unconditional Signal Detect indication from PMD | ||||
9 | Descrambler Lock | 0,RO/LL | Descrambler Lock: | |
Active high 100Base-TX Descrambler Lock indication from PMD | ||||
8 | Page Received | 0,RO | Link Code Word Page Received: | |
1 = | A new Link Code Word Page has been received. This bit is a duplicate of Page Received (bit 1) in the ANER register and it is cleared on read of the ANER register (0x0006). | |||
0 = | Link Code Word Page has not been received. | |||
This bit will not be cleared upon a read of the PHYSTS register. | ||||
7 | MII Interrupt | 0,RO | MII Interrupt Pending: | |
1 = | Indicates that an internal interrupt is pending. Interrupt source can be determined by reading the MISR Register (0x0012). Reading the MISR will clear this Interrupt bit indication. | |||
0 = | No interrupt pending | |||
6 | Remote Fault | 0,RO | Remote Fault: | |
1 = | Remote Fault condition detected. Fault criteria: notification from Link Partner of Remote Fault via Auto-Negotiation. Cleared on read of BMSR register (0x0001) or by reset. | |||
0 = | No remote fault condition detected | |||
5 | Jabber Detect | 0,RO | Jabber Detect: | |
1 = | Jabber condition detected. This bit has meaning only in 10 Mb/s mode. This bit is a duplicate of the Jabber Detect bit in the BMSR register (0x0001). | |||
0 = | No Jabber | |||
This bit will not be cleared upon a read of the PHYSTS register. | ||||
4 | Auto-Neg Status | 0,RO | Auto-Negotiation Status: | |
1 = | Auto-Negotiation complete | |||
0 = | Auto-Negotiation not complete | |||
3 | MII Loopback Status | 0,RO | MII Loopback: | |
1 = | Loopback active (enabled) | |||
0 = | Normal operation | |||
2 | Duplex Status | 0,RO | Duplex Status: | |
1 = | Full duplex mode | |||
0 = | Half duplex mode | |||
This bit indicates duplex status and is determined from Auto-Negotiation or Forced Modes. Therefore, it is only valid if Auto-Negotiation is enabled and complete and there is a valid link or if Auto-Negotiation is disabled and there is a valid link. | ||||
1 | Speed Status | 0,RO | Speed Status: | |
1 = | 10 Mb/s mode | |||
0 = | 100 Mb/s mode | |||
This bit indicates the status of the speed and is determined from Auto-Negotiation or Forced Modes. Speed Status is only valid if Auto-Negotiation is enabled and complete and there is a valid link or if Auto-Negotiation is disabled and there is a valid link. | ||||
0 | Link Status | 0,RO | Link Status: | |
1 = | Valid link established (for either 10 or 100 Mb/s operation). This bit is a duplicate of the Link Status bit in the BMSR register (0x0001). | |||
0 = | Link not established | |||
This bit will not be cleared upon a read of the PHYSTS register. |
This register implements the PHY Specific Control register. This register allows access to general functionality inside the PHY to enable operation in reduced power modes and control interrupt mechanism.
This register contains events status and enables for the interrupt function. If an event has occurred since the last read of this register, the corresponding status bit will be set. If the corresponding enable bit in the register is set, an interrupt will be generated if the event occurs. The PHYSCR register (0x0011) bits 1 and 0 must also be set to allow interrupts. The status indications in this register will be set even if the interrupt is not enabled.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:14 | RESERVED | 00, RO | RESERVED: Writes ignored, read as 0. |
13 | Link Status Changed INT | 0,RO, COR | Change of Link Status interrupt:
1 = Change of link status interrupt is pending 0 = No change of link status |
12 | Speed Changed INT | 0,RO, COR | Change of Speed Status interrupt:
1 = Change of speed status interrupt is pending 0 = No change of speed status |
11 | Duplex Mode Changed INT | 0,RO, COR | Change of duplex status interrupt:
1 = Duplex status change interrupt is pending 0 = No change of duplex status |
10 | Auto-Negotiation Completed INT | 0,RO, COR | Auto-Negotiation Complete interrupt:
1 = Auto-negotiation complete interrupt is pending. 0 = No Auto-negotiation complete event is pending |
9 | FC HF INT | 0,RO, COR | False Carrier Counter half-full interrupt:
1 = False carrier counter (Register FCSCR, address 0x0014) exceeds half-full interrupt is pending 0 = False carrier counter half-full event is not pending |
8 | RE HF INT | 0,RO, COR | Receive Error Counter half-full interrupt:
1 = Receive error counter (Register RECR, address 0x0015) exceeds half full interrupt is pending 0 = No Receive error counter half full event pending |
7:6 | RESERVED | 00, RO | RESERVED: Writes ignored, read as 0. |
5 | Link Status Changed EN | 0, RW | Enable Interrupt on change of link status |
4 | Speed Changed EN | 0, RW | Enable Interrupt on change of speed status |
3 | Duplex Mode Changed EN | 0, RW | Enable Interrupt on change of duplex status |
2 | Auto-Negotiation Completed EN | 0, RW | Enable Interrupt on Auto-negotiation complete event |
1 | FC HF EN | 0, RW | Enable Interrupt on False Carrier Counter Register half-full event |
0 | RE HF EN | 0, RW | Enable Interrupt on Receive Error Counter Register half-full event |
This register contains events status and enables for the interrupt function. If an event has occurred since the last read of this register, the corresponding status bit will be set. If the corresponding enable bit in the register is set, an interrupt will be generated if the event occurs. The PHYSCR register (0x0011) bits 1 and 0 must also be set to allow interrupts. The status indications in this register will be set even if the interrupt is not enabled.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
14 | AN Error INT | 0,RO, COR | Auto-Negotiation Error Interrupt:
1 = Auto-negotiation error interrupt is pending 0 = No Auto-negotiation error event pending |
13 | Page Rec INT | 0,RO, COR | Page Receive Interrupt:
1 = Page has been received 0 = Page has not been received |
12 | Loopback FIFO OF/UF INT | 0,RO, COR | Loopback FIFO Overflow/Underflow Event Interrupt:
1 = FIFO Overflow/Underflow event interrupt pending 0 = No FIFO Overflow/Underflow event pending |
11 | MDI Crossover Changed INT | 0,RO, COR | MDI/MDIX Crossover Status Changed Interrupt:
1 = MDI crossover status changed interrupt is pending 0 = MDI crossover status has not changed |
10 | Sleep Mode INT | 0,RO, COR | Sleep Mode Event Interrupt:
1 = Sleep Mode event interrupt is pending 0 = No sleep mode event pending |
9 | Polarity Changed INT | 0,RO, COR | Polarity Changed Interrupt:
1 = Data polarity changed interrupt pending 0 = No Data polarity event pending |
8 | Jabber Detect INT | 0,RO | Jabber Detect Event Interrupt:
1 = Jabber detect event interrupt pending 0 = No Jabber detect event pending |
7 | RESERVED | 0,RW | RESERVED: Writes ignored, read as 0 |
6 | AN Error EN | 0,RW | Enable Interrupt on Auto-Negotiation error event |
5 | Page Rec EN | 0,RW | Enable Interrupt on page receive event |
4 | Loopback FIFO OF/UF EN | 0,RW | Enable Interrupt on loopback FIFO overflow/underflow event |
3 | MDI Crossover Changed EN | 0,RW | Enable Interrupt on change of MDI/X status |
2 | Sleep Mode Event EN | 0,RW | Enable Interrupt sleep mode event |
1 | Polarity Changed EN | 0,RW | Enable Interrupt on change of polarity status |
0 | Jabber Detect EN | 0,RW | Enable Interrupt on Jabber detection event |
This counter provides information required to implement the "False Carriers" attribute within the MAU managed object class of Clause 30 of the IEEE 802.3u specification.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | RESERVED | 0000 0000, RO | RESERVED: Writes ignored, read as 0 |
7:0 | FCSCNT | 0,RO / COR | False Carrier Event Counter:
This 8-bit counter increments on every false carrier event. This counter stops when it reaches its maximum count (FFh). When the counter exceeds half full (7Fh), an interrupt event is generated. This register is cleared on read. |
This counter provides information required to implement the "Symbol Error During Carrier" attribute within the PHY managed object class of Clause 30 of the IEEE 802.3u specification.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15:0 | RX Error Count | 0, RO, / COR | RX_ER Counter:
When a valid carrier is present (only while RXDV is set), and there is at least one occurrence of an invalid data symbol, this 16-bit counter increments for each receive error detected. The RX_ER counter does not count in MII loopback mode. The counter stops when it reaches its maximum count of FFFFh. When the counter exceeds half-full (7FFFh), an interrupt is generated. This register is cleared on read. |
This register is used for Build-In Self Test (BIST) configuration. The BIST functionality provides Pseudo Random Bit Stream (PRBS) mechanism including packet generation generator and checker. Selection of the exact loopback point in the signal chain is also done in this register.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0 | |
14 | PRBS Count Mode | 0, RW | PRBS Single/Continues Mode: | |
1 = | Continuous mode, the PRBS counters reaches max count value, pulse is generated and counter starts counting from zero again. | |||
0 = | Single mode, When BIST Error Counter reaches its max value, PRBS checker stops counting. | |||
13 | Generate PRBS Packets | 0, RW | Generated PRBS Packets: | |
1 = | When packet generator is enabled, generate continuous packets with PRBS data. When packet generator is disabled, PRBS checker is still enabled. | |||
0 = | When packet generator is enabled, generate single packet with constant data. PRBS gen/check is disabled. | |||
12 | Packet Generation Enable | 0, RW | Packet Generation Enable: | |
1 = | Enable packet generation with PRBS data | |||
0 = | Disable packet generator | |||
11 | PRBS Checker Lock | 0,RO | PRBS Checker Lock Indication: | |
1 = | PRBS checker is locked and synced on received bit stream | |||
0 = | PRBS checker is not locked | |||
10 | PRBS Checker Sync Loss | 0,RO,LH | PRBS Checker Sync Loss Indication: | |
1 = | PRBS checker lose sync on received bit stream – This is an error indication | |||
0 = | PRBS checker is not locked | |||
9 | Packet Gen Status | 0,RO | Packet Generator Status Indication: | |
1 = | Packet Generator is active and generate packets | |||
0 = | Packet Generator is off | |||
8 | Power Mode | 0,RO | Sleep Mode Indication: | |
1 = | Indicate that the PHY is in normal power mode | |||
0 = | Indicate that the PHY is in one of the sleep modes, either active or passive | |||
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. | |
6 | Transmit in MII Loopback | 0, RW | Transmit Data in MII Loop-back Mode (valid only at 100BT): | |
1 = | Enable transmission of the data from the MAC received on the TX pins to the line in parallel to the MII loopback to RX pins. This bit may be set only in MII Loopback mode – setting bit 14 in BMCR register (0x0000). | |||
0 = | Data is not transmitted to the line in MII loopback | |||
5 | RESERVED | 0, RO | RESERVED: Must be 0 | |
4:0 | Loopback Mode | 0, RW | Loop-back Mode Select:
The PHY provides several options for Loopback that test and verify various functional blocks within the PHY. Enabling loopback mode allows in-circuit testing of the TLK10xL digital and analog data path |
|
Near-end Loopback | ||||
00001 = | PCS Input Loopback | |||
00010 = | PCS Output Loopback | |||
00100 = | Digital Loopback | |||
01000 = | Analog Loopback (requires 100Ω termination) | |||
Far-end Loopback: | ||||
10000 = | Reverse Loopback |
This register configures the RMII Mode of operation. When RMII mode is disabled, the RMII functionality is bypassed.
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15:6 | RESERVED | 0000 0000 00, RO | RESERVED: Writes ignored, read as 0. | |
5 | RMII Mode | 0, RW, Pin_Strap | RMII Mode Enable: RMII Mode is operational if device powered up in RMII mode (pin_strap) and 50Mhz clock present. Please note, that in order to switch from RMII to MII and vise versa, the PHY must initialize after power up in RMII mode (Strap is '1' and REF_CLK is 50MHz). If the PHY initializes in MII mode, this bit has no effect. | |
1 = | Enable RMII (Reduced MII) mode of operation | |||
0 = | Enable MII mode of operation | |||
4 | RMII Revision Select | 0, RW | RMII Revision Select: | |
1 = | (RMII revision 1.0) CRS_DV will remain asserted until final data is transferred. CRS_DV will not toggle at the end of a packet. | |||
0 = | (RMII revision 1.2) CRS_DV will toggle at the end of a packet to indicate de-assertion of CRS. | |||
3 | RMII OVFL Status | 0, COR | RX FIFO Over Flow Status: | |
1 = | Normal | |||
0 = | Overflow detected | |||
2 | RMII OVFL Status | 0, COR | RX FIFO Under Flow Status: | |
1 = | Normal | |||
0 = | Underflow detected | |||
1:0 | ELAST_BUF | 01, RW | Receive Elasticity Buffer Size:
This field controls the Receive Elasticity Buffer which allows for frequency variation tolerance between the 50MHz RMII clock and the recovered data. The following values indicate the tolerance in bits for a single packet. The minimum setting allows for standard Ethernet frame sizes at ±50ppm accuracy for both RMII and Receive clocks. For greater frequency tolerance the packet lengths may be scaled (for ±100ppm, divide the packet lengths by 2). |
|
00 = | 14 bit tolerance (up to 16800 byte packets) | |||
01 = | 2 bit tolerance (up to 2400 byte packets) | |||
10 = | 6 bit tolerance (up to 7200 byte packets) | |||
11 = | 10 bit tolerance (up to 12000 byte packets) |
This register provides the ability to directly manually control the Link LED output.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:11 | RESERVED | 0000 0, ro | RESERVED: Writes ignored, read as 0. |
10:9 | Blink Rate | 10, RW | LED Blinking Rate (ON/OFF duration):
00 = 20Hz (50mSec) 01 = 10Hz (100mSec) 10 = 5Hz (200mSec) 11 = 2Hz (500mSec) |
8 | RESERVED | RO | RESERVED |
7 | LED Link Polarity | 0, RW, Pin_Strap | LED Link Polarity Setting:
1 = Active High polarity setting 0 = Active Low polarity setting The Link LED polarity is defined by the strap value of this pin. If the pin is strapped high via a pull-up resistor, the LED will be active low. If the pin is strapped low via a pull-down resistor, the LED will be active high. This register allows override of the strapping value. |
6 | RESERVED | RO | RESERVED |
5 | RESERVED | RO | RESERVED |
4 | Drive Link LED | 0, RW | Drive LED Link to the forced On/Off setting defined in bit 1:
1 = Drive value of On/Off bit onto LED_LINK output pin 0 = Normal operation |
3 | RESERVED | RO | RESERVED |
2 | RESERVED | RO | RESERVED |
1 | Link LED On/Off Setting | 0, RW | Value to force on Link LED output |
0 | RESERVED | RO | RESERVED |
This register provides the ability to control and set general functionality inside the PHY.
This register provides the ability to control and read status of the PHY’s internal 10Base-T functionality.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:14 | RESERVED | 000, RO | RESERVED: Writes ignored, read as 0. |
13 | Receiver TH | 0, RW | Lower Receiver Threshold Enable:
1 = Enable 10Base-T lower receiver threshold to allow operation with longer cables 0 = Normal 10Base-T operation |
12:9 | Squelch | 0000, RW | Squelch Configuration:
Used to set the Peak Squelch ‘ON’ threshold for the 10Base-T receiver. Every step is equal to 50mV and allow raising/lowering the Squelch threshold from 200mV to 600mV. The default Squelch threshold is set to 200mV. |
8 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
7 | NLP Disable | 0, RW | NLP Transmission Control:
1 = Disable transmission of NLPs 0 = Enable transmission of NLPs |
6:5 | RESERVED | 00, RO | RESERVED: Writes ignored, read as 0. |
4 | Polarity Status | 0, RO | 10Mb Polarity Status:
1 = Inverted Polarity detected 0 = Correct Polarity detected This bit is a duplication of bit 12 in the PHYSTS register (0x0010). Both bits will be cleared upon a read of 10BTSCR register, but not upon a read of the PHYSTS register. |
3:1 | RESERVED | 000, RO | RESERVED: Writes ignored, read as 0. |
0 | Jabber Disable | 0, RW | Jabber Disable:
1 = Jabber function disabled 0 = Jabber function enabled Note: This function is applicable only in 10Base-T |
This register provides the total number of error bytes that was received by the PRBS checker and defines the Inter packet Gap (IPG) for the packet generator.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | BIST Error Count | 0, RO | BIST Error Count:
Holds number of erroneous bytes that were received by the PRBS checker. Value in this register is locked when write is done to bit[0] or bit[1] (see below). When PRBS Count Mode set to zero, count stops on 0xFF. See BISCR register (0x0016) for further details Note: Writing “1” to bit 15 will lock counter’s value for successive read operation and clear the BIST Error Counter. |
7:0 | BIST IPG Length | 0111 1101, RW | BIST IPG Length:
Inter Packet Gap (IPG) Length defines the size of the gap (in bytes) between any 2 successive packets generated by the BIST. Default value is 0x7D which is equal to 125 bytes |
This register allows programming the length of the generated packets in bytes for the BIST mechanism.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:11 | RESERVED | 0000 0, RO | RESERVED: Writes ignored, read as 0. |
10:0 | BIST Packet Length | 101 1101 1100, RW | BIST Packet Length:
Length of the generated BIST packets. The value of this register defines the size (in bytes) of every packet that generated by the BIST. Default value is 0x5DC which is equal to 1500 bytes |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | Diagnostic Start | 0, RW | Cable Diagnostic Process Start:
1 = Start execute cable measurement 0 = Cable Diagnostic is disabled Diagnostic Start bit is cleared with raise of Diagnostic Done indication. |
14:10 | RESERVED | 000 00, RO | RESERVED: Writes ignored, read as 0. |
9:8 | Link Quality | 00, RO | Link Quality Indication
00 = Reserved 01 = Good Quality Link Indication 10 = Mid Quality Link Indication 11 = Poor Quality Link Indication The value of these bits are valid only when link is active – While reading “1” from “Link Status” bit 0 on PHYSTS register (0x0010). |
7:4 | RESERVED | 0000, RO | RESERVED: Writes ignored, read as 0. |
3:2 | RESERVED | 00, RO | RESERVED: Writes ignored, read as 0. |
1 | Diagnostic Done | 0, RO | Cable Diagnostic Process Done:
1 = Indication that cable measurement process completed 0 = Diagnostic has not completed |
0 | Diagnostic Fail | 0, RO | Cable Diagnostic Process Fail:
1 = Indication that cable measurement process failed 0 = Diagnostic has not failed |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | Software Reset | 0, RW,SC | Software Reset:
1 = Reset PHY. This bit is self cleared and has same effect as Hardware reset pin. 0 = Normal Operation |
14 | Software Restart | 0, RW,SC | Software Restart:
1 = Reset PHY. This bit is self cleared and resets all PHY circuitry except the registers. 0 = Normal Operation |
13:0 | RESERVED | 00 0000 0000 0000, RO |
Writes ignored, read as 0 |
This register allows generation of test patterns for compliance testing.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:6 | RESERVED | 0000 0000 00, RO | Writes ignored, read as 0 |
5 | Test Mode Select | 0, RW | MSB bit for 100Base-TX test mode. Note: bit 4 must be '0' for 100Base-TX test modes. |
4:0 | Test Configuration | 0 0000, RW | Bit 4 enables 10Base-T test modes. 1 = 10Base-T test modes 0 = 100Base-TX test modes |
For 10Base-T testing, bits [3:0] select the 10Base-T pattern as follows: 0000 = Single NLP 0000 = Single NLP 0001 = Single Pulse 1 0010 = Single Pulse 0 0011 = Repetitive 1 0100 = Repetitive 0 0101 = Preamble (repetitive '10') 0110 = Single 1 followed by TP_IDLE 0111 = Single 0 followed by TP_IDLE 1000 = Repetitive '1001' sequence 1001 = Random 10Base-T data 1010 = TP_IDLE_00 1011 = TP_IDLE_01 1100 = TP_IDLE_10 1101 = TP_IDLE_11 1001 = Random 10Base-T data |
|||
For 100Base-TX testing, bits {5,[3:0]} select the transmit sequence. The test mode transmits a repetitive sequence consisting of a '1' followed by a configurable number of '0' bits. Bits {5,[3:0]} define the number of '0' bits that follow the '1'. 1 to 31 '1' bits may be selected. 0,0001 - 1,1111: single '0' to 31 zeroes 0,0000: Clear the register |
|||
Note 1: Bit 4 must be '0' for 100Base-TX test modes. Note 2: 100Base-T test modes must be cleared before applying a new value. Bits {5,[3:0]} must be written to 0x0 before configuring a new value. Note 3: When performing 100Base-TX or 10Base-T tests, the speed must be forced using the Basic Mode Control Register (BMCR), address 0x0000. |
This register configures the .
BIT | BIT NAME | DEFAULT | DESCRIPTION | |
---|---|---|---|---|
15:7 | RESERVED | <0000 0>, RO | RESERVED: Writes ignored, read as 0. | |
6:4 | cfg_1588_TX_pin_sel | 0, RW | IEEE 1588 TX Pin Select: Assigns transmit SFD pulse indication to pin selected by value in column at right. | 001 - LED_ACT Pin 010 - LED_SPEED Pin 011 - LED_LINK Pin 100- CRS Pin 101 - COL Pin 110 - PWDNN/INT Pin 111 - No pulse output |
3 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. | |
2:0 | cfg_1588_RX_pin_sel | 0, RW | IEEE 1588 RX Pin Select: Assigns receive SFD pulse indication to pin selected by value in column at right. |
This register allows programming the length of the generated packets in bytes for the BIST mechanism.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:13 | cfg_1588_TX_set_phase | <101>, RW | PTP Transmit Timing: Set 1588 indication for TX path (8ns step) |
12:10 | cfg_1588_RX_set_phase | <101>, RW | PTP Receive TIming: Set 1588 indication for RX path (8ns step) |
9:8 | cfg_TX_ERR_sel | 0, (TRIM) | Configure TX ERR Input Pin:
00 - No TX ERR 01 - Use LED ACT as TX_ERR 10 - Use PWRDN as TX_ERR 11 - USe COL as TX_ERR |
7:0 | RESERVED | <0100 0100>, RW | RESERVED |
This register allows programming the phase of the MII transmit clock (TX_CLK pin). The TX_CLK has a fixed phase to the XI pin. However the default phase, while fixed, may not be ideal for all systems, therefore this register may be used by the system to align the reference clock (XI pin) to the TX_CLK. The phase shift value is in 4ns units. The phase shift value should be between 0 and 10 (0ns to 40ns). If value greater than 10 is written, the update value will be the written value modulo 10.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:5 | RESERVED | 0000 0000 000, RO | RESERVED: Writes ignored, read as 0 |
4 | Phase Shift Enable | 0,RW,SC | TX Clock Phase Shift Enable:
1 = Perform Phase Shift to the TX_CLK according to the value written to Phase Shift Value in bits [4:0]. 0 = No change in TX Clock phase |
3:0 | Phase Shift Value | 0000,RW | TX Clock Phase Shift Value:
The value of this register represents the current phase shift between Reference clock at XI and MII Transmit Clock at TX_CLK. Any different value that will be written to these bits will shift TX_CLK by 4 times the difference (in nSec). For example, if the value of this register is 0x2, Writing 0x9 to this register shifts TX_CLK by 28nS (4 times 7).However, since the maximum difference between XI and TX_CLK could be 40nSec (value of 10) in case of writing value bigger than 10, the updated value is the written value modulo 10. |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 1, RO | RESERVED |
14 | RESERVED | 0, RO | RESERVED |
13:9 | RESERVED | 00 000, RO | RESERVED |
8:6 | Power Back Off | 0, RW | Power Back Off Level: See Application Note SLLA328
000 = Normal Operation 001 = Level 1 (up to 140m cable between TLK link partners) 010 = Level 2 (up to 100m cable between TLK link partners) 011 = Level 3 (up to 80m cable between TLK link partners) Others = Reserved |
5:0 | RESERVED | 10 0000, RO | RESERVED |
This register gives the host processor the ability to power down the voltage-regulator block of the PHY via register access. This power-down operation is available in systems operating with an external power supply.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | alcd_start | 0, SC | 1 = Start ALCD |
14:13 | 00, RO | RESERVED: Writes ignored, read as 0. | |
12 | alcd_done | 0, RO | TPTD Diagnostic Bypass
1 = Bypass TPTD diagnostic. TDR on TPTD pair is not executed. 0 = TDR is executed on TPTD pair |
11:4 | alcd_out1 | 0000 0000, RO | alcd_out1 |
3 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0 |
2:0 | alcd_ctrl | 001,RW | Control of ALCD Average factor |
Use CDSCR1 to select the channel for the cable diagnostics test. CDSCR1 contains the enable and bypass bits for the diagnostic tests, and defines the number of executed and averaged TDR sequences. CDSCR2 - CDSCR4 configure other parameters for cable diagnostics.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
14 | Diagnostic Cross Disable | 0, RW | Cross TDR Diagnostic mode
1 = Disable TDR Cross mode – TDR will be executed in regular mode only 0 = Diagnostic of crossing pairs is enabled In Cross Diagnostic mode, the TDR mechanism is looking for reflection on the other pair to check short between pairs. |
13 | Diagnostic TPTD Bypass | 0, RW | TPTD Diagnostic Bypass
1 = Bypass TPTD diagnostic. TDR on TPTD pair will not be executed. 0 = TDR is executed on TPTD pair In bypass TPTD, results are available in TPRD slots. |
12 | Diagnostic TPRD Bypass | 0, RO | TPRD Diagnostic Bypass
1 = Bypass TPRD diagnostic. TDR on TPRD pair will not be executed. 0 = TDR is executed on TPRD pair |
11 | RESERVED | 1, RW | RESERVED: Must be Set to 1. |
10:8 | Diagnostics Average Cycles | 110, RW | Number Of TDR Cycles to Average:
<000>: 1 TDR cycle <001>: 2 TDR cycles <010>: 4 TDR cycles <011>: 8 TDR cycles <100>: 16 TDR cycles <101>: 32 TDR cycles <110>: 64 TDR cycles (default) <111>: Reserved |
7:0 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:4 | RESERVED | 1100 1000 0101, RW | RESERVED: Ignore on read |
3:0 | TDR pulse control | 1100, RW | Configure expected self reflection in TDR |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | Cable length cfg | 1111 1111, RW | Configure duration of listening to detect long cable reflections |
7:0 | RESERVED | 1111 1111, RW | RESERVED: Ignore on read |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:13 | RESERVED | 000, RW | RESERVED: Ignore on read |
12:8 | Short cables TH | 1 1000, RW | TH to compensate for strong reflections in short cables |
7:0 | RESERVED | 1001 0110, RW | RESERVED: Ignore on read |
This register provides the peaks locations after execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | TPTD Peak Location 2 | 0000 0000, RO | Location of the Second peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into distance from the PHY |
7:0 | TPTD Peak Location 1 | 0000 0000, RO | Location of the First peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into distance from the PHY |
This register provides the peaks locations after execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | TPTD Peak Location 4 | 0000 0000, RO | Location of the Fourth peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into distance from the PHY. |
7:0 | TPTD Peak Location 3 | 0000 0000, RO | Location of the Third peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into distance from the PHY. |
This register provides the peaks locations after execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | TPRD Peak Location 1 | 0000 0000, RO | Location of the First peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into distance from the PHY. |
7:0 | TPTD Peak Location 5 | 0000 0000, RO | Location of the Fifth peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into distance from the PHY. |
This register provides the peaks locations after execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | TPRD Peak Location 3 | 0000 0000, RO | Location of the Third peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into distance from the PHY. |
7:0 | TPRD Peak Location 2 | 0000 0000, RO | Location of the Second peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into distance from the PHY. |
This register provides the peaks locations after execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:8 | TPRD Peak Location 5 | 0000 0000, RO | Location of the Fifth peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into distance from the PHY. |
7:0 | TPRD Peak Location 4 | 0000 0000, RO | Location of the Fourth peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into distance from the PHY. |
This register provides the peaks amplitude measurement after the execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0,RO | RESERVED: Writes ignored, read as 0. |
14:8 | TPTD Peak Amplitude 2 | 000 0000, RO | Amplitude of the Second peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [15:8] in register CDLRR1 (0x180) |
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
6:0 | TPTD Peak Amplitude 1 | 000 0000, RO | Amplitude of the First peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [7:0] in register CDLRR1 (0x180) |
This register provides the peaks amplitude measurement after the execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0,RO | RESERVED: Writes ignored, read as 0. |
14:8 | TPTD Peak Amplitude 4 | 000 0000, RO | Amplitude of the Fourth peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [15:8] in register CDLRR2 (0x181) |
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
6:0 | TPTD Peak Amplitude 3 | 000 0000, RO | Amplitude of the Third peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [7:0] in register CDLRR2 (0x181) |
This register provides the peaks amplitude measurement after the execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
14:8 | TPRD Peak Amplitude 1 | 000 0000, RO | Amplitude of the First peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [15:8] in register CDLRR3 (0x182) |
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
6:0 | TPTD Peak Amplitude 5 | 000 0000, RO | Amplitude of the Fifth peak discovered by the TDR mechanism on Transmit Channel (TPTD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [7:0] in register CDLRR3 (0x182) |
This register provides the peaks amplitude measurement after the execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
14:8 | TPRD Peak Amplitude 3 | 000 0000, RO | Amplitude of the Third peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [15:8] in register CDLRR4 (0x183) |
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
6:0 | TPRD Peak Amplitude 2 | 000 0000, RO | Amplitude of the Second peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [7:0] in register CDLRR4 (0x183) |
This register provides the peaks amplitude measurement after the execution of the TDR. The values of this register are valid after reading 1 in Diagnostic Done bit 1 in register CDCR (0x1E).
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
14:8 | TPRD Peak Amplitude 5 | 000 0000, RO | Amplitude of the Fifth peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [15:8] in register CDLRR4 (0x184) |
7 | RESERVED | 0, RO | RESERVED: Writes ignored, read as 0. |
6:0 | TPRD Peak Amplitude 4 | 000 0000, RO | Amplitude of the Fourth peak discovered by the TDR mechanism on Receive Channel (TPRD). The value of these bits is translated into type of cable fault and-or interference. This amplitude value refers to peak location stored in bits [7:0] in register CDLRR4 (0x184) |
This register provides general measurement results after the execution of the TDR. The Cable Diagnostic software should post process this result together with other Peaks’ location and amplitude results.
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15 | TPTD Peak Polarity 5 | 0, RO | Polarity of the Fifth peak discovered by the TDR mechanism on Transmit Channel (TPTD) |
14 | TPTD Peak Polarity 4 | 0, RO | Polarity of the Fourth peak discovered by the TDR mechanism on Transmit Channel (TPTD) |
13 | TPTD Peak Polarity 3 | 0, RO | Polarity of the Third peak discovered by the TDR mechanism on Transmit Channel (TPTD) |
12 | TPTD Peak Polarity 2 | 0, RO | Polarity of the Second peak discovered by the TDR mechanism on Transmit Channel (TPTD) |
11 | TPTD Peak Polarity 1 | 0, RO | Polarity of the First peak discovered by the TDR mechanism on Transmit Channel (TPTD) |
10 | TPRD Peak Polarity 5 | 0, RO | Polarity of the Fifth peak discovered by the TDR mechanism on Receive Channel (TPRD) |
9 | TPRD Peak Polarity 4 | 0, RO | Polarity of the Fourth peak discovered by the TDR mechanism on Receive Channel (TPRD) |
8 | TPRD Peak Polarity 3 | 0, RO | Polarity of the Third peak discovered by the TDR mechanism on Receive Channel (TPRD) |
7 | TPRD Peak Polarity 2 | 0, RO | Polarity of the Second peak discovered by the TDR mechanism on Receive Channel (TPRD) |
6 | TPRD Peak Polarity 1 | 0, RO | Polarity of the First peak discovered by the TDR mechanism on Receive Channel (TPRD) |
5 | Cross Detect on TPTD | 0, RO | Cross Reflection were detected on TPTD. Indicate on Short between TPTD and TPRD |
4 | Cross Detect on TPRD | 0, RO | Cross Reflection were detected on TPRD. Indicate on Short between TPTD and TPRD |
3 | Above 5 TPTD Peaks | 0, RO | More than 5 reflections were detected on TPTD |
2 | Above 5 TPRD Peaks | 0, RO | More than 5 reflections were detected on TPRD |
1:0 | RESERVED | 00, RO | RESERVED: Writes ignored, read as 0 |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:4 | RESERVED | RO | |
3:0 | alcd_out2 | <0011>, RW | Control word to analog PGA |
BIT | BIT NAME | DEFAULT | DESCRIPTION |
---|---|---|---|
15:12 | RESERVED | 0000, RO | RESERVED |
11:0 | FAGC Accumulator | 0110 0000 0000, RW | FAGC Accumulator: |