-
Notifications
You must be signed in to change notification settings - Fork 7.6k
LAN8720 PHY can fail to initialize or crash. Methods to monitor or query this are inaccessible for arduino core >=2.0.0 #6500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @smuellener, can you please test this on 2.0.3-RC1 too? |
@VojtechBartoska yes this applies to 2.0.3-RC1 as well. |
@smuellener How do you reset the Phy? |
@TD-er using a dedicated gpio |
I was affraid you would say that, as my boards don't have the LAN8720 RST pin connected to a GPIO. Does power cycle (of the LAN chip) help here on these issues? |
That could well be but I have not tested this. Do you have any means to do electrical discharge tests? |
Board
ESP32 PICO D4 with LAN7820
Device Description
Custom
Hardware Configuration
LAN7820 connected to ESP32 via RMII in a standard way. ETH.begin() can be called without arguments.
Version
v2.0.2
IDE Name
Arduino IDE with VisualMicro
Operating System
Windows 11
Flash frequency
40Hz
PSRAM enabled
no
Upload speed
115200
Description
Before arduino-esp32 v. 2.0.0 we could call the following function:
Those functions helped us to monitor the PHY more closely as the PHY can crash during operation (e.g. due to electrostatic discarges). In case the phy crashed, we reinitialized it using
Those functions are not available anymore in arduino core version >= 2.0.0 therefore this monitoring is not possible anymore.
Please reintroduce a possibility to read the PHY registers so that we can monitor the correct operation of the PHY again. We are particularly interested in:
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: