Advanced Search

Hai,
Im facing the same issue, dfu is recognized by windows and showing STM32 DFU, but not showing in the dfuse updater software. So I decided to update the bootloader via ST-Link v2 device.

could u please send the wiring diagram to connect devo 10 to ST-link v2.

I think it is actually quite simple, I have the same driver issue some times, when using several flight controllers and deviation, it seems windows picks the wrong driver, automatically.... and have been playing with all kind of solutions drivers fixes zadig but could not get it to work reliably. But actually it is simple to sort;

In WIN10,
you have to go to device manager,
go to the STM32 Bootloader of DFU port which does not work, right click it, select update driver,
select browse my computer for drivers,
select let me pick from a list of available drivers on my computer,
There you select,the other Driver than currently selcted. (probabaly there are multiple drivers)
click Next
click close done.

You should see immediately in Dfuse your Tx apear, (assuming you started deviation transmitter, with button pressed in DFU mode, not usb drive mode)

It could be if you want to flash your Betaflight F7 controller in DFU mode you have to go here back again and change it again.....

Or you can upgrade devo 7e into an ultimate Devo 7e, but not for the fainthearted, I have them with voice and is totally fine. (it becomes basically TGSG V2 Plus)
these guides are perfect;
silpstream.com/54/ultimate7e-upgrade-the-devo7e-processor/
silpstream.com/103/ultimate7e-flashing-the-bootloader/

Thats why im asking if anyhas has a guide .. every one using different pins depending on their programmer. I have a ST-Link V2 how will i connect the pins to that ?

are the pins the same as devo 7 ?

Read this topic
deviationtx.com/forum/6-general-discussi...e-bootloader?start=0

hi can someone give a guide on how to burn a new bootloader on a devo 12s ? i cant find anything online.
thnx in advance

Walkera Dfuse V2.31 can't damage bootloader, so it looks like you have hardware problem.

Hi Is there any demonstrate or picture how to do this?
I'm quite not understand.

yes that would work indeed also. But first get it to work with your Frsky Receiver via Smartport at the Flight controller. If all good, you can connect the Tx module smartport to flight controller and flash.


(FYI never happened to me, but with Frsky, always take care when flashing, not disconnect etc etc, Frsky use there own bootloader, if you manage to brick it, damage the bootloader you can throw in the bin..)

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?

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:

Do not use Dfuse 3.0.5, you can damage transmitter bootloader, it's demo version Dfuse, not Walkera Dfuse.

Try write to transmitter USB drive "devo.fs" file from firmware archive.

To use 4in1 module you will need to edit "hardware.ini" file inside ""devo.fs" file. It's not trivial task, search the forum for help.

So I bought a Devention F12E about half a year ago and I really like it.
It is the transmitter I always wanted (well almost, but its as close as commercial transmitters go).
However Walkera receivers are quite hard to get here in germany (they all ship from china) and getting one thats not just SBUS/PPM seems pretty much impossible.
Because of this I checked out Deviation (I already have a lot of DSM2 receivers as I used Spektrum before).
However I get quite a mixed feeling. All the official documentation says the F12E is not really supported.

So what is not supported on the F12E ?
What could happen worst case ?
I assume Deviation does not touch the bootloader, so I could flash back a stock firmware at any time right ?
If there is still important stuff missing for F12E (or generic), I would happily help implementing it (I work as a software engineer in C/C++).
Also is there a reason releases stopped with version 5 almost 4 years ago, despite development going on ?

Sincerely,
Thalhammer

Thanks

I think these bootloaders are original, dumped from Devo transmitters. Except devo7e-256 bootloader, it's modified devo7e bootloader..

Please, anyone?

I have a question about the download section.
I saw that there are bootloaders for all radios.
My question is:

This bootloader are original, or modified?
Thanks

Downloads \ Miscellaneous
Transmitter Bootloaders = You have no rights to access this category
Transmitter Stock Firmwares = You have no rights to access this category