-
Notifications
You must be signed in to change notification settings - Fork 7.6k
OTA updates from server error 8 #3909
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
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
So it looks like no one cares that there's a bug that makes it so that some Arduino devices can't use the Arduino ota update but whatever I guess lol it's a pretty easy fix for the user if they just want to delete the magic byte check (doesn't fix the problem but a quick way around it) |
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future. |
Same issue here. I removed the lines @Mr-HaleYa suggested and the update process starts and finishes fine. |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
glad it worked for you. just wished someone would actually reply, even if to say this can be fixed (more like they won't since code can always be fixed) then have a useless stale bot close issues they don't want to reply to |
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future. |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Keeping this issue alive.... |
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future. |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Still not resolved... |
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future. |
You could try something like what I use, just set the FIRMWARE_URL and call updateFIRMWARE() in your program.
|
@star297 Do you have a place where I can learn how to perform ota updates from the firebase storage? I tried looking at the library you included, but I'm not that experienced so I need some help with it. |
Create a Firebase account here: You can look at our updater for some instructions: |
@star297 Thank you for the quick reply. Yeah I need it for a product that I'm making, so it's potentially (fingers crossed) going to be hundreds of devices worldwide. Therefore, I need the device to support future updates, so not only will I be able to update the mobile app, but also the esp32 device. |
If you are developing a app mabe put a update feature in the app that could
"post" the update from the app.
1 - check for update on server using app.
2 - download update in app.
3 - post update from app.
… |
Why would I go through all that when I can just do an OTA update from the esp32 straight away. I'll basically tell the esp32 to update by sending a message via BLE (which is what the app uses) when a button is pressed on the mobile app. So that the esp32 can do its job and just fetch the bin file. |
You do you, I was just suggesting that since you would not need to store a
certificate in the esp32 for secure server connection.
Le lun. 17 mai 2021 7 h 39 p.m., ziadalkalza ***@***.***> a
écrit :
… Why would I go through all that when I can just do an OTA update from the
esp32 straight away. I'll basically tell the esp32 to update by sending a
message via BLE (which is what the app uses) when a button is pressed on
the mobile app. So that the esp32 can do its job and just fetch the bin
file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3909 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHBFDCQ26LC5GESWYT7U7A3TOGSLLANCNFSM4MIPUDSA>
.
|
We found using Firebase Storage the best solution for multiple remote ESP32 device ota updates in our case. We have used ESP8266 with 4Mbyte Flash, but we needed more analog functions. |
@star297 Yes this was my initial approach, but I can't seem to find a way to:
|
Ok I think for a secure anonymous connection to the Firebase storage, all we need is to include the host link and the secrets authentication token in the device firmware. Conversely, if you want to use proper user sign in, you'll need to include the email and password. Is my understanding correct? Or is there something I'm missing regarding this aspect of the code? |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions. |
is anyone even maintaining this? |
Hello, I have the same issue, and I'm trying to delete the lines you attached here, but it seems the source code of Updater.cpp has changed. Could you please give me the exact lines I must delete in Updater.cpp? Best regards, |
I'm doing an OTA update from an HTTP server using the example. https://github.com/espressif/arduino-esp32/blob/master/libraries/Update/examples/AWS_S3_OTA_Update/AWS_S3_OTA_Update.ino
I have it working now but I had to modify the Update.cpp file because I was getting an error: 8 even tho my magic bytes are starting correctly.
I deleted https://github.com/espressif/arduino-esp32/blob/master/libraries/Update/src/Updater.cpp#L218-L221
Now it works perfectly. I'm assuming this is a bug... I found an old issues post on here #325 that describes this problem but it has been closed a long time and it doesn't seem that the issue was fully fixed...
Is there any way to fix this other than modifying the library files?
The text was updated successfully, but these errors were encountered: