WG82574L S LBA8 Intel, WG82574L S LBA8 Datasheet
WG82574L S LBA8
Specifications of WG82574L S LBA8
Related parts for WG82574L S LBA8
WG82574L S LBA8 Summary of contents
Page 1
... GB of physical memory — Programmable host memory receive buffers (256 bytes to 16 KB) — Intelligent interrupt generation features to enhance driver performance — Descriptor ring management hardware for transmit and receive software controlled reset ...
Page 2
... Intel Corporation (“Intel”). In the event that you do not agree with any of these terms and conditions, do not use or install the Pre-Release Product and promptly return it unused to Intel. ...
Page 3
Datasheet—82574 GbE Controller Contents 1.0 Introduction ............................................................................................................ 10 1.1 Scope .............................................................................................................. 10 1.2 Number Conventions ......................................................................................... 10 1.3 Acronyms......................................................................................................... 11 1.4 Reference Documents ........................................................................................ 12 1.5 82574 Architecture Block Diagram ....................................................................... 13 1.6 System Interface............................................................................................... 13 1.7 Features Summary ............................................................................................ ...
Page 4
NC-SI...............................................................................................................58 3.5.1 Interface Specification .............................................................................59 3.5.2 Electrical Characteristics ..........................................................................59 4.0 Initialization ............................................................................................................60 4.1 Introduction ......................................................................................................60 4.2 Reset Operation.................................................................................................60 4.3 Power Up..........................................................................................................62 4.3.1 Power-Up Sequence ................................................................................62 4.3.2 Timing Diagram......................................................................................70 4.4 Global Reset (PE_RST_N, PCIe In-Band Reset) ......................................................71 4.4.1 Reset Sequence......................................................................................71 ...
Page 5
Datasheet—82574 GbE Controller 7.1.5 Packet Split Receive Descriptor .............................................................. 128 7.1.6 Receive Descriptor Fetching ................................................................... 131 7.1.7 Receive Descriptor Write Back................................................................ 131 7.1.8 Receive Descriptor Queue Structure........................................................ 132 7.1.9 Receive Interrupts................................................................................ 134 7.1.10 Receive Packet Checksum Offloading ...................................................... 137 7.1.11 ...
Page 6
... Terminology......................................................................................... 228 8.11.2 System Topology .................................................................................. 230 8.11.3 Data Transport ..................................................................................... 231 8.12 NC-SI Support................................................................................................. 233 8.12.1 Supported Features............................................................................... 233 8.12.2 NC-SI Mode - Intel Specific Commands.................................................... 234 8.13 Basic NC-SI Workflows ..................................................................................... 239 8.13.1 Package States..................................................................................... 239 8.13.2 Channel States ..................................................................................... 240 8.13.3 Discovery ............................................................................................ 240 8 ...
Page 7
Datasheet—82574 GbE Controller 10.2 Configuration and Status Registers - CSR Space .................................................. 276 10.2.1 Register Summary Table ....................................................................... 276 10.2.2 General Register Descriptions ................................................................ 283 10.2.3 PCIe Register Descriptions..................................................................... 302 10.2.4 Interrupt Register Descriptions............................................................... 310 10.2.5 Receive Register Descriptions ................................................................ ...
Page 8
Layout Considerations for the Ethernet Interface....................................... 431 13.5.6 Physical Layer Conformance Testing ........................................................ 437 13.5.7 Troubleshooting Common Physical Layout Issues ...................................... 437 13.6 SMBus and NC-SI ............................................................................................ 438 13.6.1 NC-SI Electrical Interface Requirements................................................... 439 13.7 82574 Power Supplies ...................................................................................... ...
Page 9
... Updated sections 6.3.1.3, 10.2.3.11, and 10.2.8.8. February 2009 2.4 • Updated table 66. • Added section 8.12.2.3 - Set Intel Management Control Formats. • Added section 8.12.3.4 - Get Intel Management Control Formats. • Added section 10.2.3.12 - 3GPIO Control Register 2 - GCR2. December 2008 2.3 • ...
Page 10
Introduction The 82574 family (82574L and 82574IT) are single, compact, low power components that offer a fully-integrated Gigabit Ethernet Media Access Control (MAC) and Physical Layer (PHY) port. The 82574 uses the PCI Express* (PCIe*) architecture and provides a ...
Page 11
... The 4-byte or 16-byte address that designates the Ethernet controller within the IP communication protocol. This address is dynamic and can be updated frequently during runtime. Intelligent Platform Management Interface Specification. Local Area Network. Also known as the Ethernet. The 6-byte address that designates Ethernet controller within the Ethernet protocol. ...
Page 12
... I C Specification NC-SI Specification Other reference documents include: • Intel® 82574 Family GbE Controller Specification Update, Intel Corporation. • PCI Express* Specification v2.0 (2.5 GT/s) • Advanced Configuration and Power Interface Specification • PCI Bus Power Management Interface Specification 12 Definition System Management Bus ...
Page 13
... Features Summary This section describes the 82574’s features that were present in previous Intel client GbE controllers and those features that are new to the 82574. SMBus SMBus ...
Page 14
... GB of physical memory Programmable host memory receive buffers (256 bytes to 16 KB) Intelligent interrupt generation features to enhance software device driver performance Descriptor ring management hardware for transmit and receive Software controlled reset (resets everything ...
Page 15
Introduction—82574 GbE Controller Table 3. Manageability Features Feature NC-SI over RMII for remote management core SMBus advanced pass through Table 4. Performance Features Feature Configurable receive and transmit data FIFO; programmable increments TCP segmentation capability compatible with ...
Page 16
... Table 6. Product Ordering Codes Part Number Intel® 82574L Gigabit Network WG82574L Connection Intel® 82574IT Gigabit Network WG82574IT Connection 16 82574 GbE Controller—Introduction Product Name • Embedded and Entry Server GbE LAN. ...
Page 17
Introduction—82574 GbE Controller Note: This page intentionally left blank. 17 ...
Page 18
Pin Interface 2.1 Pin Assignments The 82574 supports a 64-pin QFN package with an Exposed Pad* (e-Pad*). Note that the e-Pad is ground MDI_MINUS[3] 50 MDI_PLUS[3] 51 AVDD1p9 52 MDI_MINUS[2] 53 MDI_PLUS[2] 54 MDI_MINUS[1] ...
Page 19
Pin Interface—82574 GbE Controller 2.2 Pull-Up/Pull-Down Resistors and Strapping Options • As stated in the Name and Function table columns, the internal Pull-Up/Pull-Down (PU/PD) resistor values are 30 K ± 50%. • Only relevant (digital) pins are listed; analog or ...
Page 20
Table 7. PCIe Symbol Lead # PE_Rp 24 23 PE_Rn PE_WAKE_N/ 16 JTAG_TDO PE_RST_N 17 2.3.2 NVM Port Table 8. NVM Port Symbol Lead # NVM_SI 12 NVM_SO 14 NVM_SK 13 NVM_CS_N 15 20 82574 GbE Controller—Pin Interface Op Type ...
Page 21
Pin Interface—82574 GbE Controller 2.3.3 System Management Bus (SMBus) Interface Table 9. SMBus Interface Symbol SMB_DAT SMB_CLK SMB_ALRT_N Note: If the SMBus is disconnected, an external pull-up should be used for these pins, unless it is guaranteed that manageability is ...
Page 22
Table 10. NC-SI and Testability Symbol Lead # AUX_PWR/ 39 JTAG_TCK NVMT/JTAG_TMS 38 JTAG_TDI 40 2.3.5 LEDs Table 11 lists the functionality of each LED output pin. The default activity of each LED can be modified in the NVM. The ...
Page 23
Pin Interface—82574 GbE Controller Table 12. PHY Pins Symbol MDI_PLUS[0] MDI_MINUS[0] MDI_PLUS[1] MDI_MINUS[1] MDI_PLUS[2] MDI_MINUS[2] MDI_PLUS[3] MDI_MINUS[3] XTAL1 XTAL2 ATEST_P ATEST_N RSET 2.3.7 Miscellaneous Pin Table 13. Miscellaneous Pin Symbol DEV_OFF_N 28 Op Lead # Type Mode Media Dependent Interface[0]: ...
Page 24
Power Supplies and Support Pins 2.3.8.1 Power Support Table 14. Power Support Symbol CTRL10 62 CTRL19 64 DIS_REG10 59 2.3.8.2 Power Supply Table 15. Power Supply Symbol Lead # 4, 11, 18, 27, VDD1p0 37, 41, 60 22, 44, ...
Page 25
Pin Interface—82574 GbE Controller 2.4 Package The 82574 supports a 64-pin QFN package with e-Pad. package schematics. Figure 3. 82574 QFN Package Figure 3 shows the 25 ...
Page 26
Interconnects 3.1 PCIe PCIe is a third generation I/O architecture that enables cost competitive, next generation I/O solutions providing industry leading price/performance and feature richness industry-driven specification. PCIe defines a basic set of requirements that comprehends ...
Page 27
Interconnects—82574 GbE Controller A packet is the fundamental unit of information exchange and the protocol includes a message space to replace the number of side-band signals found on many of today’s buses. This movement of hard-wired signals from the physical ...
Page 28
Physical Interface Properties • Point to point interconnect — Full-duplex; no arbitration • Signaling technology: — Low voltage differential — Embedded clock signaling using 8b/10b encoding scheme • Serial frequency of operation: 2.5 GHz. • Interface width of one ...
Page 29
Interconnects—82574 GbE Controller Transaction Type Memory Write Request I/O Read Request I/O Write Request Read Completions Message Flow control types: • Posted request headers • Posted request data payload • NPH - Non-posted request headers • ...
Page 30
Table 18. Supported Message in The 82574 (As a Receiver) Message Routing code [7:0] r2r1r0 0x14 100 0x19 011 0x41 100 0x43 100 0x40 100 0x45 100 0x47 100 0x44 100 0x50 100 0x7E 010,011,100 0x7E 010,011,100 0x7F 010,011,100 0x7F ...
Page 31
Interconnects—82574 GbE Controller 3.1.3.5 Data Alignment 4 KB Boundary: Requests must never specify an address/length combination that causes a memory space access to cross boundary hardware’s responsibility to break requests into 4 KB-aligned requests (if ...
Page 32
Transaction Attributes 3.1.3.8.1 Traffic Class (TC) and Virtual Channels (VC) The 82574 supports only and (default). 3.1.3.8.2 Relaxed Ordering The 82574 takes advantage of the relaxed ordering rules in PCIe by setting the ...
Page 33
Interconnects—82574 GbE Controller 3.1.3.9 Error Forwarding If a Transaction Layer Protocol (TLP) is received with an error-forwarding trailer, the packet is dropped and not delivered to its destination. The 82574 does not initiate any additional master requests for that PCI ...
Page 34
Table 20. Allocation of FC Credits Credit Type Posted Request Header (PH) Posted Request Data (PD) Non-Posted Request Header (NPH) Non-Posted Request Data (NPD) Completion Header (CPLH) Completion Data (CPLD) Rules for FC updates: • The 82574 maintains two credits ...
Page 35
Interconnects—82574 GbE Controller 3.1.5 Host I/F 3.1.5.1 Tag IDs PCIe device numbers identify logical devices within the physical device (the 82574 is a physical device). The 82574 implements a single logical device with one PCI function - LAN. The device ...
Page 36
Completion Timeout Mechanism In any split transaction protocol, there is a risk associated with the failure of a requester to receive an expected completion. To enable requesters to attempt recovery from this situation in a standard manner, the completion ...
Page 37
Interconnects—82574 GbE Controller Device Control :: Correctable Error Reporting Enable Device Control :: Unsupported Request Reporting Enable Device Control :: Non-Fatal Error Reporting Enable Device Control :: Fatal Error Reporting Enable Parity Error Response Rcv Msg Error Message Processing Secondary ...
Page 38
Error Name Data link layer Violations of Flow Control protocol error initialization protocol TLP errors Poisoned TLP TLP with Error Forwarding received • Wrong config access • MRdLk • Config Request Type1 • Unsupported vendor • Not valid MSG code ...
Page 39
Interconnects—82574 GbE Controller 3.1.6.1.2 Error Pollution Error pollution can occur if error conditions for a given transaction are not isolated to the error's first occurrence. If the PHY detects and reports a receiver error, to avoid having this error propagate ...
Page 40
Table 24. DLLPs initiated by The 82574 Remarks ACK NAK PM_Enter_L1 PM_Enter_L23 PM_Active_State_Request_L1 InitFC1-P InitFC1-NP InitFC1-Cpl InitFC2-P InitFC2-NP InitFC2-Cpl UpdateFC-P UpdateFC-NP 1. UpdateFC-Cpl is not sent because of the infinite FC-Cpl allocation. 3.1.7.3 Transmit EDB Nullifying In case of a ...
Page 41
... The 82574 MAC is optimized for full-duplex operation in 1000 Mb/s mode. Half-duplex 1000 Mb/s operation is not supported. The PHY features 10/100/1000-BaseT signaling and is capable of performing intelligent power-management based on both the system power-state and LAN energy-detection (detection of unplugged cables). Power management includes the ability to shutdown ...
Page 42
... MAC register bits STATUS.SPEED each time MAC speed has not been forced. • MAC Dx power state indication - The MAC indicates its ACPI power state (PWR_STATE) to the PHY to enable it to perform intelligent power-management (provided that the PHY power-management is enabled in the MAC CTRL register). 3.2.2 ...
Page 43
Interconnects—82574 GbE Controller 3.2.2.1 Full Duplex All aspects of the IEEE 802.3, 802.3u, 802.3z, and 802.3ab specifications are supported in full duplex operation. Full duplex operation is enabled by several mechanisms, depending on the speed configuration of the 82574 and ...
Page 44
The PHY performs auto-negotiation per 802.3ab clause 40 and extensions to clause 28. Link resolution is obtained by the MAC from the PHY after the link has been established. The MAC accomplishes this via the MDIO interface, via specific signals ...
Page 45
Interconnects—82574 GbE Controller 3.2.3.1.2 MAC Speed Resolution For proper link operation, both the MAC and PHY must be configured for the same speed of link operation. The speed of the link can be determined and set by several methods with ...
Page 46
When MAC speed is neither forced nor auto-sensed by the MAC, the current MAC speed setting and the speed indicated by the PHY is reflected in the Device Status register bits STATUS.SPEED. 3.2.3.1.3 MAC Full/Half Duplex Resolution The duplex configuration ...
Page 47
... The 82574 contains an Adaptive IFS register (see implementation of a driver-based adaptive IFS algorithm for collision reduction, which is similar to Intel's other Ethernet products (such as PRO/100 adapters). Adaptive IFS throttles back-to-back transmissions in the transmit MAC and delays their transfer to the CSMA/CD transmit function and then can be used to delay the transmission of back-to-back packets on the wire ...
Page 48
Flow Control Flow control as defined in 802.3x, as well as the specific operation of asymmetrical flow control defined by 802.3z, are supported in the MAC. The following seven registers are defined for the implementation of flow control: • ...
Page 49
Interconnects—82574 GbE Controller Figure 6. 802.3x MAC Control Frame Format Where S is the start-of-packet delimiter and T is the first part of the end-of-packet delimiters for 802.3z encapsulation. The receiver is enabled to receive flow control frames if flow ...
Page 50
Discard Pause Frames and Pass MAC Control Frames Two bits in the Receive Control register are implemented specifically for control over receipt of pause and MAC control frames. These bits are Discard PAUSE Frames (DPF) and Pass MAC Control ...
Page 51
Interconnects—82574 GbE Controller 3.2.6.4 Software Initiated Pause Frame Transmission The 82574 has the added capability to transmit an XOFF frame via software. This is accomplished by software writing the SWXOFF bit of the Transmit Control register. Once ...
Page 52
Flash: The size of the Flash is selected by the system integrator according to its usage. The 82574 supports a maximum size devices, which is beyond any requirements. The typical Flash size for many applications of the ...
Page 53
Interconnects—82574 GbE Controller 3.3.3.1 CRC Field CRC calculation and management is done by software. 3.3.4 Device Operation with an External EEPROM When the 82574 is connected to an external EEPROM, it provides similar functionality to its predecessors with the following ...
Page 54
Address 8K Address 4K Address 00 Figure 7. NVM Shadow RAM 3.3.6.1 Flash Mode The 82574 is initialized from the NVM. As part of the initialization sequence, the 82574 copies the 4 KB content from the ...
Page 55
Interconnects—82574 GbE Controller 3.3.7 NVM Clients and Interfaces There are several clients that might access the NVM or shadow RAM listed in the following table. Listed are the various clients and their access type to the NVM: software device driver, ...
Page 56
Note: When software accesses the EEPROM or Flash spaces via the bit banging interface, it should follow these steps: 1. Write the Request bit in the FLA or EEC registers. 2. Poll the Grant bit in the ...
Page 57
Interconnects—82574 GbE Controller Case 2 - The 82574 is connected to a physical Flash device: 1. The 82574 writes the data to the shadow RAM and sets the Done bit in the EEWR register. 2. Update of the shadow RAM ...
Page 58
Until new data is written to the FLSWDATA register, the Flash clock is paused. 9. Once data is written to the FLSWDATA by the software, the DONE bit in the FLSWCTL register is cleared and is set after hardware ...
Page 59
Interconnects—82574 GbE Controller MC LLC - LOGICAL LINK CONTROL MAC - MEDIA ACCESS CONTROL RECONCILIATION Figure 8. NC-SI Interface 3.5.1 Interface Specification The 82574 NC-SI interface meets the RMII Specification, Rev. 1 PHY-side device. The following NC-SI capabilities ...
Page 60
Initialization 4.1 Introduction This chapter discusses initialization steps. This includes: • General hardware power-up state • Basic device configuration • Initialization of transmit and receive operation • Link configuration and software reset capability • Statistics initialization 4.2 Reset Operation ...
Page 61
Initialization—82574 GbE Controller • Force TCO - This reset is generated when manageability logic is enabled only generated if the reset on the Force TCO bit of the NVM's Management Control word is 1b. In pass-through mode it ...
Page 62
The Wake-Up Management (WUM) registers include the following: — Wake-up filter control. — IP address Valid. — IPv4 address table — IPv6 address table — Flexible filter length table — Flexible filter mask table 5. The following register fields ...
Page 63
Initialization—82574 GbE Controller Figure 9. 82574 Power Up - General Flow Start Power-On-Reset Flash EEPROM A Load Flash Load EEPROM C Initialize manageability and PHY D Read NVM after PERST# de-assertion E Initialize PCIe and PHY Bring up PCIe link ...
Page 64
Figure 10. 82574 Initialization - Power-On Reset 64 Start Power ramp up (3.3 V dc, 1.9 V dc, 1.05 V dc) Start Xosc stabe From power-up <10 Internal power-on- reset triggers From power-up <50 82574 samples NVMT strapping Determine NVM ...
Page 65
Initialization—82574 GbE Controller Read signature at word 2K+0x12 ~0 Bad signature 82574 set to default values Set EEC.Auto_RD 0 Figure 11. 82574 Initialization - Flash Load Notes sector is read in a single burst, so the ...
Page 66
Set EEC.Auto_RD 0 Figure 12. 82574 Initialization - EEPROM Load Each word is read separately using a 5-byte command (1 byte instruction, 2 byte address, and 2 byte data). Total time ...
Page 67
Initialization—82574 GbE Controller No need to load 82574 set to default values Clear SW/HW NVM semaphore 0 Figure 13. 82574 Initialization - PHY and Manageability Each PCIe register write takes ~20 PCIe clocks (31.25 MHz) per table entry <=> 640 ...
Page 68
Check valid Shadow and signature ~0 Load base area (0x00- 0x40) from Shadow RAM Set EEC.Auto_RD ~0.0032 Figure 14. 82574 Initialization - NVM Load After PE_RST_N 68 D PERST# is de-asserted by the platform PHY is powered down ~0 NVMT ...
Page 69
Initialization—82574 GbE Controller Load Extended Configuration from Shadow RAM Clear SW/HW NVM semaphore ~0.42 Figure 15. 82574 Initialization - PHY and PCIe E Enable the PHY PHY was in power-down during NVM load 11 Flash 4 Start PCIe link training ...
Page 70
Timing Diagram Power txo 1 g Xosc Power-On-Reset (internal) PCIe reference clock PERST# NVM Load PHY State PCIe Link up Manageability / Wake D-State Figure 16. Power-Up Timing Diagram Table 28. Notes to Power-Up Timing Diagram Note 1 Xosc ...
Page 71
Initialization—82574 GbE Controller 4.4 Global Reset (PE_RST_N, PCIe In-Band Reset) 4.4.1 Reset Sequence Figure 17 and Figure 18 de-assertion or PCIe in-band reset) and until the device is ready to accept host commands. Check valid Shadow and signature ~0 Load ...
Page 72
Load Extended Configuration from Shadow RAM Clear SW/HW NVM semaphore ~0.42 Figure 18. 82574 Global Reset - PHY and PCIe 4.4.2 Timing Diagram The following timing diagram shows the 82574’s behavior through a PE_RST_N reset Enable the PHY ...
Page 73
Initialization—82574 GbE Controller PCIe reference clock PERST# NVM Load PHY State Active PCIe Link up L0 Wake D-State Figure 19. Global Reset Timing Diagram Table 29. Notes to Global Reset Timing Diagram Note The system must assert PE_RST_N before stopping ...
Page 74
Timing Parameters 4.5.1 Timing Requirements The 82574 requires the following start-up and power state transitions. Table 30. Timing Requirements Parameter txog Xosc stable from power stable tPWRGD- PCIe clock valid to PCIe power good CLK Power rails stable to ...
Page 75
Initialization—82574 GbE Controller 4.6 Software Initialization Sequence The following sequence of commands is typically issued to the device by the software device driver in order to initialize the 82574 to normal operation. The major initialization steps are: 1. Disable Interrupts ...
Page 76
Interrupts During Initialization Most drivers disable interrupts during initialization to prevent re-entrancy. Interrupts are disabled by writing to the IMC register. Note that the interrupts need to be disabled also after issuing a global reset typical driver ...
Page 77
Initialization—82574 GbE Controller — CTRL.TFCE - Must be set by software after reading flow control resolution from PHY registers. — CTRL.SPEED - Don't care; speed setting is established from PHY's internal indication to the MAC (SPD_IND) after PHY has auto-negotiated ...
Page 78
MAC/PHY duplex and speed settings both forced by software (fully-forced link setup). (CTRL.FRCDPLX = 1b, CTRL.FRCSPD = 1b, CTRL.SLU = 1b) — CTRL.FD - Set by software to desired full-/half- duplex operation (must match duplex setting of the PHY). ...
Page 79
Initialization—82574 GbE Controller 4.6.5.1 Initialize the Receive Control Register To properly receive packets requires simply that the receiver is enabled. This should be done only after all other setup is accomplished. If software uses the Receive Descriptor Minimum Threshold Interrupt, ...
Page 80
Program the TIPG register with the following (decimal) values to get the minimum legal IPG: • IPGT = 8 • IPGR1 = 2 • IPGR2 = 10 Note: IPGR1 and IPGR2 are not needed in full-duplex, but it is easier ...
Page 81
Initialization—82574 GbE Controller Note: This page intentionally left blank. 81 ...
Page 82
Power Management and Delivery The 82574 supports the Advanced Configuration and Power Interface (ACPI 2.0) specification as well as Advanced Power Management (APM). This section describes how power management is implemented in the 82574. Implementation requirements were obtained from ...
Page 83
Power Management and Delivery—82574 GbE Controller 5.3 Power Delivery 82574 operates from the following power rails: • power rail for internal power regulation and for periphery. The 3 should be supplied by an external ...
Page 84
Internal Power On Reset assertion PE_RST_N assertion Figure 20. Power Management State Diagram 5.4.2 Auxiliary Power Usage If ADVD3WUC=1b, the 82574 uses the AUX_PWR indication that auxiliary power is available to the controller, and therefore advertises D3cold wake up support. ...
Page 85
Power Management and Delivery—82574 GbE Controller The AUX Power PM Enable bit in the PCIe Device Control register determines if the 82574 complies with the auxiliary power regime defined in the PCIe specification. If set, the 82574 might consume higher ...
Page 86
When entering the D0u state, the 82574 disables all wake ups and asserts a reset to the PHY while the NVM is being read. If the APM Mode bit in the NVM's Initialization Control Word 2 is set, then APM ...
Page 87
Power Management and Delivery—82574 GbE Controller 5.4.4.2.3 Entry to D3 State Transition to the D3 state is through a configuration write to the Power State field of the PCI-PM registers. Prior to transition from D0 to the D3 state, the ...
Page 88
Dr State Transition to Dr state is initiated on three occasions: • At system power state begins with the assertion of the internal power detection circuit (Internal Power On Reset) and ends with the assertion of ...
Page 89
Power Management and Delivery—82574 GbE Controller 5.4.4.4 Device Disable For a LOM design, it might be desirable for the system to provide BIOS-setup capability for selectively enabling or disabling LOM devices. This might allow the designers more control over system ...
Page 90
PCIe Reference Clock PCIe PwrGd Reading EEPROM D3 write PHY Reset 1 PCIe Link L0 Wake Up Enabled PHY Power State full DState D0a Figure 21. D3hot Transition Timing Diagram Table 32. Notes to D3hot Timing Diagram Note 1 Writing ...
Page 91
Power Management and Delivery—82574 GbE Controller PCIe Reference Clock PCIe PwrGd Internal PCIe clock (2.5 GHz) Internal PwrGd (PLL) Reading EEPROM Reset to PHY (active low) D3 write 1 PCIe Link L0 Wake Up Enabled PHY Power State full DState ...
Page 92
Wake Up The 82574 supports two types of wake-up mechanisms: • Advanced Power Management (APM) wake up • PCIe power management wake up The PCIe power management wake up uses the PE_WAKE_N pin to wake the system up. The ...
Page 93
Power Management and Delivery—82574 GbE Controller 5.5.2 PCIe Power Management Wake Up The 82574 supports PCIe power management based wake ups. It can generate system wake-up events from three sources: • Reception of a Magic Packet*. • Reception of a ...
Page 94
Pre-Defined Filters The following packets are supported by the 82574's pre-defined filters: • Directed packet (including exact, multicast indexed, and broadcast) • Magic Packet* • ARP/Ipv4 request packet • Directed IPv4 packet • Directed IPv6 packet Each of these ...
Page 95
Power Management and Delivery—82574 GbE Controller 5.5.3.1.4 Magic Packet* Once the 82574 has been put into the Magic Packet* mode, it scans all incoming frames addressed to the node for a specific data sequence, which indicates to the controller that ...
Page 96
Accepting broadcast Magic Packets* for wake up purposes when the Broadcast Accept bit of the Receive Control Register (RCTL.BAM change from previous devices, which initialized RCTL.BAM APM was enabled in the NVM, but ...
Page 97
Power Management and Delivery—82574 GbE Controller # of Offset Bytes ...
Page 98
Offset Bytes 5.5.3.2 Flexible Filter The 82574 supports four flexible filters for host wake up and two flexible filters for TCO wake up. For more details refer to ...
Page 99
Power Management and Delivery—82574 GbE Controller # of Offset bytes 5.5.3.2.2 Directed IPX Packet A valid directed IPX packet contains: • The station's MAC address. • A protocol type of 0x8137. • an IPX ...
Page 100
... NVM words and fields that vary, like the examples of NVMTYPE or NVSIZE. For the latest 82574 NVM images, contact your Intel representative. 6.1 EEUPDATE Intel has an MS-DOS* software utility called EEUPDATE that can be used to program EEPROM images in development or production-line environments. To obtain a copy of this program, contact your Intel representative. 6.2 ...
Page 101
Non-Volatile Memory (NVM) Map—82574 GbE Controller Word Used By 0x0B HW 0x0C HW 0x0D HW 0x0E HW 0x0F HW 0x10 HW 0x11 HW 0x12 HW 0x13 HW 0x14 HW 0x15 HW 0x16 HW 0x17 HW 0x18 HW 0x19 HW 0x1A ...
Page 102
... Network Interface Card (NIC), and thus unique for each copy of the NVM image. The first three bytes are vendor specific - for example, the IA is equal to [00 AA 00] or [00 A0 C9] for Intel products. The value from this field is loaded into the Receive Address Register 0 (RAL0/RAH0). ...
Page 103
Non-Volatile Memory (NVM) Map—82574 GbE Controller Bit Name 3 Reserved 2 PCI Bridge 1:0 Reserved 6.2.1.3 OEM LED Configuration (Word 0x04) Bit Name 15:12 Reserved 11:8 LED 2 Control 7:4 LED 1Control 3:0 LED 0 Control 6.2.1.4 Initialization Control Word ...
Page 104
Subsystem ID (Word 0x0B) If the load subsystem IDs in word 0x0A is set, this word is loaded to initialize the subsystem ID. The default value is 0x0. 6.2.1.6 Subsystem Vendor ID (Word 0x0C) If the load subsystem IDs ...
Page 105
Non-Volatile Memory (NVM) Map—82574 GbE Controller Bit Name 6 Reserved 5 Reserved 4 Reserved 3 Reserved 1 Reserved 0 Reserved 6.2.1.9 NVM Protected Word 0 - NVP0 (Word 0x10) Bit Name 15:8 Reserved 7:0 Reserved 6.2.1.10 NVM Protected Word 1 ...
Page 106
Extended Configuration word 1 (Word 0x14) Bit Name 15:13 Reserved 12 Reserved 11:0 Reserved 6.2.1.13 Extended Configuration Word 2 (Word 0x15) Bit Name 15:8 Reserved 7 Reserved 6 Reserved 5 Reserved 4 Reserved 3 Reserved 2 Reserved 1 Reserved ...
Page 107
Non-Volatile Memory (NVM) Map—82574 GbE Controller 6.2.1.16 PCIe Init Configuration 1 Word (Word 0x18) Bit Name 15 Reserved 14:12 L1_Act_Ext_Latency 11:9 L1_Act_Acc_Latency 8:6 L0s_Acc_Latency 5:3 L0s_Se_Ext_Latency 2:0 L0s_Co_Ext_Latency 6.2.1.17 PCIe Init Configuration 2 Word (Word 0x19) Bit Name DLLP timer ...
Page 108
PCIe Init Configuration 3 Word (Word 0x1A) Bit Name 15 Master_Enable 14 Scram_dis 13 Ack_Nak_Sch 12 Cache_Lsize 11:10 PCIE_Cap 9 IO_Sup 8 Packet_Size 7 Reserved 6 Reserved 5 Reserved 4 Reserved 3:2 Act_Stat_PM_Sup 1 Slot_Clock_Cfg Loop back polarity 0 ...
Page 109
Non-Volatile Memory (NVM) Map—82574 GbE Controller 6.2.1.19 PCIe Control (Word 0x1B) Bit Name Latency_To_E 1:0 nter_L1 Electrical 2 IDLE 3 Reserved 4 Skip Disable 5 L2 Disable 6 Reserved 9:7 MSI_X_NUM Leaky Bucket 10 Disable Good 11 Recovery 12 PCIE_LTSSM ...
Page 110
LED 1 Configuration Defaults/PHY Configuration (Word 0x1C) Bit Name 3:0 LED1 Mode 4 Reserved LED1 Blink 5 Mode 6 LED1 Invert 7 LED1 Blink 8 Reserved 9 D0LPLU 10 LPLU Disable 1000 11 in non-D0a 12 Class AB 13 ...
Page 111
Non-Volatile Memory (NVM) Map—82574 GbE Controller 6.2.1.22 LED 0-2 Configuration Defaults (Word 0x1F) Bit Name 3:0 LED0 Mode 4 Reserved LED0 Blink 5 Mode 6 LED0 Invert 7 LED0 Blink 11:8 LED2 Mode 12 Reserved LED2 Blink 13 Mode 14 ...
Page 112
Flash LAN Address - FLANADD (Word 0x21) Bit Name 15 DISLFB 14:12 LANSIZE 11:8 LBADD 7 DISLEXP 6:1 Reserved 0 Reserved 6.2.1.25 LAN Power Consumption (Word 0x22) Bit Name LAN D0 15:8 Power 7:5 Reserved LAN D3 4:0 Power ...
Page 113
... PBA Number (Word 0x08 and 0x09) The nine-digit Printed Board Assembly (PBA) number used for Intel manufactured Network Interface Cards (NICs) are stored in a 4-byte field. The dash itself is not stored, neither is the first digit of the 3-digit suffix always zero for the affected products ...
Page 114
Boot Configuration Start Address (Word 0x3D) Bit Name 15:0 Address 6.2.2.5 Checksum Word Calculation (Word 0x3F) The checksum word (0x3F) is used to ensure that the base NVM image is a valid image. The value of this word ...
Page 115
Non-Volatile Memory (NVM) Map—82574 GbE Controller 6.3.1.3 APT SMBus Control (Word 0x27) Bit Name SMBus 15:8 Fragment Size Notification 7:0 Timeout 6.3.1.4 APT Init Flags (Word 0x28) Bit Name 15:6 Reserved 5 Reserved 4 Force TCO Enable 3 SMB ARP ...
Page 116
APT Code Pointer (Word 0x2A) Bit Name 15:12 Reserved 11:0 Pointer 1. Code in the NVM is organized such that the lower word of a Dword code, is stored first. Note: APT code size and pointer should be configured ...
Page 117
Non-Volatile Memory (NVM) Map—82574 GbE Controller 6.3.2.4 NC-SI Configuration (Word 0x2E) Bit Name 15 Reserved 14:12 Package ID 11:0 Code Pointer 1. Code in the NVM is organized such that the lower word of a Dword code is stored first. ...
Page 118
Inline Functions 7.1 Packet Reception Packet reception consists of recognizing the presence of a packet on the wire, performing address filtering, storing the packet in the receive data FIFO, transferring the data to one of the two receive queues ...
Page 119
Inline Functions—82574 GbE Controller Good packets are defined as those packets with no: • CRC error • Symbol error • Sequence error • Length error • Alignment error • Where carrier extension or RX_ERR errors are detected. However, if the ...
Page 120
VLAN Tag 1. The checksum indicated here is the unadjusted 16-bit ones complement of the packet. A software assist might be required to back out appropriate information prior to sending upper software layers. The packet ...
Page 121
Inline Functions—82574 GbE Controller TCPCS (bit 5) - TCP checksum calculated on packet UDPCS (bit 4) - UDP checksum calculated on packet VP (bit 3) - Packet is 802.1q (matched VET) Reserved (bit 2) - Reserved EOP (bit 1) - ...
Page 122
TCPE (bit 5) - TCP/UDP checksum error CXE (bit 4) - Carrier extension error Rsv (bit 3) - Reserved SEQ (bit 2) - Sequence error SE (bit 1) - Symbol error CE (bit 0) - CRC error or alignment error ...
Page 123
Inline Functions—82574 GbE Controller 7.1.4.1 Buffer Address (64-Bit, Offset 0.0) The field contains the physical address of the receive data buffer. The size of the buffer is defined by the RCTL register (RCTL.BSIZE, RCTL.BSEX, RCTL.DTYP and RCTL. FLXBUF fields). 7.1.4.2 ...
Page 124
Packet Checksum (16-Bit, Offset 0.48) For standard 802.3 packets (non-VLAN) the packet checksum is by default computed over the entire packet from the first byte of the DA through the last byte of the CRC, including the Ethernet and ...
Page 125
Inline Functions—82574 GbE Controller UDPV (bit 10) - Valid UDP XSUM IPIDV (bit identification valid TST (bit 8) - Time stamp taken Rsvd (bit 7) - Reserved IPCS (bit 6) IPv4 checksum calculated on packet - same ...
Page 126
ACK (bit 15): The ACK bit indicates that the received packet was an ACK packet with or without TCP payload depending on the RFCTL.ACKD_DIS bit. PKTTYPE (bit 19:16): The PKTTYPE field defines the type of the packet that was detected ...
Page 127
Inline Functions—82574 GbE Controller CE (bit 4) - CRC error or alignment error - Same as legacy descriptor. Reserved (bits 7, 3:0) - Reserved RXE IPE TCPE CXE SEQ SE CE: Same as legacy descriptor. Length (16-bit, offset 8.32): Same ...
Page 128
Packet Split Receive Descriptor The 82574 uses the packet split feature when the RFCTL.EXSTEN bit is set and RCTL.DTYP=01b. The software device driver must also program the buffer sizes in the PSRCTL register. Descriptor Read Format ...
Page 129
Inline Functions—82574 GbE Controller Descriptor Write-Back Format Packet Checksum 8 VLAN Tag 1 Length Note: Light-blue fields are mutually exclusive by RXCSUM.PCSD MRQ - Same as extended Rx descriptor. Packet Checksum, IP Identification, RSS ...
Page 130
HLEN (bit 9:0): The HLEN field indicates the header length in byte count that was analyzed by the 82574. The 82574 posts the first HLEN bytes of the incoming packet to buffer zero of the Rx descriptor. Packet types supported ...
Page 131
Inline Functions—82574 GbE Controller 7.1.6 Receive Descriptor Fetching The fetching algorithm attempts to make the best use of PCIe bandwidth by fetching a cache-line (or more) descriptor with each burst. The following paragraphs briefly describe the descriptor fetch algorithm and ...
Page 132
Null Descriptor Padding Hardware stores no data in descriptors with a null data address. Software can make use of this property to cause the first condition under receive descriptor packing to occur early. Hardware writes back null descriptors with ...
Page 133
Inline Functions—82574 GbE Controller The receive descriptor head and tail pointers reference 16-byte blocks of memory. Shaded boxes in the figure represent descriptors that have stored incoming packets but have not yet been recognized by software. Software can determine if ...
Page 134
Receive Interrupts The following indicates the presence of new packets: • Receive Timer (ICR.RXT0) due to packet delay timer (RDTR) A predetermined amount of time has elapsed since the last packet was received and transferred to host memory. Every ...
Page 135
Inline Functions—82574 GbE Controller Initial State DISABLED other receive interrupts INT GENERATED Figure 27. Packet Delay Timer Operation (With State Diagram) Figure 28 shows how the packet timer and absolute timer can be used together: packet received & xferred to ...
Page 136
C ase A: U sing only an absolute tim er PKT #1 C ase B: U sing an absolute tim e in conjunction w ith the P acket tim er A bsolute Tim er Value PKT #1 PKT #2 1) ...
Page 137
Inline Functions—82574 GbE Controller Receive interrupts can also be generated for the following events: • Receive Descriptor Minimum Threshold (ICR.RXDMT) — The minimum descriptor threshold helps avoid descriptor under-run by generating an interrupt when the number of free descriptors becomes ...
Page 138
Packet Type IPv4 packets IPv6 packets IPv6 packet with next header options: Hop-by-Hop options Destinations options Routing (with len 0) Routing (with len >0) Fragment Home option IPv4 tunnels: IPv4 packet in an IPv4 tunnel IPv6 packet in an IPv4 ...
Page 139
Inline Functions—82574 GbE Controller 7.1.10.3 IPv4 Filter This filter checks for valid IPv4 headers. The version field is checked for a correct value (4). IPv4 headers are accepted if they are any size greater than or equal to 5 (Dwords). ...
Page 140
However, RSS is the only usage that is described specifically. Other uses should make use of the available hardware. Multiple receive queues are enabled when the RXCSUM.PCSD bit is set (packet checksum is disabled) and the Multiple Receive Queues Enable ...
Page 141
Inline Functions—82574 GbE Controller Parsed receive packet RSS Hash 32 Packet descriptor MRQ disables or (RSS & not decodeable) Figure 29. RSS Block Diagram 7.1.11.1 RSS Hash Function The 82574’s hash function follows Microsoft’s* definition. A single hash function is ...
Page 142
IPv6Ex - The 82574 parses the packet to identify an IPv6 packet. Extension headers should be parsed for a Home-Address-Option field (for source address) or the Routing-Header-Type-2 field (for destination address). Note that the packet is not required to ...
Page 143
Inline Functions—82574 GbE Controller IPv6 hash types: • S2a - TcpIPv6 is enabled as defined above, or • S2b - TcpIPv6, IPv6Ex, and IPv6 are enabled - the packet is first parsed according to TcpIPv6 rules. If not identified as ...
Page 144
The following four pseudo-code examples are intended to help clarify exactly how the hash performed in four cases, IPv4 with and without ability to parse the TCP header, and IPv6 with an without a TCP header. 7.1.11.1.1 ...
Page 145
Inline Functions—82574 GbE Controller 7.1.11.3 RSS Verification Suite Assume that the random key byte-stream is: 0x6d, 0x5a, 0x56, 0xda, 0x25, 0x5b, 0x0e, 0xc2, 0x41, 0x67, 0x25, 0x3d, 0x43, 0xa3, 0x8f, 0xb0, 0xd0, 0xca, 0x2b, 0xcb, 0xae, 0x7b, 0x30, 0xb4, 0x77, ...
Page 146
Transmission Flow Using Simplified Legacy Descriptors Software defines a descriptor ring and configures the 82574's transmit queue with the address 1 location, length, head, and tail pointers of the ring. This step is executed once per Tx descriptor ring. ...
Page 147
Inline Functions—82574 GbE Controller • Software places the rest of the data to be transmitted in the host memory indicated to the hardware by additional data descriptors. • Hardware splits the data into multiple packets according to the Maximum Segment ...
Page 148
Descriptors between the head and the tail pointers are descriptors that have been prepared by software and are owned by hardware. 7.2.4.1 Transmit Descriptor Fetching The descriptor processing strategy for transmit descriptors is essentially the same as for receive descriptors. ...
Page 149
Inline Functions—82574 GbE Controller 7.2.4.3 Determining Completed Frames as Done Software can determine if a packet has been sent by the following method: • Setting the RS bit in the transmit descriptor command field and checking the DD bit of ...
Page 150
The device automatically selects the appropriate mode to use based on the current packet transmission: legacy, extended, or segmentation. Note: While the architecture supports arbitrary ordering rules for the various descriptors, there are restrictions including: — Context descriptors should not ...
Page 151
Inline Functions—82574 GbE Controller 7.2.8 Transmit Interrupts Hardware supplies the transmit interrupts described below. These interrupts are initiated via the following conditions: • Transmit Descriptor Ring Empty (ICR.TXQE) - All descriptors have been processed. The head pointer is equal to ...
Page 152
Transmit Descriptor Formats The original descriptor is referred to as the legacy descriptor and is described in section 7.2.10.1. The two new descriptor types are collectively referred to as extended descriptors. One of the new descriptor types is quite ...
Page 153
Inline Functions—82574 GbE Controller 7.2.10.1.2 Length Length (TDESC.LENGTH) specifies the length in bytes to be fetched from the buffer address. The maximum length associated with any single legacy descriptor is 16288 bytes. Note: The maximum allowable packet size for transmits ...
Page 154
IDE (bit 7) - Interrupt Delay Enable VLE (bit 6) - VLAN Packet Enable DEXT (bit 5) - Descriptor extension (0b for legacy mode) RSV (bit 4) - Reserved RS (bit 3) - Report status IC (bit 2) - Insert ...
Page 155
Inline Functions—82574 GbE Controller When IC is set, hardware inserts a checksum value calculated from the CSS bit value to the CSE bit value the end of packet. The checksum value is inserted in the header at the ...
Page 156
VLAN Field The VLAN field is used to provide the 802.1Q/802.1ac tagging information. The VLAN field is ignored if the VLE bit the EOP bit is 0b PRI CFI 7.2.10.2 Context Transmit ...
Page 157
Inline Functions—82574 GbE Controller IPCSS - IP Checksum Start - Specifies the byte offset from the start of the DMA'd data to the first byte to be included in the checksum. Setting this value to 0b means the first byte ...
Page 158
Header Length - HDRLEN HDRLEN is used to specify the length (in bytes) of the header to be used for each frame of a TCP segmentation operation. The first HDRLEN bytes fetched from data descriptor(s) are stored internally and ...
Page 159
Inline Functions—82574 GbE Controller IDE (bit 7) - Interrupt Delay Enable SNAP (bit 6) - SNAP DEXT (bit 5) - Descriptor extension (must be 1b for this descriptor type) Rsv (bit 4) - Reserved RS (bit 3) - Report status ...
Page 160
The TCP bit identifies the packet as either TCP or UDP (non-TCP). This affects the processing of the header information. 7.2.10.7 Status - STA Four bits are reserved to provide transmit status, although only one is currently assigned for this ...
Page 161
Inline Functions—82574 GbE Controller 7.2.11.1 Data Length - DTALEN The Data Length field (TDESC.DTALEN) is the total length of the data pointed to by this descriptor (the entire send), in bytes. For data descriptors not associated with a TCP segmentation ...
Page 162
Although the transmit interrupt might be delayed, the descriptor write-back requested by setting the RS bit is performed without delay unless descriptor write-back bursting is enabled. VLE indicates that the packet is a VLAN packet (for example, that the hardware ...
Page 163
Inline Functions—82574 GbE Controller 7.2.11.4 Status - STA The status field is written back to host memory in cases where the RS bit is set in the command field. The DD bit indicates that the descriptor is done after the ...
Page 164
VLAN The VLAN field is used to provide the 802.1Q tagging information. The special field is ignored if the VLE bit in the DCMD command byte is 0b PRI 7.3 TCP Segmentation TCP segmentation is an offloading ...
Page 165
Inline Functions—82574 GbE Controller L2 Ethernet Figure 35. TCP/IP Packet Format Frame formats supported by the 82574 include: • Ethernet 802.3 • IEEE 802.1q VLAN (Ethernet 802.3ac) • Ethernet Type 2 • Ethernet SNAP • IPv4 headers with options • ...
Page 166
TCP Segmentation Source Data Once the TCP segmentation context has been set, the next descriptor (data descriptor) provides the initial data to transfer. This first data descriptor must point to data containing an Ethernet header of the type indicated. ...
Page 167
Inline Functions—82574 GbE Controller 7.3.6 TCP Segmentation Use of Multiple Data Descriptors TCP segmentation enables a series of data descriptors, each referencing a single physical address page, to reference a large packet contained in a single virtual-address buffer. The only ...
Page 168
IP/TCP/UDP Header Updating IP/TCP/UDP header is updated for each outgoing frame based on the IP/TCP header prototype (partial pseudo-header) which the hardware gets from the first descriptor(s) and stores on chip. The IP/TCP/UDP headers are fetched from host memory ...
Page 169
Inline Functions—82574 GbE Controller IPv4 Header • IP Identification: incremented from last value (wrap around) • IP Total Length = MSS + HDRLEN - IPCSS • IP Checksum IPv6 Header • Payload Length = MSS + HDRLEN - IPCSS - ...
Page 170
UDP Header • UDP length: (last frame payload bytes + HDRLEN) - TUCSS • UDP Checksum 7.4 Interrupts The 82574 supports the following interrupt modes: • PCI legacy interrupts • PCI MSI - Message Signaled Interrupts • PCI MSI-X - ...
Page 171
Inline Functions—82574 GbE Controller The following configuration and parameters are involved: • The IVAR.INT_Alloc[4:0] entries map two Tx queues, two Rx queues and other events to 5 interrupt vectors • The ICR[24:20] bits reflect specific interrupt causes • Five MSI-X ...
Page 172
The interrupt causes include: • The receive and transmit related interrupts (including new per queue cause). • Other bits in this register are the legacy indication of interrupts as the MDIC complete, management and link status change. There is a ...
Page 173
Inline Functions—82574 GbE Controller 7.4.4 Interrupt Moderation The 82574 implements interrupt moderation to reduce the number of interrupts software processes. The moderation scheme is based on a timer called ITR Interrupt Throttle register). In general terms, the ITR defines an ...
Page 174
No Yes No No Figure 37. Interrupt Throttle Flow Diagram For cases where the 82574 is connected to a small number of clients desirable to fire off the interrupt as soon as possible with minimum latency. For these ...
Page 175
Inline Functions—82574 GbE Controller Case A: Heavy load, interrupts moderated Intr Pkt Pkt Case B: Light load, interrupts immediately on packet receive Intr Pkt 7.4.5 Clearing Interrupt Causes The 82574 has three methods available for to clear ICR bits: auto-clear, ...
Page 176
Write to Clear The ICR register clears specific interrupt cause bits in the register after writing 1b to those bits. Any bit that was written with a 0b remains unchanged. Read to clear All bits in the ICR register are ...
Page 177
Inline Functions—82574 GbE Controller The bit ordering is as follows: Octet 1 UP CFI 7.5.2 Transmitting and Receiving 802.1q Packets Since the 802.1q tag is only four bytes, adding and stripping of tags could be done completely in software. (In ...
Page 178
The Virtual LAN ID field indexes a 4096 bit vector. If the indexed bit in the vector is one; there is a virtual LAN match. Software might set the entire bit vector to ones if the node does not implement ...
Page 179
Inline Functions—82574 GbE Controller Each of the three LED's might be configured to use one of a variety of sources for output indication. The Mode bits control the LED source: • LINK_100/1000 is asserted when link is established at either ...
Page 180
The 1588 standard specifically addresses the needs of measurement and control systems: • Spatially localized • s to sub-s accuracy • Administration free • Accessible for both high-end devices and low-cost, low-end devices The time sync mechanism activation is possible ...
Page 181
Inline Functions—82574 GbE Controller T1 Timestamp Master T4 Timestamp Figure 38. Sync Flow and Offset Calculation The hardware responsibilities are: 1. Identify the packets that require time stamping. 2. Timestamp the packets on both Rx and Tx paths. 3. Store ...
Page 182
Table 43. Chronological Order of Events for Sync and Path Delay Generate a sync packet with timestamp notification in descriptor. Timestamp the packet and store the value in registers (T1). Timestamp incoming sync packet, store the value in register and ...
Page 183
Inline Functions—82574 GbE Controller 7.7.3.1 System Time Structure and Mode of Operation The time sync logic contains an up counter to maintain the system time value. This is a 64-bit counter that is built of the SYSTIML and SYSTIMH registers. ...
Page 184
On the Rx this logic parses the traversing frame and if Rx timestamp is enabled and it matches the Ethertype, UDP port (if needed), version and message type as defined in the register described in latched in the timestamp registers. ...
Page 185
Inline Functions—82574 GbE Controller After offset calculation the system time register should be updated. This is done by writing the calculated offset to TIMADJL and TIMADJH registers. The order should be as follows: 1. Write the lower portion of the ...
Page 186
Offset in Bytes Bits Sourceuuid sourceportid 29 30 sequenceId 31 32 control 33 reserved 34 flags 35 1. Should be all zero. Table 44. V1 and V2 PTP Message Structure Note: Only the ...
Page 187
Inline Functions—82574 GbE Controller Table 48. Message Decoding for V2 (MessageId Field at Offset 0) MessageId PTP_SYNC_MESSAGE PTP_DELAY_REQ_MESSAGE PTP_PATH_DELAY_REQ_MESSAGE PTP_PATH_DELAY_RESP_MESSAGE Unused PTP_FOLLOWUP_MESSAGE PTP_DELAY_RESP_MESSAGE PTP_PATH_DELAY_FOLLOWUP_MESSAGE PTP_ANNOUNCE_MESSAGE PTP_SIGNALLING_MESSAGE PTP_MANAGEMENT_MESSAGE Unused If V2 mode is configured in PTP_PATH_DELAY_REQ_MESSAGE and PTP_PATH_DELAY_RESP_MESSAGE for any value ...
Page 188
... Software-based management applications provide the ability to administer systems while the operating system is functioning in a normal power state (not in a pre-boot state or powered-down state). The Intel® System Management Bus (SMBus) Interface and the Network Controller - Sideband Interface (NC-SI) for fills the the 82574 management void that exists when the operating system is not running or fully functional ...
Page 189
... NC-SI specification) and the protocol layer is completely different. 8.4 SMBus Pass-Through Interface SMBus is the system management bus defined by Intel® Corporation in 1995 used in personal computers and servers for low-speed system management communications. The SMBus interface is one of two pass-through interfaces available in the 82574. ...
Page 190
... General The SMBus sideband interface includes the standard SMBus commands used for assigning a slave address and gathering device information as well as Intel® proprietary commands used specifically for the pass-through interface. 8.4.2 Pass-Through Capabilities This section details the specific manageability capabilities the 82574 provides while in SMBus mode ...
Page 191
System Manageability—82574 GbE Controller 2. Receive Filtering – In this mode only certain types of packets are directed to the manageability block. The MC should set the RCV_TCO_EN bit together with the specific packet type bits in the manageability filtering ...
Page 192
The high-level structure of manageability filtering is done using two steps: 1. Packets are filtered by L2 criteria (MAC address and unicast/multicast/broadcast). 2. Packets are filtered by the manageability filters (port, IP, flex, etc.). Some general rules apply: • Fragmented ...
Page 193
System Manageability—82574 GbE Controller Multicast filtering - only 12 bits out of the packet's destination MAC address are compared against the multicast entries. These entries can be configured only by the software device driver and cannot be controlled by the ...
Page 194
Manageability Filtering The manageability filtering stage combines some of the checks done at the previous stages with additional L3/L4 checks into a final decision whether to route a packet to the MC. The following sections describe the manageability filtering ...
Page 195
System Manageability—82574 GbE Controller Port 0x298/0x26F filtering - The 82574 supports filtering by fixed destination port numbers, port 0x26F and port 0x298. Flex port filtering - The 82574 implements four flex destination port filters. The 82574 directs packets whose L4 ...
Page 196
filter is enabled in the register, the OR filters are ignored in the decision (the filter might still match). • If one or more OR filter is enabled in the register, then at least one of ...
Page 197
System Manageability—82574 GbE Controller Table 50. Assignment of Decision Filters Bits L2 Unicast Address Broadcast Manageability VLAN IP Address L2 Unicast Address Broadcast Multicast 1 ARP Request 1 ARP Response Neighbor Solicitation Port 0x298 Port 0x26F Flex Port 3:0 Reserved ...
Page 198
Table 51. Manage 2 Host Bits Description Determines if packets that have passed decision filter 0 are also forwarded to the host operating 0 Decision Filter 0 system. Determines if packets that have passed decision filter 1 are also forwarded ...
Page 199
System Manageability—82574 GbE Controller Table 52. Shorthand Field Name Field Name S SMBus START Symbol P SMBus STOP Symbol PEC Packet Error Code A ACK (Acknowledge) N NACK (Not Acknowledge) Rd Read Operation (Read Value = 1b) Wr Write Operation ...
Page 200
Clearing the AR flag means that the 82574 responds to the following SMBus ARP transactions that are issued by the master. The SMBus master issues a Get UDID command (general or directed) to identify the devices on the SMBus. The ...