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

Default Font unreadable after Upload #417

Closed
Creautre opened this issue Apr 28, 2017 · 2 comments
Closed

Default Font unreadable after Upload #417

Creautre opened this issue Apr 28, 2017 · 2 comments

Comments

@Creautre
Copy link

I flashed MWOSD via Arduino IDE onto the MicrominimOSD Board. [ I didn't do EEPROM_CLEAR prio to this ].

Everything looked fine except that I had the wrong Symbols. Instead of battery I had an Arrow etc. so I used MWOSD Configurator and connected to the OSD via Serialpassthrough through my SPRacing F3 Evo board running Betaflight.

After I connected I used the "Change" button below "FONT:" and chose the default Font, selected it and hit Upload. Afterwards everything seemed to be in the right place but absolutely unreadable.

I tried using EEPROM Clear on Arduino IDE and reflashing the firmware over and over again but it never worked [ desoldered from my Circuit of course ].

I managed to fix the Issue by Using the "FLASH" function of MWOSD Configurator. I first uploaded ClearEEPROM, then Bold font installer and then "Default minim Betaflight 1.7.1". For test purposes I used the first Font update method that messed everything up and it happened again. Exact same issues. After doing my procedure again, everything works fine.

You can check my thread to see the whole process and how it looked

http://intofpv.com/t-microminimosd-not-programmable

Hope you can fix this issue or tell me what i did wrong

@ShikOfTheRa
Copy link
Owner

Thank you for reporting. Confirm bug found. Updated configurator being deployed to store today.

Estimate this will be available 12:00 UTC 11/05/2017
Configurator Version 1.7.1.5

@ShikOfTheRa
Copy link
Owner

This has been resolved by app update. Confirmed by one of the users

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

No branches or pull requests

2 participants