Espeasy compatible unit with wired ethernet?

Message

Teknor · #1 Post by **Teknor** » 05 Aug 2021, 23:29

Is there a espeasy compatible hw unit with wired ethernet connection, with RJ45 / LAN port? …like nodemcu but cable network instead of wifi?

TD-er · #2 Post by **TD-er** » 05 Aug 2021, 23:57

All boards made by Olimex are supported (unless they recently made a new one)
All boards which have a LAN8710A or LAN8720A
wESP32
Probably other boards too.

iron · #3 Post by **iron** » 06 Aug 2021, 09:33

WT32-ETH work well for me :

https://www.aliexpress.com/item/1005002023028892.html

-D

Teknor · #4 Post by **Teknor** » 06 Aug 2021, 14:22

iron wrote: ↑06 Aug 2021, 09:33 WT32-ETH work well for me :

https://www.aliexpress.com/item/1005002023028892.html

-D

Great. Thanks. Orderen two of those. Which .bin file do you use to flash the unit?

Ath · #5 Post by **Ath** » 06 Aug 2021, 14:26

There are several that have the '_ETH' marker in the bin name, these have the (wired) Ethernet options enabled.

Teknor · #6 Post by **Teknor** » 12 Aug 2021, 10:34

Ath wrote: ↑06 Aug 2021, 14:26 There are several that have the '_ETH' marker in the bin name, these have the (wired) Ethernet options enabled.

Super. Thanks, will have a look at the relevant .bins when the board arrives. I have a usb to serial adapter to flash the board, is there also a trick to set the board in flash mode or can I simply connect the serial adapter and use the flash tool like I do with nodeMCU?

Ath · #7 Post by **Ath** » 12 Aug 2021, 10:45

Depending on the board, the flash mode needs to be manually set or not.
My experience with ESP32 boards with a micro-usb connector (almost always having an on-board serial adapter) is that those that have both 'en' and ' boot' buttons, need to be set manually into flash-mode, by holding the 'boot' button, and pressing the 'en' button shortly, when the flasher is searching for the board.
The boards that only have an 'en' (or 'reset') button will go into flash-mode automatically, just like the NodeMCU and Wemos D1 Mini boards.

TD-er · #8 Post by **TD-er** » 12 Aug 2021, 11:03

And just a tip.
If you flashed ESPEasy with ETH support, please go to the factory reset page, select a pre-selected board definition and perform a factory reset.
This will configure the settings like preferred pins for I2C and the configuration for ethernet.

I will (soon) also move this pre-defined selection to the Hardware tab of the web UI to make configuring ethernet a bit more practical without the need to perform a factory reset.
You can of course set all parameters by yourself, but that's quite a lot to setup.
So if the board you ordered is in the pre-defined list, it will make setup a lot easier for you.

Teknor · #9 Post by **Teknor** » 12 Aug 2021, 13:10

Thanks for your detailed answer @TD-er - well worth a donation.

'coffee'

https://Ko-fi.com/home/coffeeshop?txid= ... ghtsomeone

TD-er · #10 Post by **TD-er** » 12 Aug 2021, 13:28

You're welcome

Have fun with it.
Ethernet is a great addition to ESPEasy and it makes the unit incredible responsive.
I've got some units running ethernet and those are running very stable.

You may need to realize that the ethernet module will add roughly 100 mA to the power consumption of a normal board, so it isn't the best option for running on battery.

Teknor · #11 Post by **Teknor** » 19 Aug 2021, 20:01

Received the WT32-ETH board and trying to flash it with ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH.bin

The RX/TX is crossed in the wiring.

The board does not have any buttons.

I have tried various ways to set the board in flash mode, but guess I dont succeed and this is the most likely error source? See attaced log.

Tried to boot with wire from GND to IO0 and flash
Tried to boot with wire from GND to IO0, disconnect GND/IO0 and then flash
...and a few more variations.

No luck.

Something I am missing here?

Code: Select all

######2021-08-19######
#######0.04.007#######
######FLASH INFO######
BIN file: ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH.bin
COM port: (COM3) Silicon Labs CP210x USB to UART Bridge (Port_#0003.Hub_#0001)
Baud rate: 115200
! FORCED DOUT ENABLED !
######POST FLASH######
No post flash information entered...
######FLASH LOG######
[esptool.exe -vv -bm dout -cd nodemcu -cb 115200 -cp COM3 -ca 0x00000 -cf "C:\Users\Downloads\ESPEasy_ESP32_mega-20210802\bin\ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH.bin"]
[19.08.2021 19:46:55] esptool v0.4.12 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
[19.08.2021 19:46:55] setting flash mode from qio to dout
[19.08.2021 19:46:55] 	setting board to nodemcu
[19.08.2021 19:46:55] 	setting baudrate from 115200 to 115200
[19.08.2021 19:46:55] 	setting port from  to COM3
[19.08.2021 19:46:55] 	setting address from 0x00000000 to 0x00000000
[19.08.2021 19:46:55] 	espcomm_upload_file
[19.08.2021 19:46:55] 	espcomm_upload_mem
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] opening bootloader
[19.08.2021 19:46:55] resetting board
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] resetting board
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] resetting board
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] trying to connect
[19.08.2021 19:46:55] 	flush start
[19.08.2021 19:46:55] 	setting serial port timeouts to 1 ms
[19.08.2021 19:46:55] 	setting serial port timeouts to 1000 ms
[19.08.2021 19:46:55] 	flush complete
[19.08.2021 19:46:55] 	espcomm_send_command: sending command header
[19.08.2021 19:46:55] 	espcomm_send_command: sending command payload
[19.08.2021 19:46:55] 	read 0, requested 1
[19.08.2021 19:46:55] warning: espcomm_sync failed
[19.08.2021 19:46:55] error: espcomm_open failed
[19.08.2021 19:46:55] error: espcomm_upload_mem failed
[2021-08-19 19:46:55] STOPPED due to 2 errors! (try reset on the unit, then start a new flash attempt)

Teknor · #12 Post by **Teknor** » 19 Aug 2021, 20:55

Trying the esptool on my MAC instead of the flashtool in Windows i get this log. Pretty sure I need to set the bord in flash mode to accept the incoming data stream...

Code: Select all

JTE@Js-MBP-2 ~ % esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 write_flash --flash_size=1MB -fm dout 0 ~/Downloads/ETH.bin
esptool.py v2.5.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting........_____....._____....._____....._____....._____....._____....._____

A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header
JTE@Js-MBP-2 ~ %

A common way to enter flash mode is to "hold flash / boot button and press reset and it will enter UPLOAD MODE" - however, this board does not have any buttons...

Ath · #13 Post by **Ath** » 19 Aug 2021, 21:22

That boot button is normally connected to GPIO-0. So if you connect that to GND while powering up the board (after a few seconds it can be released), it should go into flash-mode. (I received my first similar board today (no buttons, no USB), but didn't get to flashing it yet, so I'm in the same boat

)

Teknor · #14 Post by **Teknor** » 19 Aug 2021, 21:39

Ath wrote: ↑19 Aug 2021, 21:22 That boot button is normally connected to GPIO-0. So if you connect that to GND while powering up the board (after a few seconds it can be released), it should go into flash-mode. (I received my first similar board today (no buttons, no USB), but didn't get to flashing it yet, so I'm in the same boat )

At least it's great to share boat with you @Ath .
The RX/TX flashes rapidly for 10 secs or so when not trying to set in into flash mode and then I get the error. After trying GND/GPIO0 and then flash only one of the leds hardly flashes, so at least something is happening.

Ath · #15 Post by **Ath** » 19 Aug 2021, 21:47

Teknor wrote: ↑19 Aug 2021, 21:39 After trying GND/GPIO0 and then flash only one of the leds hardly flashes, so at least something is happening.

The rapidly flashing led is the ESP-rx, the ESP-tx sends a confirmation every block of data, so that does sound right

TD-er · #16 Post by **TD-er** » 19 Aug 2021, 21:49

Please be aware that the ethernet chip, if it is enabled, may take another 100 - 200 mA extra.
So double check the voltage is constant at where you supply it to the board.

I don't know how it is wired on that board, nor what the existing firmware may do before you flashed ESPEasy to it, so it is very well possible the LAN chip is enabled and powered and thus drawing quite a bit more current than a normal board would do.

Teknor · #17 Post by **Teknor** » 19 Aug 2021, 21:58

I have tried to wire

Code: Select all

USB   --  WT32
5v   <--> 5v
and
3.3v <--> 3.3v

...with same results.

