-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Hello. I'm new to microcontrollers and CircuitPython, but I think I may have found a bug in the reset logic here:
Adafruit_CircuitPython_Wiznet5k/adafruit_wiznet5k/adafruit_wiznet5k.py
Lines 167 to 172 in cd08178
| # reset wiznet module prior to initialization | |
| if reset: | |
| reset.value = True | |
| time.sleep(0.1) | |
| reset.value = False | |
| time.sleep(0.1) |
I'm using the W5100S-EVB-Pico, and have run the test code I found here without issue: #49 (comment)
I've also run some similar test code from WIZnet without issue: https://github.com/Wiznet/RP2040-HAT-CircuitPython/blob/master/examples/Network/W5x00_Ping_Test.py
What I noticed is that they differ in what pin they use for the reset line:
GP15: https://gist.github.com/anecdata/3c6f37c05a91f7b769dad7517bfe3aa1#file-code-py-L13
vs
According to the Getting Started guide, GP20 is the correct pin. However, changing the reset pin to GP20 in the gist example caused the module to fail to initialize:
code.py output:
Hard reset...
Init...
Traceback (most recent call last):
File "code.py", line 39, in
File "/lib/adafruit_wiznet5k/adafruit_wiznet5k.py", line 180, in init
AssertionError: Failed to initialize WIZnet module.
Looking closer at the WIZnet example, it succeeds using GP20 by not passing it into the module, thus skipping the reset block shown above. Both examples implement their own reset logic external to the module, and I assert that the only reason the GP15 example doesn't fail when it specifies the reset pin into the module, is because it happens to be the wrong pin.
I changed my local copy of adafruit_wiznet5k.py so that the reset logic works like the external reset in the gist example, False, wait 1 second, True, and now it still initializes when GP20 is specified.
I'm uncertain if this change would negatively effect other boards that are sharing this logic however, otherwise I would have provided a PR.