ENC28J60/SO Microchip Technology, ENC28J60/SO Datasheet - Page 8
![IC ETHERNET CTRLR W/SPI 28SOIC](/photos/6/59/65909/150-28-soic_sml.jpg)
ENC28J60/SO
Manufacturer Part Number
ENC28J60/SO
Description
IC ETHERNET CTRLR W/SPI 28SOIC
Manufacturer
Microchip Technology
Specifications of ENC28J60/SO
Controller Type
Ethernet Controller, MAC/10Base-T
Interface
SPI
Voltage - Supply
3.1 V ~ 3.6 V
Current - Supply
160mA
Operating Temperature
-40°C ~ 85°C
Mounting Type
Surface Mount
Package / Case
28-SOIC (7.5mm Width)
For Use With
DM163024 - BOARD DEMO PICDEM.NET 2AC164123 - BOARD DAUGHTER ETH PICTAIL PLUSAC164121 - BOARD DAUGHTER PICTAIL ETHERNET
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Part Number:
ENC28J60/SO
Manufacturer:
MICROCHIP/微芯
Quantity:
20 000
Revision B4 and are included for informational purposes.
ENC28J60
Ethernet Conformance Issues
The following conformance issues were noted in testing
the B1 and B4 silicon revisions for compliance with IEEE
Standard 802.3. These issues are not present after
1. Issue:
2. Issue:
DS80349C-page 8
The observed TP_IDL pattern transmitted by
ENC28J60 was observed to not stay within the
standard defined template when using the TPM
(Twisted Pair Model) and TP Test Load 2.
Reference:
Figures 14-10 and 14-11
Potential Application Impact
The TP_IDL test requires a total of six separate
subtests, using three different test loads with and
without TPM. The fact that the device consistently
passed five of the six sub tests, while narrowly
missing the sixth, leads to the conclusion that this
is a minor issue. No failures have been observed
due to this issue.
Work around
Use silicon revision B5 or later.
Affected Silicon Revisions
The ENC28J60 was observed to improperly
accept a frame with no preceding LTPs (Link Test
Pulse). When a device is in the Link Test Fail state,
it should exit this state when a valid packet is
received, however, the first packet should not be
accepted. The second and subsequent packets
should be accepted while the device is in the Link
Test Pass state.
Reference: IEEE Std 802.3, Figure 14-6
Potential Application Impact
Link Test Pulse is an integral part of every
10Base-T system. It is used to notify a link partner
of the presence of a 10Base-T device. An absence
of LTPs signifies that the Ethernet cable is not con-
nected or a link partner is missing. Even when a
cable is not connected, a 10Base-T device would
continuously send out LTPs. This fact makes it
unlikely that there will ever be a situation in which
a device would be receiving valid Ethernet frames
without already being in the Link Test Pass state.
B1
X
B4
X
TP_IDL Pattern
Exiting Link Test Fail State
IEEE
B5
B7
Std
802.3,
§14.3.1.2.1,
3. Issue:
In the unlikely event that this situation does occur,
higher layer protocols would protect the system
from accepting unwanted data. It is unlikely that
this failure will have significant impact on a
networked application. No failures have been
observed due to this issue.
Work around
Use silicon revision B5 or later.
Affected Silicon Revisions
The delay from the collision event to collision
enforcement with the jam pattern is approximately
50 BT (Bit Times), which is greater than the
specified limit of 36 BT.
Reference: IEEE Std 802.3, Annex B, § B.1.2
Potential Application Impact
A collision in a half-duplex 10Base-T is not an
unexpected event. It exists as a normal part of the
network operation. The purpose of the jam pattern
is to ensure that the duration of the collision is
sufficient to be noticed by the other transmitting
station(s) involved in the collision. A longer delay
between the collision event and the start of jam
pattern would cause the duration of the collision to
be longer.
After each collision, both transmitting stations
would back off and wait a random amount of time
before attempting to transmit again. The minimum
Idle time between each Ethernet frame is 9.6 s.
The longer collision duration of 14 BT, or 1.4 s,
can be considered as a small fraction of time
wasted for each collision. It is unlikely that this
issue will have significant impact on networked
applications. No failures have been observed due
to this issue.
Work around
Use silicon revision B5 or later.
Affected Silicon Revisions
B1
B1
X
X
B4
B4
X
X
Collision Handling
B5
B5
2010 Microchip Technology Inc.
B7
B7