search

helgenodland / arducam-osd

Automatically exported from code.google.com/p/arducam-osd
0 stars 0 forks source link

MinimOSD firmware missing? #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Can't connect with setup software

What is the expected output? What do you see instead?
- Failed to talk to bootloader.

What version of the product are you using? On what operating system?
MinimOSD v1.1

Please provide any additional information below.
- Seems it doesn't have firmware inside. 
Any help how to flash it? Just hex file or do I need to flash bootloader? 
Please help ASAP. Thanks!

Original issue reported on code.google.com by virgi...@gmail.com on 6 Sep 2012 at 6:59

GoogleCodeExporter commented 9 years ago 
I've flashed the bootloader with Arduino 1.01 and config software worked, but 
only for firmware update.. after that I can't access it anymore. I think it 
overwrites the bootloader flashed via Arduino?

Virgis

Original comment by virgi...@gmail.com on 6 Sep 2012 at 7:54

GoogleCodeExporter commented 9 years ago 
any ideas or where can I get proper bootloader and what are the fuses for 
Atmega 328p to work as it should? Thanks for any help here!

Virgis

Original comment by virgi...@gmail.com on 7 Sep 2012 at 8:35

GoogleCodeExporter commented 9 years ago 
Virgis,
Did you get this resolved?
Rick

Original comment by Eism...@gmail.com on 13 Sep 2012 at 4:55

GoogleCodeExporter commented 9 years ago 
Nope. You are the first one to respond :)
At the moment I have working OSD, but can't configure, because firmware 
overwrites bootloader and can't connect with PC software.

Virgis

Original comment by virgi...@gmail.com on 13 Sep 2012 at 5:45

GoogleCodeExporter commented 9 years ago 
Sorry guys. I'm mortally busy these days. Here goes some tips:

As you said, it was needed to re-upload the Arduino Bootloader. OK. So, you 
should be able to use the Configurator tool to update the board's firmware 
normally by using an FTDI 6-wire cable. Maybe you've uploaded the wrong 
bootloader?
The bootloader it uses is the "ATmegaBOOT_168_atmega328.hex" from your Arduino 
installation's "hardware\arduino\bootloaders\atmega" folder.
BTW. What programmer are you using?

Original comment by sbeni...@gmail.com on 13 Sep 2012 at 2:24

GoogleCodeExporter commented 9 years ago 
I'm having exactly the same issue. It seems to have happened when I switched to 
either APM v2.70 or v2.71 - I'm not sure which one. The OSD still worked on APM 
2.72, but I just can't talk to it with the configurator. I didn't try to upload 
a new boot loader because I didn't know which one was proper to use. I've since 
sent it back to 3DR over 2 weeks ago but still nothing back. Seems like pretty 
slow service. Would suggest not doing that if you can avoid it.

Original comment by kahlj...@gmail.com on 13 Sep 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Thanks for support.
I am using USBASP programmer. I have changed the fuses for Atmega. What should 
be the correct ones?
I will try to flash the correct bootloader now and will let you know about 
progress.
Thanks again!

Virgis

Original comment by virgi...@gmail.com on 13 Sep 2012 at 5:03

GoogleCodeExporter commented 9 years ago 
Tried to flash correct bootloader via USBASP programmer via AVRDUDE. Got the 
same result. Updating firmware from ArduCAM OSD Config software it writes OK, 
but that is the last time I can connect it. OSD is working OK, but can't 
connect and configure it anymore. Seems I am messed up with fuses?

Virgis

Original comment by virgi...@gmail.com on 13 Sep 2012 at 5:31

GoogleCodeExporter commented 9 years ago 
Maybe you've locked the EEPROM...?
Just in case, this is the whole set of commands using your programmer:
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

Original comment by sbeni...@gmail.com on 13 Sep 2012 at 10:57

GoogleCodeExporter commented 9 years ago 
Thanks! That's what I need! :)
Will report the progress tomorrow!

Virgis

Original comment by virgi...@gmail.com on 13 Sep 2012 at 11:25

GoogleCodeExporter commented 9 years ago 
I've tried those commands without success. I am not sure what I am doing wrong 
here.
fuses wrote OK, firmware OK (I've changed the original name of the 
ATmegaBOOT_.. hex to short just "Atmega.hex", so file is the same).
Maybe AVRDUDE firmware is old? It gives a warning message: cannot set sck 
period..
Thanks for support here! I really appreciate it!

Original comment by virgi...@gmail.com on 14 Sep 2012 at 6:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Guys, any ideas what is wrong with it?
THanks.

Virgis

Original comment by virgi...@gmail.com on 20 Sep 2012 at 8:58

GoogleCodeExporter commented 9 years ago 
About the sentence "cannot set sck period": it happens with USBasp programmers.
Just ignore it. I have one that shows exactly the same and it works perfectly.

About the OSDConfig: Are you using the FTDI 6pin cable? If not what is the 
serial adapter?

Original comment by sbeni...@gmail.com on 1 Oct 2012 at 10:35

GoogleCodeExporter commented 9 years ago 
I've updated the USBASP programmer firmware and error is gone.

I am using one with Silicon Labs chip CP2102:
http://www.b2cqshop.com/ebayphoto/cp2102_a.jpg
Thanks for help!

Virgis

Original comment by virgi...@gmail.com on 1 Oct 2012 at 11:41

