- Posts: 24
Is Devo 12E supported by the Deviation Uploader?
- andrej
- Topic Author
- Offline
Is it feasible to flash the device with the current Deviation Uploader? The uploader refuses to automatically create a filesystem in this case. I assume I could connect it via USB in the mass storage mode after firmware flashing, format the device manually as vfat and populate it from a v5 Devo 10 firmware build, as recommended here . But my assumption may be totally wrong and I definitely wouldn't like to brick this thing. This forum post says that Devo 12E is indeed not supported yet.
I tried to look at the (recommended) Dfuse tool from Walkera, but the archive contains a strange file with a name ending in ".exe". That definitely won't run on any of my systems. Is there perhaps a development build of the Deviation Uploader with Devo 12E support?
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Please Log in or Create an account to join the conversation.
- Deal57
- Offline
- Posts: 857
Deviation Devo7e 3way switch mod, A7105, NRF24L01
Devo6s 2x2 switch mod, trim mod, haptic, multimodule, A7105, NRF24L01, CC2500
Devo12e 4-in-1 with voice mod -- it speaks!!
Please Log in or Create an account to join the conversation.
- Moeder
- Offline
- Posts: 796
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Firing Root
Determining device status: statue=dfuERROR status=10
dfuERROR, clearing status
Determining device status: statue=dfuIDLE status=0
dfuIDLE, continuing
Determining device status: statue=dfuIDLE status=0
dfuIDLE, continuing
Setting address pointer to 0x8000400
Poll timeout 104 ms
bytes_per_hash=1024
Starting device read
Hotplug detected
Found: Runtime [00483:df11] cfg=0, intf=0, alt=0, name='1155:57105:@Internal Flash :@SPI Flash: Config:@SPI Flash: Library'
Determining device status: statue=dfuUPLOAD-IDLE status=0
aborting previous incomplete transfer
Determining device status: statue=dfuIDLE status=0
dfuIDLE, continuing
Determining device status: statue=dfuIDLE status=0
dfuIDLE, continuing
Setting address pointer to 0x8000400
Poll timeout 104 ms
bytes_per_hash=1024
Starting device read
Device Interface Start End Size Count
DEVO_UNKNOWN
0 08004000 0803ffff 2048 120
1 00002000 0001ffff 4096 30
2 00020000 001fffff 65536 30
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
- Download a spyware VirtualBox appliance from here , 64-bit, version 10, "stable".
- Configure the virtual appliance (roughly) like this. (It will definitely work with less CPU and RAM, but my machine has 32 CPUs and 128 GB of RAM, so I don't care that much.)
- Configure USB forwarding for the virtual appliance like this:
- Start the virtual appliance.
- Download the Dfuse USB upgrade tool from here , version 3.0.5 .
- Avoid zadig _like_ _the_ _plague_; it won't help in this case. One needs to do the following instead (in the running appliance):
- Install the Dfuse USB upgrade tool in the appliance. That will also unpack a suitable driver for the DFU device (see below).
- Plug in your Devo in the DFU mode (power on while holding EXT) and wait until it gets connected to the appliance and initialized. It will be called something like COM5, blabla, not working.
- Go to Device Manager in the appliance and choose to update the driver for the DFU device manually. Point the driver updater to C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.5\Bin\Driver\Win8.1\x64
- Start the DfuSeDemo application in the appliance. It should see the DFU device now.
- Flash the device with the Deviation firmware for Devo 12E from the end of this thread using the tool you installed; for some reason it's called DfuSeDemo. The tool should recognize and display that it's a Devo 12E that you're connecting.
- Stop the VirtualBox appliance.
- Connect the device in mass storage mode (hold ENT while powering on).
- Format the device that appears (happened to be /dev/sdh in my case; check dmesg for yours) as FAT12, e.g. like this: mkfs.vfat -F 12 -n DEVO12E /dev/sdh
- Mount /dev/sdh (or whatever device this is on your system) and copy a Devo 10 filesystem into it, either from an existing Devo 10 (my case) or from the v5.0.0 Devo 10 zip image; simply copy the following files from the archive into the new FAT12 filesystem:
- Unmount, disconnect, power cycle the Devo 12E and you're good to go.
Please Log in or Create an account to join the conversation.
- Moeder
- Offline
- Posts: 796
It should probably just have worked with deviation uploader, as it reads the device flash areas correctly. Could you please share the output of lsusb for the devo device?
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Bus 003 Device 018: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0483 STMicroelectronics
idProduct 0xdf11 STM Device in DFU Mode
bcdDevice 2.00
iManufacturer 1 STMicroelectronics
iProduct 2 STM32 DFU
iSerial 3 DEVO-12E㘠ᙍ姿힂̸ㄅQ
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 45
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 64mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 2
iInterface 4 @Internal Flash /0x08004000/00*002Ka,120*002Kg
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 2
iInterface 5 @SPI Flash: Config/0x00002000/030*04Kg
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 2
iInterface 6 @SPI Flash: Library/0x00020000/030*064Kg
Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType 33
bmAttributes 11
Will Detach
Manifestation Intolerant
Upload Supported
Download Supported
wDetachTimeout 255 milliseconds
wTransferSize 1024 bytes
bcdDFUVersion 1.1a
Device Status: 0x0000
(Bus Powered)
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Moeder wrote: Hehe, that seems a little overkill on cpu and ram for running dfuse
It should probably just have worked with deviation uploader, as it reads the device flash areas correctly. Could you please share the output of lsusb for the devo device?
So I tried to flash the Devo 12e with the Java flasher, but it didn't work. It just says "Copy complete" immediately and does nothing.
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
EDIT: This can be fixed using the DfuSe USB Upgrade tool (version <3) instead of the DfuSeDemo tool (version >=3). Not sure where the difference is, but the older tool identifies and flashes the Devo 12e just fine.
Please Log in or Create an account to join the conversation.
- Deal57
- Offline
- Posts: 857
The Java Uploader doesn't see the Devo 12e as anything but Unknown, so it is not usable.
The DFUse 3.05 version sees the Devo 12e will allow you to backup the original Walkera Config, Internal and Library images, and they can be reloaded with 2.31. However version 3.05 will not reliably flash the Deviation images.
Deviation Devo7e 3way switch mod, A7105, NRF24L01
Devo6s 2x2 switch mod, trim mod, haptic, multimodule, A7105, NRF24L01, CC2500
Devo12e 4-in-1 with voice mod -- it speaks!!
Please Log in or Create an account to join the conversation.
- UABMaddog
- Offline
- Posts: 6
I just love Deviation and this group of transmitter hackers.
Any advice for the mods to the 12E? (I have killed one 7E with the infamous pin 13 soldering.....successfully modified 2 others though....LOL)
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Mods that I'd love to see would be Hall effect gimbals, but preferably easy to install, without too much drilling and 3D printing. And an open-source flashing tool that would support the 12E would be very helpful. So that one doesn't need to start NSA (R) Spyware (TM) in a virtual machine for each Deviation upgrade.
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Please Log in or Create an account to join the conversation.
- andrej
- Topic Author
- Offline
- Posts: 24
Once you create the FAT12 filesystem, Devo 12e will not tolerate file replacements or file editing done by mounting it via USB. Your entire filesystem will then become an inconsistent bunch of random characters and presumably, Devo 12e won't boot from it if it gets too bad. It mostly affects the languages/ directory, but also other directories.
The solution is to never overwrite files, not even within one single mount. Simply prepare all your Devo 12e filesystem beforehand, including all the model definitions and all the zip contents highlighted above. Then copy all of it once (wihtout ever overwriting or otherwise replacing / deleting anything on the FAT filesystem) to the Devo 12e, unmount it and don't mount it again, because it seems that even mounting and unmounting the FS a second time turns it into a pile of broken trash.
This is very strange and it doesn't occur on my Devo 10. However, editing and saving models on the Devo 12e works perfectly fine, so internally it doesn't clobber its own filesystem beyond readability. Just the mounts are troublesome.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- General
- General Discussions
- Is Devo 12E supported by the Deviation Uploader?