-
Notifications
You must be signed in to change notification settings - Fork 97
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
USB connected w/o battery does not go into bootloader #35
Comments
After some digging I found the problem with the booltoader mode when running from USB power only. It is a bug in the crazyflie2-nrf-bootloader that does not enable 500mA USB current limit. The crazyflie2-nrf-bootloader can be rebuilt with |
There is a (currently undocumented) functionality in the MBS that allows to safely flash a new bootloader and (possibly) BLE softdevice over the air. It requires to flash the new bootloader anywhere in flash and then to write a structure at a specific place in flash. At next reboot the MBS will then check the bootloader CRC, flash the new bootloader, verify that the flash is done successfully and clear the structure. If anything fails, the structure is still there and the flashing attempt will restart at next reboot. This procedure is safe as long as the new bootloader is working. So this is not to be used for development but should be OK for deployment of a tested and released bootloader. Using this functionality likely require change in the bootloader client to handle writing images in different places in flash. |
What is the status of this issue? @tobbeanton |
When the USB is connected and there is no battery connected as well, a long press of the power button does not result the CF2 to go into bootloader mode. LED M2 does start blinking with the long press but upon release it will just restart the CF2
The text was updated successfully, but these errors were encountered: