i recieved my new Minim OSD V1.1 from hobbykong. Wohooo, again able to do FPV flights!

But wait...nono...
First things first.

- Solder the two 5V pads, as i will not use 12V on videoports.
- Upload most recent Team_KV version to it.
Now my problem:
- Of course before i upload KV-sketch, i upload EEPROM_clear sketch....BUT it does not work.I am not able to upload anything.....

Message at verbose upload:
Code: Select all
Binäre Sketchgröße: 790 Bytes (von einem Maximum von 30.720 Bytes)
C:\Program Files (x86)\Arduino\hardware/tools/avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega328p -carduino -P\\.\COM4 -b57600 -D -Uflash:w:C:\Users\Nocturn\AppData\Local\Temp\build4124390543560591445.tmp\EEPROM_Clear.cpp.hex:i
avrdude: Version 5.11, compiled on Sep 2 2011 at 19:38:36
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "C:\Program Files (x86)\Arduino\hardware/tools/avr/etc/avrdude.conf"
Using Port : \\.\COM4
Using Programmer : arduino
Overriding Baud Rate : 57600
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Recv:
avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude done. Thank you.
What i have tried so far:
-double, triple, octo check my connections.
-try to reverse RX/TX from FTDI.
-test different versions of Arduino SW 1.0-1.05
-update FTDI drivers.
-connect FPV cam and transmitter, to get an additional GND. (This was mentioned in some topics across the web)
->now i have the "waiting for mavlink heartbeats" message on my FPV screen, so i assume the OSD is not dead.
-try to use all other versions of the ATMEGA 328 board instead of "Arduino Pro or Pro Mini (5v 16mhz) w/ ATMEGA 328" for upload.
-tested FTDI on my old minim osd V0.1 -> working without problems.
-tested FTDI also with my FC -> everything fine
What i was not able to do:
- Burn a new bootloader, as i dont have the neccesary programmer.
So, shouldnt it have a working arduino bootloader?
Is this the only thing left to try? Any advices?
Its frustrating to wait for 2010293093 days (32 days


Ok, as i dont like to give up, i proceed with repairing the OSD i never intendet to use again.
The Minim OSD 0.1 from goodluckbuy.

It was the one that just popped out a resistor during flight and resetted my FC leading to a fatal crash.
Now, i have a question. What would this resistor do for the MAX chip?
What i have done:
-I was not able to resolder the resistor, as it did not stick to its solderingpoints anymore. Seems like its soldering contact went away. Refuses all solder.
-Because i did not care anymore about this board and i wanted to know what happens, i just soldered a bridge instead of the resistor.
-Now i was shocked

-As i am afraid of this board, i left it connected to KV-GUI with simulating enabled for around an hour. With the result that everything seems to work as it should.
-There was no heat up and no fading away. Just perfect

Before i let this board levitate again, i wanted to ask for some feedback, if it may theoretical be ok, also without the resistor.
Of course i´d prefer to use the new Minim OSD V1.1......pfffff....

It will make me very happy if anyone has an idea on how to solve this upload problems, or if someone knows if i may be fine with the old "resistor modded" "Minim OSD V0.1" for now.

Thank you!
Greetz Noc