Skip to content
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

Fix Ethernet builds with V4 #4502

Open
1 task done
netmindz opened this issue Jan 18, 2025 · 3 comments
Open
1 task done

Fix Ethernet builds with V4 #4502

netmindz opened this issue Jan 18, 2025 · 3 comments
Labels

Comments

@netmindz
Copy link
Collaborator

What happened?

No target

To Reproduce Bug

Add env

Expected Behavior

Working ethernet

Install Method

Self-Compiled

What version of WLED?

0.16.0.dev

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@netmindz netmindz added the bug label Jan 18, 2025
@netmindz netmindz added this to the 0.16.0 candidate milestone Jan 18, 2025
@netmindz
Copy link
Collaborator Author

ethfreeze.txt

@kilrah
Copy link
Contributor

kilrah commented Jan 27, 2025

I tried uncommenting the DISABLE_ESPNOW, doesn't help

env:

[env:esp32_eth_V4]
board = esp32-poe
platform = ${esp32_idf_V4.platform}
build_unflags = ${common.build_unflags}
build_flags = ${common.build_flags} ${esp32_idf_V4.build_flags} -D WLED_RELEASE_NAME=\"ESP32_Ethernet\" -D RLYPIN=-1 -D WLED_USE_ETHERNET -D BTNPIN=-1
  -D WLED_DISABLE_ESPNOW ;; ESP-NOW requires wifi, may crash with ethernet only
  ${esp32.AR_build_flags}
lib_deps = ${esp32_idf_V4.lib_deps}
  ${esp32.AR_lib_deps}
board_build.partitions = ${esp32.default_partitions}
board_build.flash_mode = dio
upload_speed = 921600

Everything's fine until the ethernet type is selected, WT32-ETH01 in my case. Once done it'll hang whether a cable is connected or not and I have to wipe config to get it back.

@troyhacks
Copy link
Contributor

troyhacks commented Jan 28, 2025

@netmindz IDF v4.0.0 and up uses ARDUINO_EVENT_ instead of SYSTEM_EVENT_

This PR should fix it up...

#4526

Some crazy issues getting this to work which seem to be down to an older Tasmota version.

Use this Tasmota build which is based on IDF 4.4.6:

https://github.com/tasmota/platform-espressif32/releases/download/2023.10.04/platform-espressif32.zip

Do not use this build, which is based on IDF 4.4.4:

https://github.com/tasmota/platform-espressif32/releases/download/2023.06.02/platform-espressif32.zip

Tested with connecting and disconnecting Ethernet, boots correctly with Ethernet, fails back and forth successfully.

I had to add a secondary WiFi.disconnect(true); as it seems the WiFi events aren't reliable on bootup or something else is overriding connectivity things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants