Failed to talk to bootloader

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Connecting to minimosd through Arducam 2.1.2.0
2.Using DIYDRONES FTDI cable ttl-232r-3v3
3.Running Windows 7

What is the expected output? What do you see instead?
trying to read from osd and upload, getting the "failed to talk to bootloader" 
message

What version of the product are you using? On what operating system?
2.1.2.0 Arducam config and version 1.1 minimosd operating system Windows 7

Please provide any additional information below.

I'm converting fromn using the Remzibi OSD by 3DR to the minimosd.  Using the 
same cable from DIYDrones that worked on the Remzibi.  Verified the connection 
still works to Remzibi and does.  I have both 12volt and 5 volts supplied to 
board.  Both red led's on.
I get overlay from osd just fine when connected to APM 2.5. and veiwing on 
monitor.  Mavlink heartbeat detected and all messages appearing on osd overlay.

Appears to be in the linkup between the config program and FTDI.  Since the 
communications between the FTDI drivers detect the Comm port and when connected 
back to the Remzibi OSD all functions of read and writing to Remzibi work fine.

Original issue reported on code.google.com by trea...@earthlink.net on 30 Jan 2013 at 5:08

[GoogleCodeExporter]

I have the same problem. It worked at the begining then it stops . Now I am 
getting Failed to Talk to Bootloader

Could you please provide a setp by step procedure for fix it with FTDI cable

Thanks

Original comment by Prof.Avi...@gmail.com on 8 Feb 2013 at 1:43

[GoogleCodeExporter]

I am experiencing the same problem... Connecting on Com6 and I get bootloader 
problems....

Original comment by pino.ago...@gmail.com on 22 Mar 2013 at 3:26

[GoogleCodeExporter]

Same problem here.  Trying to update the display to remove things we don't need 
in the current config.
With the board on the bench, the OSD config program and the Atmel are not 
talking to each other.  On an Oscope I see the config program sending bits to 
the Atmel but the Atmel never answers on the TX pin - No bits appear there at 
all.  Tried watching the pins with the scope when power is applied and see no 
handshake there either (as would be the case with a native Atmel boot loader).

Is there any support for this program?

Jim 

Original comment by j...@coloradosatellite.com on 9 Apr 2013 at 8:22

[GoogleCodeExporter]

I have the same problem. but I have 3 of them 2 work one does not ? very 
frustrating. 

Original comment by adrianle...@me.com on 31 May 2013 at 9:39

[GoogleCodeExporter]

Yep, I'm having the same issues. Worked fine at first but after that... dead. 
Now can't connect, message "failed to talk to bootloader" appears.

I'm using the FDTI connection.

Please help!!

Guido

Original comment by gbj.jans...@gmail.com on 13 Jun 2013 at 4:20

[GoogleCodeExporter]

Same here, worked once, when I configured using DIY Drones FTDI cable but after 
that I'm getting the same error message anything I try. Both led's power up, 
soldered the pads on both sides, powering using 5v , never used more than 5v to 
power it. Nothing shows on the monitor, just a black screen.

Original comment by ovis...@gmail.com on 24 Jun 2013 at 8:40

[GoogleCodeExporter]

I fixed this issue as follow:

* Reprogram a boot-loader on the Atmel by using a USB ASP programmer connected 
to the header on the minim osd board. (This is not the FTDI cable).
* I Used Arduino sketch 1.0.5
* Click on Tools > Board > Arduino Pro or Pro Mini (5V,16MHz)w/Atmega 328
* Ensure the correct Com Port is selected for your programmer.
* Click on Tools > Burn Bootloader

*After this process is successful you can connect your FTDI cable again as 
normal. Load your firmware, character set and your panels.

Original comment by Francois...@gmail.com on 1 Dec 2013 at 6:42

[GoogleCodeExporter]

Is this program compatible with Window 8.

I am not a computer programmer and cannot understand how to configure the 
camera.  Does anyone out there speak English?

Original comment by sjoagpar...@gmail.com on 18 Dec 2013 at 1:23

[GoogleCodeExporter]

I have the same issues as above. My minimosd V1.1 is from hobbyking. There 
seems to be an issue with the bootloader. Connecting to APM osd works fine, all 
data is overlaid on screen. But it just doesn't talk to my computer via FTDI. 
Tried the reset button also did't work. And same i am not sure how to go about 
using USBasp to burn a new bootloader onto the minimosd board.

Very frustrating.

Original comment by alanlo...@gmail.com on 21 Jan 2014 at 2:42