Closed razvanphp closed 5 days ago
Initially I though this is because MKR ETH Shield uses W5500 chipset with a built-in hardware TCP/IP stack, while Portenta H7 uses LAN8742AI, an Ethernet PHY that requires a software TCP/IP stack like LwIP.
But today I tried to flash the exact same board with micropython and ping times look perfect:
64 bytes from 192.168.10.252: icmp_seq=10 ttl=255 time=0.075 ms
64 bytes from 192.168.10.252: icmp_seq=11 ttl=255 time=0.086 ms
64 bytes from 192.168.10.252: icmp_seq=12 ttl=255 time=0.082 ms
64 bytes from 192.168.10.252: icmp_seq=13 ttl=255 time=0.069 ms
64 bytes from 192.168.10.252: icmp_seq=14 ttl=255 time=0.072 ms
64 bytes from 192.168.10.252: icmp_seq=15 ttl=255 time=0.092 ms
64 bytes from 192.168.10.252: icmp_seq=16 ttl=255 time=0.094 ms
64 bytes from 192.168.10.252: icmp_seq=17 ttl=255 time=0.095 ms
64 bytes from 192.168.10.252: icmp_seq=18 ttl=255 time=0.085 ms
64 bytes from 192.168.10.252: icmp_seq=19 ttl=255 time=0.067 ms
64 bytes from 192.168.10.252: icmp_seq=20 ttl=255 time=0.094 ms
64 bytes from 192.168.10.252: icmp_seq=21 ttl=255 time=0.071 ms
64 bytes from 192.168.10.252: icmp_seq=22 ttl=255 time=0.086 ms
64 bytes from 192.168.10.252: icmp_seq=23 ttl=255 time=0.084 ms
64 bytes from 192.168.10.252: icmp_seq=24 ttl=255 time=0.069 ms
64 bytes from 192.168.10.252: icmp_seq=25 ttl=255 time=0.105 ms
64 bytes from 192.168.10.252: icmp_seq=26 ttl=255 time=0.084 ms
64 bytes from 192.168.10.252: icmp_seq=27 ttl=255 time=0.095 ms
Are there any settings or optimisations that I could try? Seems the issue is not in HW. Thanks!
this has nothing to do with the Ethernet library for W5500
cc: @per1234
this has nothing to do with the Ethernet library for W5500
You mean that this repo is only for W5500?
For Portenta I should open an issue here? https://github.com/arduino/ArduinoCore-mbed/tree/main/libraries/Ethernet/src
this repo is only for W5500?
Yes, the Ethernet library hosted in this repository only provides support for the WIZnet W5100, W5200, and W5500 Ethernet controllers. When you compile a sketch for the Portenta H7 board, the Arduino sketch build system automatically uses that different Ethernet library you linked, which is bundled with the "Arduino Mbed OS Portenta Boards" platform.
For Portenta I should open an issue here?
Yes, to report bugs or request features specific to the Ethernet library used by the Portenta H7, you should submit those to the issue tracker in the arduino/ArduinoCore-mbed
repository where that library's codebase is hosted.
Not sure if this should belong in ArduinoCore-mbed, but I assume it has more to do with this stack, than with the platform itself?
After migrating our app from MKR WiFi 1010 + ETH shield to Portenta H7 + Vision Shield, we noticed increased and uneven/unstable ping response times.
Here it is how it looks like on MKR:
And here it is on Portenta H7:
I suspect this is impacting our app's performance, since we need sub ms processing of the data received over ethernet, but not sure how to approach this problem.
Userland code is basically inexistent, as I'm testing just with this:
Thank you! R