I've been working on dragging my gear forward to the latest BF and ELRS versions. This FC is doing something I've not seen before. It's a betafpv F4 1S AIO 12A elrs 2.2 (build here) and I have downloaded the latest firmware from betafpv's site: BF4SX1280 4.4.2_M85_A_ELRS v2.2_ELRS 3.0_20230202.hex

When I "auto detect" the quad, BF identifies it just fine. I load the local firmware file and BF shows it is loaded in the bottom left.  I click the flash button, it greys out, and that's it. The FC seems to reset but no flash happened. This happens with 10.9.0 on both linux and windows, with firmware downloaded separately by each OS but from the same, official source.

Any ideas? Is there a log I can check for a clue as to what's actually happening? 

lol. I'm hoping the answer isn't "disconnect the vtx", because I'll have to pull the top plate off and the stack apart to get to the solder points. Besides, it's been a reliable build so far and I'd prefer not to futz with it. Thanks guys!

Sometimes you have to get the FC into bootloader mode. The easiest way would be to connect into BFC. There is a button that goes into bootloader/DFU mode. Or go to CLI and type "bl".

Then flash the firmware.

Oops. I forgot to mention I tried that as well...

If I enter dfu mode from BF then the "exit dfu mode" button is lit on the flash page. It greys out along with the load and flash buttons when flash is pressed. If I restart BF the exit dfu button is lit again. Pressing it removes the FC from dfu mode and I can connect to it again normally with BF.

It might have been an earlier version of configurator, but I had to select ENABLE EXPERT MODE and change drodown to DEVELOPMENT before it would flash a local hex file. Otherwise it just did nothing when I clicked on flash. Not sure if you are encountering something similar, but worth a try.

Hmm. I have expert mode permanently enabled. I poked around in the settings and on the flash page and didn't notice anything related to "development".

Thank you! I will look again when I get home this afternoon...

Okay. It seems the default description for that pull-down is now "choose a board" and lists all the targets alphabetically. No "development" option... I'll try to reach out to betafpv and see what they say... Still open to suggestions.

You have to select show release candidates, then you will see that dropdown. Logically that should only affect what firmware you can select from the list, but it is worth a try.
https://betaflight.com/docs/wiki/configu...l-flashing

Ha! That was it. Thank you sir... Pretty sure I've not had to do that in the past. Of course my memory isn't what it used to be. lol.

Nope it doesn't make sense that you would need to change that setting for a local file and does not seem documented, that's probably why I remember it. Maybe Betafpv devs forgot to set a flag in their hex and somehow it messes up the configurator and prevents the flashing. That's just a guess, but glad it also worked for you.