-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32S3 N32R8 won't boot correct partition after OTA #232
Comments
After going over all the used libraries I discovered my IDE was using an older AsyncTCP version when compiling. Removing that redirected the IDE to the correct library during compiling. The issue now seems to have been resolved. |
Cheered to soon. It works, but not with 32MB. The OTA not launching for ESP32S3 Wroom 2 has been resolved by fixing the double library issue, as mentioned above. However when using a 32MB partition scheme (16/16) it doesn't boot the update firmware after OTA, but the previous one. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Hello,
I have noticed an issue where using the eps32s3 wroom 2 vs. esp32s3 results in not being able to browse to the OTA page.
I use an AP and browse to 192.168.4.1/update.
When I compile it with ESP32S3 dev settings within Arduino IDE, it works fine.
When I compile it with ESP32S3 dev Module Octal (Wroom2), the chip I actually use (ESP32S3 Wroom 2 N32R8), it will launch the AP but won't load the server/webpage.
Another thing I noticed is that when using the ElegantOTA "successfully" it doesn't reboot the uploaded firmware but the original one. Firmware is correct/working cause when uploaded via USB no issues in that regard. So somehow, when using OTA it won't select the right partition? just guessing here. Any help would be appreciated.
Thank you in advance.
Kind regards,
Jay
The text was updated successfully, but these errors were encountered: