JL82572EI Intel, JL82572EI Datasheet

Page 1

... Intel 82571EB/82572EI Ethernet ® Controller Specification Update July 2010 Revision 6.3 322206US ...

Page 2

... Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents that have an ordering number and are referenced in this document, or other Intel literature, may be obtained from: Intel Corporation P ...

Page 3

Specification Update Revision History Revision Revision Date 1.0 Jan 2004 1.1 Jan 2004 1.2 Feb 2004 1.3 Mar 2004 1.4 Apr 2004 1.5 May 2004 1.6 Jun 2004 1.7 Jul 2004 1.8 Jan 2005 1.9 Jun 2005 2.0 Sep ...

Page 4

... Gigabit Ethernet Controller Datasheet, Intel Corporation. • 82571EB/82572EI Gigabit Ethernet Controller Design Guide, Intel Corporation. • PCIe* Family of Gigabit Ethernet Controllers Software Developer's Manual, Intel Corporation This document is intended for hardware system manufacturers and software developers of applications, operating systems or tools. It may contain Specification Changes, Errata, and Specification Clarifications ...

Page 5

Specification Update 2. Nomenclature This document uses various definitions, codes, and abbreviations to describe the Specification Changes, Errata, Sightings and/or Specification Clarifications that apply to the listed silicon/steppings: Table 1. Definitions Name Modifications to the current published specifications. These ...

Page 6

Codes and Abbreviations Name Specification Change, Erratum, or Specification Clarification that applies to this stepping. X Document change or update that will be implemented. Doc This erratum is intended to be fixed in a future stepping of the component. ...

Page 7

... Revision ID is located at Config address 0x8 bits 7:0 323853 Revision: 6.3US July 2010 Top Marking Q-Specification JL82571EB Q866 HL82571EB Q864 JL82572EI Q867 HL82572EI Q865 JL82571EB N/A HL82571EB N/A JL82572EI N/A HL82572EI N/A Vendor Device ID ID 8086 105E 8086 105F 8086 1060 8086 107D 8086 107E 8086 ...

Page 8

... Table 4. MM Numbers Product HL82571EB HL82572EI JL82571EB JL82572EI Figure 1. Example 82571EB/82572EI Identifying Marks Note: Lead-free parts will have “JL” as the prefix for the product code (vs. “HL”) and the “Q” designator refers to the Q Specification number in the table above. Note: The devices can also have a “ ...

Page 9

Specification Update 5. Summary Table of Changes No. D0 Plans SMBus Operation at 1MHz Not Supported Doc iSCSI Header Split Is Not Supported 2 X Doc The EEPROM Initialization Control 2 (word 0Fh) bit ...

Page 10

Enabling or Disabling RSS in the Middle of Received Packets 18 X NoFix May Stop Receive Flow. Packets with IPV6-Tunneled-in-IPV4 with a Certain Value NoFix Last IP Options Will Have an Incorrect RSS Hash Value. Formed and ...

Page 11

Specification Update First Two Bytes Packet Forwarded to the BMC Might Image Dropped, Degrading Performance. SMBus Might Hang if the BMC Is Reset in the Middle Fix. Transaction. ...

Page 12

MDI Return Loss Is Marginal Near 40MHz at 115ohm Load Doc PCIe Output Driver Amplitude Can Be Set Incorrectly By the 5 X Doc EEPROM. Only One Port Can Be Disabled at a Time; LAN Disable 6 X ...

Page 13

Specification Update 6. Specification Changes 1. SMBus Operation at 1 Mhz Is Not Supported (400 kHz Operation Not Affected) Operation of the SMBus at 1 MHz is not supported. Operation at the standard SMBus frequency (400 kHz) is not ...

Page 14

Packet types supported by the packet split: The 82571/82572 provides header split for the packet types listed below. Other packet types are posted sequentially in the buffers of the packet split receive buffers. Packet Type 0x0 MAC , (VLAN/SNAP) Payload ...

Page 15

... ECC error Writing 1 to this bit clears the error counter and error 0 address fields When set, enables single bit ECC error correction. When 0 clear, ECC errors will be detected, but not corrected. Intel recommends that this bit be enabled. Description 82571/82572 Specification Update Datasheet 17 ...

Page 16

Errata 1. When Two Functions Have Differing MAX_PAYLOAD_SIZE, the Device Might Use the Larger Value For All Functions. Problem: MAX_PAYLOAD_SIZE is programmed per function. If two PCIe functions have different MAX_PAYLOAD_SIZE, the device might use the larger value for ...

Page 17

Specification Update 4. PCIe Differential- and Common-Mode Return Loss Is Higher Than Specified Value. Problem: The PCIe transmitter’s differential return loss instead of the -10 dB requirement. A PCIe Engineering Change Notice sets -10 ...

Page 18

