-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[BUG]WT32-ETH01 ethernet only on cold boot #4934
Comments
Can you also include the used settings (screenshot is good enough) of the Hardware tab where it shows the Ethernet config? And also which revision of this board you're using? (maybe a photo of the board where it shows any identifying info) |
I will start digging through my parts to see if I have a rev 1.2 here. Can you try to set GPIO-16 to pull-up on the same Hardware tab where other Ethernet settings are stored? I think I already have a clue to why this may fail, as GPIO-16 is being used for PSRAM when it is available. I think I will disable PSRAM support for ESP32 builds with Ethernet (or maybe add a separate build) as this is really unfortunate they used GPIO-16 for the power pin. Edit: |
doesn'1 make any difference |
I just made a build which should have PSRAM disabled As it is completely untested, please try on boards which are accessible to flash again via serial when things go wrong. |
thank you so much for your time - first automated reboot after flash was ok but manually reboot does not get an ip-adress from AVM Fritz!Box, if i disconnect power about 10 seconds is everything ok. |
So at least it does reboot fine now? Maybe you can already backup your settings file and check all checkboxes on the "Factory Reset" page and save those settings. I will make a build for you later this evening based on IDF5.1 to see if this fixes some stuff. |
Next few days im busy. On monday i will give a try on litte network with another AVM Frit!Box and only this testing unit, maybe there is some problem with dhcp on the avm router. thank you so much |
As far as I know, the only issues with AVM hardware is when using WiFi. And I also have lots of AVM stuff here, so I can test (as soon as I can find those boards, I recently saw them...) |
Build: ESP_Easy_mega_20231225_normal_ESP32_4M316k_LittleFS_ETH Dec 25 2023 Is it possible flashing LittleFS Firmware in Tools Update Firmware or only with USB-TTL-Adapter and NodeMC flasher? |
If you want to keep your current configuration, when the device uses SPIFFS (non-LittleFS binaries) then you'll have to backup your config using the Tools/Save button, then use OTA update (Update Firmware) to install the LittleFS build, then restore the |
ESP_Easy_mega_20240111_normal_ESP32_4M316k_ETH.factory.bin
13.858 : (241644) Info : : Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) INIT : Booting version: ESP_Easy_mega_20240111_normal_ESP32_4M316k_ETH, (Self built) bugfix/ESP32_factoryDefaults_a95ad3b (ESP32 SDK 4.4.6) |
now started again - wondering about wrong date / time 2036-02-07 ? ? ?
without NTP
|
that's really odd , unless you have setup a specific NTP server? |
Unit is not visible on other units with older firmware release (ESP_Easy_mega_20231013_normal_ESP32_4M316k_ETH Oct 13 2023), but on this unit you can see units having older firmware releases. Reverted al my units back to ESP_Easy_mega_20231130_normal_ESP32_4M316k_ETH Nov 30 2023 |
Did you have the UDP port set on the Tools->Advanced page? |
Yes, after upgrade checked the port an tested 8265 an then back to 8266 on this unit. |
That might be a bug in the p2p code which is already fixed in the latest code in the 'mega' branch. |
Build: ESP_Easy_mega_20240118_normal_ESP32_4M316k_ETH Jan 18 2024 p2p works and ntp works - Works in my condition as expected ;-)
|
Can you maybe also check this build as it is soon to be merged: But please only do this on units which are already on your desk so you can recover easily when it failed for whatever reason. N.B. please use a Custom LittleFS ETH build, which may also wipe your file system if you were using SPIFFS. |
ESP_Easy_mega_20240128_normal_ESP32_4M316k_ETH Jan 28 2024
ESP_Easy_mega_20240128_normal_ESP32_4M316k_LittleFS_ETH Jan 28 2024
|
And did you notice anything "new" when looking at the root page (or sysinfo page)? ;) |
Ah you used the "normal" build, then you won't see the new stuff on the root page or sysinfo page.... |
ESP_Easy_mega_20240128_collection_A_ESP32_4M316k_ETH Jan 28 2024 i can see mDNS but at my home network it is not reachable http://espeasy-t2.local/ this will work for me http://espeasy-t2 |
That was not what I meant... I meant the IPv6 I added. I will have a look at the mDNS why it is not working. No need to enable mDNS as it is a bit of an odd protocol and could be used to do malicious stuff, so if it is disabled, just leave it as is. |
WT32-ETH01 ethernet only on cold boot - reboot on tools Reboot connects to wifi
Used platform (please complete the following information):
Platform Specifics (when applicable, please complete the following information):
*** Soft Reboot ***
`
*** cold boot ***
`
The text was updated successfully, but these errors were encountered: