-
Notifications
You must be signed in to change notification settings - Fork 3
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
Documentation: How to create the tup files for the OTA update #127
Comments
Have you read this? Maybe it already helps. But I agree it could be extended a bit. Maybe you want to do it😋? So basically you need to build the tool first which is relatively easy. We can provide the binary with the releases in the future as well. Then you you create a folder and call it how ever you want. You build the ui and the firmware and copy both to the folder. The ui goes into a „ui“ folder inside your newly created folder just like you would do on the SD card. Then in the „.pio“ folder you should be able to finde the „firmware.bin“ when the build of the controller fw is finished. This is copied next the ui folder. Then you run „tupt.exe update.tup <your_folder>“. That’s it😋. |
I'll try to make a guide in the next days 👍🏻 |
After installing g++, choosing the right directory in the command line (update-package-tool folder) and using: the following errors occured. Are my files corrupted or is this a "bigger problem"? `In file included from src\main.cpp:17: |
Should be a relatively easy thing. Your compiler needs support for C++17. This should be the case starting from GCC 8.x. |
Thanks, I will try it 👍🏻 |
correlate with #56 where we plan to build these update packages automatically |
Thanks! Now that makes even more sense to me! Sorry that I didn`t saw this earlier :) |
We now build the Update Tool directly in our workflow First artifact see here @PhilippDenn: https://github.com/TheRealKasumi/TesLight/suites/10578590933/artifacts/526760769 |
To avoid confusion, please note this. |
A step by step manual for non "IT guys" on how to create the OTA update files would be nice ;)
The text was updated successfully, but these errors were encountered: