Yes, you should see "DFU" in Betaflight Configurator where the COM port is usually listed.

Check in Windows Device Manager what device appears when you connect the FC in boot mode.

(11-Aug-2021, 12:42 PM)SnowLeopardFPV Wrote: Yes, you should see "DFU" in Betaflight Configurator where the COM port is usually listed.

Check in Windows Device Manager what device appears when you connect the FC in boot mode.

i see that :
https://i.imgur.com/gGWgUA5.png

but i don'k exactly know how to fix because as i said i pushed long enought the bootloader botton before and a bit more the windows noise that is been connected a new device.

what i should do ?

there are different guide on youtube, one seems to use ImpulseRC but i don't exactly understand how to do that:



when you lunch that programm "impulseRC" you have to connect the drone to pc in bootloader mode (with the button pushed down) ?


here on devices and printers in windows is showed this other thing: https://i.imgur.com/nOctsAu.png
"driver non disponibile" > "drivers not available" and below: Stato: sono necessarie operazioni > "are necessary operations"

i tried even on a second pc and when i press bootloader botton and connect to pc using usb i only see the COM4 port !

Run Zadig and and install the "WinUSB (v6.1.7600.16385)" driver. The connected "STM32 BOOTLOADER" device should then appear under "Universal Serial Bus devices" (instead of under "Other devices" with a yellow exclamation mark against it). Then try flashing the Betaflight firmware again from Betaflight Configurator.

(07-Aug-2021, 10:53 AM)SnowLeopardFPV Wrote: You can safely upgrade from Betaflight 4.2.2 to Betaflight 4.2.9 if you want to. If you do so you will get any bug fixes and small enhancements that were made between Betaflight 4.2.2 and 4.2.9.

First run both the "dump all" and "diff all" commands in the Betaflight Configurator and save the output to files on your computer. Then flash Betaflight 4.2.9 firmware using the GEPRCF405 target ensuring that you have "Full chip erase" switched on. Then connect Betaflight Configurator to your FC and click on the "Apply Custom Defaults" button when the prompt to do so appears. Then go to the CLI tab and copy/paste everything from the "diff all" file you saved into the CLI text box and press <ENTER>. That is all

(11-Aug-2021, 07:50 PM)SnowLeopardFPV Wrote: Run Zadig and and install the "WinUSB (v6.1.7600.16385)" driver. The connected "STM32 BOOTLOADER" device should then appear under "Universal Serial Bus devices" (instead of under "Other devices" with a yellow exclamation mark against it). Then try flashing the Betaflight firmware again from Betaflight Configurator.

At the end yesterday evening i solved using "ImpulseRC_Driver_Fixer", i connected the drone to pc and i launched that software and then when i boot the drone in bootloader mode it immediatly was in DFU mode.

and i did the upgrade of fw.

(07-Aug-2021, 10:53 AM)SnowLeopardFPV Wrote: You can safely upgrade from Betaflight 4.2.2 to Betaflight 4.2.9 if you want to. If you do so you will get any bug fixes and small enhancements that were made between Betaflight 4.2.2 and 4.2.9.

First run both the "dump all" and "diff all" commands in the Betaflight Configurator and save the output to files on your computer. Then flash Betaflight 4.2.9 firmware using the GEPRCF405 target ensuring that you have "Full chip erase" switched on. Then connect Betaflight Configurator to your FC and click on the "Apply Custom Defaults" button when the prompt to do so appears. Then go to the CLI tab and copy/paste everything from the "diff all" file you saved into the CLI text box and press <ENTER>. That is all

So now i have to copy exactly all that text:



even the first parth "Betaflight / STM32F405 (S405) 4.2.2"

in the CLI ?

or i could do "carica da file" >> "upload from file" ?

https://i.imgur.com/pGTkSvK.png

(12-Aug-2021, 11:50 AM)Rosssiiii Wrote: So now i have to copy exactly all that text:

even the first parth "Betaflight / STM32F405 (S405) 4.2.2"

in the CLI ?

or i could do "carica da file" >> "upload from file" ?

https://i.imgur.com/pGTkSvK.png

You can use either method. Copy/Paste or load from file. Both will do the same.

Any lines with a "#" at the beginning just gets ignored. They are "comment" lines.

(12-Aug-2021, 12:01 PM)SnowLeopardFPV Wrote: You can use either method. Copy/Paste or load from file. Both will do the same.

Any lines with a "#" at the beginning just gets ignored. They are "comment" lines.

1) But in my case, where probabily Custom Defaults are stock of betaflight, and i personaly didn't make any changes, is however required to restore the "diff all" file ?

2) is there a fast way, to see if settings with which I received my drone and which I had backed up are the basic settings of betaflight?

(12-Aug-2021, 12:09 PM)Rosssiiii Wrote: 1) But in my case, where probabily Custom Defaults are stock of betaflight, and i personaly didn't make any changes, is however required to restore the "diff all" file ?

2) is there a fast way, to see if settings with which I received my drone and which I had backed up are the basic settings of betaflight?

1) It doesn't matter. As long as you clicked the "Apply Custom Defaults" button after flashing new firmware then Betaflight is clever enough to figure out which settings you apply are actually different from the custom defaults. If you end up re-applying the same value to a setting then it just remains the same. Betaflight has a record of the default values stored in memory from when you flashed the firmware.

2) Only by comparing the settings in your "diff all" backup file with the settings of a "dump all" from the FC straight after you flashed new firmware to it and applied the custom default settings.

I would just leave it on 4.2.2 myself. I don't think of any new features have been added between .2 and .9. Unless there was a problem on 4.2.2 I don't see a reason to change it.

(12-Aug-2021, 12:15 PM)SnowLeopardFPV Wrote: 1) It doesn't matter. As long as you clicked the "Apply Custom Defaults" button after flashing new firmware then Betaflight is clever enough to figure out which settings you apply are actually different from the custom defaults. If you end up re-applying the same value to a setting then it just remains the same. Betaflight has a record of the default values stored in memory from when you flashed the firmware.

2) Only by comparing the settings in your "diff all" backup file with the settings of a "dump all" from the FC straight after you flashed new firmware to it and applied the custom default settings.

Hello
with "It doesn't matter" you mean that is not necessary restore previously backup that i made considering that was with lot probability a stock betaflight backup because as i listened on youtube eachine didn't changed anything.
i say that because i'm not sure to have interpreted well the first expression...so better a more conferm then crash because i didn't understand that thing 

then i continued to work on the base configuration and i generated that "diff all" to ask you some advice if there is something else easy important to do that maybe i missed :
Actual diff all: https://drive.google.com/file/d/11Kx0Ans...sp=sharing

backup diff all: https://drive.google.com/file/d/1_2KPiJa...sp=sharing

I don't have a factory CLI dump for the Eachine Wizard X220 V2 so I can't do any comparisons, but if you flash new firmware, then click "Apply Custom Defaults", then run in the original factory CLI diff all, then run a new "diff all", that last "diff all" will then contain all of the real differences that Eachine made to the default firmware settings that you can then use going forward.

(15-Aug-2021, 11:27 PM)SnowLeopardFPV Wrote: I don't have a factory CLI dump for the Eachine Wizard X220 V2 so I can't do any comparisons, but if you flash new firmware, then click "Apply Custom Defaults", then run in the original factory CLI diff all, then run a new "diff all", that last "diff all" will then contain all of the real differences that Eachine made to the default firmware settings that you can then use going forward.

Hello

that was original dump all file: https://drive.google.com/file/d/1IuB4vUJ...sp=sharing

Diff all indicates only chages that i made from Custom Defaults and for it are indicated only these things that i changed so far:


that is current dump all: https://drive.google.com/file/d/1_bw7lFo...sp=sharing

here are showed all settings ,please let me if i set something important wrong !