This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
misc:hacks:betaflight [2017-04-07 17:01] theseankelly [What's Supported] |
misc:hacks:betaflight [2017-04-23 17:07] theseankelly [Building] |
||
---|---|---|---|
Line 19: | Line 19: | ||
===== Building ===== | ===== Building ===== | ||
- | <WRAP center round info> | ||
- | TEMPORARY: As of this writing, the changes for the Crazyflie 2.0 target have not been merged back into the Betaflight repo -- temporarily working out of a [[https:// | ||
- | </ | ||
Execute the following from a bash shell (uses the same toolchain as the crazyflie-firmware project -- this can be done on the [[projects: | Execute the following from a bash shell (uses the same toolchain as the crazyflie-firmware project -- this can be done on the [[projects: | ||
- | - git clone https:// | + | - git clone https:// |
- | - git checkout cf2 | + | |
- export TARGET=CRAZYFLIE2 | - export TARGET=CRAZYFLIE2 | ||
- make | - make | ||
- | You should see " | + | You should see " |
===== Flashing ===== | ===== Flashing ===== | ||
To flash the board, follow the [[https:// | To flash the board, follow the [[https:// | ||
- | These instructions call for booting with the BOOT0 pin held high to boot the chip into DFU mode. The Crazyflie can be [[projects: | + | These instructions call for booting with the BOOT0 pin held high to boot the chip into DFU mode. The Crazyflie can be [[projects: |
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. 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. To change the driver, follow these steps: | ||
Line 50: | Line 46: | ||
To use a client that uses the legacy commander packet type (cfclient, mobile apps, older versions of DeviationTx) ensure the max roll/pitch angles are set to 50.0 degrees and the max yaw rate is set to 400deg/s. The handler for this packet type rescales the degree setpoint into a PWM-style value (range of 1000-2000) and assumes these values as max values when making the conversion. Using other values should work but might produce unexpected results. | To use a client that uses the legacy commander packet type (cfclient, mobile apps, older versions of DeviationTx) ensure the max roll/pitch angles are set to 50.0 degrees and the max yaw rate is set to 400deg/s. The handler for this packet type rescales the degree setpoint into a PWM-style value (range of 1000-2000) and assumes these values as max values when making the conversion. Using other values should work but might produce unexpected results. | ||
- | Using the new CPPM Emulation commander type (supported in [[https:// | + | Using the new CPPM Emulation commander type (supported in [[https:// |