Newly flashed ESP32 AP Not appearing, but lights show default boot display. #1212
Comments
|
On board #1 (the problem child), does the erase_flash command stop the LEDs from doing anything after it completes? |
|
@huggy-d1 IIRC, the LEDS would stay whatever color they were last set at as long as I didn't disconnect power to reset it (the power is coming from my power supply, not the ESP32, though they are both connected to the PS via the bread board power rail), but I'll need to try again later to be 100% sure of that. I tried a lot of things and may be misremembering |
|
If you connect the ESP32 RX & TX & GND lines to a USB FTDI adapter's TX/RX/GND lines (swapping RX & TX), you can then use a terminal program to read debug data written by WLED. |
|
Is there a way to do this with just the existing micro USB connection or do i need to get some extra piece of hardware (FTDI adapter)? |
|
With this kind of esp32 dev Boards it should be possible to use your usb cable. Just plug it in and use monitor in vscode=platformio or serial monitor in arduino ide |
|
Does the blue led come on? |
|
Cant remember where I got the bootloader bin file from though. |
|
They package the bootloader in the assets for each release and theres also a link in one of the linked issues in my comment, but per my opening comment, I am flashing the bootloader, specifically this line in my original post: I could try to do it with this tool though |
|
When I flash with Arduino IDE sometimes it doesn't startup and the blue led doesn't come on. I then save the bin file and flash with the above tool and the blue led lights and I can get to the AP.? |
|
Alright I'm able to do some more testing now. @huggy-d1 to answer your first question, erasing the flash does not change the LED colors that it booted with. To go into a bit more detail, I just did this:
But after this, I wait a minute, and the AP never shows up :( To your point, @toto79, it seems either there aren't debug logs, or more likely my development board isn't set up to write to serial over USB, as the arduino serial monitor has nothing on it. Not sure if its worth noting that I had to install some USB to UART Bridge VCP driver to get it to register as a serial device at all, so not sure if thats somehow related to that lack of functionality. Not sure where to go from here unless I purchase a "USB FTDI adapter"? :/ |
|
And unfortunately the ESP Flash Download Tool is not available for mac, although I'm pretty certain I'm doing the equivalent of what that tool would do, especially considering the steps work for a different board. |
|
@rclough : As mentioned in product description you have a CP2102 chip onboard, so this is what you are looking for with a usb to uart bridge. And if flashing is possible, monitoring is also possible. Once you plug in the usb cable you should see an additional com port, which you have to select in arduino ide. Beside this you have to add some code lines to enable debug in wled in plattfomio.ini in the env section of your board.
|
|
Gotcha, the build flags I think were the missing piece, it wasn't clear that I should be building/deploying WLED to enable logging. I'll have to try and figure out how to get platformio working tonight, I've never used it before. |
|
you can give https://gitpod.io#https://github.com/Aircoookie/WLED/tree/master an try
find your firmware.bin file in folder .pio/build/env:type, save as... and flash to your esp like you did it before |
|
When I freshly flash the esp32 bin file, I don't see any AP from it. Can someone upload a working bin? |
I seem to have the same problem flashing tasmota32.bin |
|
I seem to have the same problem on D1 mini ESP32 clone. Have tried with 3 different boards of same type, will try with some other ESP32 boards. ESPTOOL output Detecting chip type... ESP32 Serial monitor output entry 0x400806ac rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
|
@rclough @salopette @RetroRule |
|
Many thanks kernowquack. |
I have successfully used your bin on my Adafruit ESP32 Huzzah (4MB). I would like to know what you changed in the platform.io file when you compiled. I have it set to both D1 Mini and ESP32dev in the config file and neither have worked for me. Your bin did but I need to change the pin assignment and compile with that pin assignment. I am building from master which is only 8 days old. |
|
I compiled for wemos_d1_mini32 using VSCode and PlatformIO, hope this helps. If it still doesn't work I will take a look and see if I can remember if I did anything else. |
|
I determined the issue for my setup! This maybe something to add to documentation or maybe it is there and I missed it! The bootloader must be addressed to 0x00000 and the compiled firmware must be addressed to 0x10000 when running the esptool.py commands. I have successfully compiled from esp32dev in the repo with a custom pin assignment and my changes are working as is WLED! Woot! |
|
I remember now! Sorry had meant to write down what I did and upload but
can't find what I wrote. Sorry Guys.
Tony Hook
*Director*
[image: Steren-Limited]
t: 01736 759 140 e: [email protected]
m: 07540 118 120 w: www.steren.co.uk
[image: Find Us]
<https://hashpoint.org/gb/TR275DQ/B> [image: Download
Directions] <https://drive.google.com/open?id=0B_IaavTnTneVazJFWmVxSl9QbG8>
Steren Ltd is a company registered in England and Wales. Registered number:
07853600. Registered office: Steren Ltd, 35 Treeve Lane, Connor Downs,
Hayle, TR27 5DQ. This message is private and confidential. If you have
received this message in error, please notify us and remove it from your
system. The opinions expressed in this email are the opinions of the
individual author and may not reflect the opinions of Steren Ltd
…On Thu, 3 Dec 2020 at 20:53, Jamie Meredith ***@***.***> wrote:
I determined the issue for my setup! This maybe something to add to
documentation or maybe it is there and I missed it!
The bootloader must be addressed to 0x00000 and the compiled firmware must
be addressed to 0x10000 when running the esptool.py commands. I have
successfully compiled from esp32dev in the repo with a custom pin
assignment and my changes are working as is WLED! Woot!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1212 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGKT2GMXLOKCPRUDTNTE5S3SS73DTANCNFSM4R4V4OHA>
.
--
--
Steren Ltd is a company registered in England and
Wales. Registered
number: 07853600. Registered office: Steren Ltd, 35
Treeve Lane, Connor
Downs, Hayle, TR27 5DQ.
This
message is private and confidential. If
you have received this message
in error, please notify us and remove it
from your system.
The opinions expressed in this email are the opinions
of the individual author and may not reflect the opinions of Steren Ltd
|
|
This is a big gap in both ESP32 documentation and WLED downstream documentation. I have worked in tech related fields in the opensource community for 17+ years and it is always the small stuff that slips through the cracks, lol. There are probably 20K people out there who tried to move to the ESP32 and this was a roadblock! My synopsis at this point is that the "tools" available for programming ESP based boards are all designed for a single register for uploading from a GUI. The ESP boards introduce the ability to write you own bootloader, which requires a different address than the runtime code. I am new to hardware level software so forgive any mistakes or lack of understanding. I am going to block off some time to see how I can get involved in the WLED community as I have specific needs that it meets perfectly for my projects. I will see what I can do to get involved in helping improve things like this. Thanks for the input on this old thread. |
Is you have homebrew installed on a mac, then try installing I've flash esp8266's and esp32's with it, however esp8266's have worked better for me so far. |
|
Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. |
stale
bot
added
the
stale
|
I am facing exactly the same issue and tried wledEsp32_dump.bin poster by @kernowquack and I tried using all the tools I can find (command and GUI. WLED_0.12.0_ESP32.bin will not run on my board and I tried several.
Problem started when tried to upgrade to WLED_0.12.0_ESP32 after that it kept giving error:
I managed to get the bootloader successfully installed using esptool.exe not esptool.py on windows machine using the same options for the command line. once that is installed I installed a sketch using esphome and then used their GUI to upload WLED_0.11.0_ESP32_ledpin16.bin successfully. other than I could not get the botched upgrade to reinstall correctly. |
stale
bot
removed
the
stale
|
Hi - I've been having the same problems and found a workaround that works for me - Use ESPhome-flasher >flash with Tasmota > hard reset > flash with WLED and the WLED-AP appears as expected :) |
|
Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. |
stale
bot
added
the
stale
|
I know this is an olf thread but its very few and far between when i dig out the old of box of esp 8266 and esp32 to have a play and come across this problem with both esp8266 and esp32. really struggle to get anything higher than 8.5 stably on the 8266 and 12 (with inlcuded bootloader) via notmal flashing routes. tried all software and flashing and had multiple instances of AP not showing. stumbled across which lets me flash the latest via webrowser and have successfully flashed all my problematic devices upto wled 13.3!! |
Hi there, thanks for all the hard work you've put into the WLED project.
I recently purchased a 4 pack of ESP32 dev boards, these specifically. I plugged one into a bread board with some WS2812B strips attached to data, and attempted to get up and running. I originally attempted to flash with NodeMCU PyFlasher, and when this didn't work, I tried ESPHome flasher, and eventually moved to using esptool.py. But the AP never showed up.
Somewhere in between the above I also I discovered the steps described in the (previous issue documenting the needed extra steps for ESP32)[https://github.com//issues/517#issuecomment-571333712]. Doing this, I was able to get a 2nd board working as expected with this series of commands:
But the original board I attempted does not work with this, nor seemingly any order of the commands. What is strange is it does seem to be booting WLED: The first whatever handful of LEDs turn orange, and the buttons on the board change color/turn them on/off. But the AP is never displayed.
Is it possible this particular board has a defective WIFI module, or maybe I could have loosened a component when utting it into the bread board? Is there anything I can do to debug what may be happening?
Thanks for any help/direction! I'd rather not have to order extras if I don't need to
The text was updated successfully, but these errors were encountered: