[pulser13]

Hi everybody!
I have quite the same situation: I had cc3d atom flashed with openpilot SW. When I updated it with librepilot SW, process was interrupted (disconnected USB ). Now I have only green LED lit on the board.

I have tried Resque and Upgrade procedure with connection before and after pushing the buttons. With no effect. Windows shows me "devise not recognized". OS X - no USB port open
However, with "STMicroelectronics Flash loader Demo" with UART FTDI board I can flash "Cleanflight" SW and it works.
What can I do with it? Anybody have bootloader file in HEX?
 

[Mateusz]

Hi everybody!
I have quite the same situation: I had cc3d atom flashed with openpilot SW. When I updated it with librepilot SW, process was interrupted (disconnected USB ). Now I have only green LED lit on the board.

I have tried Resque and Upgrade procedure with connection before and after pushing the buttons. With no effect. Windows shows me "devise not recognized". OS X - no USB port open
However, with "STMicroelectronics Flash loader Demo" with UART FTDI board I can flash "Cleanflight" SW and it works.
What can I do with it? Anybody have bootloader file in HEX?

There is a firmware when you build librepilot

Code: [Select]

~/librepilot$ ls build/firmware/
bl_coptercontrol    bu_discoveryf4bare  ef_oplinkmini       fw_osd
bl_discoveryf4bare  bu_oplinkmini       ef_osd              fw_revolution
bl_gpsplatinum      bu_osd              ef_revolution       fw_revonano
bl_oplinkmini       bu_revolution       ef_revonano         fw_revoproto
bl_osd              bu_revonano         ef_revoproto        fw_simposix
bl_revolution       bu_revoproto        fw_coptercontrol    uavobjects
bl_revonano         ef_coptercontrol    fw_discoveryf4bare
bl_revoproto        ef_discoveryf4bare  fw_gpsplatinum
bu_coptercontrol    ef_gpsplatinum      fw_oplinkmini


• fw is the firmware alone
• ef is entire flash bootloader+firmware
• bl is the bootloader alone
• bu is the bootloader updater that is in opfw file, this can be flashed from GCS and does not require soldering SBL pads like for all bin files

[TheOtherCliff]

If you were just doing a normal upgrade, you were just updating normal firmware and not bootloader.  If that is the case, then you only have corrupt normal firmware.

Just do a standard Rescue operation beginning with board unplugged.  Press Firmware -> Rescue button, then plug in board in USB, then you can flash, etc.

[f5soh]

If Upgrade/erase button before connecting board do not work, you should update bootloader first using STM Flash loader.

Check procedure and BL file attached.

[pulser13]

Upgrade/erase button before connecting board do not work...........

Check procedure and BL file attached.

I made Flash bootloader procedure as described in the attached file, thank you. Bootloader flashed successfully, that's it  .
When I reconnect cc3d controller blue LED does not lit and other actions with Upgrade/erase buttons do not work.
In the Windows device manager -device descriptor request failed.

Is it possible to flash with FTDI cable a full firmware file? If "yes"- do you have it?

[f5soh]

yes, try file attached :

[pulser13]

Thank you. It also flashed with no errors, but blue led does not lit after reconnect.
May be something wrong with board.. or with my hands  . But once again, when I flash the controller with cleanflight_cc3d.hex blue led is slowly flashing.
Just in case- should I flash full firmware with start address 8000000 as bootloader?

[f5soh]

Strange.. still no communication when you hit Upgrade button and after connect board?

Start address looks fine

[pulser13]

Alas - no.
And the last point - When I flash cleanflight SW wit BIN file bleu led does not lit, but when with HEX it is works. Of cause I choice the correct extension when download the files.
My steps:
1. Connect FTDI with CC3D
2. Connect SBL pads
3. Connect USB FTDI with PC.
4.Remove SBL connection
5 Start STM program - choice the port- next-next-next-erase all(successful) -back- download from file -choise ef_coptercontrol.bin-next(successful)
6. reconnect USB - no blue led
7 . disconnect USB-Start GCS-firmware-push Rescue- Connect USB-Timed out 
8.Disconnect USB-push Update Erase-connect USB- timed out 

[f5soh]

Here is another page with procedure, looks the same...
http://www.southquay3d.com/index.php?route=news/article&news_id=9

So no blue led blinking at all ?
Try files attached, watchdog is disabled.

[pulser13]

No blue at all with all files you sent me.
Anyway thank you. Will buy a new board.
I forgot to say cleanlflight works only via FTDI cable, USB also does not worked.

[pulser13]

Problem solved!
 It was contact issue. I heat the board with hot air gun. Blue led starts blink. After I started Update/Erase and connect the board to PC. Now everything is OK, except  chanel 6 . I thing I overheat the board and lose the contact. Anybody knows which controller pin going to 470 Ohm resistor to CH6 receiver? Sorry for offtop

[f5soh]

Cool

here is the schematic :
https://bitbucket.org/librepilot/librepilot/raw/ac76fc768f235a7548dacd698d8e9b218e3f9820/hardware/Production/CopterControl%203D/CopterControl%203D%20Schematic.pdf

[JaeMelo]

Hi everybody!
I have quite the same situation: I had cc3d atom flashed with openpilot SW. When I updated it with librepilot SW, process was interrupted (disconnected USB ). Now I have only green LED lit on the board.

I have tried Resque and Upgrade procedure with connection before and after pushing the buttons. With no effect. Windows shows me "devise not recognized". OS X - no USB port open
However, with "STMicroelectronics Flash loader Demo" with UART FTDI board I can flash "Cleanflight" SW and it works.
What can I do with it? Anybody have bootloader file in HEX?

There is a firmware when you build librepilot

Code: [Select]

~/librepilot$ ls build/firmware/
bl_coptercontrol    bu_discoveryf4bare  ef_oplinkmini       fw_osd
bl_discoveryf4bare  bu_oplinkmini       ef_osd              fw_revolution
bl_gpsplatinum      bu_osd              ef_revolution       fw_revonano
bl_oplinkmini       bu_revolution       ef_revonano         fw_revoproto
bl_osd              bu_revonano         ef_revoproto        fw_simposix
bl_revolution       bu_revoproto        fw_coptercontrol    uavobjects
bl_revonano         ef_coptercontrol    fw_discoveryf4bare
bl_revoproto        ef_discoveryf4bare  fw_gpsplatinum
bu_coptercontrol    ef_gpsplatinum      fw_oplinkmini


• fw is the firmware alone
• ef is entire flash bootloader+firmware
• bl is the bootloader alone
• bu is the bootloader updater that is in opfw file, this can be flashed from GCS and does not require soldering SBL pads like for all bin files

Any idea where exactly can I get a copy of all these files?!

[f5soh]

This files are available when you compile Gcs/firmware from sources
https://librepilot.atlassian.net/wiki/display/LPDOC/Developer+Manual

Witch files / board you need ?