Strange character artifacts and issues with latest CT Tool for MinimOSD Extra 2.3.0.8 Pre Release r676

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Flash Mavlink osd v1.0 with MinimOSD-Extra_Plane_Pre-release_2.4_r676.hex 
2.update charset to MinimOSD_2.3.0.8
3. watch it suck.

What is the expected output? What do you see instead?
normal screen with characters and horizon displaying as expected. what is seen 
instead ar starnge characters appearing on the horizon, and the compass

What version of the product are you using? On what operating system?
using  CT Tool for MinimOSD Extra 2.3.0.8 Pre Release r676

Please provide any additional information below.

I have tried this on two separate mavlink osd devices and see the same rsults 
on both.

Original issue reported on code.google.com by JohnnyFa...@gmail.com on 28 Sep 2013 at 5:37

[GoogleCodeExporter]

Had this as well, When you upload the charset you need to have the 12V side of 
the minimOSD connected as well, the charset upload to the analog video chip 
which is powered from the 12V side.

Original comment by shays....@liveperson.com on 2 Oct 2013 at 11:27

[GoogleCodeExporter]

I'm having this same problem: After updating to 2.4.0.0 pre I see garbled 
characters on the screen when the horizon tilts and in a few other places.

I tried re-uploading the charset while the 12v side was powered via battery, 
but it didn't seem to help. Any other suggestions?

Original comment by ge...@deconcept.com on 6 Feb 2014 at 3:19

[GoogleCodeExporter]

I am having the EXACT same issue? Any luck? I tried uploading the CHAR set 
multiple times, I am afraid to power it with 12v as its rev .1 and the board is 
all powered up from the FTDI (the jumpers are soldered) 

Original comment by brandon0...@gmail.com on 27 Feb 2014 at 2:33

[GoogleCodeExporter]

I ended up downgrading to an earlier version - I couldn't get it to work 
without the garbled text on the prerelease version.

Original comment by ge...@deconcept.com on 27 Feb 2014 at 3:17

[GoogleCodeExporter]

Hi i have just got my first minimOSD and tried to install it.
Tried 232 and got artifacts, mostly to do with the artificial horizon which was 
any char but --

So i tried removing the 5v jumpers and powering the one side via 12v no joy. 
Tried the same again but on a different 12v one side and 5v (was just over 
according to the scope) on the digital side. Same again odd artifacts. 

Tonight i re-installed the 5v jumpers and went backwards through the builds one 
at a time and every time i got artifacts until i got to build 2.2.
This build went fine programming at 5v with the jumpers installed. So i am sure 
this is not a 12v issue as why would this build work? There must be something 
with every build since 2.2

Original comment by thomas...@gmail.com on 23 Apr 2014 at 8:55

[GoogleCodeExporter]

Hi guys, I have an update for you.

I purchased another minimOSD for a tenner off ebay and gave flashing another 
try. I downloaded the latest build and attempted to install exactly the same as 
I have before. Ie using 5v only with the jumpers set. It worked with out issue 
and is perfect. I wonder if all our units have a hardware issue where it wont 
take the new char set.

Right the first minimOSD was purchased from hobbyking, I tried all ways to 
flash it with no joy. One thing I found was the actual chip that does the gfx 
ran rather warm when powered by either method.
The second I purchased from newgoodtime on ebay, this came pre jumped to run on 
5 volt. Flashed using my cable no issues with the latest build, and the gfx 
chip does not seem to run hot at all compared to the hobbyking one.

Hope this helps you out.

Trev

Original comment by thomas...@gmail.com on 2 May 2014 at 3:29

[GoogleCodeExporter]

i also have a very cheap Ebay version and it loaded fine,  and works fine. 
however my slightly older HK version has just a garbled output when i tried to 
load the latest firmware,  so i will have to try going back as well to older 
firmware,  as it scares me trying to power both sides of the same board with 
jumpers attached as i think it will fry my laptop

Original comment by mikesmai...@gmail.com on 27 May 2014 at 4:12

[GoogleCodeExporter]

Hi Mike,
If you are intent on trying to program it by powering both sides, you must 
remove the jumpers first then program, and then reapply them after you have 
finished programming. Although I tried this with the HK one a few times without 
success. I think the real problem is the HK one is not taking on the new 
Character set hence the garbled appearance. I suspect there is something 
suspect with the HK board, it could be that the actual OSD chip is a copy and 
not a genuine part, or maybe the crystal that it uses is not right or something 
along those lines.

Original comment by thomas...@gmail.com on 28 May 2014 at 7:15

[GoogleCodeExporter]

I too have the HK board and this problem. Found a partial fix, using this 
charset (which is also smaller font):
https://code.google.com/p/minimosd-extra/issues/detail?id=3

My screen/panel 1 works fine now with correct chars, but my secondary panel 2 
is still garbled.

Original comment by anthonys...@gmail.com on 3 Jul 2014 at 6:01

[GoogleCodeExporter]

Closed as we have a new version.

Ifthe problem is still present please reopen it.

Original comment by gabek...@gmail.com on 28 Nov 2014 at 11:44

• Changed state: Done

[GoogleCodeExporter]

I had the same Problems with a HobbyKing minimosd v1.1 and the 2.4 firmware 
with 2.4 character set. I bridged the two stages and power them with 5v. The 
failure was: I used a 3.3v ftdi for upload. after uploading same fw and char 
set with an 5v ftdi it's working. Hope  that helps.

Original comment by lu...@lukas-kamper.de on 10 Jan 2015 at 7:17

[GoogleCodeExporter]

I have a minimosd board from witespy and too was unable to get the R800 or 2.4 
pre-release firmware character set to install.  I could not downgrade to 2.2 
(no extra.)  

My fix was to power the split the 5V and 12V side of the board, power 
separately AND change the FTDI programmer to output 5V (instead of 3.3V.)  The 
5V FTDI programmer voltage output change was the key that I was missing.  
(thanks poster #11 for the suggestion.)

Original comment by ryan.bor...@gmail.com on 30 Jun 2015 at 5:31