I've ported MinimOSD to Remzibi's hardware

Hello everyone. Recently I port the MinimOSD to the Remzibi OSD's harware, so a poor man can enjoy MinimOSD's convenience now (no need to modify APM's software anymore).

Because of the limited flash space of Atmega16, the code of OSD is slightly changed, and it is not compatible with Michael's original config tool. So I adapt the config tool as well.

The Remzibi's OSD uses Megaload bootloader, so please use the Megaload programmer to upload the firmware. (The config tool can also upload the firmware, but I have to admit that it is not quite good right now.)

Anyway, here is the firmware and config tool, and here is the source code.

Thank binzi for providing the hardware.

Views: 18160

Comment by Jani Hirvinen on March 19, 2012 at 9:48pm

Yeah porting it to at16 is not easy task as we already had a lot of problems on doing it on at328 chip. Great work.

Comment by Dario Lindo Andres on March 20, 2012 at 12:37am

Wow!! Great job Hazy!! I have a Remzibi´s OSD on the desk now, so I will try to run your code. Could be posible see in the video the RSSI and the video battery´s voltage that come from the OSD analog inputs?? I think this is the handicap on the MinimOSD...


Thanks for your effort Hazy!

Regards from Spain,


Comment by hazy on March 20, 2012 at 12:45am

The possibility of displaying RSSI and video battery's voltage actually depends on the size of AD code. Right now the firmware uses about 14KB flash size, so there is 1KB left. I will try.

Comment by kolin on March 20, 2012 at 1:48am

Great work, thank you!

Comment by Graham Dyer on March 20, 2012 at 1:52am

Fantastic, will try it out

Comment by Sandro Benigno on March 20, 2012 at 4:44am

Great job, Hazy!
Very interesting approach on putting external vars and functions inside the ArduOSD class.
BTW, there is a place for RSSI data on MAVLink. APM 2.0 will "fill" it soon.
I believe in your case it would be easiest by reading it directly from an exposed analog input of Renzibi board.

Comment by Graham Dyer on March 20, 2012 at 6:44am

Trying this now but hit a snag, uploaded the .hex file but the screen just shows strange characters.

I've tried updating the charset but the config tool shows 'Charset done' but the console window shows 'Write error'

MegaLoad crashes if I try load the charset file. Help?

Comment by hazy on March 20, 2012 at 8:24am

It seems that the watch dog cause a timeout when uploading the charset. I have updated the OSD hex file and Config tool, please download hazys-osd v0.2, flash the hex file, and then upload the charset file using config tool.

I'm sorry for this inconvenience.

Comment by Graham Dyer on March 20, 2012 at 9:14am

It WORKS! No inconvenience at all, just glad for the rapid response and fix. Very nice, I do like it.

The only problem I'm having is saving/uploading a screen setup to the OSD. 'Read from OSD' and 'Save to OSD' don't work for me, anything special I should do?

Comment by Graham Dyer on March 20, 2012 at 9:49am

Managed to get a screen setup loaded, not quite sure how but it's there.

Couple things:

  • most important - when arming APMx the OSD firmware goes into a loop, booting up, waiting for heartbeats, requesting datastreams and repeating, etc. It never connects again, if APM is reset then it connects but as soon as APM arms the loop starts. So it's actually unusable at this stage.
  • If the OSD is disconnected and reconnected it also boot loops, never finding the heartbeats.
  • An indication of disarmed or armed would be nice


You need to be a member of DIY Drones to add comments!

Join DIY Drones


Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service