Skip to content
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

Add new target SPEEDYBEEF405V3S #517

Closed

Conversation

SpeedyBee-OSS
Copy link

SPEEDYBEEF405V3S and SPEEDYBEEF405V3 are the same FC board, we changed BMI270 to ICM42688 in SPEEDYBEEF405V3S.
Due to ICM42688 align changed, we need add a new target to separate it.

@ot0tot
Copy link
Contributor

ot0tot commented Aug 10, 2024

This target cannot be approved as already explained on the Discord.

Due to the motor resource assignments chosen, this FC requires using burst or bitbang DMA to generate the motor outputs. In either of these modes, they gyro is not assigned DMA because of an issue with the F4 MCU. The only reason this kind of works on the F405V3 is because the BMI270 gyro has a 3.2kHz sample rate and it's possible to read in polled mode. The ICM42688p has an 8kHz sample rate, and cannot be read in polled mode without requiring significant CPU overhead. Combined with having blackbox and OSD on a shared SPI bus, this FC is a complete non-starter.

This is the most poorly designed FC of the modern era, and a large part of the reason the Betaflight partners program exists is so this never happens again. Please discontinue this design and move on to the V4. This target will not be approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants