JL82572EI Intel, JL82572EI Datasheet - Page 40

• Manufacturer Part Number: JL82572EI
• Manufacturer: Intel

Specifications of JL82572EI

• Mounting: Surface Mount
• Pin Count: 256
• Lead Free Status / RoHS Status: Compliant

64.
Problem:
Implication: The 82571/82572 may wake the system on a non-wakeup packet.
Workaround: None.
Status:
65.
Problem:
Implication: In Link training and recovery this could result in the upstream device or the 82571EB-
Workaround: None. Devices should self-recover.
Status:
66.
Problem:
Implication: Test equipment checking for compliance of Master/Slave resolution may report failures
Workaround: None.
Status:
82571/82572 Specification Update
Datasheet
42
Wakeup Event Occurs on Magic Packet that Doesn’t Pass
Address Filter
SKP (SKIP ordered set) Will Reset TS (Training Sequence)
Count.
Internal Copper PHY: Test Equipment May Report Master/Slave
Device Doesn't Correctly Implement Master/Slave Resolution.
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 packet (non-
magic packet) is accepted according to the address filtering scheme.
No fix.
Upon reception of a SKP, the TS counter will be reset. In link training and recovery, even
if the upstream PCIe device sends the correct number of TS, the device may not count all
of them if a SKP is sent in between the TS. The 82571EB-82572EI needs 8 consecutive
TS1 and then 8 consecutive TS2 to move forward in the LTSSM state machine. If a SKP is
sent in between those 8, the internal count of these will start over at 0.
82572EI timing out and going back to detect and starting the training process again. If
both devices follow the timeouts given the in the PCIe specification, they should self-
recover and eventually link.
No Fix
When the internal Copper PHY is operating in 1000 Mbps forced slave mode, illegal data
may be detected from the device during the transition from 10 Mbps mode (auto
negotiation) to 1000 Mbps mode after master/slave resolution is complete.
when the device is in Force Slave mode. In Forced Slave mode, the device should not
transmit any 1000 Mbps signals, which it is does not. However some test equipment
looks for any activity sent from the device in forced slave mode and considers this a
failure instead of looking for valid 1000 Mbps signals. Therefore, the illegal data may
results in failures reported by test equipment.
Internal validation shows the device compiles with IEEE 802.3 Table 40-5; for all
configurations, the device resolves to the correct defined mode
No Fix
82571/82572 Specification Update
Revision: 6.3US
July 2010
323853