esp32 S2 mini dont work

[olegeras]

hi, after flashing firmware_esp32_s2_mini_WS281x_RGB.bin using esptool and rebooting the board, the com port does not appear. ( esptoo.exe --port COM8 write_flash 0x000 firmware_esp32_s2_mini_WS281x_RGB.bin) If I flash adafruit-circuitpython-lolin_s2_mini-en-7.3.3, then everything works, micropython appears com port and usb disk. what could be the problem?

[awawa-dev]

Hi
You are doing it in the wrong way, flash it exactly like e.g. WLED: esptool.py write_flash 0x10000 firmware_....bin pay attetion to 0x10000. Just re-flash the board and should be fine. There may be some garbage below 0x10000 address because of your previuos attempt so if it doesnt work immediately, execute esptool.py erase_flash and reflash again using the first command. Then reset the board.

[awawa-dev]

If the esp32-s2 doesn't appear as a com port after flashing and reset then it's 100% fault in uploading procedure. Did you erase the flash? This board is CDC type and needs proper firmware to be uploaded (and I can assure you that official firmwares v9 are 100% valid and already tested by some users) to be detected at all. In other case it simply disappears and only dfu mode is available for the rescue.

[awawa-dev]

WARNING: ESP32-S2FNR2 (revision v0.0) chip was placed into download mode using GPIO0.
esptool.py can not exit the download mode over USB. To run the app, reset the chip manually.

I warned about it and what needs to be done.....

Edit: if wont help try #24 (reply in thread) procedure with micropython/circuitpython-lolin_s2_mini firmware, still I didnt need it for my boards

[d22b]

Thanks for your input. No, the S2 doesnt appear after flashing. But the process is seems to be successfull. Yes i erease it before.

[d22b]

Finish for today. I will try it tomorrow again.

[awawa-dev]

OK then circuitpython-lolin_s2_mini firmware

[awawa-dev]

@d22b

1. put the board into dfu mode (using board buttons) and esptool.py erase_flash
2. get https://downloads.circuitpython.org/bin/lolin_s2_mini/pl/adafruit-circuitpython-lolin_s2_mini-pl-8.0.0.bin
   esptool.py write_flash 0x0 adafruit-circuitpython-lolin_s2_mini-pl-8.0.0.bin
3. esptool.py write_flash 0x10000 firmware_esp32_s2_mini_WS281x_RGB.bin
4. reset the board manually

[awawa-dev]

And you still use level shifter and common ground between ESP and LED?

[awawa-dev]

if im not mistaken it's esp8266 not esp32-s2 mini

[d22b]

Yes. The picture is only for explaining. I tried with both esp32/8266 no luck. I can not believe that three boards are faulty.

[awawa-dev]

Pretty sure

No, in fact it's very, very important if you use esp8266 or esp32-s2 with this motherboard that suddenly appeared out of nowhere... completely different pinout. GPIO2 on ESP32-S2 doesn't even connect with this motherboard. You can dose the information here as you like, but don't count it solving the problem as there are many other things I can reallocate my time to. I think I have presented the case honestly based on the facts. Anyway, the software works judging by the logs, so you need to check the wiring, including the levelshifter and common ground, and in particular the pin for the LED output. Good luck.

[d22b]

Thanks for pointing. I found the reason for the issue. For anybody who has the same issue while using an dedicated WLED board for this solution:

you have to rebuild the firmware for the specific led strip and change the data pinout from 2 (default) to 16. That does the trick and everything works as designed. Take care if you using an different (spi) led strip and change it so that it fits the layout.

[kenny-nt]

Sorry everyone, I am just an ESP beginner.
I bought ESP32-S2 Mini Lolin.
My current connection: Leds Strip connect to Arduino Nano, Arduino Nano - miniUSB to USB 3.0 on my PC
My HyperHDR set Leds Instance as Adalight
I want to use this ESP32-S2 Mini Lolin for replacing Arduino Nano (upgrade to HyperSerialESP32)
I have did all:

