To change the driver, follow these steps: Note: If you’ve previously installed the libusb-win32 driver on the Crazyflie 2.0 device node using Zadig in Windows, the driver must be changed before it will enumerate as a COM device after flashing. Note that the Betaflight configurator will reboot the STM32 after flashing but it will not reset the NRF51 – the whole board must be power cycled after flashing in order to restore the NRF51’s Rx functionality. The Crazyflie can be booted in to DFU mode without needing to short this pin. These instructions call for booting with the BOOT0 pin held high to boot the chip into DFU mode. Be sure to choose ‘full chip erase’ for the first flash. To flash the board, follow the Betaflight flashing instructions. You should see “betaflight_3.2.0_CRAZYFLIE2.hex” (version number may be newer) appear in the obj directory of the project. Access to JTAG or SWD is highly recommended and may be necessary to re-provision with the stock Crazyflie firmware/bootloader.Įxecute the following from a bash shell (uses the same toolchain as the crazyflie-firmware project – this can be done on the Bitcraze VM for example) There’s very low risk of bricking or damaging your hardware (the main STM bootloader is in ROM and can’t be erased), but it’s recommended you only try this out if you know what you’re doing and can accept a bit of risk. WARNING: Running Betaflight on the Crazyflie 2.0 is still experimental and in development.
It also doesn’t support many of the crazyflie core features like the logging framework, the parameter framework, etc. The target currently doesn’t support the magnetometer, the barometer, or any expansion decks. Mileage on the other clients may vary – please report findings in the forum. However, currently only DeviationTx and the Android mobile app have been tested. The NRF51 code was intentionally left unchanged so all existing crazyflie clients ought to continue working without modification (including Bluetooth clients). This target currently supports basic functionality required to fly - motors, accel/gyro, LEDs, and handling of the syslink/crtp protocols (though, limited to commander packets) from the NRF51. One of the hallmark features of the Betaflight/Cleanflight/Baseflight ecosystem is support for an extensible “target” framework which allows the firmware to run on a wide variety of ARM chips/boards. Betaflight was originally an R&D fork from Cleanflight focused on bleeding edge performance improvements/experiments but has since become one of the most popular flight controller firmwares in use today.
0 kommentar(er)
