Im in the same situation! Help Please!!!

I once bricked a flight controller with corrupt data from an Xbee radio. Someone had a technique to brute-force load a firmware through the UART ports using an FTDI. Basically you connect the FTDI to the computer first and start the bootloader. Then start uploading the firmware before connecting to the BGC board. Once the upload process is starting connect the FTDI to the UART TX/RX ports that the bluetooth uses with the 5V reference and ground.

Of course be sure to have the FTDI setup for correct parity and baud rate as the BGC, as well as the FTDI will need to use 5V reference for the the reference. No guarantee this will work. It worked on a flight controller which is ion theory is a similar device as a BGC. Since it is bricked no harm in trying.

@Alexmos, what about the basecam board of DYS 3 axis gimbals for GoPro?

I can't find these jumpers to re-flash the firmware. The board is different :(

I have this kind of board and I can't find any flash pins... http://www.rcgroups.com/forums/showatt.php?attachmentid=6820315

I have newer got the idea why there is need to have so many different boards of the same design.

On my experience BaseCam SimpleBGC 32-bit board is an excellent normal board, with enough power for most applications.

The Flyduino board is nice for higher current applications, but I hope they would use the same IMUs as BaseCam SimpleBGC 32-bit, With these IMUs I have had no I2C issues.

BaseCam SimpleBGC 32-bit Tiny is under test, I much like the form-factor.

These board have all their place, normal, high power and small. why should there be different copies of these boards? that might omit something important like Flash pin, or have problems with I2C errors, etc. It would be much better just to focus making these boards better.

If because commercial etc. reasons someone wants to make board with his logo etc. ok, but why should it be different design, different layout, different connectors. This is also problem with the above mentioned SimpleBGC 32-bit board and Flyduino board. they have same IMU connector, but different pinout is used?

What I really would want to see is separated power board and processor board. those could be stacked. There could be different power boards, Higher voltage/current version, the processor board would always be the same. This would make the board much more compact and easy to instal and less expensive to add more power to the system if needed (as only power board needs to be replaced).

Also later on if there is a more powerful processor, with more memory etc. it could be compatible with the existing power boards. Also maybe if in future there is improved IMUs with better connection than I2C, only processor board and IMUs would need to be changed. and as there already is encoders, maybe an encoder version of the processor board...

So yes, I am asking for yet an other design, but hopefully such that would be for long time, and using all the good parts of existing designs. Harmonising all the boards and IMUs to same form-factor, to same pin layouts, to same connectors, to be interchangeable.

And the boards should also have clear version numbering, so that they would be easy to identify.

The link to this article has been changed and is now at http://uavblue.com/content/Restoring_Firmware_to_Alexmos_DYS32.pdf

Now i read that my board is 8bit? maybe it makes a issue on firmware update...

This is exactly my board http://rctimer.com/images/goods/20140204/11b1e70cf88b488e.jpg

Can anyone tell me, where I can find the flash pins on this 8bit board above? I have the exact same one. Need to recover it, because there is no chance to get a connection after flashing the wrong firmware (2.50b3).