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
Kakute H7 Mini 4.3-RC4 locks up when performing certain actions #11506
Comments
Yes confirm - sometimes it works all the time other times there is no port detected after the reboot took place. In this case Windows gives the following warning: See also: #11417 |
Ahh, much appreciated. Ill keep an eye on that. Thanks! |
may be fixed in master - please test - by #11524 |
@thujones which compass is that module using? Can you try setting mag_hardware manually in cli to the compass that's on the module? |
Closing as stale. |
Describe the bug
When using Betaflight 4.3-RC4, Flight controller appears to lockup after saving most configuration settings. Flash pattern appears to be 4/5 rapid flashes followed by 5 or so slow flashes. Non responsive until power cycled.
Note, however, settings that were applied do appear to stick
To Reproduce
Backed up 4.3-RC3 config via diff
Full chip erase and flash with 4.3-RC4
Apply custom defaults after first initialization
Apply diff
During diff apply the usual beeps and bloops that one would hear do not appear to be happening
Restart flight controller, appears fine, all settings I expect to be there are there
Make a change to ports (for example was retuning GPS to change baud rate)
Upon save and reboot operation, flight controller goes into described lockup state
Reflashed full chip erase again, attempt to set up from scratch no diff (only applying custom defaults) results in same behavior when save/rebooting basically anywhere
Reverted to 4.3-RC3, apply diff, and normal function resumes without issues
Expected behavior
Flight controller configuration
Flight controller
Holybro Kakute H7 Mini - From US retailer RDQ
Other components
How are the different components wired up
No response
Add any other context about the problem that you think might be relevant here
At first I was coming to this RC4 from flashing Ardupilot and testing it. Thought maybe that might have something to do with it, but I cant imagine what since the full chip was erased to reflash. Figure its worth mentioning at least
The text was updated successfully, but these errors were encountered: