WT32-ETH01

Message

Rub87 · #51 Post by **Rub87** » 30 Jan 2021, 13:51

How can i attempt to resolve that?

TD-er · #52 Post by **TD-er** » 30 Jan 2021, 14:53

Not sure, I have to look into the code for this.

Rub87 · #53 Post by **Rub87** » 31 Jan 2021, 23:06

Code: Select all

217 : Info   : Connect to:
217 : Info   : Ethernet
218 : Info   : Eth Wifi mode: Ethernet ETH: PHY Typee: LAN8710 PHYAddr: 0 Eth Clock mode: External crystal oscillator MDC Pin: 16 MIO Pin: 17 Power Pin: -1
222 : Info   : ETH Started
4223 : Info   : ETH Connected
4224 : Info   : firstLoopConnectionsEstablished
7230 : Info   : ETH MAC: A4:CF:12:64:B3:8F IPv4: 10.0.1.44 (ESP-Easy) GW: 10.0.1.1 SN: 255.255.255.0 FULL_DUPLEX 100Mbps

seems the clock mode has to be set to External osc...

TD-er · #54 Post by **TD-er** » 01 Feb 2021, 00:50

Ah, so it does have its own crystal oscillator?
Yep, then you should set it to have one external

Rub87 · #55 Post by **Rub87** » 01 Feb 2021, 08:13

Yep. Just spotted it also..

The new lan8720 i put on has quite different look then old one. It is more round off whereas the old was very edgy, alot like these bga memory chips. Wasnt easy to get it on with a paint removal gun

TD-er · #56 Post by **TD-er** » 01 Feb 2021, 12:43

Wow, you removed it using a paint removal gun?

The LAN8710A does have 32 pads, while the LAN8720A has only 24 (25 if you count the GND at the bottom)
Difference between both is that the LAN8720A only supports RMII and no longer the older 4 wire version.
But since we only use that one, it doesn't matter to us.

Rub87 · #57 Post by **Rub87** » 01 Feb 2021, 15:11

Weapon of choice

TD-er · #58 Post by **TD-er** » 01 Feb 2021, 15:20

Well I don't think I can do that with such a blower myself, so respect

Rub87 · #59 Post by **Rub87** » 03 Feb 2021, 11:57

Now could you aybe add the setting for the wESP32 in the code so there will also be a .bin which has directly the correct settings inside for other users that maybe also like the wESP32? despte its higher price its pretty well made thing with proper PoE power identification and galvnic isolation etc.

TD-er · #60 Post by **TD-er** » 03 Feb 2021, 13:44

Please show me the settings you now use and I will add them.

Rub87 · #61 Post by **Rub87** » 03 Feb 2021, 13:50

Code: Select all

 Eth Wifi mode: Ethernet ETH: PHY Typee: LAN8710 PHYAddr: 0 Eth Clock mode: External crystal oscillator MDC Pin: 16 MIO Pin: 17 Power Pin: -1

Smotek7 · #62 Post by **Smotek7** » 03 Feb 2021, 15:48

Hi,
is in the current release for ESP32 .bin which one can flasch to WT32-ETH1?
Or I need to create my own for WT32.

TD-er · #63 Post by **TD-er** » 03 Feb 2021, 16:36

You can flash any esp32 eth build as long as your board uses LAN8710A or LAN8720A (or the tk<somewhat> board which I forgot the name)

Only thing is, you may need to configure the eth yourself by hand as we don't have a predefined "factory default" setting for it yet.

Smotek7 · #64 Post by **Smotek7** » 03 Feb 2021, 22:24

Everything works.
To summarize:
Board WT32-ETH01
USB to RS232 converter
IO0 to GND
Flash: ESP_Easy_mega_20210114_normal_ESP32_4M316k_ETH-factory.bin
Connect to wifi and setting lan.

: lan set.JPG (53.86 KiB) Viewed 96273 times

