-
Notifications
You must be signed in to change notification settings - Fork 28
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
nk3 update: generator didn't stop after throw() #394
Comments
Hi! same here when trying to upgrade firmware from 1.0.1 to 1.4.0. Installed within a venv.
Here is the actual try:
|
@samweisgamdschie This looks like a different error to me. Do you have the udev rules installed on your system? |
I'm also getting these errors upon updating my NK3, the last time updating from 1.4.0 to 1.5.0. So maybe this is just a timing issue? If the first attempt to connect to the bootloader fails, just wait a few seconds and try again? Here are my logs: Logfile of failed update
|
@sebastian-de I agree that this looks like a timing issue, but we already re-try the bootloader connection three times with a delay. Unfortunately, neither me nor any of my colleagues can reproduce the issue so it is hard for me to find the point where the delay would be needed. I tried to fix the problem in #378 by adding additional connection checks but it did not fix the problem for another affected user. But maybe you can give it a try too. I’ll try to come up with a different approach to fix this. |
For some users, the NK3 firmware update fails with a
RuntimeError
: generator didn't stop after throw().Workaround:
Run
nitropy nk3 reboot --bootloader
beforenitropy nk3 update
.Full output:
Reports:
The text was updated successfully, but these errors were encountered: