Advanced Search

Monitor the radio for random resets. I went down this route and reverted to DevoOS due to the radio just rebooting for no rhyme or reason. Tried different versions of DevoationTX same issue. Went back to DevoOS and it was fine after that. Sold it now.

This thread is almost 4 years old and clearly no-one has responded in that time. I no longer have an F12E bit remember when I did go down this route I never had an issue with model saving. I do remember there being a correct procedure involved in installing DeviationTX on it due to the limited ram. Perhaps revisit your procedure.

In the end I reverted to DevoOS because I found the radio would randomly reboot using Deviation

Hi Firefoxf18,

I finally got it to work after tinkering with it for a few years

Basically, I followed your link on installing on the F series and it now works.

1. I installed Walkera dfuse on a fresh computer (no previous versions of dfuse or deviation upload).

2. Put the F12E into DFU mode and upgraded with the latest nightly built. (31/7/2020)

3. Switched off the F12E after firmware had been successfully uploaded.

4. Switched on the F12E and it mounted as an external drive.

5. Deleted the Devo.fs file on the F12E and replaced it with the one that came with nightly built.

6. Ejected the usb disk and kept my fingers crossed.

7. Fired up the F12E and it works!!!!

I tried binding with a DSM2 model and connect to a video source. Both with success. And more importantly it saved the settings after powering down.

Will put in the other rf modules in due time. All the best to you.

I am experiencing the same issue. Installed with the latest nightly built, 28/7/2020.

After replacing the flash memory of my f12e, the flash is normal. After a period of time, the latest version in the nightly build that I redrew yesterday started to use the dfusedemo. It shows success, but even if the boot card is in the programming mode, the USB mode will not enter. Then use dfuse USB Upgrade to brush, it shows that there is DFU mode, but it can't be swiped in. At last, it's only with jar that the brush is successful. It can also enter USB mode, and the boot is normal. What's the problem? I want to swipe bootloader again, but how to swipe it with JLINK? God help to solve it!Now it's not good to use the official software brush of Huake after normal operation. It should be usable after replacing flash memory. Why not now?

Recently, after adding three wireless modules to my f12e, I still don't know how to use the xn297 protocol. I have a small four-axis wireless module, xn297. Who can teach me how to use this protocol to compare small airplanes? thank!

How to use ?
is there any ready-made firmware without having to change existing files such as "hardware.ini" to be able to connect all receivers in this 4in1 module.

I tried it but none of them can connect with my devo F12E which has installed the 4in1 module with firmware nightly build V.5.0.0

You will need "BuildFS.exe" to extract, edit "hardware.ini" and create a new devo.fs:

Usage of buildfs.exe is inside buildfs.zip file:
www.deviationtx.com/downloads-new/category/3-miscellaneous

thank you very much, I was able to replace the firmware with nightly build v.5 by deleting the devo.fs file on the usb drive & replacing it with the existing devo.fs file in the firmware folder after extracting.

I will try to connect with eachine e011 & other receivers that support the 4in1 module.

if there is a problem I will give news here.

Okay, I will try to insert the file "devo.fs" from the firmware zip file after extracting it into the USB deviation

Do you try to rewrite this file? It can be damaged or empty. Try rewrite USB drive "devo.fs" file with "devo.fs" file from firmware archive.

It seems that there is already a "devo.fs" file. reads on a computer / laptop in drive G. & After I reboot it still says USB deviation on the screen.

Flash Deviation firmware with Dfuse 2.31, reboot transmitter, you will get "Deviation USB" screen, then copy to transmitter USB drive "devo.fs" file from firmware archive and reboot transmitter.

Right. the screen is always "USB deviation". After that what should I do step by step to complete the nightly build firmware installation.

You can't format Devo D12E USB drive, it has fixed format.

After flashing Deviation firmware with Dfuse 2.31, reboot transmitter, you will get "Deviation USB" screen, then copy to transmitter USB drive "devo.fs" file from firmware archive and reboot transmitter. Without this file you will always get "Deviation USB".

yes and have you tried to format the usb hd in your f12e to format ?

Yes, I returned it to normal. I re-flash with dfuse 2.31 & firmware 1.5A.
Can I still reinstall the firmware so that it can support the 4in1 module. which version of firmware & nightly build to make installation easy using dfuse 2.31 without any failure on the screen, only "Deviation USB" appears.

Yon wrote: After I tried again it turned out that it was really just a problem with the driver.
devo I succeeded in Dfuse. then I flash with firmware v.5.0.0-ac7f63e using the Dfuse 2.31 upgrade tool & found a problem. the monitor screen is just written "Deviation USB".
I was curious to try to flash again with the dfuse 3.0.5 upgrade tool. "Upgrade Program" without having to restore the button.

what should I do to move to a normal position.
Please help

as i know this is normal you have only to format the usb and copy the "rest" to the drive

If you can't get DFU mode (firmware upgrade mode, EXT + Power On), probably you damaged bootloader.

1) You need bootloader file for Devo F12E - "devof12ebootloader.bin"
www.deviationtx.com/downloads-new/catego...nsmitter-bootloaders

2) You need flash bootloader. I don't know how do it with Devo F12E, but for Devo 7e:
silpstream.com/103/ultimate7e-flashing-the-bootloader/
www.deviationtx.com/forum/6-general-disc...-7e-bootloader#34250

connect "RESET" on the Tx to pin 15 (NRST) on the stlink
connect "TMS" on the Tx to pin 7 (TMS) on the stlink
connect "TCK" on the Tx to pin 9 (TCK) on the stlink
connect "GND" on the Tx to pin 20 (GND) on the stlink
connect "Vdd" (3.3V) on the Tx to pin 1 (Vcc) on the stlink

connect MCU BOOT0 (pin 94) to 3.3V (with 1K resistor, first check if pin 94 is not connected to GND).

For the 10pin st-link the connections are:
tms > swdio
tck > swclk
gnd > gnd
vdd > 3.3V

Be sure not to use the st-link 5V line as it will damage the mcu




Power bypass points, 2 pads to the right from "DC IN" connector:

I did the wrong procedure
tell me the link how to return the devo F12E to its normal position?