Disconnect IO0
Restart and the module will connect to the lan.

enesbcs · #65 Post by **enesbcs** » 03 Feb 2021, 22:43

Smotek7 wrote: ↑03 Feb 2021, 22:24 Flash: ESP_Easy_mega_20210114_normal_ESP32_4M316k_ETH-factory.bin
Connect to wifi and setting lan.
lan set.JPG

Yes, i can confirm.

viewtopic.php?p=49536#p49536

iron · #66 Post by **iron** » 04 Feb 2021, 20:09

@TD-er perhaps it is safe to assume it is time to set a predefined setting for this ?

hamster · #67 Post by **hamster** » 04 Feb 2021, 21:38

I created a nice enclosure for the WT32-ETH01 + Relays
see thingiverse.. https://www.thingiverse.com/thing:4750234

TD-er · #68 Post by **TD-er** » 04 Feb 2021, 22:35

iron wrote: ↑04 Feb 2021, 20:09 @TD-er perhaps it is safe to assume it is time to set a predefined setting for this ?

Yep.
Can you make an issue on Github for it, as these things on the forum as next to impossible to find back later when I'm at a computer I can actually code and compile on and the forum doesn't have a mark unread....

TD-er · #69 Post by **TD-er** » 04 Feb 2021, 22:36

hamster wrote: ↑04 Feb 2021, 21:38 I created a nice enclosure for the WT32-ETH01 + Relays
see thingiverse.. https://www.thingiverse.com/thing:4750234

Nice enclosure!

Cdzn · #70 Post by **Cdzn** » 22 Nov 2021, 08:35

Is there any chance to start lan8720 on esp 32 DevKit V1? I have no GPIO-0!

Ath · #71 Post by **Ath** » 22 Nov 2021, 08:43

You should be able to use another unused GPIO pin instead of GPIO0, the configuration for the LAN interface on the _ETH builds is quite flexible.
Might be better to avoid the (few) input-only pins, I assume, those can be used for switches etc.

TD-er · #72 Post by **TD-er** » 22 Nov 2021, 09:03

GPIO-0 is sadly the only one to use when your LAN board has an external crystal, like those boards sold on Ali Express.

But, there is hope, as I am also using those on my board designs

There are 2 ways you can make this work:
- Wire a GPIO pin to the enable pin of the crystal (probably need a transistor to make sure it remains low at boot)
- Add one of those "analog switch" chips to toggle between the LAN clock and "normal GPIO-0" mode.

I implemented the latter as it seemed to be easier for me, when designing my own boards. But those chips are quite small so no way to implement it on a breadboard.
See part of my schematics below.
The 2x7 pins pinheader is wired for those boards from Ali.
The NC pin on that header is here labelled for "OSC_EN" just in case I needed to go for option 1, but the analog switch performs fine.

On previous builds I used another chip, but those are out of stock at JLCPCB, so that's why I used this one.

Keep in mind that the clock signal is high frequency (25 or 50 MHz), so keep it as short as possible.
The LAN chip may take quite a lot of current. 50 - 100 mA is not uncommon when enabled.

If your board doesn't have GPIO-0 output to a pin, you may want to look at the "boot" switch, as that one is connected to GPIO-0
But for an external eth board with crystal you must use GPIO-0.
Not sure what may happen if you just short the crystal output by pressing the button, so you may also remove the button and make it into a pin header. In case of emergency you can then disconnect the ETH clock signal and short the pins to enter flash mode (if the onboard transistors can't help you here)

Cdzn · #73 Post by **Cdzn** » 22 Nov 2021, 09:31

TD-er wrote: ↑22 Nov 2021, 09:03 GPIO-0 is sadly the only one to use when your LAN board has an external crystal, like those boards sold on Ali Express.

But, there is hope, as I am also using those on my board designs

There are 2 ways you can make this work:
- Wire a GPIO pin to the enable pin of the crystal (probably need a transistor to make sure it remains low at boot)
- Add one of those "analog switch" chips to toggle between the LAN clock and "normal GPIO-0" mode.

I implemented the latter as it seemed to be easier for me, when designing my own boards. But those chips are quite small so no way to implement it on a breadboard.
See part of my schematics below.
The 2x7 pins pinheader is wired for those boards from Ali.
The NC pin on that header is here labelled for "OSC_EN" just in case I needed to go for option 1, but the analog switch performs fine.

On previous builds I used another chip, but those are out of stock at JLCPCB, so that's why I used this one.

Keep in mind that the clock signal is high frequency (25 or 50 MHz), so keep it as short as possible.
The LAN chip may take quite a lot of current. 50 - 100 mA is not uncommon when enabled.

If your board doesn't have GPIO-0 output to a pin, you may want to look at the "boot" switch, as that one is connected to GPIO-0
But for an external eth board with crystal you must use GPIO-0.
Not sure what may happen if you just short the crystal output by pressing the button, so you may also remove the button and make it into a pin header. In case of emergency you can then disconnect the ETH clock signal and short the pins to enter flash mode (if the onboard transistors can't help you here)

So many manipulation. Easy way is buy new esp32)
I found this solution but it works, i guess, only with custom firmware. can't figure out how starting it with my esp.

TD-er · #74 Post by **TD-er** » 22 Nov 2021, 09:44

What do you mean by only working with a custom build?

Which eth module do you use?
And what do you mean with "how starting it with my esp."
I assumed it was about the GPIO-0 being toggled at boot.

Another way is to let the ESP32 send the clock to the eth board, but that probably requires modification on the external eth board, if you're using the one I think you are using.

Cdzn · #75 Post by **Cdzn** » 22 Nov 2021, 09:57

TD-er wrote: ↑22 Nov 2021, 09:44 What do you mean by only working with a custom build?

Which eth module do you use?
And what do you mean with "how starting it with my esp."
I assumed it was about the GPIO-0 being toggled at boot.

Another way is to let the ESP32 send the clock to the eth board, but that probably requires modification on the external eth board, if you're using the one I think you are using.

Custom means firmware for arduino. i forget send link http://arduino.ru/forum/apparatnye-vopr ... -devkit-v1
I using lan8720
starting means how can i get this works with esp32.
Td-er please read the link above, maybe You can find out how get this work together.

TD-er · #76 Post by **TD-er** » 22 Nov 2021, 10:17

If Google translate didn't mess up, then I think this is almost exactly what I described:

Either disable the crystal during boot by connecting the OSC_EN pin with the eth power pin (which can be configured in ESPEasy)
Only you have to probably invert the signal, hence my remark for the transistor.

The other idea they mention, so you don't need to use the clock on GPIO-0 is to use it on GPIO-17 (which is one of the options in ESPEasy if I'm not mistaken) but then you need to keep the OSC_EN pin pulled down.

Just make sure all other pins you need (see my schematic) are present on your board.
If GPIO-0 is missing, what other pins may be missing too?

Cdzn · #77 Post by **Cdzn** » 22 Nov 2021, 10:33

TD-er wrote: ↑22 Nov 2021, 10:17 If Google translate didn't mess up, then I think this is almost exactly what I described:

Either disable the crystal during boot by connecting the OSC_EN pin with the eth power pin (which can be configured in ESPEasy)
Only you have to probably invert the signal, hence my remark for the transistor.

The other idea they mention, so you don't need to use the clock on GPIO-0 is to use it on GPIO-17 (which is one of the options in ESPEasy if I'm not mistaken) but then you need to keep the OSC_EN pin pulled down.

Just make sure all other pins you need (see my schematic) are present on your board.
If GPIO-0 is missing, what other pins may be missing too?

I have all pins needed except GPIO-0. I tryed his wiring but don`t get success.
in second case GPIO-17 i should connect to nINT/RETCLK (lan 8270). NC no need connection so it`s empty.
help with my screenshot please.

: 2021-11-22 163212.jpg (207.96 KiB) Viewed 91615 times

Ath · #78 Post by **Ath** » 22 Nov 2021, 10:37

Ah, another reason to avoid those 30 pin ESP32-Devkit1 boards, they lack some GPIOs being made available externally

and especially GPIO0 can be nice to have available...

When using the, rather good available, actual WT32-ETH1 board, this shouldn't be an issue, AFAICS.

Ath · #79 Post by **Ath** » 22 Nov 2021, 10:38

Not sure how much difference it makes, but selecting the "Ethernet PHY type: LAN8720" could be of help?

Cdzn · #80 Post by **Cdzn** » 22 Nov 2021, 10:42

Ath wrote: ↑22 Nov 2021, 10:37 Ah, another reason to avoid those 30 pin ESP32-Devkit1 boards, they lack some GPIOs being made available externally and especially GPIO0 can be nice to have available...

When using the, rather good available, actual WT32-ETH1 board, this shouldn't be an issue, AFAICS.

Yep. Now i know.

TD-er · #81 Post by **TD-er** » 22 Nov 2021, 10:44

Pleae try with I2C address set to 1

Cdzn · #82 Post by **Cdzn** » 22 Nov 2021, 10:49

TD-er wrote: ↑22 Nov 2021, 10:44 Pleae try with I2C address set to 1

Lan blinking bot don`t get addresse.

is it right what i`m doing on screenshot?

: InkedWaveshare-LAN8720-modifications_LI.jpg (1.63 MiB) Viewed 91601 times

TD-er · #83 Post by **TD-er** » 22 Nov 2021, 11:05

You probably need to pull the enable pin down via a 4k7 resistor.
And how is the clock signal connected to the ESP?

Cdzn · #84 Post by **Cdzn** » 22 Nov 2021, 11:07

TD-er wrote: ↑22 Nov 2021, 11:05 You probably need to pull the enable pin down via a 4k7 resistor.
And how is the clock signal connected to the ESP?

Yep with 4k7 R.
nINT/RETCLK connected to GPIO-17.

TD-er · #85 Post by **TD-er** » 22 Nov 2021, 11:13

I don't know if the phase of the clock matters here.
GPIO-17 is the inverse signal of GPIO-16 (at least when it is set to be used as clock)
So you may also try GPIO-16.

Does the log suggest the ETH board is found?

Cdzn · #86 Post by **Cdzn** » 22 Nov 2021, 11:23

TD-er wrote: ↑22 Nov 2021, 11:13 I don't know if the phase of the clock matters here.
GPIO-17 is the inverse signal of GPIO-16 (at least when it is set to be used as clock)
So you may also try GPIO-16.

Does the log suggest the ETH board is found?

FOund something
AP Mode: Client connected:Connected devices: 1
213841: UNKNOWN WIFI/ETH EVENT: 18
216695: WD : Uptime 4 ConnectFailures 0 FreeMem 175572 WiFiStatus WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
216702: UNKNOWN WIFI/ETH EVENT: 18

TD-er · #87 Post by **TD-er** » 22 Nov 2021, 11:28

The summary like "ETH PHY Type: " should even be printed before it attempts to initialize the eth module.
Make sure it is still set to use Ethernet and not WiFi.

Smotek7 · #88 Post by **Smotek7** » 22 Nov 2021, 11:29

I did it about a year ago.
It worked, but I don't remember the settings.
Then I bought a WT32.

: LAN.JPG (31.3 KiB) Viewed 91572 times

TD-er · #89 Post by **TD-er** » 22 Nov 2021, 11:31

Cdzn wrote: ↑22 Nov 2021, 11:23
TD-er wrote: ↑22 Nov 2021, 11:13 I don't know if the phase of the clock matters here.
GPIO-17 is the inverse signal of GPIO-16 (at least when it is set to be used as clock)
So you may also try GPIO-16.

Does the log suggest the ETH board is found?
FOund something
AP Mode: Client connected:Connected devices: 1
213841: UNKNOWN WIFI/ETH EVENT: 18
216695: WD : Uptime 4 ConnectFailures 0 FreeMem 175572 WiFiStatus WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
216702: UNKNOWN WIFI/ETH EVENT: 18

What build are you running?
And especially what reported SDK version?

Cdzn · #90 Post by **Cdzn** » 22 Nov 2021, 11:32

TD-er wrote: ↑22 Nov 2021, 11:28 The summary like "ETH PHY Type: " should even be printed before it attempts to initialize the eth module.
Make sure it is still set to use Ethernet and not WiFi.

I guess it will not work properly. I`m done today. almost 8 hours i wasted for it . Thanks all.

Cdzn · #91 Post by **Cdzn** » 22 Nov 2021, 11:34

Smotek7 wrote: ↑22 Nov 2021, 11:29 I did it about a year ago.
It worked, but I don't remember the settings.
Then I bought a WT32.
LAN.JPG

Will try it later. Thank You. Need some rest.

Cdzn · #92 Post by **Cdzn** » 22 Nov 2021, 11:38

TD-er wrote: ↑22 Nov 2021, 11:31
Cdzn wrote: ↑22 Nov 2021, 11:23
TD-er wrote: ↑22 Nov 2021, 11:13 I don't know if the phase of the clock matters here.
GPIO-17 is the inverse signal of GPIO-16 (at least when it is set to be used as clock)
So you may also try GPIO-16.

Does the log suggest the ETH board is found?
FOund something
AP Mode: Client connected:Connected devices: 1
213841: UNKNOWN WIFI/ETH EVENT: 18
216695: WD : Uptime 4 ConnectFailures 0 FreeMem 175572 WiFiStatus WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
216702: UNKNOWN WIFI/ETH EVENT: 18
What build are you running?
And especially what reported SDK version?

: Безымянный.png (77.37 KiB) Viewed 91560 times

TD-er · #93 Post by **TD-er** » 22 Nov 2021, 11:39

If you have another of those modules, maybe you can (later) try it.
The LAN7820 is not as ESD resistant as I would have hoped.
I do have 2 boards here that show symptoms of ESD damage (or maybe bad solder joints?) which are not found anymore by the ESP, but the LED comes to life when you plugin in an ethernet cable.
So it is not entirely dead, but it is unusable.

DangerD · #94 Post by **DangerD** » 04 Jan 2022, 01:29

Can you help me with uploading?

Code: Select all

Configuring upload protocol...
AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Auto-detected: COM8
Uploading .pio\build\esp32-wt32-eth01-ble-eth\firmware.bin
esptool.py v3.1
Serial port COM8
Connecting....
Chip is ESP32-D0WD (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 8c:ce:4e:94:89:b0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00170fff...
Compressed 17104 bytes to 11191...
Writing at 0x00001000... (100 %)
Wrote 17104 bytes (11191 compressed) at 0x00001000 in 0.4 seconds (effective 374.8 kbit/s)...
File  md5: c7cb2e45cc40c8b7cce87e020697828a
Flash md5: c0cd99e3e52010a71f140072d1617ce2
MD5 of 0xFF is 7ea35274918423fa507e1777596ea577

A fatal error occurred: MD5 of file does not match data in flash!

TD-er · #95 Post by **TD-er** » 04 Jan 2022, 12:35

Are you uploading the "factory" file (bin file with "factory" in the name) ?

DangerD · #96 Post by **DangerD** » 04 Jan 2022, 12:37

TD-er wrote: ↑04 Jan 2022, 12:35 Are you uploading the "factory" file (bin file with "factory" in the name) ?

I'm using Visual Studio Code (platformio)

TD-er · #97 Post by **TD-er** » 04 Jan 2022, 12:50

Hmm that doesn't look like the ESPEasy project.

So I have no idea if the file is even correct.
You can check it by uploading it to just any ESP32 board, to see if that will work, just to make sure it is a correct binary.

DangerD · #98 Post by **DangerD** » 04 Jan 2022, 12:56

TD-er wrote: ↑04 Jan 2022, 12:50 Hmm that doesn't look like the ESPEasy project.

So I have no idea if the file is even correct.
You can check it by uploading it to just any ESP32 board, to see if that will work, just to make sure it is a correct binary.

Sorry, that was openmqttgateway, but with ESPEasy same situation
ESP Easy flasher:

Code: Select all

[04.01.2022 14:11:23] trying to connect
[04.01.2022 14:11:23] 	flush start
[04.01.2022 14:11:23] 	setting serial port timeouts to 1 ms
[04.01.2022 14:11:23] 	setting serial port timeouts to 1000 ms
[04.01.2022 14:11:23] 	flush complete
[04.01.2022 14:11:23] 	espcomm_send_command: sending command header
[04.01.2022 14:11:23] 	espcomm_send_command: sending command payload
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] 	espcomm_send_command: receiving 4 bytes of data
[04.01.2022 14:11:23] Uploading 1711296 bytes from C:\Users\dangerd\Downloads\ESPEASY\bin\ESP_Easy_mega_20211224_normal_ESP32_4M316k_ETH.bin to flash at 0x00000000
[04.01.2022 14:11:23] 	erasing flash
[04.01.2022 14:11:23] 	size: 1a1cc0 address: 000000
[04.01.2022 14:11:23] 	first_sector_index: 0
[04.01.2022 14:11:23] 	total_sector_count: 418
[04.01.2022 14:11:23] 	head_sector_count: 16
[04.01.2022 14:11:23] 	adjusted_sector_count: 402
[04.01.2022 14:11:23] 	erase_size: 192000
[04.01.2022 14:11:23] 	espcomm_send_command: sending command header
[04.01.2022 14:11:23] 	espcomm_send_command: sending command payload
[04.01.2022 14:11:23] 	setting serial port timeouts to 16256 ms
[04.01.2022 14:11:23] 	read 0, requested 1
[04.01.2022 14:11:23] 	setting serial port timeouts to 1000 ms
[04.01.2022 14:11:23] warning: espcomm_send_command: didn't receive command response
[04.01.2022 14:11:23] warning: espcomm_send_command(FLASH_DOWNLOAD_BEGIN) failed
[04.01.2022 14:11:23] closing bootloader
[04.01.2022 14:11:23] 	flush start
[04.01.2022 14:11:23] 	setting serial port timeouts to 1 ms
[04.01.2022 14:11:23] 	setting serial port timeouts to 1000 ms
[04.01.2022 14:11:23] 	flush complete
[04.01.2022 14:11:23] error: espcomm_upload_mem failed
[2022-01-04 14:11:23] DONE! BUT WITH (1) ERRORS!
############################
[2022-01-04 14:11:23] The COM port was already in use... the post-flash did not complete.
[2022-01-04 14:11:23] JOB COMPLETED, over and out!

RX/TX connected to TX0/RX0, IO0 to GND and 3v3 to 3v3...

TD-er · #99 Post by **TD-er** » 04 Jan 2022, 13:14

Don't use the ESPEasy flasher (the blue/white Windows tool) with ESP32.
You can use the included Espressif download tool.

Also make sure to use a flasher which can handle enough current as the eth part does add 40 - 100 mA to the current consumption.

Ath · #100 Post by **Ath** » 04 Jan 2022, 14:06

If you get checksum errors, it may be that your AV is interfering with your build process. You may want to exclude the ESPEasy folder (and subfolders) from scanning by AV. And possibly processes like the flash tools.

Who is online