i can not understand, i like to change my rx config, graphical application doesnt work, stucks or just doesnt change. various quads, even on the old bfc and on actual ones. on different pc and quads same result, i dont believe its anything hardware related from my side.
someone else get these issue? i have same problem on osd tab, its just a gamble, maybe it saves it after many tries. 

its a brushed whoop on bf 4.0, i just like to check if it still works, long time ago i got annoyed by betaflight wont loose my time on something like that


someone know the cli command to set spi in the cli?

thanks in advance for any help

I'm guessing that you are using the latest version of the Betaflight Configurator (10.8.0) with an FC that has Betaflight 4.0 on it. There is probably a bug in the new configurator when trying to use it with some of the older Betaflight firmwares.

You could try Betaflight Configurator 10.5.1 (HERE) which was released at the same time as the Betaflight 4.0.x firmware.

Alternatively, the following CLI commands will set the receiver to be a Flysky SPI receiver...

thank you snow

turned out it was just me, it was another board than i thought, one with frsky spi and additional i didnt recognize it was bf4 performance edition for f3, so rx settup on firmware target.
after all i got my old brushed whoop back in the air :-) didnt fly that bad on a good 300mah battery, will be fun to compare different ages of whoop culture on the track :-)

I have the same Betaflight performance edition firmware on my CrazybeeF3 FC equipped UK65 whoop with just the FrSky SPI receiver protocol compiled into it.

When firmware is streamlined like that with less features actually compiled into the firmware itself, unfortunately Betaflight Configurator has no way of knowing what features the firmware has been compiled with and thus still presents you with a full list of the hardware options to choose even if the firmware isn't capable of using some of those options. If you happen to choose an option that the FC isn't capable of, the setting just reverts back when you reboot the FC. At least that explains what your issue was