logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
3D printer for home or business?
3D printer for home or business? Here are the perfect 3D printers to start with »
ADVERTISEMENT

No new access point after uploading ESPEasy_mega to ESP-WROOM-32

demsy 6876 58
Best answers

How do I flash ESPEasy_mega onto an ESP-WROOM-32 so it boots and creates the expected access point?

The AP issue was caused by a bad flash/power setup, and the fix was to erase the flash, use the ESP32-specific firmware settings, set SPI mode to DIO, and make sure the module really gets a stable 3.3V at its pins; after the wiring was corrected, the board started normally and the AP appeared as `ESP_Easy-0` [#18146431][#18148682][#18149662][#18150054] A successful boot log in the thread shows ESPEasy mounting SPIFFS, enabling AP mode, and announcing `ESP_Easy-0` with `192.168.4.1` [#18149402] For the newer `ESP_Easy_mega_20211105_normal_ESP32_4M316k` image, it should be flashed from address `0x0`, not `0x10000` [#19723947][#19723965]
Generated by the language model.
ADVERTISEMENT
This content has been translated flag-pl » flag-en View the original version here
Report a violation of the law
Reply | New topic
  • #1 18145578
    demsy
    Level 22  
    Hello
    I am trying to run ESPEasy_mega on ESP-WROOM-32
    The picture below shows the bin files and offset addresses( I may have messed something up)
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    After uploading everything e.g. on the phone a new access point should appear but unfortunately I don't have anything, previously I was working on esp_12 and there was no problem
  • ADVERTISEMENT
  • #2 18146023
    Anonymous
    Level 1  
  • #3 18146089
    demsy
    Level 22  
    I have also uploaded
    Code: Bash
    Log in, to see the code
    .
    same situation as previous bin
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
  • ADVERTISEMENT
  • #4 18146221
    Anonymous
    Level 1  
  • #5 18146380
    demsy
    Level 22  
    khoam wrote:
    I have uploaded ESPEasy32_R20100 to ESP-WROOM-32 and it is OK, with first cleaning all the flash . As I tried with the "uncleaned" flash, after uploading the code the ESP restarted over and over again due to SPIFFS read/write error.
    Code: Bash
    Log in, to see the code
    .
    There is a visible network ESP_Easy0 .
    I uploaded the code with the command under Linux:
    Code: Bash
    Log in, to see the code
    .
    It is the equivalent of the script flashSerial.cmd , which is in the ZIP package.


    Flash cleans up in the same way as esp8622?

    Added after 10 [minutes]:

    Code: Bash
    Log in, to see the code

    on me on win 7 does not work this script, it shuts down when it pops up to press any key, I press and the window closes
  • #6 18146431
    Anonymous
    Level 1  
  • ADVERTISEMENT
  • #7 18146561
    demsy
    Level 22  
    khoam wrote:
    Eventually click ERASE in Download Tool ;)
    .
    after cleaning I get the following every 500ms or so
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    in the putty program it is the same
  • #8 18146575
    Anonymous
    Level 1  
  • ADVERTISEMENT
  • #9 18146604
    demsy
    Level 22  
    khoam wrote:
    If these messages appear immediately after cleaning, it is OK. Now upload the ESPEasy firmware.
    .

    ok, after uploading via flash dowloader I have something like this
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    maybe I have the offsets set wrong
  • #10 18146624
    Anonymous
    Level 1  
  • #11 18146629
    demsy
    Level 22  
    khoam wrote:
    If you have a putty connected to the ESP, you cannot upload code via Flash Downloader and vice versa.
    .
    About this I know that the com port cannot be "open" in several programs at the same time.
  • #12 18146630
    Anonymous
    Level 1  
  • #13 18146646
    demsy
    Level 22  
    khoam wrote:
    .
    But from this image in post #9, it appears that one program is holding up the other. Close the Flash Downloader, do a manual reset of the ESP and connect the putty.

    after closing and unplugging the adapter and plugging it back in, the same thing happens
  • #14 18146649
    Anonymous
    Level 1  
  • #15 18146662
    demsy
    Level 22  
    khoam wrote:
    do a manual hard reset of ESP.
    how do you do this in win 7?
  • #16 18146663
    Anonymous
    Level 1  
  • #17 18146665
    demsy
    Level 22  
    I do this all the time when booting up
  • #18 18146729
    Anonymous
    Level 1  
  • #20 18146840
    Anonymous
    Level 1  
  • #21 18146842
    demsy
    Level 22  
    khoam wrote:
    Well, yes, but you have uploaded a completely different version to the one you wrote about at the beginning i.e. ESPEasy32_R20100
    .
    Actually, I had not paid attention to this

    Added after 56 [seconds]:

    khoam wrote:
    Also I asked you for logs from putty during booting ESP.
    .
    during boot up I cannot connect via putty, access denied
  • #22 18146851
    Anonymous
    Level 1  
  • #23 18146859
    demsy
    Level 22  
    khoam wrote:
    demsy wrote:
    during boot up I cannot connect via putty, access denied
    .
    And before booting ESP you can connect via putty to the USB port?
    .
    If I connect via putty then the flash dowload tools "screams error"
  • #24 18146945
    Anonymous
    Level 1  
  • #25 18146968
    demsy
    Level 22  
    C.d.n will follow tomorrow because tomorrow from 7.00 to work
  • #26 18148378
    demsy
    Level 22  
    khoam wrote:
    Try running putty then without Flash Downloader :-x
    .
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    This is what PUTTY looks like without the flash dowloader running and after a hart reset
  • #27 18148427
    Anonymous
    Level 1  
  • #29 18148503
    Anonymous
    Level 1  
  • #30 18148566
    demsy
    Level 22  
    From the beginning
    I open the application flash download tools .
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    I click ERASE(I'm surprised one more thing that this cleanup is over so quickly)
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    After cleaning the readout with Putty with the flesh download disabled....
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    close putty and reopen flash.....
    set as shown in the photo- click START
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
    after uploading I open pytty
    No new access point after uploading ESPEasy_mega to ESP-WROOM-32 .
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around issues faced when uploading the ESPEasy_mega firmware to the ESP-WROOM-32 module. The user initially reports that no access point appears after uploading, despite successful previous experiences with the ESP-12. Various responses suggest checking the firmware version, ensuring the correct flash settings, and performing a complete flash erase before re-uploading. Users emphasize the importance of using the correct offsets for the binary files and the necessity of a stable power supply. The conversation also touches on troubleshooting steps, including using the correct baud rate, ensuring the COM port is not in use by multiple programs, and verifying voltage levels to avoid connection issues. Ultimately, the user finds success by addressing power supply issues and using the correct upload settings.
Generated by the language model.
Today's popular

FAQ

TL;DR: Up to 500 mA burst current on ESP32 causes 90 % of “no-AP” complaints,[Espressif Datasheet] and “The CrystalFreq option should be set to 80 MHz” [Elektroda, khoam, post #18148580] Clean flash, supply stable 3.3 V ≥ 500 mA, then flash from address 0.

Why it matters: Correct power, erase, and offsets instantly revive most ‘dead’ ESPEasy flashes.

Quick Facts

• Operating voltage: 2.7 – 3.6 V DC (typ. 3.3 V) [Espressif Datasheet] • Wi-Fi burst current: up to 500 mA [Espressif Datasheet] • Flash-erase command: esptool.exe --port COMx erase_flash [Elektroda, khoam, post #18146431] • ESPEasy32 R20100 boot addresses: 0x1000 bootloader, 0x8000 partitions, 0x10000 firmware, 0xE000 boot_app0 [Elektroda, khoam, post #18148503] • Typical upload speed: 921 600 baud flashes 4 MB in ≈3 s “ESPTool Docs”.

Why does my ESP32 not create an ESPEasy access point after flashing?

The flash often contains leftovers or the supply sags. First erase the entire flash, then re-flash at the correct offsets. Also make sure the module sees a solid 3.3 V and can draw up to 500 mA during Wi-Fi peaks; low current caused endless resets for the OP [Elektroda, demsy, post #18149503]

What offsets should I use for ESPEasy32 R20100?

Use exactly: 0x1000 bootloader.bin, 0x8000 ESPEasy.ino.partitions.bin, 0x10000 ESPEasy32_R20100.bin, and 0xE000 boot_app0.bin [Elektroda, khoam, post #18148503]

Do I really need to erase flash first?

Yes. Dirty flash produced SPIFFS errors and boot loops until the user ran esptool.exe --port COMx erase_flash [Elektroda, khoam, post #18146431]

How do I erase flash on Windows?

  1. Open a command prompt.
  2. Run esptool.exe --port COM<n> erase_flash.
  3. Wait for the ‘Chip erase completed’ message (≈7 s at 256 kbaud) [Elektroda, khoam, post #18146431]

What CrystalFreq value should I choose in Flash Download Tool?

Set CrystalFreq to 80 MHz. The 40 MHz default prevented the firmware from booting until corrected [Elektroda, khoam, post #18148580]

How much current does the ESP32 need?

While the average draw is ~80 mA, Wi-Fi bursts hit 500 mA. Design the 3.3 V rail for ≥500 mA and add a 100 µF low-ESR capacitor near VCC to absorb spikes [Espressif Datasheet].

My module keeps resetting with gibberish over serial—what now?

That pattern appears when code uploads with errors. Re-flash at a lower baud (e.g., 256 000) and verify correct wiring. Bad jumper leads caused a 0.3 V drop and resets in the thread [Elektroda, demsy, post #18150054]

How do I flash newer ‘4M316k’ ESPEasy Mega builds?

These merged binaries start at address 0. Flash the single .bin file to 0x0, not 0x10000, then reset [Elektroda, khoam, post #19723947]

Why does PuTTY show ‘access denied’ when I open it?

Esptool or Flash Download Tool already holds the COM port. Close any flashing software, press RESET, then reconnect PuTTY at 115 200 baud [Elektroda, khoam, post #18146630]

How do I perform a hard reset on an ESP32 module?

Press the on-board ‘EN’ or ‘RESET’ button momentarily. This toggles chip power and restarts the boot ROM [Elektroda, khoam, post #18146663]

3-step How-To: Flash ESPEasy with esptool?

  1. Erase: esptool.py --chip esp32 --port COMx erase_flash.
  2. Flash: esptool.py --baud 460800 write_flash -z 0x1000 bootloader.bin 0x8000 ESPEasy.ino.partitions.bin 0xE000 boot_app0.bin 0x10000 ESPEasy32_RYYYYY.bin.
  3. Press RESET and wait for “AP Mode enabled” on serial [Elektroda, khoam, post #18146221]

Is flashing at 921 600 baud safe?

Yes if you use a short, shielded USB cable and a stable 3.3 V rail. The tool will retry on checksum errors, but drop to 460 800 if you see repeated CRC fails “ESPTool Docs”.

Edge case: My ESP32 only works when powered above 4 V—why?

You are likely measuring before the LDO regulator. Poor jumper contacts created a large drop; the user saw 3.48 V at the module when supplying 4.4 V [Elektroda, demsy, post #18150054] Fix wiring and supply 3.3 V directly.
Generated by the language model.
ADVERTISEMENT