... Workaround: The driver must ensure that the first descriptor points to the (L2+L3+L4) Header and at least two bytes of the data (payload). This has been implemented in the Intel drivers. This workaround must be applied before activating TSO when MULR=1. Alternatively, register 0x3940 “TARC1” bit 22 can be set at initialization time to workaround this issue ...

Page 19

Specification Update 2 10 Transactions: When Working with Bus Speeds 400 KHz or Higher, the Bus Might Hang When the Master Reads More Bytes than the Slave Reported. Problem: When working in I responds with a block ...

Page 20

... XOFF packet(s). Workaround: To minimize the likelihood of a Receive FIFO overrun, Receive Flow-Control Thresholds should be based on the expected maximum pause interval in the link partner’s XOFF packet. This has been implemented in the Intel drivers. Status: No Fix: There are no plans to fix this erratum. ...

Page 21

Specification Update 15. Missed RX Packets. Problem: When the device operates with multiple-requests or Large Send enabled, there could be receive packet loss. When the Tx FIFO is full, the Tx flow may block the host DMA interface of ...

Page 22

... WoL uses RAR[0] only, magic packets to port 0 will not wake up the system. This has been implemented in the Intel drivers. The following information shows how the workaround can be implemented: • A boolean flag named laa_is_present is added to the adapter structure to identify to the driver that the workaround applied ...

Page 23

