-
Notifications
You must be signed in to change notification settings - Fork 48
Ethernet.begin() does not return under certian circumstances #4
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
Issue reproduced. This is under investigation. |
Hi all, |
Gave it a quick try: Looks like it changes the behavior in the way, that now calling Ethernet.begin() a second time, after the first try failed, always locks the program inside the function, no matter if ethernet is still unavailable or not. |
Confirmed, issue is fixed. |
Thanks guy. |
I'm having the same problem with my Arduino UNO and ethernet shield. How exactly do I fix the problem when it hangs? Examples of hanging:
It works fine when:
|
This library is designed for STM32 boards with native Ethernet. |
In the past, with the Arduino-Ethernet-Shield, I used the following code to wait for ethernet connection to get available, so that I can have at least some limited functionality when ethernet is not available at this time, and automatically jump to full functionality as soon as link gets available.
With the Nucleo 429ZI this does not work. As long as the cable is unplugged everthing is fine, but as soon as it is plugged in and ethernet gets available, the program gets locked inside the Ethernet.begin() function and never returns.
Am I misusing the function and it worked just coincidentally with the standard ethernet-shield, or is this a bug?
If this usage of the begin() function is not intended, is there another way to achieve that the board tries reconnecting itself?
The text was updated successfully, but these errors were encountered: