-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
Create a new special intermediary firmware #4
Comments
You could skip some of the unplugging with soft resets: /~https://github.com/trezor/trezor-mcu/issues/438 |
Yes, I had a terrible experience attempting to upgrade an old Trezor to the latest firmware (since the new firmwares are too big for the old bootloader). |
This comment has been minimized.
This comment has been minimized.
We will create a new "artificial" firmware, which will perform the first upgrade and then the second one right away. Of course Wallet/Suite needs to support this. We might also do the soft resets while we are at it. |
Just a little irritating question on possible delivery date of this feature @ZdenekSL |
So to recap the strategy from intermediate FW's point of view:
|
This bundles the bootloader.dat file. That is the bootloader latest 1.8.0 version right? Could we build a new version 1.8.1 from master and include that one? It includes some new features such us the soft-reset so we should update to the latest IMHO. Is there any reason not to? |
It's the exactly same version that is used for normal firmware (it's a symlink). So it's either 1.8.0 or 1.8.1. |
Let's test this when it is in Suite, that means after trezor/trezor-suite#2338 is implemented. |
To make onboarding easier let's create a new firmware, which will update bootloader to its newest version and firmware to the newest version, so user does not have to update (and unplug) its device several times.
The text was updated successfully, but these errors were encountered: