You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started #11474 last year in order to incorporate Ethernet for more stable networking. I am now trying to make a more robust ESP32 + W5500 system by connecting W5500's reset pin to ESP32. But it seems that the driver is including the reset pin only in the latest 1.23.0 release, but not any earlier releases (checked between .20 and .23 preview, no reset in struct):
My experience with 1.20, which doesn't support W5500 reset pin, is that my W5500 reset pin is pulled up on the W5500 module. I was able to reboot ESP32 and reconnecting to Ethernet every time ESP32 rebooted. I wonder if this stability despite not using the reset pin was due to the driver issuing a software reset command to W5500 via SPI upon initialization. Now that the new MP version .23 is implementing W5500 reset pin, If I update my MP to .23, I wonder if I must issue nic.active(0) after each ESP32 soft reset. It sounds counter-intuitive.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I started #11474 last year in order to incorporate Ethernet for more stable networking. I am now trying to make a more robust ESP32 + W5500 system by connecting W5500's reset pin to ESP32. But it seems that the driver is including the reset pin only in the latest 1.23.0 release, but not any earlier releases (checked between .20 and .23 preview, no reset in struct):
micropython/ports/esp32/network_lan.c
Line 54 in a61c446
I wonder if the following side discussions about using nic.active(0) is a result of implementing the reset pin:
https://github.com/orgs/micropython/discussions/15294#discussioncomment-9795263
My experience with 1.20, which doesn't support W5500 reset pin, is that my W5500 reset pin is pulled up on the W5500 module. I was able to reboot ESP32 and reconnecting to Ethernet every time ESP32 rebooted. I wonder if this stability despite not using the reset pin was due to the driver issuing a software reset command to W5500 via SPI upon initialization. Now that the new MP version .23 is implementing W5500 reset pin, If I update my MP to .23, I wonder if I must issue nic.active(0) after each ESP32 soft reset. It sounds counter-intuitive.
Beta Was this translation helpful? Give feedback.
All reactions