Boot loop starts before I can write these values to CLI in case they have anything to do with stopping the Boot Loopĭiff CLI dump version INAV/MATEKF722SE 2.1.0 / 18:49:07 ( a5a92b5) GCC-7.3.Frequently when there is a commuter issue with theįlight controller in Windows, you might get errors when press the button “Flash Firmware”. I had success with the Dec 26 2.1.0 firmware and also failure with it and others.Īdditional context This version was working fine. I also have a DIFF dump from the functioning iNAV 2.1 variant from Dec 26 if that helps. I'm happy to put iNAV on to help with the troubleshooting if asked. Like in Issue #4076, I'm keeping this F722-SE on Betaflight until hoping the bugs can be resolved. Betaflight on the board also functions properly for DFU mode with GPS and SBUS and all other Serial devices connected whereas iNAV firmwares required them to be disconnected. Once a successful DFU is connected, the FC can be installed with iNAV but only to have it Boot Loop before any CLI settings can be examined to troubleshoot OR it can be installed with Betaflight and all of the problems go away. after much frustration, the RC1 version was released so I hoped this communication would be fixed and installed the RC1 firmware and the Boot Looping started again and it happened with EVERY iNAV 2.1 firmware attempted.Īlso, the ONLY WAY to get the FC recognized by Windows 10 with Zadig and ImpulseRC was to unsolder the 5V power to the GPS and R9-SBUS otherwise ImpulseRC would report and error of: "Unexpected number of devices detected" and FC would NEVER get into DFU and be recognized by windows. I could not get the Sik radio to communicate with the FC on UART3. I fully configured my quad with compass and mag. It seems that by fluke only, the Dec 26 version installed and Boot Looping stopped. The Nov 20 version resulted in Boot Looping and each time it happened it would be necessary to fix windows with Zadig and then the ImpulseRC tool. I installed the iNAV firmware from the Matek website (after the versions in the configurator failed with Boot Loops) which offered TWO variants of 2.1.0 at the time. I very recently completed a 250mm Quad build with a Matek F722-SE board and Betaflight 3.5 installed flawlessly. I think this problem in Issue #4076 still persists.
0 kommentar(er)