Teknor · #18 Post by **Teknor** » 19 Aug 2021, 22:51

Reset-pin continously connected to GND and using esptool:

Code: Select all

JTE@Js-MBP-2 ~ % esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 write_flash --flash_size=1MB -fm dout 0 ~/Downloads/factory.bin
esptool.py v2.5.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting.......
Detecting chip type... ESP32
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 7c:87:ce:44:ba:00
Uploading stub...
Running stub...
Stub running...
Configuring flash size...

A fatal error occurred: File /Users/JTE/Downloads/factory.bin (length 1741392) at offset 0 will not fit in 1048576 bytes of flash. Use --flash-size argument, or change flashing address.

I hope my several tries have corrupted the memory, or perhaps the .bin file is too large? Cannot find a smaller one on the mega-pack.

Teknor · #19 Post by **Teknor** » 19 Aug 2021, 23:05

Might have solved it:

Code: Select all

JTE@Js-MBP-2 ~ % esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 write_flash --flash_size=4MB -fm dout 0 ~/Downloads/factory.bin
esptool.py v2.5.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting....
Detecting chip type... ESP32
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 7c:87:ce:44:ba:00
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Compressed 1741392 bytes to 972336...
Wrote 1741392 bytes (972336 compressed) at 0x00000000 in 86.0 seconds (effective 162.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Edit 1: Flashing seems to work now!
GPIO0 and GND connected all the time and changed flash_size to 4mb in the terminal command.

TD-er wrote: ↑12 Aug 2021, 11:03 And just a tip.
If you flashed ESPEasy with ETH support, please go to the factory reset page, select a pre-selected board definition and perform a factory reset.
This will configure the settings like preferred pins for I2C and the configuration for ethernet.

I will (soon) also move this pre-defined selection to the Hardware tab of the web UI to make configuring ethernet a bit more practical without the need to perform a factory reset.
You can of course set all parameters by yourself, but that's quite a lot to setup.
So if the board you ordered is in the pre-defined list, it will make setup a lot easier for you.

Edit 2: Board selection
In the Factory reset drop-down menu, there are no boards in the list to chose from. Only "Default" is available (using the esp32.normal.eth.factory.bin)

Edit 3: No signs of wired LAN connection.
No menu item or configuration of this as far as I can see. Was hoping to find somewhere to activate the LAN functionality. Wlan and web interface as such for the esp32 looks and works perfect and is very similar to the esp8266 version.

I appreciate guidance here

iron · #20 Post by **iron** » 20 Aug 2021, 11:18

Teknor wrote: ↑19 Aug 2021, 20:01 Received the WT32-ETH board and trying to flash it with ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH.bin

Keep in mind for initial flashing you need to use the -factory.bin version of the file

So in this case you need the :

ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH-factory.bin

-D

Teknor · #21 Post by **Teknor** » 20 Aug 2021, 12:54

Hi Iron,
Yes, tried both. And the Factory version flashed correctly. Still in search for what is nxt step

Ath · #22 Post by **Ath** » 20 Aug 2021, 13:33

If it is starting correctly there should be a WiFi AP called 'ESPEasy', that you can connect to using the password configesp (not really secret). When connected, you will be presented a list of WiFi AP's where you can then enter credentials to have the unit connect to your WiFi, get an IP address, that is then the way you can access and configure it from a webbrowser (I prefer to use a laptop, but others do that from their phone or tablet).

Teknor · #23 Post by **Teknor** » 20 Aug 2021, 13:45

Thanks Ath,
For sure quite familiar with the web interface of esp_easy and how it works with wifi. I have a few nodes up and running stable since 2018

However, i see no signs of wired ethernet config menu items and it doesnt seem to be plug and play. The board connects perfectly to my wlan now.

Will next step be to enter web config mode and forget the wlan setup and pray for an established eth connection after putting in the wired lan cable?

Ath · #24 Post by **Ath** » 20 Aug 2021, 14:56

No, you will have to setup the Ethernet connections first, there is no hardware auto-detect. It should be available on the Hardware page: https://espeasy.readthedocs.io/en/lates ... dware.html, if not you probably didn't flash an '_ETH' build...

Teknor · #25 Post by **Teknor** » 20 Aug 2021, 18:38

Thanks Ath, you were of course perfectly right. I used the .bin with Factory only.

New try now with the correct .bin file.

Code: Select all

JTE@Joakims-MBP-2 ~ % esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 write_flash --flash_size=4MB -fm dout 0 ~/Downloads/ESP_Easy_mega_20210802_normal_ESP32_4M316k_ETH-factory.bin
esptool.py v2.5.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting....
Detecting chip type... ESP32
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 7c:87:ce:44:ba:00
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Compressed 1767088 bytes to 985370...
Wrote 1767088 bytes (985370 compressed) at 0x00000000 in 87.2 seconds (effective 162.2 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

iron · #26 Post by **iron** » 20 Aug 2021, 18:40

This is my ETH conf for this board

Teknor · #27 Post by **Teknor** » 20 Aug 2021, 18:48

Thanks, this is the default setup after having done a factory reset with the board WT32-ETH. I see power pin varies between the two configurations. Will try both.

: sc.png (135.9 KiB) Viewed 48854 times

Update: When selecting GPIO16 for the power pin and clicking submit, something overrides it and sets it back to GPIO12 after reboot.

Teknor · #28 Post by **Teknor** » 21 Aug 2021, 01:12

Works like a charm.

Thanks for all support, tips and tricks.

: 2021-08-21 kl. 01.09.06.png (176.55 KiB) Viewed 48834 times

iron · #29 Post by **iron** » 24 Aug 2021, 09:44

So what Power pin works for you 16 or 12 ?

Teknor · #30 Post by **Teknor** » 24 Aug 2021, 11:29

iron wrote: ↑24 Aug 2021, 09:44 So what Power pin works for you 16 or 12 ?

16 works (pin 12 was standard config for the board and did not work).

iron · #31 Post by **iron** » 24 Aug 2021, 18:45

@Ath pergaps we shouls update the default config to gpio 16 for power ?

TD-er · #32 Post by **TD-er** » 24 Aug 2021, 19:09

iron wrote: ↑24 Aug 2021, 18:45 @Ath pergaps we shouls update the default config to gpio 16 for power ?

Or double check with the original design to see if there are perhaps 2 boards with the same name. Or maybe different revisions of the board.

Teknor · #33 Post by **Teknor** » 24 Aug 2021, 22:50

Version 1.2 is printed on my board

iron · #34 Post by **iron** » 25 Aug 2021, 21:21

TD-er wrote: ↑24 Aug 2021, 19:09
iron wrote: ↑24 Aug 2021, 18:45 @Ath pergaps we shouls update the default config to gpio 16 for power ?
Or double check with the original design to see if there are perhaps 2 boards with the same name. Or maybe different revisions of the board.

My ESP32_WT32-ETH boards are several months old and I used the GPIO settings from the documentation provided at Tasmota from much longer ago, so I can say if that GPIO is fixed on that device.

My Olimex ESP32_ETH boards use GPIO 12 for power so there is a good chance that information got carried over to the ESP32_WT32-ETH configuration accidentally ?

TD-er · #35 Post by **TD-er** » 25 Aug 2021, 21:39

iron wrote: ↑25 Aug 2021, 21:21 [...]

My Olimex ESP32_ETH boards use GPIO 12 for power so there is a good chance that information got carried over to the ESP32_WT32-ETH configuration accidentally ?

Nah.... that would suggest I do copy/paste coding...

Will have a look at it.
So the default for WT32-ETH it should be GPIO 16 instead of 12?

TD-er · #36 Post by **TD-er** » 25 Aug 2021, 23:01

I looked through the documents for the seeedstudio module and I can't find what pin is used for the pwr pin of the ETH module.
So I find it a bit difficult to conclude if there is "Only one" version of the WT32-ETH module regarding pin configuration.

iron · #37 Post by **iron** » 26 Aug 2021, 12:07

TD-er wrote: ↑25 Aug 2021, 23:01 I looked through the documents for the seeedstudio module and I can't find what pin is used for the pwr pin of the ETH module.
So I find it a bit difficult to conclude if there is "Only one" version of the WT32-ETH module regarding pin configuration.

Can you point to any reference that shows pin 12 for power pin on WT32-ETH module ? Everything I find, even "older" posts point to pin 16

TD-er · #38 Post by **TD-er** » 26 Aug 2021, 12:43

Well I can only point to the source code

And since that was likely changed quite a while ago, where only now it appears to be incorrect, makes me think that there might be 2 versions of it.
Otherwise I would expect people would have noticed it sooner.

Teknor · #39 Post by **Teknor** » 25 Sep 2021, 17:55

Does anybody know which pins are safe to use for a 4x relay board? Limited documentation on the www as far as I have found.

I've found out that IO2 and IO12 work fine. Because I'm afraid to fry the unit with trial and error, I would very much like to have some help here. Which other two pins can safely be used?

I cannot see that the following pins work:
IO0
IO39 (this shuts down the board)
IO14
IO35
IO4

I use the following command to control the pin: http://192.168.1.105/control?cmd=GPIO,12,0 / http://192.168.1.105/control?cmd=GPIO,12,1

Edit: I might have corrupted the board trying to control pin39........

: esp.jpg (278.1 KiB) Viewed 47214 times

Ath · #40 Post by **Ath** » 25 Sep 2021, 18:49

GPIO pins 34, 35, 36 and 39 are input-only. But setting it as an output should not damage the hardware, it should just do nothing.

The details for use of other pins can be found here: https://randomnerdtutorials.com/esp32-p ... nce-gpios/

You can also use RX and TX pins as input/output, just disable the serial log. Be aware that some data will be sent through the serial port at boot, before it can be turned off. That may activate a relay when connected.

TD-er · #41 Post by **TD-er** » 25 Sep 2021, 20:08

On the more recent builds, it is shown when pins are used by ethernet.
So you cannot select them, and/or get a warning symbol with the reason next to it.
This is shown in any combo box where you can select a GPIO pin.

Teknor · #42 Post by **Teknor** » 26 Sep 2021, 15:24

Hmmm. The lights at the btm of the LAN port are gone and there is no connectivity. I think it happened after trying to set pin 39 high. Is there a way to reset this, or perhaps the only solution is to try to reflash?

TD-er · #43 Post by **TD-er** » 26 Sep 2021, 21:07

Pin 39 is input-only, so you cannot set it high.
See the link Ton posted and also: https://espeasy.readthedocs.io/en/lates ... e-on-esp32

You have to watch out for switching the wrong pins when using Ethernet. It is very easy to destroy the LAN8720 chip.
That's why I added those labels in the web UI.

When unsure, you can perform a factory reset, which also gives you the opportunity to select the predefined config for that board (on the factory reset page), which may help you to get the pins configured with less effort.

Teknor · #44 Post by **Teknor** » 26 Sep 2021, 22:18

Thanks TD-er. I might have destroyed the LAN8720 chip then.. Is it possible to do a factory reset without getting access to the web UI?

TD-er · #45 Post by **TD-er** » 26 Sep 2021, 22:59

You can also enter WiFi credentials via serial (as long as you have not disabled serial in the advanced settings)

Code: Select all

wifissid,YourWiFiSSID
wifikey,YourTopSecretWiFiPassword
save

Teknor · #46 Post by **Teknor** » 27 Sep 2021, 21:45

And the story continues...

hope this update is not interpreted as spam

Did a reflash of the unit with ETH_factory.bin and the unit is back on track. It remembered all the configuration I had done, the ETH settings etc --> just plug and play.

Will be more cautious when playing with the GPIO pins from now on. If somebody has a mapping table between the esp pin documentation linked earlier in this thread with the WT32-ETH01 pins it would be very helpful.

Teknor · #47 Post by **Teknor** » 08 Oct 2021, 12:27

These GPIO pins are now controlling the relays:

: Skjermbilde 2021-10-08 kl. 12.27.07.png (516 KiB) Viewed 46259 times

angelo67 · #48 Post by **angelo67** » 27 Nov 2021, 14:01

Hi,
what program do you use to program..... ESP.Easy.Flasher ?
Alternatively, i can be used the CP210x programmer ?

Ath · #49 Post by **Ath** » 27 Nov 2021, 14:08

If the ESPEasy provided flasher can't recognize your USB-Serial adapter, it is advised to use the official Espressif flash tool from: https://www.espressif.com/en/support/do ... ther-tools

seersucker · #50 Post by **seersucker** » 26 Dec 2021, 02:44

fwiw I just got one of these working using the expressif flash download tool. Then did the update from the Tools/Update Firmware page. I had flashed using an offset of 0x1000 which is wrong for a factory image, the offset should be 0x0000.

(Removed a possibly misleading pic showing the flash tool image with an offset)

Who is online