I am trying to get WLED 0.14 working on a M5Stack Atom S3 Lite. (link: https://shop.m5stack.com/products/atoms3-lite-esp32s3-dev-kit )
After compiling and flashing the device with esptool, the device stays in a boot loop… (hearing that bwop…unplug…whop…plug-in…whop…unplug sound all the time on my Windows PC).
I have read all topics about it, even about the (older, non S3 version) and tried 20+ rebuilds… Some people said the older (M5stack Atom Lite) was doing a boot-loop because the led pin was mapped to the reset pin… (see: Both .13 betas cause loop reboot on M5stack atom lite · Issue #2108 · Aircoookie/WLED · GitHub ). But setting the LED pin correctly did not work.
According to the pictures, it shows that BTN PIN: G41 and RGB LED: G35.
The device has 8MB Flash and -not- 8MB ram.
What I’ve tried:
- Compile with: -D LEDPIN=35 -D BTNPIN=39
- Compiled with default_envs=sp32s3dev_8MB as well as esp32s3dev_8MB_PSRAM_opi as well as m5atom. I am quite sure it are not those last two because it has no 8MB PSRAM and the m5atom is just esp32dev, not esp32s3.
- Compiled with: board_build.flash_mode = qio and board_build.flash_mode = dio
- Compiled with: D ARDUINO_USB_CDC_ON_BOOT=0 and -D ARDUINO_USB_CDC_ON_BOOT=1 as well as -D ARDUINO_USB_MODE=1
Now trying to terminal monitor this device, but I am a little new on that (from platform IO).
Help me fixing this and I send you a free M5Stack Atom S3
Update: I get exactly the same when I only flash the bootloader to the device and unplug it… then when plugging it… it will also boot loop. Is that normal behavior?