GEP RC GEP-F722-35A AIO lost Gyro and possibly other ports after flashing BF fireware 4.40 and 4.4.2
upyopyo opened this issue · 12 comments
Describe the bug
Hi, I tried to flash BF fireware from the original version to 4.4.0 and 4.4.2 in order to use newer generation's GPS. And after flashing with sucessful update, Gyro is not detected anymore. (Sorry, I forgot the original BF version, possibly 4.2.x). Before flashing fireware, my drone is working fine.
At the beginning, the firmeware uploading was frozen at initializing step. Then I ran ImpulseRC_Driver_Fixer.exe. Althoguh it finished with error message, now I can upload the BF firewares. Then I tried to flash with 4.4.0 and 4.4.2 and the both don't detect Gyro.
Next I found this link and a magic line for custom defines:
betaflight/betaflight#12138
GYRO_SPI_MPU6000 ACC_SPI_MPU6000
However, it still did not fix my Gyro detection, and now I have no idea how to fix this issue.
Actually I found other issues. Airunit does not output video, and receiver does not receive signal although UARTs set properly as same as before flashing. Thus, I am thinking the problem is not only Gyro, but also other components, too.
Maybe, I am missing very critical process. Please let me know how to fix all, thanks.
These attached screenshots are after flashing frimewares.
To Reproduce
rerun to flash fireware updatings.
Expected behavior
I am expecting to see detect Gyro and
Support ID
*** Support data submitted ***
Id: "2bf4e59c-4bdd-44d7-b9cc-cd98510d3235"Flight controller
GEP-F722-35A AIO
Other components
receiver Futaba
VTX DJI airunit
GPS HGLRC M100_MINI GPS
buzzer gepRC superBuzzer
How are the different components wired up (including port information)
No response
Add any other context about the problem that you think might be relevant here
No response
Please flash core only and submit support ID so we can add hardware defines to configuration.
Thanks for your reply, and I see what you mean!
*** Support data submitted ***
Id: "176ae1e2-0205-4c22-b670-2a706d2d6dbf"
There are I2C errors in status, but still no gyro or baro. For gyro all drivers are included in CORE build. Are you sure you have the correct target (there is also a HD version)? Auto-detect only reads what firmware has been flashed previously.
According to https://geprc.com/wp-content/uploads/2022/05/F722-35A-AIO-USER-MANUAL2.pdf you will need firmware GEPRC_F722_AIO
additionally, 10.9 has a bug that requires "expert-mode" enabled.
or you can use the 10.10-RC1 https://github.com/betaflight/betaflight-configurator/releases/tag/10.10.0-RC1
A
you will need firmware GEPRC_F722_AIO
Yes, I thought too, but there is no exact F722_AIO, and "BT" indicates a stack board item. Mine is a just singal board.
B
For gyro all drivers are included in CORE build.
umm, if you say so, , did I misstake a critical procedure after flashing firmware? At least, I hit 'connect' button' and selected 'apply custom Defaults' button. Then should it be all good, right?
C
10.9 has a bug that requires "expert-mode" enabled.
I tried to do the flash firmware 4.4.2 with 'Enable Expert Mode' ON, but it's the same story, not working. Do you imply to try development versions like pre-release?
additional questions to double check:
D
Do I need to install such Zadig and STM things? Because I can already do the flash Firmware in BF by USB connection, I don't need to do it, right? (Or this could be problem??)
E
There is no AIO version in the list of BF. Should I get a firmeware from official GEP RC website? (I don't think they have the one.)
you forgot the GYRO_SPI_MPU6000 ACC_SPI_MPU6000 defines
but i believe you need as @haslinghuis reported.
FAQ: no gyro, etc: https://hackmd.io/@nerdCopter/ByheaoLQh
I tried the falshing with export mode and GYRO_SPI_MPU6000 ACC_SPI_MPU6000
However, it did not work. Critically Other UARTs also have not working neither since flashing. For instance, a receiver does not work although its power light is up. My guess is I need to downloadd GEPRCF722AIO build from somewhere ??
Great, now All suncion are working, thank you so much!!!!
One last thing is about OSD's GPS satelites info.
WTF cannot get satelite's numbers and home direction although Original OSD shows those values. I guess this issue is from new BF version 4.4. Can you fix this? or should I ask to WTF team?
Discord for "support"; Github for bug-tracking.
for now, I got solution for my first question, then clsoing this ticket. Thanks for the supports!