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.
Comment #1
Posted on Feb 8, 2013 by Grumpy OxI 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
Comment #2
Posted on Mar 22, 2013 by Grumpy BearI am experiencing the same problem... Connecting on Com6 and I get bootloader problems....
Comment #3
Posted on Apr 9, 2013 by Happy RabbitSame 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
Comment #4
Posted on May 31, 2013 by Quick RabbitI have the same problem. but I have 3 of them 2 work one does not ? very frustrating.
Comment #5
Posted on Jun 13, 2013 by Helpful DogYep, 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
Comment #6
Posted on Jun 24, 2013 by Happy HorseSame 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.
Comment #7
Posted on Dec 1, 2013 by Happy PandaI 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.
Comment #8
Posted on Dec 18, 2013 by Grumpy PandaIs 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?
Comment #9
Posted on Jan 21, 2014 by Helpful ElephantI 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.
Status: New
Labels:
Type-Defect
Priority-Medium