-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Signed binaries fail signature verification when doing OTA via Arduino IDE #5875
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
Comments
@imavroukakis ESP-01 => does it have a Puya flash chip? If so, you need to build with Puya support enabled, otherwise onboard writing won't work correctly. |
@devyte thanks for the tip. It is indeed a Puya and I've been reading up on the horror stories. Is what's described at #5493 (comment) what's required to enable support for it? |
I added |
So here's what I've done In the build output I can see
and for good measure, added btw, I'm not using SPIFFS at all. |
Hey :) any updates/suggestions about this ? |
#6334 fixed this, as the problem was espota.py was taking the unsigned binary, not the signed one, by default. @thangktran fixed it to check and upload the xxx.signed version, should it exist, automatically. |
Basic Infos
Platform
Settings in IDE
Problem Description
Uploading the same signed binary using OTA via the Arduino IDE fails with the following message
OTA updates with unsigned binaries are not affected, and the initial signed binary upload via OTA works fine.
MCVE Sketch
Debug Messages
The text was updated successfully, but these errors were encountered: