Wiznet W5500. Teensy 4.0 pin connection
- Thread starter Balam
- Start date
joepasquariello
Well-known member
See the PJRC page below for some clues. This is for a module, not direct to the 5500 chip, but may be helpful.
https://www.pjrc.com/store/wiz820_sd_adaptor.html
thanks for the info. very useful ! I been reading more about the problem and here is a short article from a blogger that describes the problems and solutions.
I ordered 2 modules from wiznet ( the one that I been using its not the authentic wiznet module ) once they arrive I will give it a try
https://bigdanzblog.wordpress.com/2015/09/26/wiring-wiz820io-ethernet-module-to-teensy-3-1-or-3-2/
maybe spam?
BriComp
Well-known member
PaulStoffregen
Well-known member
Whether the RESET signal on W5500 is truly needed is indeed a good question. The WIZ820+SD adaptor was designed & tested before W5500 existed. The older W5200 chip absolutely did require RESET. It was even sometimes drive its MISO pin at startup if RESET was just connected to 3.3V.
I can tell you I did get W5500 to work with RESET just tied to 3.3V. But whether that is 100% reliable, I do not know.
I can tell you I did get W5500 to work with RESET just tied to 3.3V. But whether that is 100% reliable, I do not know.
I been testing the https://www.wiznet.io/product-item/wiz550io/
with webserver sample from ethernet library
after upload it works and ramdomly works after replug to power.
I a not using the reset code - with this test, even the reset code does not help
any advice?
with webserver sample from ethernet library
after upload it works and ramdomly works after replug to power.
I a not using the reset code - with this test, even the reset code does not help
any advice?
thanks, I found online a Ethernet3 library that seems to make the wiznet module work reliable! ( need more testing ). this library has a reset pin function.
https://github.com/sstaub/Ethernet3
https://github.com/sstaub/Ethernet3
This Ethernet3 library may be just the thing I need. I am currently using pin9 on a T4.0 for pwm and it cannot be changed as it is hardwired on a pcb. The function to allow changing the RST pin for the wiznet module should get me out of this conflict. Will try it out and let forum know.
PaulStoffregen
Well-known member
Why not simply use digitalWrite() before you call Ethernet.begin() ?
PaulStoffregen
Well-known member
Looks like this library just uses digitalWrite() and delay().
https://github.com/sstaub/Ethernet3...9e48bb909a08c54aeb0439e/src/Ethernet3.cpp#L35
https://github.com/sstaub/Ethernet3...9e48bb909a08c54aeb0439e/src/Ethernet3.cpp#L35
Code:
void EthernetClass::hardreset() {
if(_pinRST != 0) {
digitalWrite(_pinRST, LOW);
delay(1);
digitalWrite(_pinRST, HIGH);
delay(150);
}
}PaulStoffregen
Well-known member
I am not aware of any Teensy 4 specific bugs. We did have a bug some time ago impacting only the W5100 chip, where Teensy 4 was too fast. Adding a 10ns delay fixed it.
https://github.com/PaulStoffregen/Ethernet/commit/525279c940989c363b1b7031657bf2799642910d
It's theoretically possible we could have unknown bugs. But many people have used W5500 with Teensy 4. I have personally used the WebClient example many times.
However, almost all testing has been done with the plain W5500 modules, which look like this:
I believe that module you're using may have a PIC microcontroller which takes control of the W5500 chip to do certain initialization. Maybe it's interfering?
I also purchase this module from wiznet, I have not tested yet. I had originally purchase a reproduction from amazon and I had a very bad connectivity with that module. I personally prefer the one that has the Mac address, I am using this hardware to handle a interactive light sculpture that I am currently working.
PaulStoffregen
Well-known member
The standard ethernet library will not make use of the mac address supplied by the PIC chip on that board.