search

betaflight / betaflight.com

49 stars 75 forks source link

Board support notices #224

Closed khari05 closed 7 months ago

khari05 commented 1 year ago

Hi there, I just wanted to let you know that the current wiki still includes the STM32F3Discovery as a supported board target. I understand that it is technically supported but you might want to add a deprecation/old firmware warning to the STM32 dev board page for the F3 board.

github-actions[bot] commented 11 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

github-actions[bot] commented 11 months ago

Issue closed automatically as inactive.

haslinghuis commented 11 months ago

Agree the board sections needs updating as we already use a board link in configurator for easy access.

github-actions[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

github-actions[bot] commented 9 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

fbdfbd3371 commented 8 months ago

Good afternoon! Please tell me why the mpu6000 gyroscope is listed in the wiki on board tmotorf7. The website https://store.tmotor.com/product/f7-flight-controller.html lists the BMI270 gyroscope. Thanks a lot!

nerdCopter commented 8 months ago

Good afternoon! Please tell me why the mpu6000 gyroscope is listed in the wiki on board tmotorf7. The website store.tmotor.com/product/f7-flight-controller.html lists the BMI270 gyroscope. Thanks a lot!

Generally, hardware manufacturers change gyro chips at will without regard to software that supports them. TMOTORF7 has had several versions with the following gyros: BMI270, ICM42688P, MPU6000, MPU6500.

Docs are also stale and being worked on.

github-actions[bot] commented 7 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

github-actions[bot] commented 7 months ago

Issue closed automatically as inactive.