I’ve soldered headers to allow a serial port and programming mode
I can run esptool.py and upload the WLED_0.13.3_ESP01.bin image
This boots and I can connect using WIFI to the web server using the WLED-AP
However
It doesn’t advertise the AP. On my laptop, iwlist doesn’t show anything. It is there, because if tell my laptop or phone to connect to WLED-AP it works, and the AP name is then advertised. I’ve tried doing an erase_flash before write_flash and that makes no difference. That seems odd. Any thoughts? It’s not a deal-breaker but it seems odd. I though the default behaviour would be to advertise even if you can hide the AP later.
(EDIT: Removed an earlier question as it was user error on my part)
Have you tried to flash a more recent version of WLED?
0.14.2 is out and has some ESP8266 specific stuff in it.
I’d personally leave the new 160MHz setting alone - at least until you’ve tried everything else.
The other immediate thought would be enable/disable WiFi deep sleep mode.
You might try a full power boot after flashing to see if the AP will come up on it’s own.
The other thing to note - with the header attached, you’re probably grounding IO0 to put the chip in “Flash Mode”.
Removing the header clip and power booting, should give a “clean” startup.
0.14.2 seems slightly better in this regard. Sometimes it’s discoverable after a power cycle, sometimes it isn’t.
I’m aware about the GPIO0/header thing. It’s definitely booting correctly and can connect to the AP after a few seconds, but it doesn’t seem to be broadcasting the AP name reliably. I suppose it’s possible that my laptop is taking its time getting into sync with chances in APs around it.
I’ve tried an explicit “erase flash” before the flashing operation in case it was some sort of undefined setting, but that doesn’t seem to be it either.
At the end of the day, it’s not a completely critical fault, but it seems odd.