GoogleCodeExporter commented 9 years ago 
Perhaps it could be an error at the reset line.
Did you try to press OSD's reset button after clicking on the "Read/Write"?
It's just like the early Arduino's days. By this way we would try to verify if 
the error is coming from the adapter or so.

Original comment by sbeni...@gmail.com on 2 Oct 2012 at 3:21

GoogleCodeExporter commented 9 years ago 
Thanks! you are Genius!
Issue fixed, I was missing just reset command :)
I've even replaced Atmega.. :)
Now I can setup OSD and make it boot OK (CharSet updated).
Thanks a lot!

Virgis
P.S. Issue fixed/closed

Original comment by virgi...@gmail.com on 2 Oct 2012 at 5:06

GoogleCodeExporter commented 9 years ago 
Great!
I'm happy that you've got it working properly.
Have fun!

Original comment by sbeni...@gmail.com on 2 Oct 2012 at 5:21

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
with cp2102 i've made a reset mod. So you don't need to manually reset anymore.

Original comment by alf...@gmail.com on 8 Jan 2013 at 7:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Do you have some basic instructions for reburning the bootloader on minimosd? I 
have a jdrones 1.0 board that I need to reburn. I have a USBASP programmer that 
I use on kkboards and an atmel chip connector that I use to reflash ESC's. The 
process is similar? I use the kkmulticopter program to burn ESCs.

Original comment by stevetor...@gmail.com on 5 Apr 2013 at 7:46

GoogleCodeExporter commented 9 years ago 
@Steve: if you're experienced on USBASP so it's quite easy.

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

The bootloader is the "ATmegaBOOT_168_atmega328.hex" from the [Arduinno install 
folder] -> /hardware/arduino/bootloaders/atmega

Original comment by sbeni...@gmail.com on 5 Apr 2013 at 8:47

GoogleCodeExporter commented 9 years ago 
My only experience is with doing SimonK reflashing so I have a usbasp and atmel 
overthechip connector. I will give it a try.

Original comment by stevetor...@gmail.com on 6 Apr 2013 at 3:32

GoogleCodeExporter commented 9 years ago 
You can do the same via Arduino 1.0 or latter, just choose as Arduino mini pro 
5v and it will flash correct bootloader.
Then flashing firmware with OSD software, don't forget to press reset as I've 
done then needed to complete the task :)

Virgis

Original comment by virgi...@gmail.com on 6 Apr 2013 at 7:25

GoogleCodeExporter commented 9 years ago 
I've read about pressing reset but exactly when do you press it during the 
process? I ended up reburning the minimosd with windows 7 command prompt and 
the overthechip connector and usbasp. Was easy! I will try arduino next time.

Original comment by stevetor...@gmail.com on 8 Apr 2013 at 11:55

GoogleCodeExporter commented 9 years ago 
Just click option you need to do (upload or update something in software) then 
press reset after 0-1sec :) Lets say at the same time.

Original comment by virgi...@gmail.com on 8 Apr 2013 at 12:14

GoogleCodeExporter commented 9 years ago 
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 comment by MartinGornitzka on 19 May 2013 at 6:34

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
hello friends, I haven't any experience with programing so I have the usbasp 
but what Do I do?

Original comment by cesarjul...@gmail.com on 22 Aug 2013 at 6:37

GoogleCodeExporter commented 9 years ago

Original comment by sbeni...@gmail.com on 19 Sep 2013 at 10:06

GoogleCodeExporter commented 9 years ago 
You can still use 4 wire FTDI cable just right after initiating any operation 
(Burn Boot Loader, "Read from OSD" or "Save current tab to OSD" or update FW) 
click reset button. Details http://vimeo.com/66105099

I've used cheapest 4 wire FTDI cable (3$ on eBay) AvrdudeR at 57600 to upload 
bootloader file C:\Program Files 
(x86)\Arduino\hardware\arduino\bootloaders\atmega\ATmegaBOOT_168_atmega328.hex

to OSD that had this problem. Also with this cable I am able to do all other 
operations with minimOSD.

Original comment by i...@koronker.ru on 7 Nov 2013 at 6:15

GoogleCodeExporter commented 9 years ago 
Select Tools > Board and select your board (mine is the Arduino Pro or Pro Mini 
(5v, 16MHz) w/ATmega128)

Select Tools > Programmer > USBasp

COM port can't change (USBasp not need COM port)

Select Tools > Burn Bootloader

Wait 2-3 mins and you’ll probably get an error of “warning: cannot set sck 
period. Please check for usbasp firmware update”. Just ignore it.

Unplug the USBasp board and plug in your FTDI (with MinimOSD)

Open the MinimOSD configuration software, select the COM port and click ‘Read 
from OSD’

Original comment by mouchadi...@gmail.com on 22 Jun 2014 at 2:46

GoogleCodeExporter commented 9 years ago 
pls use USBasp programmer (cek 
http://www.unmannedtechshop.co.uk/usbasp-avr-programmer.html)

Original comment by mouchadi...@gmail.com on 22 Jun 2014 at 2:51

GoogleCodeExporter commented 9 years ago 
Hi,

I have the same problem with my MinimOSD !
Have you find a solution ?

Thx

Original comment by sup3rs0n...@gmail.com on 25 Sep 2014 at 10:28