-
Notifications
You must be signed in to change notification settings - Fork 481
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
Implement bootloader warmboot in the client GUI #473
Milestone
Comments
ataffanel
added a commit
that referenced
this issue
Mar 2, 2021
krichardsson
added a commit
that referenced
this issue
Mar 3, 2021
krichardsson
added a commit
that referenced
this issue
Mar 3, 2021
krichardsson
added a commit
that referenced
this issue
Mar 3, 2021
krichardsson
added a commit
that referenced
this issue
Mar 3, 2021
krichardsson
added a commit
that referenced
this issue
Mar 4, 2021
krichardsson
added a commit
that referenced
this issue
Mar 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to prepare for flashing the lighthouse deck firmware (and any other future deck firmware), we need to be able to bootload the Crazyflie starting from an active connection.
This is called warmboot and it is a much more practical and safer way to bootload the Crazyflie.
In order to implement this functionality, the bootloader GUI as well as the sequencing needs to be modified.
The text was updated successfully, but these errors were encountered: