WG82574L S LBA9 Intel, WG82574L S LBA9 Datasheet - Page 235

• Manufacturer Part Number: WG82574L S LBA9
• Description: CONTROLLER, ENET, INTEL 82574L, 64PQFN
• Manufacturer: Intel

Specifications of WG82574L S LBA9

• Ethernet Type: IEEE 802.3, IEEE 802.3u, IEEE 802.3ab
• Supply Voltage Range: 3V To 3.6V
• Operating Temperature Range: 0°C To +85°C
• Digital Ic Case Style: QFN
• No. Of Pins: 64
• Package / Case: QFN
• Interface Type: I2C, JTAG, PCI, SPI
• Rohs Compliant: Yes
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

System Manageability—82574 GbE Controller
8.9
8.9.1
8.9.2
8.9.3
Function
Receive
Enable
Read
(0x0F)
Count
Byte
Data returned from the 82574L:
SMBus Troubleshooting
This section outlines the most common issues found while working with pass-through
using the SMBus sideband interface.
SMBus Commands are Always NACK'd by the 82574L
There are several reasons why all commands sent to the 82574L from a MC could be
NACK'd. The following are the most common:
SMBus Clock Speed is 16.6666 KHz
This can happen when the SMBus connecting the MC and the 82574L is also tied into
another device (such as an ICH) that has a maximum clock speed of 16.6666 KHz. The
solution is to not connect the SMBus between the 82574L and the MC to this device.
A Network Based Host Application is not Receiving any Network
Packets
Reports have been received about an application not receiving any network packets.
The application in question was NFS under Linux. The problem was that the application
was using the RMPC/RMCP+ IANA reserved port 0x26F (623), and the system was also
configured for a shared MAC and IP address with the OS and MC.
The management control to host configuration, in this situation, was setup not to send
RMCP traffic to the OS (this is typically the correct configuration). This means that no
traffic send to port 623 was being routed.
The solution in this case is to configure the problematic application NOT to use the
reserved port 0x26F.
15
Function
• Invalid NVM Image - The image itself might be invalid, or it could be a valid image;
• The MC is not using the correct SMBus address - Many MC vendors hard-code the
• The SMBus address(es) can also be dynamically set using the SMBus ARP
• Bus Interference - the bus connecting the MC and the 82574L might be unstable.
Receive
Enable
Read
however, it is not a pass-through image, as such SMBus connectivity is disabled.
SMBus address(es) into their firmware. If the incorrect values are hard-coded, the
82574L does not respond.
mechanism.
Data 1
Code)
(Op-
0xDA
Command
0xDA
Receive
Data 2
Control
Byte
Data
Addr
MAC
LSB
3
…
…
Data
Addr
MAC
MSB
8
Data
Addr
LSB
IP
9
…
…
IP Addr
Data
MSB
12
SMBus
Data
Addr
MC
13
Data
Data
Byte
I/F
14
Value
Data
Alert
Byte
15
235