w5500 Ds V106e 141230
w5500 Ds V106e 141230
w5500 Ds V106e 141230
Version 1.0.6
http://www.wiznet.co.kr
Features
- Supports Hardwired TCP/IP Protocols : TCP, UDP, ICMP, IPv4, ARP, IGMP, PPPoE
- Supports 8 independent sockets simultaneously
- Supports Power down mode
- Supports Wake on LAN over UDP
- Supports High Speed Serial Peripheral Interface(SPI MODE 0, 3)
- Internal 32Kbytes Memory for TX/RX Buffers
- 10BaseT/100BaseTX Ethernet PHY embedded
- Supports Auto Negotiation (Full and half duplex, 10 and 100-based )
- Not supports IP Fragmentation
- 3.3V operation with 5V I/O signal tolerance
- LED outputs (Full/Half duplex, Link, Speed, Active)
- 48 Pin LQFP Lead-Free Package (7x7mm, 0.5mm pitch)
PMODE0
PMODE1
PMODE2
AGND
RSVD
RSVD
RSVD
RSVD
RSVD
RSTn
NC
NC
41
45
43
42
39
37
46
38
48
47
44
40
TXN 1 36 INTn
TXP 2 35 MOSI
AGND 3 34 MISO
AVDD 4 33 SCLK
RXN 5 32 SCSn
RXP 6
W5500 31 XO
DNC 7 30 XI/CLKIN
AVDD 8
48LQFP 29 GND
AGND 9 28 VDD
EXRES1 10 27 ACTLED
AVDD 11 26 DUPLED
NC 12 25 LINKLED
20
21
22
23
24
18
13
14
15
16
17
19
NC
AGND
AVDD
AGND
AVDD
VBG
AGND
TOCAP
AVDD
1V2O
RSVD
SPDLED
Type Description
I Input
O Output
I/O Input / Output
A Analog
PWR 3.3V power
GND Ground
Internal
Pin No Symbol Type Description
Bias1
1 TXN - AO TXP/TXN Signal Pair
2 TXP - AO The differential data is transmitted to the media on the
TXP/TXN signal pair.
3 AGND - GND Analog ground
4 AVDD - PWR Analog 3.3V power
5 RXN - AI RXP/RXN Signal Pair
6 RXP - AI The differential data from the media is received on the
RXP/RXN signal pair.
7 DNC - AI/O Do Not Connect Pin
8 AVDD - PWR Analog 3.3V power
9 AGND - GND Analog ground
10 EXRES1 - AI/O External Reference Resistor
It should be connected to an external resistor (12.4K,
1%) needed for biasing of internal analog circuits.
Refer to the External reference resistor (Figure.2) for
details.
11 AVDD - PWR Analog 3.3V power
12 - - NC
13 - - NC
14 AGND - GND Analog ground
15 AVDD - PWR Analog 3.3V power
16 AGND - GND Analog ground
17 AVDD - PWR Analog 3.3V power
18 VBG - AO Band Gap Output Voltage
This pin will be measured as 1.2V at 25.
It must be left floating.
19 AGND - GND Analog ground
20 TOCAP - AO External Reference Capacitor
This pin must be connected to a 4.7uF capacitor.
The trace length to capacitor should be short to
stabilize the internal signals.
21 AVDD - PWR Analog 3.3V power
22 1V2O - AO 1.2V Regulator output voltage
1 0 1 Not used
1 1 0 Not used
.
46 - - - NC
47 - - - NC
The 12.4K(1%) Resistor should be connected between EXRES1 pin and analog ground (AGND)
as below.
SCSn SCSn
SCLK SCLK
MOSI MOSI
MISO MISO
SCSn SCSn
SCLK SCLK
MOSI MOSI
MISO MISO
The SPI protocol defines four modes for its operation (Mode 0, 1, 2, 3).Each mode
differs according to the SCLK polarity and phase. The only difference between SPI
Mode 0 and SPI Mode 3 is the polarity of the SCLK signal at the inactive state.
With SPI Mode 0 and 3, data is always latched in on the rising edge of SCLK and
always output on the falling edge of SCLK.
SCLK SCLK
MISO/MOSI MISO/MOSI
Mode 0 : SCLK idle level low Mode 3 : SCLK idle level high
Address Phase specifies 16 bits Offset Address for W5500 Register or TX/RX Memory.
Control Phase specifies the block to which Offset (set by Address Phase) belongs, and
specifies Read/Write Access Mode and SPI Operation Mode (Variable Length Data /
Fixed Length Data Mode).
And Data Phase specifies random length (N-bytes, 1 N) Data or 1 byte, 2 bytes and
4 bytes Data.
If SPI Operation Mode is set as Variable Length Data Mode (VDM), SPI Bus Signal SCSn
must be controlled by the External Host with SPI Frame step.
At the Variable Length Data Mode, SCSn Control Start (Assert (High-to-Low)) informs
W5500 of SPI Frame Start (Address Phase), and SCSn Control End (De-assert (Low-to-
High) informs W5500 of SPI Frame End (Data Phase End of random N byte).
Data Phase
Address Phase Control Phase
N >= 1
MSB first MSB first
N+2
0 1 2 3
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
16btis Offset Address Control Byte Data 1 ... Data N
Block R OP
Select Bits W Mode
W5500 supports Sequential Data Read/Write. It processes the data from the base
(the Offset Address which is set for 2/4/N byte Sequential data processing) and the
next data by increasing the Offset Address (auto increment addressing) by 1.
7 6 5 4 3 2 1 0
BSB4 BSB3 BSB2 BSB1 BSB0 RWB OM1 OM0
00100 Reserved
01000 Reserved
01100 Reserved
10000 Reserved
10100 Reserved
11000 Reserved
11100 Reserved
If the Reserved Bits are selected, it can cause the mal-function of the
W5500.
Read/Write Access Mode Bit
This sets Read/Write Access Mode.
2 RWB
0 : Read
1 : Write
SPI Operation Mode Bits
This sets the SPI Operation Mode.
SPI Operation Mode supports two modes, the Variable Length Data
Mode and the Fixed Length Data Mode.
OM[1:0] Meaning
00 Variable Data Length Mode, N-Bytes Data Phase (1 N)
01 Fixed Data Length Mode , 1 Byte Data Length (N = 1)
10 Fixed Data Length Mode , 2 Byte Data Length (N = 2)
11 Fixed Data Length Mode , 4 Byte Data Length (N = 4)
MOSI 15 14 13 3 2 1 0 4 3 2 1 0 W 0 0 7 6 5 4 3 2 1 0
MISO
...
32 33 34 35 36 37 37 39 8N + 16 8N + 24
SCLK
8-bit Data 2 ... 8-bit Data N
MOSI 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
MISO
Figure 8 shows the SPI Frame when the external host accesses W5500 for writing.
In VDM mode, the RWB signal is 1 (Write), OM[1:0] is 00 in SPI Frame Control
Phase.
At this time the External Host assert (High-to-Low) SCSn signal before
transmitting SPI Frame.
Then the Host transmits SPI Frames all bits to W5500 through MOSI signal. All
bits are synchronized with the falling edge of the SCLK.
After finishing the SPI Frame transmit, the Host deasserts SCSn signal (Low-to-
High).
When SCSn is Low and the Data Phase continues, the Sequential Data Write can
be supported.
When the Host writes Data 0xAA to Socket Interrupt Mask Register (SIMR) of
Common Register Block by using VDM mode, the data is written with the SPI Frame
below.
SCSn
When the Host writes 5 Bytes Data (0x11, 0x22, 0x33, 0x44, 0x55) to Socket 1s TX
Buffer Block 0x0040 Address by using VDM mode, 5 bytes data are written with the SPI
Frame below.
SCSn
SCSn
Figure 10. 5 Byte Data Write at 1th Sockets TX Buffer Block 0x0040 in VDM mode
MOSI 15 14 13 3 2 1 0 4 3 2 1 0 R 0 0
MISO 7 6 5 4 3 2 1 0
32 33 34 35 36 37 38 39 ... 8N + 16 8N + 24
SCLK
8-bit Data 2 ... 8-bit Data N
MOSI
MISO 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Figure 11 shows the SPI Frame when external host accesses W5500 for reading
In VDM mode, the RWB signal is 0 (Write), OM[1:0] is 00 in SPI Frame Control
Phase.
At this time the External Host assert (High-to-Low) SCSn signal before transmitting
SPI Frame.
Then the Host transmits Address and Control Phase all bits to W5500 through MOSI
signal. All bits are synchronized with the falling edge of the SCLK.
Then the Host receives all bits of Data Phase with synchronizing the rising edge of
Sampling SCLK through MISO signal.
After finishing the Data Phase receive, the Host deasserts SCSn signal (Low-to-
High).
When SCSn is Low and the Data Phase continues to receive, the Sequential Data
Read can be supported.
When the Host reads the Socket Status Register(S7_SR) of the Socket 7s Register
Block by using VDM mode, the data is read with the SPI Frame below. Lets S7_SR to
SOCK_ESTABLISHED (0x17).
SCSn
When the Host reads 5 Bytes Data (0xAA, 0xBB, 0xCC, 0xDD, 0xEE) from the Socket
3s RX Buffer Block 0x0100 Address by using VDM mode, 5 bytes data are read with the
SPI Frame as below.
SCSn
SCSn
Figure 13. 5 Byte Data Read at Socket 3 RX Buffer Block 0x0100 in VDM mode
As the SPI Frame of FDM mode is the same as SPI Frame of VDM mode (1Byte, 2
Bytes, 4 Bytes SPI Frame) except for the SCSn signal control and OM[1:0] setting, the
detail about FDM mode is not described in this section.
It is not recommended to use the FDM mode unless you are in inevitable status. In
addition, we use only 1/2/4 Bytes SPI Frame, as described in Chapter 2.4.1 &
Chapter 2.4.2. Using SPI Frame with other length of Data will cause malfunction of
W5500.
W5500 has one Common Register Block, eight Socket Register Blocks, and TX/RX
Buffer Blocks allocated to each Socket. Each block is selected by the BSB[4:0](Block
Select Bit) of SPI Frame. Figure 20 shows the selected block by the BSB[4:0] and the
available offset address range of Socket TX/RX Buffer Blocks. Each Sockets TX Buffer
Block exists in one 16KB TX memory physically and is initially allocated with 2KB.
Also, Each Sockets RX Buffer Block exists in one 16KB RX Memory physically and is
initially allocated with 2KB.
Regardless of the allocated size of each Socket TX/RX Buffer, it can be accessible
within the 16 bits offset address range (From 0x0000 to 0xFFFF).
Refer to Chapter 3.3 for more information about 16KB TX/RX Memory
organization and access method.
0xFFFF 0x3FFF
11111 (0x1F) Socket 7 RX Buffer 0x3E2C Socket 7
0xF800 0x3800
RX Buffer (2KB)
11110 (0x1E) Socket 7 TX Buffer 0xF7FF
Socket 6
11101 (0x1E) Socket 7 Register 0xF000 0x3000
RX Buffer (2KB)
0xEFFF
Socket 5
11100 (0x1C) Reserved
...
RX Buffer (2KB)
...
0x2800
11011 (0x1B) Socket 6 RX Buffer Socket 4
Socket 7 RX Buffer 0x9E2C RX Buffer (2KB)
11010 (0x1A) Socket 6 TX Buffer 0x2000
Socket 3
...
11001 (0x19) Socket 6 Register RX Buffer (2KB)
0x1800
0x1000
11000 (0x18) Reserved 0x0FFF Socket 2
0x1000
RX Buffer (2KB)
10111 (0x17) Socket 5 RX Buffer 0x0800 0x0FFF
0x07FF Socket 1
10110 (0x16) Socket 5 TX Buffer 0x0800
RX Buffer (2KB)
0x0000
Socket 0
10101 (0x15) Socket 5 Register RX Buffer (2KB)
0x0000
0x1800
TX Buffer (2KB)
01010 (0x0A) Socket 2 TX Buffer
0x1000
Socket 2
01001 (0x09) Socket 2 Register 0x0FFF
0x1000
TX Buffer (2KB)
0x0FFF
01000 (0x08) Reserved 0x0800 0x093C
Socket 1
0x07FF
0x0800
TX Buffer (2KB)
00111 (0x07) Socket 1 RX Buffer Socket 0
0x0000
TX Bufer (2KB)
00110 (0x06) Socket 1 TX Buffer 0x0000
...
Register Block(when 0n7). The n value of Socket n Register can be selected by BSB[4:0] of
SPI Frame. <Table 4> defines the 16bits Offset Address of registers in Socket n Register Block.
0x0001 (Sn_TX_WR1)
Socket n
The Socket n TX Buffer Block allocated in 16KB TX memory is buffer for saving data
to be transmitted by host. The 16bits Offset Address of Socket n TX Buffer Block has
64KB address space ranged from 0x0000 to 0xFFFF, and it is configured with
reference to Socket n TX Write Pointer Register (Sn_TX_WR) & Socket n TX Read
Pointer Register(Sn_RX_RD). However, the 16bits Offset Address automatically
converts into the physical address to be accessible in 16KB TX memory such as Figure
20. Refer to Chapter 4.2 for Sn_TX_WR & Sn_TX_RD.
The Socket n RX Buffer Block allocated in 16KB RX memory is buffer for saving the
received data through the Ethernet. The 16bits Offset Address of Socket n RX Buffer
Block has 64KB address space ranged from 0x0000 to 0xFFFF, and it is configured with
reference to Socket n RX RD Pointer Register (Sn_RX_RD) & Socket n RX Write
Pointer Register (Sn_RX_WR). However, the 16bits Offset Address automatically
converts into the physical address to be accessible in 16KB RX memory such as Figure
20. Refer to Chapter 4.2 for Sn_RX_RD & Sn_RX_WR.
MR is used for S/W reset, ping block mode and PPPoE mode.
7 6 5 4 3 2 1 0
RST Reserved WOL PB PPPoE Reserved FARP Reserved
If WOL mode is enabled and the received magic packet over UDP has
been normally processed, the Interrupt PIN (INTn) asserts to low. When
5 WOL
using WOL mode, the UDP Socket should be opened with any source port
number. (Refer to Socket n Mode Register (Sn_MR) for opening Socket.)
Notice: The magic packet over UDP supported by W5500 consists of 6
bytes synchronization stream (0xFFFFFFFFFFFF) and 16 times Target MAC
address stream in UDP payload. The options such like password are
ignored. You can use any UDP source port number for WOL mode.
Ping Block Mode
INTLEVEL configures the Interrupt Assert Wait Time (IAWT). When the next interrupt
occurs, Interrupt PIN (INTn ) will assert to low after INTLEVEL time.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
PLL_CLK
b.
a. c. IAWT d.
INTn
a. When Timeout Interrupt of Socket 0 is occurred, S0_IR[3] & SIR[0] bit set as 1
and then INTn PIN is asserted to low.
b. When the connection interrupt of Socket 1 is occurred before the previous
interrupt processing is not completed, S1_IR[0] & SIR[1] bits set as 1 and INTn PIN is
still low.
c. If the host processed the previous interrupt completely by clearing the S0_IR[3]
bit, INTn PIN is de-asserted to high but S1_IR[0] & SIR[1] is still set as 1.
d. Although S1_IR[0] & SIR[1] bit is set as 1, the INTn cant be asserted to low
during INTLEVEL time. After the INTLEVEL time expires, the INTn will be asserted to
low.
IR indicates the interrupt status. Each bit of IR can be cleared when the host writes
1 value to each bit. If IR is not equal to 0x00, INTn PIN is asserted low until it is
0x00.
7 6 5 4 3 2 1 0
CONFLICT UNREACH PPPoE MP Reserved Reserved Reserved Reserved
IMR is used to mask interrupts. Each bit of IMR corresponds to each bit of IR. When
a bit of IMR is 1 and the corresponding bit of IR is 1, an interrupt will be issued.
In other words, if a bit of IMR is 0, an interrupt will not be issued even if the
corresponding bit of IR is 1.
7 6 5 4 3 2 1 0
IM_IR7 IM_IR6 IM_IR5 IM_IR4 Reserved Reserved Reserved Reserved
SIR indicates the interrupt status of Socket. Each bit of SIR be still 1 until Sn_IR is
cleared by the host. If Sn_IR is not equal to 0x00, the n-th bit of SIR is 1 and INTn
PIN is asserted until SIR is 0x00.
7 6 5 4 3 2 1 0
S7_INT S6_INT S5_INT S4_INT S3_INT S2_INT S1_INT S0_INT
Each bit of SIMR corresponds to each bit of SIR. When a bit of SIMR is 1 and the
corresponding bit of SIR is 1, Interrupt will be issued. In other words, if a bit of
SIMR is 0, an interrupt will be not issued even if the corresponding bit of SIR is 1.
7 6 5 4 3 2 1 0
S7_IMR S6_IMR S5_IMR S4_IMR S3_IMR S2_IMR S1_IMR S0_IMR
RTR configures the retransmission timeout period. The unit of timeout period is
100us and the default of RTR is 0x07D0 or 2000. And so the default timeout period
is 200ms(100us X 2000).
During the time configured by RTR, W5500 waits for the peer response to the
packet that is transmitted by Sn_CR(CONNECT, DISCON, CLOSE, SEND, SEND_MAC,
SEND_KEEP command). If the peer does not respond within the RTR time, W5500
retransmits the packet or issues timeout.
The timeout of W5500 can be configurable with RTR and RCR. W5500 has two kind
timeout such as Address Resolution Protocol (ARP) and TCP retransmission.
At the ARP (Refer to RFC 826, http://www.ietf.org/rfc.html) retransmission
timeout, W5500 automatically sends ARP-request to the peers IP address in order to
acquire MAC address information (used for communication of IP, UDP, or TCP). While
waiting for ARP-response from the peer, if there is no response during the configured
RTR time, a temporary timeout is occurred and ARP-request is retransmitted. It is
repeated as many as RCR + 1 times. Even after the ARP-request retransmissions are
repeated as RCR+1 and there is no response to the ARP-request, the final timeout is
occurred and Sn_IR(TIMEOUT) becomes 1. The time of final timeout (ARPTO) of ARP-
request is as below.
= ( 0.1) ( + 1)
At the TCP packet retransmission timeout, W5500 transmits TCP packets (SYN, FIN,
RST, DATA packets) and waits for the acknowledgement (ACK) during the configured
RTR time and RCR. If there is no ACK from the peer, a temporary timeout occurs and
the TCP packet is retransmitted. The retransmission is repeated as many as RCR+1.
= (( 2 ) + (( ) )) 0.1
=0
N : Retransmission count, 0N M
RTRMAX : RTR x 2M
PTIMER (PPP Link Control Protocol Request Timer Register) [R/W] [0x001C] [0x0028]
PTIMER configures the time for sending LCP echo request. The unit of time is 25ms.
PMAGIC (PPP Link Control Protocol Magic number Register) [R/W] [0x001D] [0x00]
PMAGIC configures the 4bytes magic number to be used in LCP echo request.
PHAR should be written to the PPPoE server hardware address acquired in PPPoE
connection process
PSID should be written to the PPPoE sever session ID acquired in PPPoE connection
process.
PHYCFGR configures PHY operation mode and resets PHY. In addition, PHYCFGR
indicates the status of PHY such as duplex, Speed, Link.
Bit Symbol Description
Reset [R/W]
7 RST When this bit is 0, internal PHY is reset.
After PHY reset, it should be set as 1.
Configure PHY Operation Mode
1: Configure with OPMDC[2:0] in PHYCFGR
0: Configure with the H/W PINs(PMODE[2:0])
This bit configures PHY operation mode with OPMDC[2:0] bits or
PMODE[2:0] PINs. When W5500 is reset by POR or RSTn PIN, PHY
6 OPMD
operation mode is configured with PMODE[2:0] PINs by default. After
POR or RSTn reset, user can re-configure PHY operation mode with
OPMDC[2:0]. If user wants to re-configure with PMDC[2:0], it should
reset PHY by setting the RST bit to 0 after the user configures this
bit as 1 and OPMDC[2:0] .
Operation Mode Configuration Bit[R/W]
These bits select the operation mode of PHY such as following table.
5 4 3 Description
1 0 1 Not used
7 6 5 4 3 2 1 0
MULTI/ ND / MC UCASTB
BCASTB P3 P2 P1 P0
MFEN /MMB MIP6B
MULTI/
7 MAC Filter Enable in MACRAW mode
MFEN
0 : disable MAC Filtering
1 : enable MAC Filtering
This bit is applied only during MACRAW mode(P[3:0] = 0100).
When set as 1, W5500 can only receive broadcasting packet or packet
sent to itself. When this bit is 0, W5500 can receive all packets on
Ethernet. If user wants to implement Hybrid TCP/IP stack, it is
recommended that this bit is set as 1 for reducing host overhead to
process the all received packets.
Broadcast Blocking in MACRAW and UDP mode
0 : disable Broadcast Blocking
6 BCASTB 1 : enable Broadcast Blocking
This bit blocks to receive broadcasting packet during UDP mode(P[3:0] =
0010). In addition, This bit does when MACRAW mode(P[3:0] = 0100)
Use No Delayed ACK
0 : Disable No Delayed ACK option
ND/MC/
5 1 : Enable No Delayed ACK option
MMB
This bit is applied only during TCP mode (P[3:0] = 0001).
When this bit is 1, It sends the ACK packet without delay as soon as a
Multicast
0 : using IGMP version 2
1 : using IGMP version 1
This bit is applied only during UDP mode(P[3:0] = 0010) and MULTI =
1.
It configures the version for IGMP messages (Join/Leave/Report).
2 P2 P3 P2 P1 P0 Meaning
0 0 0 0 Closed
1 P1 0 0 0 1 TCP
0 0 1 0 UDP
0 1 0 0 MACRAW
0 P0
* MACRAW mode should be only used in Socket 0.
This is used to set the command for Socket n such as OPEN, CLOSE, CONNECT,
LISTEN, SEND, and RECEIVE. After W5500 accepts the command, the Sn_CR register is
automatically cleared to 0x00. Even though Sn_CR is cleared to 0x00, the command
is still being processed. To check whether the command is completed or not, please
check the Sn_IR or Sn_SR.
.
This is valid only in TCP mode (Sn_MR(P3:P0) = Sn_MR_TCP). In this
mode, Socket n operates as a TCP server and waits for
connection-request (SYN packet) from any TCP client.
The Sn_SR changes the state from SOCK_INIT to SOCKET_LISTEN.
0x02 LISTEN When a TCP client connection request is successfully established,
the Sn_SR changes from SOCK_LISTEN to SOCK_ESTABLISHED and the
Sn_IR(0) becomes 1. But when a TCP client connection request is
failed, Sn_IR(3) becomes 1 and the status of Sn_SR changes to
SOCK_CLOSED.
This is valid only in TCP mode and operates when Socket n acts as
TCP client. To connect, a connect-request (SYN packet) is sent to
TCP server configured by Sn_DIPR & Sn_DPORT(destination address
& port). If the connect-request is successful, the Sn_SR is changed
to SOCK_ESTABLISHED and the Sn_IR(0) becomes 1.
0x08 DISCON When the disconnect-process is successful (that is, FIN/ACK packet
is received successfully), Sn_SR is changed to SOCK_CLOSED.
Otherwise, TCPTO occurs (Sn_IR(3)=1)= and then Sn_SR is changed
to SOCK_CLOSED.
7 6 5 4 3 2 1 0
Reserved Reserved Reserved SEND_OK TIMEOUT RECV DISCON CON
Sn_SR indicates the status of Socket n. The status of Socket n is changed by Sn_CR
or some special control packet as SYN, FIN packet in TCP.
The following table shows a temporary status indicated during changing the status
of Socket n.
Sn_PORT configures the source port number of Socket n. It is valid when Socket n
is used in TCP/UDP mode. It should be set before OPEN command is ordered.
This register is used for MSS (Maximum Segment Size) of TCP, and the register displays MSS set
by the other party when TCP is activated in Passive Mode.
Ex) In case of Socket 0 MSS = 1460 (0x05B4), configure as below,
0x0012 0x0013
0x05 0xB4
Value (dec) 0 1 2 4 8 16
Buffer size 0KB 1KB 2KB 4KB 8KB 16KB
Value (dec) 0 1 2 4 8 16
Buffer size 0KB 1KB 2KB 4KB 8KB 16KB
Note) Because this register for representing the size information is 16 bits, it is
impossible to read all bytes at the same time. Before 16 bit-read operation is not
completed, the value may be changed.
Therefore, it is recommended that you read all 16-bits twice or more until getting
the same value.
Sn_RX_RSR indicates the data size received and saved in Socket n RX Buffer.
Sn_RX_RSR does not exceed the Sn_RXBUF_SIZE and is calculated as the difference
Note) Because this register for representing the size information is 16 bits, it is
impossible to read all bytes at the same time. Before 16 bit-read operation is not
completed, the value may be changed.
Therefore, it is recommended that you read all 16-bits twice or more until getting
the same value.
Sn_IMR masks the interrupt of Socket n. Each bit corresponds to each bit of Sn_IR.
When a Socket n Interrupt is occurred and the corresponding bit of Sn_IMR is 1, the
corresponding bit of Sn_IR becomes 1. When both the corresponding bit of Sn_IMR
and Sn_IR are 1 and the n-th bit of IR is 1, Host is interrupted by asserted INTn
PIN to low.
7 6 5 4 3 2 1 0
Reserved Reserved Reserved SEND_OK TIMEOUT RECV DISCON CON
Static latchup
Maximum
Symbol Parameter Test Condition Class Unit
value(1)
LU Static latch-up class TA = +25 C conforming I 200 mA
to JESD78A
10M Link - 75 - mA
10M Transmitting - 79 - mA
5.5 AC Characteristics
5.5.1 Reset Timing
TRC
RSTn
TPL
PLOCK
(Internal)
Frequency 25 MHz
VIH
SCLK VIL
TWH TWL
TDS TDH
VIH
MOSI VIL
TOV TOH TCHZ
VOH
HI-Z HI-Z
MISO VOL
of the circuit crosstalk and the length of the signal line. The minimum guaranteed speed of the SCLK
is 33.3 MHz which was tested and measured with the stable waveform.
Please refer to the SPI Application Note which shows the WIZnet test environment and results.
5 2.1ns is when pn loaded with 30pF. The time is shorter with lower capacitance.
5.5.6 MDIX
W5500 does not support auto-MDIX feature.
Thus, user should use straight-through cables to connect to other switches or routers and
crossover cables to connect to devices such as servers, workstations or another W5500.
However, user can use either type of cable to connect to other devices with auto-MDIX
enabled, and the interface automatically corrects for any incorrect cabling.
Note
protrusion.
2. ( ) is reference.
4. UNIT: mm
Corrected duplicated statements and typing errors (P.14, 23, 24, 28,
Ver. 1.0.6 30DEC2014 from 0x02 to 0x42 value of SOCK_MACRAW Sn_CR at 4.2 Socket
Registers(P.47)