W5500 10BASE-T compliance test: how to transmit continuous test data (min IPG / random / all-ones)?
Ethernet Chips
- W5500
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: W5500 10BASE-T compliance test: how to transmit continuous test data (min IPG / random / all-ones)?
by Grace_Koo WIZnet ·
Hello,
Thank you for your detailed questions. Please see our answers below.
1. How the compliance test data was generated
For the W5500 compliance test, the test data was generated by an MCU.
The required data pattern differs by test item. For example, for the Jitter test and the TP_IDL test, the code selects and transmits a Random, All-One, or All-Zero pattern according to each test mode.
This data was transmitted in MACRAW mode, the same mode you are using.
2. Test mode for transmitting without a link partner
The W5500 does not have a separate PHY test mode that outputs an Ethernet pattern by itself without a link partner.
If a specific pattern must be output without a link partner, this function needs to be supported by the external test equipment.
Continuous patterns are also not generated internally by the PHY. They are transmitted by connecting an MCU to the W5500 over SPI, with the MCU continuously supplying the data.
3. SEND command, SEND_OK, and minimum IPG
Sending multiple Ethernet frames with a single SEND command is not supported.
SEND_OK is generated after the data delivered from the MCU over SPI has passed through the W5500 TX buffer and has been fully transmitted to the network.
Therefore, we do not recommend issuing the next SEND command before SEND_OK.
Also, since the W5500 PHY itself has no pattern generation function for compliance testing, it cannot generate continuous frames on its own at the minimum IPG of 9.6 µs.
The actual interval between frames depends on the MCU processing time, the SPI transfer speed, and the internal processing time of the W5500, so it is difficult to give a fixed value.
The actual transmission latency and inter-frame gap need to be measured in your MCU–SPI–W5500 environment.
Best regards,
RE: W5500 10BASE-T compliance test: how to transmit continuous test data (min IPG / random / all-ones)?
by ciniml Solution ·
Thank you for the detailed answers. They match what we found, and we have now passed the 10BASE-T / 100BASE-TX compliance tests with this approach. In case it helps others, here is a minimal single-file ESP32-S3 program (ESP-IDF v5.5.4) that we used (attached:
w5500_txflood.c).It drives the W5500 directly (no esp_eth driver): SOCK0 in MACRAW mode with the full 16 KB TX buffer, PHY forced via PHYCFGR, and a serial console to select the PHY mode (
phy 10h|10f|100h|100f|auto), traffic (tx random|ones|stop) and frame length.100BASE-TX: no special firmware is needed. Forcing the PHY to 100M (PHYCFGR, auto-negotiation off) is enough. The IDLE signal is scrambled, so the W5500 continuously sends a random-like MLT-3 signal without any frames or link partner, and that signal can be used for all 100BASE-TX test items.
10BASE-T: with this method we could output the patterns required for the tests:
Link partner (10BASE-T): the W5500 does not transmit without link, so the frame-based 10BASE-T tests need a link partner forced to 10M without auto-negotiation. A forced link partner keeps sending link pulses, so the link comes up even through a test fixture that terminates the DUT's TX. A Raspberry Pi 4 Model B worked well for this:
sudo ethtool -s eth0 autoneg off speed 10 duplex half. When forced, its PHY stays MDI and does not switch pairs, so the link stayed up during the whole measurement. We used a straight cable through the fixture.Following your recommendation, SEND is always issued only after SEND_OK. We also confirmed that issuing SEND before SEND_OK corrupts the frame on the wire. To get close to the minimum IPG we:
Measured with an FPGA receiver on 10BASE-T, 1514-byte frames (SPI clock 26.7 MHz, CPU 160 MHz): 812 frames/s; the IPG was between 10.6 and 11.2 µs for all 16,243 frames in 20 seconds (average 10.92 µs), with no FCS or payload errors. The all-ones pattern gave the same IPG. If Sn_TX_WR is written only after SEND_OK (as described in the datasheet), the IPG becomes 12.6–22.4 µs (average 14.05 µs). The IPG values cluster around ~10.7 and ~11.1 µs (0.4 µs = one nibble apart) even when SEND is issued earlier, which suggests the W5500 aligns the start of the next frame internally.
Thanks again for your support.