45. Management Data Input/Output (MDIO) Interface - IEEE-SA
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 201545. Management Data Input/Output (MDIO) Interface45.2 45.2 MDIO Interface Registers Registers45.2.1 45.2.1 PMA/PMD registers45.2.1.6 PMA/PMD control 2 register (Register 1.7)Change the description of bits 1.7.5:0 of Table 45-4 7 to add the 1000BASE-RH as shown below, (publication editor will change “reserved” lines as appropriate for values defined by other approved amendments):Table 45–7—PMA/PMD control 2 register bit /PMD type selection5432101 1 0 1 0 1 1000BASE-RH PMA/PMDR/W Read/Write, RO Read only45.2.3 PCS registersReplace 3.420 through 3.1799 row with the following rows:Table 45–119—PCS registersRegister addressRegister nameSubclause3.420 through 3.499Reserved3.500TXOAM CTRL1000BASE-H OAM transmit control45.2.3.483.501 through 3.508TXOAM DATAx registers1000BASE-H OAM transmit message45.2.3.483.509RXOAM CTRL1000BASE-H OAM receive control45.2.3.4845.2.3.493.510 through 3.517RXOAM DATAx registers1000BASE-H OAM receive message45.2.3.4845.2.3.493.5181000BASE-H PCS control45.2.3.503.5191000BASE-H PCS status register 145.2.3.513.5201000BASE-H PCS status register 245.2.3.523.5211000BASE-H PCS status register 345.2.3.533.5221000BASE-H PCS status register 445.2.3.543.523 through 3.1799ReservedCopyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 51525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Insert the below subclauses after 45.2.3.47 and renumber subsequent subclauses as required:45.2.3.48 1000BASE-H OAM transmit registers (Registers 3.500 through 3.517508)These registers are used to provide an OAM channel between 1000BASE-H link partners. The OAMmessage is part of the physical header data (PHD) defined for 1000BASE-H (see Table 114–2).These registers are used to provide a OAM channel between 1000BASE-H link partners. The OAM messageis part of the physical header data subframe defined for 1000BASE-H (see Table 114–2). The transmit registers are used to compose an OAM message prior to requesting transmission to the link partner. An OAM TXcontrol/status register Register 3.500 provides control, status status, message identification and messageheader data information. Eight additional OAM TX registers hold the rest of the OAM message data. TheOAM RX stores status and received OAM message header information. Eight additional OAM RX registershold received OAM message data. .Table 45–120—OAM TX registers mission Request. It is raised by the ME to requestthe transmission of a new message. It is set to 0 by thelocal PHY to indicate that it has started the transmissionof the message.R/W3.500.14PHYTPHY Toggle bit. Corresponds to the toggle bit of the lastmessage received by the remote PHY.RO3.500.13MERTManagement Entity Read Toggle bit. Toggle bit of the lastmessage read by the Management Entity attached to theremote PHY.RO3.500.12MSGTMessage Toggle Bit. Toggles with each successive transmitted message and is used for message identification.RO3.500.11:0TXOAM HDROAM message control information. Intended to be usedby the ME to indicate the type or some information relevant about the content of OAM DATA0 through OAM DATA7 message for the proper processing of the OAMmessage by the remote ME. This information is notmanipulated by the PHY and is transparently transmittedto the link partner together with the OAM message contained in OAM DATA0 through OAM DATA7 registers.R/W3.503.15:0TXOAM DATA1OAM message 16-bit data word 1.R/W3.504.15:0TXOAM DATA2OAM message 16-bit data word 2.R/W3.505.15:0TXOAM DATA3OAM message 16-bit data word 3.R/W3.506.15:0TXOAM DATA4OAM message 16-bit data word 4.R/W3.507.15:0TXOAM DATA5OAM message 16-bit data word 5.R/WCopyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 495051525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Table 45–120—OAM TX registers definitions M DATA6OAM message 16-bit data word 6.R/W3.508.15:0TXOAM DATA7OAM message 16-bit data word 7.R/WR/W Read/Write, RO Read onlyThe assignment of bits in the 1000BASE-H OAM transmit registers is shown in Table 45–121.Table 45–121—1000BASE-H OAM transmit register bit definitionsBit(s)aNameDescriptionR/Wa3.500.15TXO REQTransmission request. It is set to one by the ManagementEntity to request the transmission of a new OAMMessage. It shall be set to zero by the local PHY toindicate that the message has been accepted fortransmission.R/W,SC3.500.14TXO PHYTTransmit Message Phy Toggle bit. It corresponds to thetoggle bit of the last message received by the remote PHY.RO3.500.13TXO MERTTransmit Message Management Entity Read Toggle bit. Itcorresponds to the toggle bit of the last message read bythe Management Entity attached to the remote PHY.RO3.500.12TXO MSGTTransmit Message Toggle bit. This bit toggles with eachnew transmitted message and is used for messageidentification.RO3.500.11:0TXO TYPETransmit Message data type information. Together withTXO DATA1 through TXO DATA8, it contains thepayload of the OAM message. This information is notmanipulated by the PHY and it is transparentlytransmitted to the link partner.R/W3.501.15:0TXO DATA1Transmit message 16-bit data word 1.R/W3.502.15:0TXO DATA2Transmit message 16-bit data word 2.R/W3.503.15:0TXO DATA3Transmit message 16-bit data word 3.R/W3.504.15:0TXO DATA4Transmit message 16-bit data word 4.R/W3.505.15:0TXO DATA5Transmit message 16-bit data word 5.R/W3.506.15:0TXO DATA6Transmit message 16-bit data word 6.R/W3.507.15:0TXO DATA7Transmit message 16-bit data word 7.R/W3.508.15:0TXO DATA8Transmit message 16-bit data word 8.R/WR/W Read/Write, RO Read only, SC Self-clearingCopyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to change.27
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 201545.2.3.48.1 TXREQ TXO REQ (3.500.15)This bit is set to request the transmission of a new OAM message. It is reset to 0 by the local PHY to indicatethat the transmission of the last requested message has started and it is ready to accept a new request fortransmission.This bit is set to one by the Management Entity to request the transmission of the OAM message written toregisters 3.500 through 3.508. It shall be set to zero by the local PHY to indicate that the message has beenaccepted for transmission, and that the registers are free to accept a new message.45.2.3.48.2 MSGT TXO PHYT (3.500.14)This bit is used for OAM message identification. It is toggled by the local PHY whenever a new message isaccepted for transmission.45.2.3.48.3 PHYT (3.500.13)This The local PHY shall indicate in this bit is the MSGT TXO MSGT bit of the last message received fromby the remote PHY.45.2.3.48.4 MERT TXO MERT (3.500.1213)This The local PHY shall indicate in this bit corresponds to the MSGT TXO MSGT bit of the last messageread by the ME Management Entity attached to the remote PHY. .45.2.3.48.5 TXOAM HDR TXO MSGT (3.500.11:012)These bits become the PHD.OAM.HDR bits upon transmission request.This bit is used for message identification; it shall contain the toggle bit of the last message accepted by thelocal PHY for transmission. It shall be toggled by the local PHY when it accepts a new message for transmission (simultaneously with the falling of bit TXO REQ)Together with bits TXO REQ, TXO PHYT and TXO MERT, this bit indicates the status of the OAMtransmission channel. There can be up-to three outstanding messages in the transmission channel: messagewritten in the OAM transmission registers that is waiting for transmission, the message being currentlytransmitted by the local PHY, and the message available in the OAM reception registers of the remote PHYwhich is waiting for processing of the remote Management Entity.Table 45–122 shows all the possible values of the four control bits, and the corresponding status of the threepossible outstanding OAM messages. The control bits can be either 0 or 1, the symbol denotes logical notoperator. Message K is the message currently being transmitted by the local PHY to the remote PHY, itsassociated toggle bit takes value ‘a’ as indicated by bit TXO MSGT. Correspondingly, message K-1denotes the previous message that was transmitted by the local PHY to the remote PHY. Its associated toggle bit takes value ‘ a’. Finally message K 1 corresponds to the OAM message being composed or yet to berequested for transmission by the local Management Entity. Its associated toggle bit will take value ‘ a’.45.2.3.48.6 TXO TYPE (3.500.11:0)These bits contain the data type of the OAM message that will be transmitted by the local PHY. These bitsare not manipulated in any way by the local or remote PHY and together with the TXO DATAx bits carrythe OAM message payload.Copyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 51525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Table 45–122—List of all possible 1000BASE-H OAM message statusTXOREQTXOPHYTTXOMERTTXOMSGTMessage K 1status0aaaNot written by localMESent by local PHYACK by remote PHYACK by remote MESent by local PHYACK by remote PHYACK by remote ME0 a aaNot written by localMESent by local PHYNo ACK by remotePHYNo ACK by remote MESent by local PHYACK by remote PHYACK by remote ME0a asNot written by localMESent by local PHYACK by remote PHYNo ACK by remote MESent by local PHYACK by remote PHYACK by remote ME0 aaaNot written by localMESent by local PHYNo ACK by remotePHYNo ACK by remote MESent by local PHYACK by remote PHYNo ACK by remote ME1aaaWritten by local MEPendingtransmission bylocal PHYSent by local PHYACK by remote PHYACK by remote MESent by local PHYACK by remote PHYACK by remote ME1 a aaWritten by local MEPendingtransmission bylocal PHYSent by local PHYNo ACK by remotePHYNo ACK by remote MESent by local PHYACK by remote PHYACK by remote ME1a aaWritten by local MEPendingtransmission bylocal PHYSent by local PHYACK by remote PHYNo ACK by remote MESent by local PHYACK by remote PHYACK by remote ME1 aaaWritten by local MEPendingtransmission bylocal PHYSent by local PHYNo ACK by remotePHYNo ACK by remote MESent by local PHYACK by remote PHYNo ACK by remote MEMessage K statusMessage K-1 status45.2.3.48.7 TXOAM DATA TXO DATAx (Registers 3.501 through 3.508)These registers contain the 128-bit OAM message data which become PHD.OAM.DATA upon transmissionrequest. The first 16 transmitted bits (PHD.OAM.DATA0) and are stored in TXOAM DATA1 (register3.501) with subsequent bits stored sequentially in registers 3.502 through 3.508.Table 45–123—1000BASE-X OAM RX registers eception Valid. The PHY sets to one to indicatethat a new message has arrived and is ready for processing.RO3.510.14:13ReservedIgnore on readROCopyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 51525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Table 45–123—1000BASE-X OAM RX registers definitions (continued)Bit(s)NameDescriptionR/Wa3.510.12RX MSGTMessage Toggle Bit. Toggles with each successive transmitted message and is used for message identification.RO3.510.11:0RX OAM HDROAM message control information. Intended to be usedby the ME to indicate the type or some information relevant about the content of OAM DATA0 through OAM DATA7 message for the proper processing of the OAMmessage by the remote ME. This information is notmanipulated by the PHY and is transparently transmittedto the link partner together with the OAM message contained in OAM DATA0 through OAM DATA7 registers.RO3.511.15:0RX OAM DATA1OAM message 16-bit data word 1.RO3.512.15:0RX OAM DATA2OAM message 16-bit data word 2.RO3.513.15:0RX OAM DATA3OAM message 16-bit data word 3.RO3.514.15:0RX OAM DATA4OAM message 16-bit data word 4.RO3.515.15:0RX OAM DATA5OAM message 16-bit data word 5.RO3.516.15:0RX OAM DATA6OAM message 16-bit data word 6.RO3.517.15:0RX OAM DATA7OAM message 16-bit data word 7.ROaR/W RO Read onlyThese registers contain the 128 data bits of the OAM message that will be transmitted by the local PHY45.2.3.49 1000BASE-H OAM control/status receive registers (Registers 3.509 through 3.517)These register are used to control and monitor the transmission of an OAM message stored in OAM DATA0:7. It includes 4 bits related to OAM message transmission and 12 user control bits for use as a header tothe OAM message.These registers are used to provide an OAM channel between 1000BASE-H link partners. The OAMmessage is part of the physical header data defined for 1000BASE-H (see Table 114–2).The receive registers hold the OAM messages received from the link partner. Register 3.509 provides statusinformation, message identification and message data information. Eight additional registers hold the rest ofthe received OAM message dataThe assignment of bits in the 1000BASE-H OAM receive registers is shown in Table 45–124.Table 45–124—1000BASE-H OAM receive register bit definitionsBit(s)NameDescription3.509.15RXO VALReception valid. The PHY sets this bit to one to indicatethat a new message has arrived and it is ready forprocessing.RO3.509.14:13ReservedIgnore on readROCopyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 495051525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Table 45–124—1000BASE-H OAM receive register bit definitionsBit(s)NameDescriptionR/Wa3.509.12RXO MSGTReceive Message Toggle bit. This bit toggles with eachnew received message and is used for messageidentification.RO3.509.11:0RXO TYPEReceive Message data type information. Together withRXO DATA1 through RXO DATA8, it contains thepayload of the OAM message.RO3.510.15:0RXO DATA1Receive message 16-bit data word 1.RO3.511.15:0RXO DATA2Receive message 16-bit data word 2.RO3.512.15:0RXO DATA3Receive message 16-bit data word 3.RO3.513.15:0RXO DATA4Receive message 16-bit data word 4.RO3.514.15:0RXO DATA5Receive message 16-bit data word 5.RO3.515.15:0RXO DATA6Receive message 16-bit data word 6.RO3.516.15:0RXO DATA7Receive message 16-bit data word 7.RO3.517.15:0RXO DATA8Receive message 16-bit data word 8.ROaRO Read only45.2.3.49.1 RXVAL RXO VAL(3.509.15)The PHY sets this bit to one to indicate the reception of an OAM message. It is set to zero when register3.517 is read. (This supports reading all nine registers with OAM message content without the registerschanging.)The local PHY shall set this bit to one to indicate the reception of a new OAM message. It shall be set tozero when the message is processed by the Management Entity. The PHY shall not update the receptionmessage registers with a new message until the previous message is processed by the Management Entity.The Management Entity signals that it has finished processing the message by first reading register 3.509having RXO VAL bit set to one, and then reading register 3.517. It is not required that the two accesses arecontiguous; the Management Entity can access any other management register in between.45.2.3.49.2 Reserved RXO MSGT (3.509.14:1312)The corresponding two bits of the received OAM message are not to be written to the register.This bit contains the toggle identifier of the received message. It shall toggle with every new received message.45.2.3.49.3 RXMSGT RXO TYPE (3.509.1211:10)This bit is the received PHD.OAM.MSGT bit.These bits contain the data type of the OAM message. These bits are not manipulated in any way by thePHY, and together with the RXO DATAx bits carry the received OAM message payload.Copyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 51525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 201545.2.3.49.4 RXOAM HDR RXO DATAx (3.509.11:012)These registers contain the 128 data bits are of the received PHD.OAM.HDR bitsOAM message.45.2.3.49.5 RXOAM DATA (Registers 3.510 through 3.517)These registers contain the received 128-bit PHD.OAM.DATA. The first 16 received bits arePHD.OAM.DATA0 and are stored in RXOAM DATA1 (register 3.510) with subsequent bits storedsequentially in registers 3.511 through 3.517.45.2.3.50 1000BASE-H PCS control register (Register 3.518) !)Table 45–125—1000BASE-H PCS control register bit on modeLoopback modeDescriptionR/WaR/W15 140 00 00 10 11 01 01 113010101x Normal operation Test mode 1 Test mode 2 Test mode 3 Test mode 4 Test mode 5 Reserved12 110 00 00 10 11 x100101x No loopback PCS GMII level loopback PCS PMD interface level loopback Line loopback ReservedR/WLoopback modes are only operative in normal operation(no test mode is configured)a3.518.9:2ReservedIgnore on readRO3.518.1OAM enable1 Enable OAM functionality0 Disable OAM functionalityR/W3.518.0EEE enable1 Enable LPI mode0 Disable LPI modeR/WR/W Read/Write, RO Read onlyThe assignment of bits in the 1000BASE-H PCS control register is shown in Table 45–126.45.2.3.50.1 Operation mode (3.518.15:13)These bits have a default value of 000, selecting normal 1000BASE-H operation. The various test modes aredefined in 114.8.45.2.3.50.2 Loopback mode (3.518.12:10)These bits have a default value of 0000 0 0, selecting normal 1000BASE-H no loopback operation. .Copyright 2015 IEEE. All rights reserved.This is an unapproved IEEE Standards draft, subject to 51525354
Draft Amendment to IEEE Std 802.3-201xIEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task ForceIEEE Draft P802.3bv/D1.1 812th July 2015Table 45–126—1000BASE-H PCS control register bit on modeLoopback modeDescriptionR/WaR/W15 140 00 00 10 11 01 01 113010101x Normal operation Test mode 1 Test mode 2 Test mode 3 Test mode 4 Test mode 5 Reserved12 110 00 00 10 11 x100101x No loopback PCS GMII level loopback PCS PMD interface level loopback Line loopback ReservedR/WLoopback modes are only operative in normal operation(no test mode is configured)3.518.9:2ReservedIgnore on readRO3.518.1OAM enable1 Enable OAM functionality0 Disable OAM functionalityR/W3.518.0EEE enable1 Enable LPI mode0 Disable LPI modeR/WaR/W Read/Write, RO Read onlyIn PCS GMII level loopback, the 1000BASE-H PCS shall accept data on the transmit data path from theGMII GMII, looping the data back to th
3.522 1000BASE-H PCS status register 4 45.2.3.54 3.523 through 3.1799 Reserved. Draft Amendment to IEEE Std 802.3-201x IEEE Draft P802.3bv/D1.1_8 . Draft Amendment to IEEE Std 802.3-201x IEEE Draft P802.3bv/D1.1_8 IEEE 802.3bv Gigabit Ethernet Over Plastic Optical Fiber Task Force 12th July 2015 3
10 VIN10 Input of high current output switch 11 VIN11 Input of high current output switch 12 VIN12 Input of high current output switch 13 VIN13 Input of high current output switch 14 VIN14 Input of high current output switch 15 VIN15 Input of high current output switch 16 VIN16 Input of high current outp
NxM ("N by M") switch ! Often N M ! Goals " High throughput ! Best is MIN(sum of inputs, sum of outputs) " Avoid contention " Good scalability ! Linear size/cost growth Input Port Input Port Input Port Input Port Input Port Input Port Output Port Output Port Output Port Output Port Output Port Output Port Switch Fabric
500 100/120V ac 1746-IA16 Input 16 120V ac Input 15 101 200/240V ac 1746-IM4 Input 4 240V ac Input 15 301 200/240V ac 1746-IM8 Input 8 240V ac Input 15 501 200/240V ac 1746-IM16 Input 16 240V ac Input 15 2703 100/120V ac 1746-OA8 Output 8 120/240V ac Output 17
JMP is interactive, comprehensive, visual software from SAS. It . Reader Input Input & Output Inquiry Report Sales Report Output Output Store System Inventory Database CRUD Logical File Interface Input & Output Cash Register Input Bar Code Label Maker Output Output Cas
8 bit voltage output DAC Programmable Input / Output Line Programmable Input / Output Line Programmable Input / Output Line Programmable Input / Output Line LM740 Page 3 of 8 44(0) 207 428 2647 www.lm-technologies.com sales@lm-technologies.com ANT Balun BFP DC / DC Converter & Charger X'tal 26Mhz VDD 1V8 SPI Charger Input 4.5V - 6.5V .
9 9 9 OUT2 Driver Output 2 Output 3 3 3 GNDP Power Ground. Connect to ground plane (GND). GND 7 7 7 V18 LDO Output Pin. Connect 1μF from V18to GND. Output 4 — 4 IN1 CMOS PWM Input 1 Logic Input — 5 — ENBL Enable Logic Input Logic Input 5 — 5 IN2 CMOS PWM Input 2 Logic Input MAX22201/MAX22202/ MAX22207 36V, 3.5A Brushed Motor Driver with
IN(X) 2, 4 2, 4 Input non-inverting op amp input terminal IN(X)- 1, 5 1, 5 Input inverting op amp input terminal OUT(X) 11, 7 13, 9 Output Op amp output OTF/SH_DN 3 3 Input/output Over temperature flag and Shutdown (see Table 1 for truth table) VCC_O(X) 8, 10 10, 12 Input Out
external drain shield to the appropriate earth ground on one end. INPUT BOARD Input 3 Common Input 3 Input 4 Common Input 4 Input 1 Input 1 Common Input 2 Input 2 Common Relay 1 NO Relay 1 C Relay 1 NC Chassis GND At Other Panel 1 2 3 485-Com 485-Com - Com-Gnd RS 485 Com Bus Cable From Diff. Panel (Remote Mount Only) Power J1 - RS485 .
