Test device network speed

[PeterMu]

Hi guys,

I want to know whether the device meets the 100Mbps full duplex need how to test?

My own test is as follows:

The device ip is 192.168.1.10, pc ip is 192.168.1.135.(The ip of pc is different in wireshark(135) and test software(25), because it is not the same pc and same test, just for your information)

First of all, when connecting the device to PC via RJ45, the Ethernet link shows 100Mbps. I used the speed test software on PC, when sending arp, icmp, tcp, udp packets to the device at the same time, the device won't reply to some of the packets, especially not to ICMP packets.

In this case, is the device considered to meet the 100 megabit full duplex? Or do all requests have to be replied by the device.

[AScha.3 · Accepted solution]

Hi,

(for H563 - just as example) see:

https://github.com/STMicroelectronics/STM32CubeH5/blob/main/Projects/STM32H573I-DK/Applications/NetXDuo/Nx_TCP_Echo_Server/README.md

I tested with my Laptop and speed was close to the limit (for 100M connection).

->

https://community.st.com/t5/stm32-mcus-embedded-software/stm32h573i-dk-poor-tcp-tx-performance-iperf/td-p/642402

[STea]

Hello @PeterMu,

As @AScha.3 mentioned depending on the device and software you could in practice get close the 100 Mbps of theoretical bandwidth. you measured speed can be affected by many variables hindering your theoretical value: interference, cable quality, software processing time can impact your measured perf, but you should stay close to your theoretical 100M maybe if you could give us more info about your product and software we could clarify more. 

BR

[Pavel A.]

@PeterMu Your question can be interpreted in two ways: (1) how to see if the PHY indeed is in 100/FDX mode, and (2) how to measure performance.

The former can be seen if you plug the board to a professional managed switch (using a good cable!). Then just look at its LEDs, or use the software of the switch to report the port status and any anomalies it can detect. On the STM32 side, read the status reported by the PHY chip: negotiation result and progress. It must match the peer state.

Note that for full-duplex, auto negotiation must be used, because the full/half mode is reported via auto-negotiation protocol. If you set the link speed manually, you must assume half duplex mode (this is what our ethernet experts told me).

For the latter - use iperf or a professional tool (Chariot).

[PeterMu]

OK, thanks a lot, i will try it.

[PeterMu]

Thanks a lot, I will try iperf for speed test.