WLED-AP never appears #517
Comments
|
Afaik, Aircookie recommends esptool .... did you see this part on https://github.com/Aircoookie/WLED/wiki: esptool.py erase_flash Did you try both? |
|
I tried all of that. Eventually, after I gave up, it connected while I was trying a manual connection (but it took a good 5 minutes for it to respond)... One major note: OS X displayed the setup page as a dialog. It did not require navigating with a browser. Once I got it connected to my wifi, it seemed to work. However, it seems there may be some other issue, as the wifi doesn't seem to stay on. It will work for 5-10 minutes, then disappear from the network. I had esphome flashed on this device previously and it was working just fine, so I suspect something in WLED is causing issues. |
|
Went back to esphome and the wifi works flawlessly. What can I do to help get WLED working? |
Aircoookie
added
the
connectivity
|
Hi and sorry for the issues! |
There seems to be a code error in the Blink sketch. Could you recommend something different that could be uploaded that will actually compile? |
|
If You have a error maybe it's something wrong with your settings. |
|
@Aircoookie any chance you contacting the esphome dev to exchange how you both handle wifi would be beneficial? |
Never used Arduino app for anything else. Haven't touched any settings. What could I have missed configuring? The error is that it's missing a constant being defined. |
Did you find and use the Compile settings at https://github.com/Aircoookie/WLED/wiki ? |
Noob to ESPs here... what do I do with those? I used the "Quick Start Guide" higher on the page and followed the instructions under "I just want to use WLED! (install release binary)" |
Because you mentioned "Never used Arduino app", and a remark was made about settings, i thought you might need those compile settings. But those, afaik, are only needed when you use Arduino IDE to flash stuff to your NodeMCU. You can find the Arduino IDE at https://www.arduino.cc/en/main/software . You could try it, it'll definitely make you learn something ;-) . Installation instructions for the Arduino IDE desktop app can be found at https://www.arduino.cc/en/Guide/HomePage . After which you could use http://help.blynk.cc/en/articles/512105-how-to-install-blynk-library-for-arduino-ide to flash the Blynk sketch to the NodeMCU. |
|
Blynk? @Aircoookie and docs keep saying "Blink", which is built-in to the Arduino IDE and what I'm referencing when I say there's a compile issue. |
|
You're right, sorry, i'm mistaken... |
|
Hi, sorry for the trouble getting it to work. I realized that even flashing the blink sketch requires you to install the ESP32 arduino core, which is not hard, but also not trivial. Just flash it to your ESP32 using and everything should work! (if it doesn't, try running the regular ESP32 flash command from quickstart again) |
|
@paularmstrong is this resolved? |
|
I switched to a D1 mini using 0.9.x and it's working |
|
I just had this problem with an ESP32S- erased, flashed, flashed bootloader in different combinations and finally saw Aircookie's response. Thanks! I flashed the esp32 bootloader binary AFTER flashing wled binary and it worked! |
|
Update: I got WLED to compile and flash with PIO without issue for a ESP32-S3-DevKitC-1-N8R2. It seems that the pre-built binary produced for ESP32S3 by WLED is missing several components being flashed alongside the binary that PIO handles automagically I assume its the bootloader at 0x0000 and the partition map at 0x8000, but I'm unsure of what 0xe000 is. |
|
|
|
It appears that the data being flashed at 0xe000 is the factory OTA image (boot_app0.bin) which is what gets booted first on a factory reset. Looks like PIO might be flashing it with a stub. It would explain why WLED wasn't booting properly previously. Would probably help if a WLED binary was built with these components built in like with Tasmota or if it was more documented |
|
Manual flashing requires you to manually flash all partitions. The web installer should take care of that for you, if the board configuration is supported, as does VSC PIO. |
I can confirm that the web flasher is still broken for the ESP32-S3-DevKitC-1-N8R2 board. Results in the behavior described in #1212 (comment) |
|
It looks like the https://github.com/Aircoookie/WLED/blob/1ff667b7eff07ebad100e48eb871c698eab11a71/platformio.ini#L45 Seems like more of a general issue with ESP32S3 builds/the web installer even for a standard board config |
S3 was not supported at the time of that issue. Unrelated. If you think web installer is broken, please open an issue there. WLED in itself is fully working on any type of S3 we have encountered so far. Main reason for non-working installation is incorrect flashing procedure or incorrect binary type for chosen chip's flash/PSRAM combination. EDIT: WLED releases page provides binaries for 3 types of S3 chip. |
So that's still the behavior I'm getting from the latest beta builds with a web flash/manual flash with the The stable build of 0.14.4 flashed from the web flasher seem to be resulting in a different behavior (resolved by flashing over PIO): It does seem related to wled/WLED-WebInstaller#22 but extended to include standard board configs as well |
The details you find in
So its 3x3 = 9 major configurations with different bootloader, partitions.bin, and firmware image. Only the "app0" partition is always the same. Unfortunately we cannot provide you with 2 or 3 firmware that "run on any S3". And ... depending on who you ask ... depending on the month of the year ... you'd probably get different opinions on what is "standard" I would strongly suggest that this discussion is put into the place where it belongs: https://github.com/Aircoookie/WLED-WebInstaller/issues |
|
A good overview of known -S3 configurations is here: https://espeasy.readthedocs.io/en/latest/ESPEasy/ESPchips.html#quad-octal-spi-mode |
|
Btw, the discussion here went very much off-topic already. The original problem report was about some esp32S (classic esp32) not running with "dio" firmware..... |
|
Looks like I am to be added to the long list of those that have this problem. Background: Once built, I installed my original firmware and all was well. I use Visual Studio with the Visual Micro add-in as my IDE. It all uploads and runs just fine. I have tried pretty much all of the ways to flash WLED onto the ESP32. This includes the WLED installer, esptool, and the Espressif flash tool. No joy. They all seem to flash but WLED doesn't show up in my network list. Here is the response from esptool...
One things that I did notice is that when I flash my code with Visial Studio (which uses esptool) the reset after the load is clean. The transmit and receive LEDs on the board are off and the star runs its default effect. However, when I use esptool from the command line, the reset is not clean. The receive LED is lit. When I open a terminal, this is what I get... `rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) ELF file SHA256: 0000000000000000 Backtrace: 0x401468bb:0x3ffb1d70 0x1d75dce5:0x3ffb1d90 |<-CORRUPTED |
No matter what I do, the wireless access point never shows up. The logs from esphomeflasher are completely blank, as if the device never actually starts up.
Logs via esptool.py
Logs via esphomeflasher
NOTE: The line from the wiki is very vague for someone unfamiliar with arduino
I believe I flashed the device with the "blink" example (though the blink example apparently is not ready out of the box and took some googling to figure out you need to add something like
#define LED_BUILTIN 13to the file before installing). I did this, it installed, then I went back and tried to install WLED again, same results.Is there something wrong with what I'm doing? Is a step missing from the instructions?
The text was updated successfully, but these errors were encountered: