The PCS PMA TEMAC Status (PPST) register is shown in the following figure. This register reports valid information when the subsystem is configured for SGMII or 1000BASE-X with the TEMAC operating at 10/100/1000 Mb/s (C_TYPE = 1 and C_PHY_TYPE = 4 or 5). It provides additional information about the serial interface status. For all other configurations, this register returns zeros.
The following table shows the PCS PMA TEMAC Status register bit definitions.
Bits | Name | Access | Reset Value | Description |
---|---|---|---|---|
31:14 | Reserved | RO | 0x000000 | Reserved |
13 | RmtFlt | RO | 0 |
RmtFlt: Remote Fault (1000BASE-X
only) When this bit is logic one, it indicates that a remote fault is detected and the type of remote fault is indicated by bits[9:8]. Note: This
bit is only de-asserted when an MDIO read is made
to status register (register 1 in
See
Management Status Register (Register
1)
). This signal has no
significance in SGMII PHY mode.
|
12 | Duplex | RO | 0 |
Duplex: Duplex Mode. This bit
indicates the Duplex mode negotiated with the link
partner
|
11:10 | Speed | RO | 00 |
Speed: Speed. This signal
indicates the speed negotiated and is only valid
when Auto-Negotiation is enabled. The signal
encoding is:
|
9:8 | RmtFltEnc | RO | 00 |
RmtFltEnc: Remote Fault Encoding
(1000BASE-X only). This signal indicates the remote fault encoding (IEEE 802.3-2008 table 37-3). This signal is validated by bit 13, RmtFlt, and is only valid when Auto-Negotiation is enabled. |
7 | PhyLinkStatus | RO | 0 |
PhyLinkStatus: PHY Link Status
(SGMII only). When operating in SGMII mode, this bit represents the link status of the external PHY device attached to the other end of the SGMII link (High indicates that the PHY has obtained a link with its link partner; Low indicates that is has not linked with its link partner). When operating in 1000BASE-X mode this bit remains Low and should be ignored. |
6 | RXNOTINTABLE | RO | 0 | RXNOTINTABLE: Receive Not In Table. The subsystem has received a code group which is not recognized from the 8B/10B coding tables. |
5 | RXDISPERR | RO | 0 | RXDISPERR: Receive Disparity Error.The subsystem has received a running disparity error during the 8B/10B decoding function. |
4 | RUDI_INVLD | RO | 0 | RUDI_INVLD: RUDI(/INVALID/). The subsystem has received invalid data while receiving/C/ or/I/ ordered set. |
3 | RUDI_I | RO | 0 | RUDI_I: RUDI(/I/). The subsystem is receiving /I/ ordered sets (Idles) |
2 | RUDI_C | RO | 0 | RUDI_C: RUDI(/C/). The subsystem is receiving /C/ ordered sets (Auto-Negotiation Configuration sequences). |
1 | LinkSync | RO | 0 | LinkSynch: Link Synchronization. This signal indicates the state of the synchronization state machine (IEEE802.3 figure 36-9) which is based on the reception of valid 8B/10B code groups. This signal is similar to Bit[0] (Link Status), but is NOT qualified with Auto-Negotiation. When High, link synchronization has been obtained and in the synchronization state machine, sync_status = OK. When Low, synchronization has failed. |
0 | LinkStatus | RO | 0 | LinkStatus: Link Status. This signal indicates the status of the link. When High, the link is valid: synchronization of the link has been obtained and Auto-Negotiation (if present and enabled) has successfully completed. When Low, a valid link has not been established. Either link synchronization has failed or Auto-Negotiation (if present and enabled) has failed to complete. When auto-negotiation is enabled this signal is identical to Bit[1]. |