[[email protected]]

The resurrect fw works. I have recovery as well. Just load the resurrect then load the most current from archive I think it's fw_revo.opfw. Works like a champ


Sent from my iPhone using Tapatalk

[TheOtherCliff]

A version of resurrect has been built into all of the 16.09 versions.

Has anyone found that 16.09RC# did not fix the issue, but using one of these firmwares DID fix the issue?

[VastSky]

OK - I'm stubborn!

My CC3D was working nicely with LibrePilot. I would be very surprised if this a HW issue. I inspected the board for stray solder etc. and everything looks clean.

I read that I could run BetaFlight on it to gain more capability and was seduced. I used STM Flash Loader Demonstrator and a FTDI to flash "betaflight_3.1.0_CC3D_OPBL.bin" and it bricked it! I only have the Green LED on solid (just as it would be if in SBL) and never the Blue LED that once merrily flashed bootloader-bootloader!!
***All recovery attempts were attempted after solder bridging the SBL pins...***

1) Windows 7 Device manager sees it a USB device, but I cannot manually update the driver. Device Manager error: "Windows has stopped this device because it has reported problems. (Code 43)"

2) FTDI (VCCto5v, Rx to TX, TX to RX Gnd to Gnd) connected to MAIN plug (and alternately - Flex) on CC3D  connection attempt: STM Flash Loader Demonstrator reports: "No response from the target the Bootloader cannot be started...

3) Using FTDI and also USB direct to CC3D tried the (Shift+Rclick) CMD (from directory): dfu-util  -d  0483:df11  -c  1  -i  0  -a  0  -D  whateverfile.bin  -s  0x08000000  Since I had nothing to lose, I tried most of the ***.bins

Code: [Select]

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to [email protected]

Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
No DFU capable USB device available
4)  Using FTDI only, tried the (Shift+Rclick) CMD (from directory): stm32flash -w bl_coptercontrol.hex -g 0x0 COMwhatevernumberyourcomportis   Since I had nothing to lose, I tried most of the ***.bins

Code: [Select]

stm32flash - http://stm32flash.googlecode.com/

Using Parser : Intel HEX
COM26: No error

I know these are a throw away, but it has me BEAT!! I'm hoping that nugget of knowledge to resurrect it can be found here.

What FC should I order to replace it with? I'm not a acro pilot - I just float the quad around the sky....

TIA!!

[f5soh]

The CC3D do not support DFU, so the dfu-util cannot work.

The two methods are:
- using FTDI: http://www.southquay3d.com/index.php?route=news/article&news_id=9
- using STlink: https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+ST-Link

[VastSky]

The CC3D do not support DFU, so the dfu-util cannot work.

The two methods are:
- using FTDI: http://www.southquay3d.com/index.php?route=news/article&news_id=9
- using STlink: https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+ST-Link

Thanks!!

It seems the STM Flash Loader Demonstrator is a bit finicky! I let windows update the FTDI driver, changes its Comm port to a low number, set its baud to 9600. It took a number of connection attempts, but the STM Flash Loader Demonstrator finally recognized the target and I was able to get the CC3D working once again.