-
Notifications
You must be signed in to change notification settings - Fork 33
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
Atom Echo install not working #36
Comments
For ESP32-PICO model you will need special binary for version 0.14.4 (with different default GPIO for LEDs). Beta version of 0.15 should provide support for PICO either natively or with WROVER binary (provided on WLED Github releases page). In the latter case use esptool to flash binary. I am not sure if web installer already supports WROVER but perhaps @lost-hope knows. |
Thanks for the quick response! Just an FYI, I also tried the 0.15.0-b4 via the web installer, but I couldn't see any logs appearing when I checked. |
The webinstaller only delivers the default esp32dev build. The difference between those two is the PSRAM right? |
Yes. For ESP32 rev.3 or later standard binary (0.15.0-b4 or later) should suffice but for ESP32 rev.1 you need WROVER binary. Unfortunately I do not own Pico (I know that @srg74 has them) so can't confirm 100% if that is truly the case with standard binary. The actual problem with Pico is not PSRAM support but default GPIO16 used for LEDs. It clashes with PSRAM GPIO. @modem7 if you did not erase entire flash when uploading 0.15.0-b4 then previous configuration may have affected your ESP. |
When installing (plain) on an atom echo, I get an unhandled exception.
wled-dev/WLED#4109
The text was updated successfully, but these errors were encountered: