Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firmware missing #68

Open
GoogleCodeExporter opened this issue Jan 19, 2016 · 3 comments
Open

Firmware missing #68

GoogleCodeExporter opened this issue Jan 19, 2016 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What is the expected output? What do you see instead?
Expected output id OSD :-) I see nothing :-(

What version of the product are you using? On what operating system?
minimOSD Version 1.0 on Windows 7

Please provide any additional information below.

Hi Guys! I'm having serious problems with flashing of the OSD. I've tried all 
day going from a working OSD v2.0 and getting the "Failed to talk to 
bootloader" to having no OSD.

I have a minimOSD v1.0
connected with six wiers to the
USBasp programmer.

I have installed the Arduino 1.0.5 - to get the bootloader
I have installed the AVRdudeGUI
I've made a "read FLASH" and "read EEPROM" in the AVR dudeGUI.
I have copied the bootloader to the AVRdude folder
I've made a batch file in the AVRdude folder going like this:
  avrdude -c usbasp -p m328p -U lfuse:w:0xFF:m  
  avrdude -c usbasp -p m328p -U hfuse:w:0xDA:m
  avrdude -c usbasp -p m328p -U efuse:w:0x05:m
  avrdude -c usbasp -p m328p -U flash:w:ATmegaBOOT_168_atmega328.hex

After that i get a red solid LED and a bright green flashing LED and of course 
no OSD firmware. I still get the "Failed to talk to bootloader" when connecting 
from "MinimOSD Config"

Original issue reported on code.google.com by MartinGornitzka on 23 May 2013 at 6:31

Attachments:

@GoogleCodeExporter
Copy link
Author

Are you trying to connect to the "Config Tool" through a USBASP programmer?
After recording the bootloader you'll connect using an FTDI cable.

Original comment by [email protected] on 23 May 2013 at 8:11

@GoogleCodeExporter
Copy link
Author

<i>Are you trying to connect to the "Config Tool" through a USBASP 
programmer?</i>
Yes

<i>After recording the bootloader you'll connect using an FTDI cable.</i>
I don't have a FTDI cable. Can't I use the USBasp programmer? Is there an other 
way than trough the FTDI cable?

Original comment by MartinGornitzka on 23 May 2013 at 8:30

@GoogleCodeExporter
Copy link
Author

Now I've gotten the FTDI Cable.
How do I know if the bootloader is installed?

Original comment by MartinGornitzka on 13 Jun 2013 at 8:36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant