'Timeout writing data to COM5' and 'Rs232 SerialPortError' after erase_flash on ESP32 S2 Mini #85
Replies: 10 comments
did you reset i? also in HyperHDR you must have exactly 169*2=338 not 339 leds |
|
yes ive reset it. the first segment is 169 leds and the second 170. do the segment have to be the exact same length? when configuring 338 leds in HyperHDR i still get the same error. |
yes, otherwise you can hang the esp |
|
after changing to 338 reset the esp and upload new logs |
|
|
lower leds to 50 and test again. esp32-s2 is crashing for some reason but there is a communication |
|
|
I cant find your fork of HyperSerialESP32 to verify the build. Did you compile the firmware on your computer? Please follow the standard path to build a firmware then we will see. |
|
Using the build from github actions made the error disapear from the logs. Also my level shifter was broken. I replaced it and now it works. Thank you for your help ❤️ |
|
Great! I'm glad you managed to get it up and running 👍 |
Uh oh!
There was an error while loading. Please reload this page.
I’m having some problems with my ESP32-S2 Mini.
The LEDs lit up and were working fine before. However, I had configured the second segment start index incorrectly, so I wanted to fix that. When re-flashing the new firmware to the ESP, I ran erase_flash for the first time, followed by flashing the factory firmware.
After that, it stopped working.
I've set up the wiring exactly the same way as shown in the segmentation example: (https://user-images.githubusercontent.com/85223482/222923979-f344349a-1f8b-4195-94ca-51721923359e.png)
These are the two error logs i get:
The changes i made to platformio.ini
How im flashing the esp:
Here is the full log output of HyperHDR:
All reactions