-
Notifications
You must be signed in to change notification settings - Fork 189
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
esp-dev-kits/examples/esp32-s3-lcd-ev-board/examples /smart_panel/ fail with ESP-IDF v5.4 (AEGHB-987) #122
Comments
See also #123. I have a workaround that allows for boot, but I don't know if that's an intelligent fix or nonsensical. |
I commented out this line And it worked. The wifi seems to work too, |
If you unplug the board (power it down), then try again, does it work? Curious how the wifi works without that call, but maybe it's a duplicate that's also done elsewhere... |
Yes, No issues. Wifi evenconnected to the access point on its own |
Thank you. |
There appears to be no incentive to upgrade to a new version of ESP-IDF. Its only met with problems. And there is so much code and so many layers, it crushing to go through it all. I have a LVGL project, and its a mess.... with v5.4 it does not run. |
Thanks for the heads-up. I see the releases come out in an interesting order. |
Answers checklist.
IDF version.
v5.4
Espressif SoC revision.
1
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S3_LCD_EV_BOARD v1.1
Power Supply used.
USB
What is the expected behavior?
Update ESP-IDF to version v5.4.
Smart_Panel example Compiles, flashes, but fails to run
On the readme page for the smart_panel example, it states:
wifi Configuration
ESP_WIFI_SSID: The name of default Wi-Fi AP.
ESP_WIFI_PASSWORD: The password of default Wi-Fi AP.
They are no longer in menuconfig
What is the actual behavior?
The boot screen appears, then it reboots over and over.
Steps to reproduce.
...
Debug Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered: