I have a ESP32 connected to a LAN8720 chip on a custom PCB.
This all works fine. And we use it to send in sensor data to the Internet.
However we noticed that sometimes in the field the LAN8720 stops responding. This could be after a week, sometimes after 20 min. So it's random.
What happens is this:
1) Communication works we have Internet connection;
2) LAN8720 stops working/responding. I'm not sure why, but Internet connection stops...
3) Our board detects loss of internet and restarts (using esp_restart() function) when no internet connection was active for 2 hours.
4) The ESP32 comes up again, but now the LAN8720 is already started (this chip is not restarted), and the ESP is locked in a loop with the following message:
"emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0 (mask 0xfff0). Current value 0xffff"
You might think "there is no clock signal present". But there is a 50 Mhz clock signal on the LAN8720. So that works.
Now to prevent this loop, we should migrate to ESP-IDF 3.2 where this bug is fixed. I am aware of that, but we keep it in the loop for now...
5) We want to use the reset pin on the LAN8720 to make it reset. So while the ESP32 is in this 'emac' loop, we pull the LAN8720 reset pin low. This works. However usually it takes 'a few times' before the ESP32 breaks the loop and starts connecting to the LAN8720 again.
6) ESP32 program code executes further, and gives a "SYSTEM_EVENT_ETH_CONNECTED" event.
7) But now.... the SMI does not respond. When I read any register on the LAN8720, it returns 0xffff.
8) Rebooting the ESP32 again causes the same "emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0 (mask 0xfff0). Current value 0xffff" loop.
9) Pulling the power plug, and connecting it again, causes everything to start up fine. ESP32 and LAN8720. But this is not a desired workflow.
In a running situation we can induce this effect ourselves like this:
1) LAN8720 and ESP32 running fine (we have internet communication).
2) We pull nRST on LAN8720 low, during runtime.
3) The LAN8720 stops working, returning 0xffff on the SMI registers.
4) After reboot the LAN8720 does not connect properly giving the "emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0 (mask 0xfff0). Current value 0xffff" error.
5) We pull the nRST pin low during this loop a few times, and the ESP32 breaks the loop.
6) We have "SYSTEM_EVENT_ETH_CONNECTED"
7) No internet, and reading the SMI registers causes a 0xffff response.
- lan8720_2.png (255.84 KiB) Viewed 9233 times
I would expect that pulling the nRST pin will restart the LAN8720 and everything is fine after that. But not...
Also, I am aware of the fact that the 50 Mhz clock signal needs to be present during the nRST pin low. I have checked that it is.
Anyone any ideas?