With current builds running on a clean-installed build (no EEPROM settings, fresh boards), you may need to perform some steps in a specific order:
- Follow normal setups steps until you are able to connect via Wi-Fi (access point mode or on your network, doesn’t matter)
BEFORE enabling ethernet, set the pin used for LEDs to another value
AFTER changing the GPIO/pin used for LEDs, then you can enable ethernet at the bottom of the Wi-Fi configuration page.
The reason the order of these steps matter, is that the default pin for LEDs is IO16. Current builds allocate the pin to the LEDs before configuration of ethernet, which causes no end of problems with ethernet working. I have a PR pending with a fix for this configuration problem, that gives priority to the ethernet configuration.
Two other minor things to be aware of:
The LEDs on the WT32-ETH01 ethernet port may not light up, even if ethernet is working. I haven’t investigated the cause of this.
There is currently no support for static network settings on the ethernet port. Not an issue for typical home use, but if using on an isolated “show” network, you’ll need to ensure there is a DHCP server.