betaflight Betaflight 3.5.4

[WaF Bot]

Maintenance Release

Please read the Betaflight 3.5 Release Notes.

This release contains bugfixes and target changes only. For a full list of new features see 3.5.0.

We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.

We also have a Facebook Group: If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this here.

Important information when upgrading from an earlier version of 3.5

• a number of users reported issues with the firmware hanging during a diff or dump. The root cause of this was identified as a bug in the MSP protocol causing corrupted configurations. This was fixed in 3.5.1. If you are using 3.5.0, it is recommended that you upgrade to at least 3.5.1, to eliminate the risk of experiencing lockups during diff or dump caused by this bug (#6696);
• unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3, FRSKYF3, RACEBASE, RMDO, SPRACINGF3, SPRACINGF3MINI, SPRACINGF3NEO, and ZCOREF3 (#6815, #6887, #6994).

Fixes:

• Fixed MSC mode issues affecting MacOS (#7145);
• Fixed issues with retry after save in SmartPort / FPort lua scripts (#7182);
• Fixed order of magnitude in GPS altitude reporting in SmartPort / FPort (#7200).

Target Updates:

• Added new target FLYWOOF7DUAL (#7098);
• Added I2C support, removed non-working blackbox flash support on target CLRACINGF7 (#7175);
• Added new target OMNIBUSF4V6 (#7129, #7230);
• Added new target EXF722DUAL (#7184).

Lire la source