So I have tested the latest stepping of the W7500P (1720 marking) and the 100Mbps problem does not appear to be resolved. I’m getting an unacceptable amount of disconnects when connection speed is 100Mbps.
I have tested both through a router and a direct connection to PC. The device is polled every 1s and dropouts were logged over a 24h period. I get approximately 1 disconnect every 3 hours over LAN. Interestingly, with a direct PC connection the disconnects are far more frequent. 1 disconnect every 3 minutes!
Running the same test, forcing 10Mbps speed, resulted in 0 disconnects over a 24h period for both LAN and direct connection. The software and libraries were identical for all tests except for calling eth.set_link(FullDuplex10). Is there an updated ethernet library I should be using in conjunction with the latest stepping to fix the 100Mbps bug?
Also, eth.set_link(FullDuplex10); is definitely not working properly even after the recommended changes to the library. It fails to force 10Mbps negotiation and defaults to 100Mbps far more often than I originally thought. I often have to reboot the device multiple times before it actually connects at 10Mbps. I’m guessing there is some sort of hard-coded timeout where if it fails to connect at a desired speed it defaults or the register that sets link speed is being reset somehow? Link speed has been verified using the W7500P device’s LEDs and in the local area connection settings on the PC. It’s also pretty obvious when it is operating at 100Mbps because of the frequency of disconnects.
Currently all devices in the field are directly connected to a PC. The connection speed is forced to 10Mbps in the PC’s network settings since setting link speed on the W7500P does not work properly. This severely limits our applications since we can only use 1 W7500P device (1 ethernet port on a PC) and have to connect the PC to our LAN via a Wifi adapter.
Hopefully there is a quick fix for this because quite frankly I’m about to give up on Wiznet