LibrePilot Forum
Development => Firmware General => Topic started by: Flat81 on April 11, 2016, 04:00:43 pm
-
Hello,
about me . My name is Erik , am 34 years and I'm from Bremen . I have a problem with my CC3D Revolution . I had flashed Race Flight on it and would back to Librepilot. But I can`t. In Ground Control Station , the board is no longer recognized . But I can access with a USB Adapter to the board . But I need a bin file for my CC3D Revolution . In Race Flight I can flash only a .hex file . Or is there another solution ?
I did that.
http://www.southquay3d.com/index.php?route=news/article&news_id=9
Thank you.
-
You need ef_revolution.bin from https://librepilot.atlassian.net/wiki/display/LPDOC/Downloads
Firmware archive: all_fw1509.tgz
ef_ is entire flash bootloader+firmware so once that is flashed you are ready to go.
There is no such a board as Revolution, I assume you must have Revolution board.
-
"Revolution" doesn't exist, there is Revolution boards and CC3D boards... not the same board.
For revolution board you don't need FTDI
See more info here:
https://forum.librepilot.org/index.php?topic=208.0
-
I thank you first for the quick responses!
FTI is required. The USB connection is not detected. USB VCP Function does not work.
Or can you tell me how to do it ? ???
-
Or can you tell me how to do it ? ???
Follow link i posted just above ?
SBL pads + dfu-util, directly via USB
-
Im in DFU Mode! But Openpilot GCS didnt see my FC.
-
With dfu mode you don't use GCS
You may flash a bootloader first with dfu-util and next flash firmware using GCS or flash directly the entire flash (ef_revolution) with dfu-util.
Again, follow and read the link i posted.
-
Short SBL and plug the board into USB and type:
dfu-util -d 0483:df11 -c 1 -i 0 -a 0 -D whateverfile.bin -s 0x08000000
I have the File on my Desktop. Now i open cmd.exe. And than??? Need help. :-[
-
For dfu use you first need to install the Zadig driver.
http://zadig.akeo.ie/
Connect your Revo with SBL pads soldered.
Download and Start Zadig software, you may see "STM32 Bootloader" displayed.
Click button "Install driver"
Download archive attached to this message
Decompress archive's contents
Double click the "Flash_revo.bat" file.
(https://forum.librepilot.org/index.php?action=dlattach;topic=1330.0;attach=2460)
Wait until flash is finished.
Hit any key to close CMD window
Remove solder join between SBL pads
Connect to GCS
-
OK. That with the flash_revo.bat worked well.
Only the Led on Revo is now green all the time.
And is not recognized by GCS.
In Windows Device Manager the Board is listen as STM32 Bootloader. Raceflight Flash works fine, i tested it again.
-
Did you really remove the solder join between SBL pads ?
-
Did you really remove the solder join between SBL pads ?
Yes. Did it several times. :(
-
If the board still recognized as "stm32 bootloader" there is something wrong with your SBL pads.
-
I thank you 1000 times . I again checked with a magnifying glass . It was a small compound . Thank you thank you thank you.
;D ;D ;D ;D ;D
It works!!!
-
::)
-
Added a wiki page for board recovery using DFU.
Updated windows dfu_script for Revolution, RevoNano and Sparky boards.
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+DFU
-
I've had much trouble with this. I tried to flash Raceflight but something was corrupt during the process. revo would no longer connect via usb and would only show solid green led, SBL pads not shorted. I tried dfu_util method with no success. i have now tried method detailed herehttp://www.southquay3d.com/index.php?route=news/article&news_id=9 (http://www.southquay3d.com/index.php?route=news/article&news_id=9) and flashed ef_revolution.bin successfully.
I still have no usb activity on PC but leds are active. solid green and pulsing long blue and short orange.
stm32 Bootloader not visible in Zadig either... running out of ideas.
-
You re-flashed the firmware via SBL on a UART, right? I suspect your USB is bad. The easiest way to test this is to short the SBL pad and plug the board into your PC. You should get an STM32 DFU device added. If you don't get that, then your USB is probably bad on the board. You can watch for the device being added either in the device manager in Windows or using dmesg on Linux. Even if you don't have the right drivers on windows it should add some USB device and will call it unknown.
-
Have you tried a different USB cable and different USB port on the computer? Bad USB cables are way more common than most people think.