-
Notifications
You must be signed in to change notification settings - Fork 121
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
TrezorActions: Allow updating firmware. #2816
Conversation
adb9459
to
0309b33
Compare
c9602f0
to
2926e85
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going in the right direction.
Tested with the manually fixed firmware file (stripping the first 256 bytes of the firmware) and it worked on a physical model one.
Only thing I missed, which I'm not sure it's possible, is some feedback that the firmware install process is being performed.
Also, trying to install the wrong firmware makes the trezor set screen hang without detecting a device disconnection.
We are unable to update firmware from TrezorActions.js. This is believed to be due to the size of the firmware and the limitations of this electron child process. We send the firmware to the main process to push to the device. The main process uses a temporary connection to trezor in order to accomplish this.
Even after disconnecting the device? I am not seeing this. Does the trezor have a message about bad headers? |
2926e85
to
f795a76
Compare
Making a simple log of progress, but probably not where we want. For trezor 1 only progress 0 and 100 are announced, but I think model T might give increments in between. I would be good to put a progress bar for the user, but can I make an issue for now? |
Correct. The sequence of events is:
After that, reconnecting the trezor device will "flash" the setup screen (i.e. it disappears for a moment, then reapears). |
Sorry for the erroneous close, misclicked the button. |
Fair enough. |
Thank for the process. I understand now. |
Hopefully this handles failures better. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working great now (modulo the header thing)!
This reverts commit bf54bf8.
Part of #2681
We are unable to update firmware from TrezorActions.js. This is believed
to be due to the size of the firmware and the limitations of this
electron child process. We send the firmware to the main process to push
to the device. The main process uses a temporary connection to trezor in
order to accomplish this.