esptool erase_flash

And after that:

esptool write_flash 0x0 firmware_esp32_s2_mini_WS281x_RGB.factory.bin

Then I reset by press RST button
What should I do next? Now my ESP32-S2 Mini recognized as USB Serial Device(COM6)
Do I need esptool write_flash 0x10000 firmware_esp32_s2_mini_WS281x_RGB.bin

[awawa-dev]

Hi

Do I need esptool write_flash 0x10000 firmware_esp32_s2_mini_WS281x_RGB.bin

No, your esp32-s2 is already flashed correctly with HyperSerialESP32.
You don't need to do anything else and the board should work as long as it detects COM.
To put it simply:
firmware_esp32_s2_mini_WS281x_RGB.factory.bin = firmware_esp32_s2_mini_WS281x_RGB.bin + bootloader

[kenny-nt]

Hi

Do I need esptool write_flash 0x10000 firmware_esp32_s2_mini_WS281x_RGB.bin

No, your esp32-s2 is already flashed correctly with HyperSerialESP32.

You don't need to do anything else and the board should work as long as it detects COM.

To put it simply:

firmware_esp32_s2_mini_WS281x_RGB.factory.bin = firmware_esp32_s2_mini_WS281x_RGB.bin + bootloader

Mean, now I can pinout to Level Shifter and ws2812b Leds right!? Just confuse about factory and base firmware... Just only need to flash one of them!? And another thing, do I need edit SPEED to 5000000 in platform.ini for ESP32-S2 Mini or release firmware files is already OK with ESP32-S2 mini?
Thanks for guiding me...

[awawa-dev]

Don't change anything for now and try to run the setup with the firmware you already have (firmware_esp32_s2_mini_WS281x_RGB.factory.bin from release?) esp32-s2 uses the CDC layer of the serial driver and generally the speed does not need to be forced because it chooses the highest available. You will check this later when you perform maximum performance tests, which are described on the blog in the last point of building the setup :

• even without LEDs connected, you can set it for a while in a temporary instance, e.g. 900 LEDs and check how many frames it will generate in the logs, if less than in my results, then you can force the speed.

But this is usually important for very large setups and I provide this method in case someone is very curious about the approximate speed at which their CDC device is actual running. Even the standard 2Mb, which is still a high speed for a serial port, is usually sufficient.

[awawa-dev]

BTW which level shifter are you using?

[kenny-nt]

Currently with Arduino Nano:

168 leds WS2812B --- Arduino Nano --- PC
         | 
     Power 5V 12A

Want to upgrade as this but PC connect to ESP32 instead of Rasp.
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglZwPUxmp0INSnMRpT0VLdCbmPrIFdAgoveADiBnUCZ39S8wz1m1CH9OVgL1oTIgT8haXcinDrjuLlb6gvMafV4sIk2b-8fPCTx1bz6Wgx2rENnVSW7lv3S3C5qWYaLO7cBhiH4jcYur73oT0T9q2774OMoimY9slYGCwDl3Z_xFdqjb5Z9WNaGHiPKQ/s6521/single_segment.png

168 Leds WS2812B --- SN74AHCT125N --- HyperSerialESP32 --- PC
        |                   |
   Power 5V 12A ----------- |

[kenny-nt]

Shifter is required for Adalight WS2812B with HyperSerialESP32 right?
About testing: my leds for 43inch Monitor is 168 leds. My controller is adalight without shifter and baud rate: 500000
Test step:

• Active Smoothing + Continuous Output and set Update frequency to 85 (above 85 led will blinking colorful)
• Remote Control > set an effect color > click to turn off led and turn on
  Log:

2024-01-27T16:00:57.370Z [COMPONENTCTRL0] LED device: enabled
2024-01-27T16:00:57.371Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-27T16:00:57.395Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-01-27T16:01:17.423Z [PERFORMANCE] [LED0: FPS = 74.15, send = 4448, processed = 4448, dropped = 550]
2024-01-27T16:02:17.423Z [PERFORMANCE] [LED0: FPS = 83.33, send = 5000, processed = 5000, dropped = 0]
2024-01-27T16:03:17.423Z [PERFORMANCE] [LED0: FPS = 83.33, send = 5000, processed = 5000, dropped = 0]

With 70 (71.43 Hz):

2024-01-27T16:09:05.939Z [COMPONENTCTRL0] LED device: enabled
2024-01-27T16:09:05.941Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-27T16:09:05.967Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-01-27T16:09:17.432Z [PERFORMANCE] [LED0: FPS = 64.71, send = 3883, processed = 3883, dropped = 402]
2024-01-27T16:09:50.744Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"","params":{},"subcommand":"hasLedClock","tan":1}]
2024-01-27T16:10:17.423Z [PERFORMANCE] [LED0: FPS = 71.43, send = 4285, processed = 4285, dropped = 0]

And with 65(66.67 Hz)

2024-01-27T16:11:07.213Z [COMPONENTCTRL0] LED device: enabled
2024-01-27T16:11:07.214Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-27T16:11:07.242Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-01-27T16:11:17.427Z [PERFORMANCE] [LED0: FPS = 66.91, send = 4015, processed = 4015, dropped = 0]
2024-01-27T16:11:39.624Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"","params":{},"subcommand":"hasLedClock","tan":1}]
2024-01-27T16:12:17.427Z [PERFORMANCE] [LED0: FPS = 66.67, send = 4000, processed = 4000, dropped = 0]

So I should set Update frequency to 65 right?

[awawa-dev]

If you want to use HyperSPI, you must follow the manual very carefully and use short cables, remembering especially that the ground from GPIO is as important as the other SPI data lines from GPIOs (users sometimes ignore it or route it in some unusual way and this leads to huge complications later)

[kenny-nt]

If you want to use HyperSPI, you must follow the manual very carefully and use short cables, remembering especially that the ground from GPIO is as important as the other SPI data lines from GPIOs (users sometimes ignore it or route it in some unusual way and this leads to huge complications later)

"Short cables" between Pi - ESP32 only?
With about 300-400leds, is HyperSerialESP32 good enough?

[awawa-dev]

It should be OK. Usually you don't have to decide on HyperSPI right away, you can start with HyperSerialESP32 and then change the firmware to HyperSPI and connect both SPI interfaces esp32 and rpi: the maximum distance with HyperSPI that I tested is about 25cm (but it may depend on the EMI in a given setup)

[kenny-nt]

It should be OK. Usually you don't have to decide on HyperSPI right away, you can start with HyperSerialESP32 and then change the firmware to HyperSPI and connect both SPI interfaces esp32 and rpi: the maximum distance with HyperSPI that I tested is about 25cm (but it may depend on the EMI in a given setup)

the maximum distance with HyperSPI

The distance here is from Rasp to ESP32 right? distance from ESP32 to shifter and leds is not matter right?

[awawa-dev]

distance from ESP32 to shifter and leds is not matter right?

Also matters but it could be longer than esp32 to rpi connection. Probably 50-70cm or maybe longer should work if you are using level shifter.

[kenny-nt]

It should be OK. Usually you don't have to decide on HyperSPI right away, you can start with HyperSerialESP32 and then change the firmware to HyperSPI and connect both SPI interfaces esp32 and rpi: the maximum distance with HyperSPI that I tested is about 25cm (but it may depend on the EMI in a given setup)
Why don't have HyperSerialArduino? I have test my Arduino Nano, baud rate can up to 2M too...

[awawa-dev]

Arduino is too slow to handle both high speed and Neopixel emulation. You have it explained in HyperSerialEsp8266 project where it all started. Maybe new series (48mhz)will change the situation a bit but still it much slower than esp and Pico and price is much higher than the old classic Arduino series. It's usually cheaper to get Pico board that has a level shifter and rp2040 offers much greater capabilities thanks to PIO co-processor which Arduino lacks.