... Set the appropriate LAA in RAR[ (adapter->hw.mac_type == e1000_82571 && adapter->hw.laa_is_present) Intel drivers share some common functions, which have been adapted to this issue: • e1000_rar_set() is used to update the RAR registers. No changes are required to adapt to this issue, but it is the function used by the following functions. • ...

Page 24

Clear RAR[1-15] */ num_rar_entry = E1000_RAR_ENTRIES; /* Reserve a spot for the Locally Administered Address to work around if ((hw->mac_type == e1000_82571) && (hw->laa_is_present == TRUE)) for(i = rar_used_count; i < num_rar_entry; i++) { } /* Clear the MTA ...

Page 25

... RSS hash value to the stack. The TCP stack will calculate the RSS hash value for a TCP packet, which will prevent it from being dropped. This has been implemented in the Intel drivers. Status: No Fix: There are no plans to fix this erratum. ...

Page 26

Workaround: None. Status: No Fix: There are no plans to fix this erratum. F 21. alse Detection of an idle_match Condition on the SerDes Interface. Problem: The idle_match function is used during the auto-negotiation process for 1000 BASE-X applications (SerDes). ...

Page 27

Specification Update 23. Frames with Alignment Errors. Problem: The device discards a frame with extra bits. According to IEEE 802.3 2002 section 4.2.4.2.1, a frame containing a non-integer number of octets should be truncated to the nearest octet boundary. ...

Page 28

Link Pulse Hits the Template Mask Due to Voltage Ripple/Glitch Problem: The 10base-T link pulse touches the template due to voltage ripple/glitch. 82571/82572 Specification Update Datasheet 30 82571/82572 Specification Update 323853 Revision: 6.3US July 2010 ...

Page 29

Specification Update Implication: Compliance with the specification is not complete, however, there is no effect at system level. Workaround: None. Status: No Fix: There are no plans to fix this erratum. 28. 10base-T TP_IDL Template Failure. Problem: The 10base-T ...

Page 30

Reception of Undersized Frames Affects Good Frame Reception. Problem: If the device receives a one-byte fragment, then the following first-received frame will be discarded. Implication: After receiving a frame with a one-byte fragment, the device rejects the following first- ...

Page 31

Specification Update 34. Device Sends Only One XOFF Even if the Link Partner Has Timed Out and It Is Still Congested. Problem: When Flow Control is enabled, the device should periodically send XOFF packets as long ...

Page 32

... A power-saving feature: When in Electrical-Idle for the PCIe bus, Receive is not enabled. Workaround: Use an EEPROM image based on dev starter version. 5.9 or above. Status: Fixed in EEPROM dev starter version. 5.9 and above. Contact your Intel representative to ensure you have the latest EEPROM release. 39. ...

Page 33

Specification Update 40. PCIe Bus Can Halt upon D3/L1 Entry If There Are Less Than 16 Posted Data (PD) Flow Control Credits (=256byte memory writes). Problem: The device PCIe transmit bus will halt when entering D3/L1 power states if ...

Page 34

... Implication: The firmware reset will cause the loss of the previous state and disconnect open RMCP sessions. Workaround: Fixed in EEPROM dev starter image version 5.10 and above. This firmware will discard packets sent while the link is down after timeout. Contact your Intel representative to ensure you have the latest EEPROM release. Status: Fixed in EEPROM dev starter version ...

Page 35

... Implication: Normal manageability traffic, such as KVM and Ping will halt in less than 15 minutes. Workaround: There is no workaround. Status: Fixed in EEPROM dev starter version. 5.12 and above. Contact your Intel representative to ensure you have the latest EEPROM release. 323853 Revision: 6.3US ...

Page 36

... Implication: The BMC will attempt to recover packets by comparing bytes received with the original packet length. This process slows perforance. Workaround: No workaround. Status: Fixed in EEPROM dev starter version. 5.12 and above. Contact your Intel representative to ensure you have the latest EEPROM release. 51. SMBus Might Hang if the BMC Is Reset in the Middle of a Transaction ...

Page 37

... Kg is NULL. Workaround: Use NULL password and NULL Kg, or always configure a Kg. Status: Fixed in EEPROM dev starter version. 5.12 and above. Contact your Intel representative to ensure you have the latest EEPROM release. 323853 Revision: 6 ...

Page 38

... The 82571EB/82572EI uses the SIK instead of the K1 key (please refer to the IPMI 2.0 specification for more information on RAKP messages and keys). The Intel Redirection SDK has the same defect in it; as such, a RMCP+ session can be properly established using the SDK, however other utilities such as IPMITool will fail when a session is established due to the integrity check failure. Workaround: RMCP+ session establishment can be modified in the user’ ...

Page 39

... Workaround: There is no work-around for this issue. Status: Fixed in EEPROM dev starter version. 5.12 and above. Contact your Intel representative to ensure you have the latest EEPROM release. 62. “Update User Password” Command Incorrectly Accepts Less ...

Page 40

Wakeup Event Occurs on Magic Packet that Doesn’t Pass Address Filter Problem: The 82571/82572 receives a magic packet that didn’t pass address filtering. The 82571/ 82572 will generate a wakeup event at the next packet if the next received ...

Page 41

Specification Update 67. 82571EB-82572EI Improperly Implements the Auto- Negotiation Advertisement Register. Problem: The 82571EB-82572EI improperly transmits the Link Code Word due to a write to register 4. The Link Code Word improperly switch immediately, which corresponds to a write ...

Page 42

Implication: When the failure occurs, the actual completion data from the new request will be corrupted. The implications of this corruption of the read data depend on the type of request the 82571/82572 was starting to send and are described ...

Page 43

Specification Update Status: No Fix 71. Link Indication: LED Remains Power State in SerDes Mode. Problem: The LED might remain power state when SerDes power down is enabled (EEPROM word 0xF, bit 2; ...

Page 44

... However, when using legacy interrupts and sharing interrupts between devices, the software may poll all the devices to find the source of the interrupt, including those devices that did not assert an interrupt. There may also be other situations in non-Intel drivers where ICR is polled even when no interrupt has been asserted. ...

Page 45

Specification Update standard Ethernet/IP/TCP headers of 54 bytes, this means that the buffer should not start 54-118 bytes before boundary. For example, 128-byte alignment for this buffer could be used to fulfill this condition. Status: No ...

Page 46

... Clarification: Link may fail if Auto MDI-X is enabled during forced 100BASE-TX mode operation. Since the device does not disable this function automatically, the driver must perform this step. Auto MDI-X can be disabled by clearing PHYREG18.12. Intel’s software drivers have been implemented in this way. ...

Page 47

... If EEPROMs with the Manageability modes enabled have been used, please contact you Intel representative to ensure you have the latest EEPROM image required for your system. If you need an updated EEPROM image, it can be obtained from your Intel representative. 323853 Revision: 6.3US July 2010 ...

Page 48

... PCI Bus Power Management Interface Specification Revision 1.1 value of 375 mA on the 3.3Aux voltage rail. In order to always meet this specification, only one port should be enabled for WOL in the 82571EB. Intel Drivers limit the use of WOL to Port 0(Port A) of the 82571EB. ...

Page 49

... LINK_UP or LINK/ACTIVITY not LINK_1000. 11. THERM_Dp (D4) and THEMR_Dn (D5) are reserved and should not be used. Clarification: In section 3.11 and Table 32 in the Intel Datasheet, are references to signals THERM_Dp (D4) and THEMR_Dn (D5), these pins are RESERVED and should not be used in any design. These pins should be left unconnected (floating). ...

Page 50

... PCIe completion timeout mechanism should be disabled by setting the GCR.Disable_timeout_mechanism. For more details on Completion Timeout operation in the 82571EB/82572EI refer to the ® Intel 82571EB/82572EI Controller Datasheet and the PCIe* GbE Controllers Open Source Software Developer's Manual. 15. Critical Session (Keep PHY Link Up) Mode Does Not Block All PHY Resets Caused by PCIe Resets Clarification: D3-> ...

Page 51

Specification Update 323853 Revision: 6.3US July 2010 82571/82572 Specification Update Datasheet 53 ...

Page 52

Specification Update Datasheet 54 82571/82572 Specification Update 323853 Revision: 6.3US July 2010 ...