80 t. (zaktualizowano 80 t.)
Bricked My FC After Betaflight Update: What Went Wrong?
Well, this is a first. Updated Betaflight from 4.2.5 to 4.3.1. Had to reset motor protocol, no big deal, but vtx info was gone. Loaded VTX table, everything errored out. Reloaded original firmware, reflashed to 4.3.1.
I bricked the FC. Busted it before it ever left the ground and for some reason, I CAN'T STOP LAUGHING.
😮 1
80 t.
Autor
I think there is a chance I can save it. I don't even know what version of BF is on it right now, but it still binds to my Boxer. So. Freaking. Weird.
Odpowiedz
80 t.
I had this issue before flashing a Flywoo. I ended up going back to original firmware and putting back in the CLI I backed up to the computer and everything went back to normal.
Odpowiedz
80 t.
Autor
I'm really hopeful I'll be able to do that. Problem is, I'm playing with it at work. On the .gov workstations. I'm pretty sure I messed something up running it through the VPN/firewall when pulling the download file.
Odpowiedz
80 t.
Oh I see. Yeah I work on a .gov computer too and that might be your issue. Do you have your CLI dump backed up at home by chance?
Odpowiedz
80 t.
Autor
I do. Thankfully, I was having the same issue at home. Immersion RC driver fixer solved the issue and I was able to grab a clean copy of the CLI, so very hopeful.
Odpowiedz
A
Dodaj komentarz