Minimicro osd programming

[trebor]

  I am trying to flash via a Ftdi adaptor and following these instructions https://github.com/ShikOfTheRa/scarab-osd/blob/master/OTHER/DOCUMENTATION/FirmwareFlashing.md
Now I,m stuck at the point where you edit the Config. h tab. I selected minimosd and cleanflight for the mandatory config parameters with this Arduino 1.6.8 thingamijig and it flashes up at the bottom in red that I may have a problem. Low memory available, stability problems may occur
Has anyone any ideas 

[Gandhi]

Not sure if this is the answer but I always run the eeprom clear sketch before I upload any new osd sketches. It';s in one of the sample/example folders for arduino I think

[trebor]

I';ll have a look for it, must admit I haven';t seen it and I don';t know what I';m doing. Still learning and making painfull progress.

[robocog]

Mine does that ...but ignoring the message and going ahead with the flash it does work fine
I also tried clearing it first...made no odds to the red message appearing

I am not worried about it as it DOES work as advertised despite the warning

Regards
Rob

[trebor]

Do I have to save it or is it automatic ?

[trebor]

Well I tried, not sure it works. What do you have to do in the Config.h tab when it says this :-  Edit the config.h tab to select the correct OSD hardware, Flight controller and aircraft type.

[Gandhi]

In the config sketch there will be lines of text with two slashes in front of them. These slashes stop that line of code being run. Find the lines that relate to your osd and flight control board and delete them. Then upload the sketch too the osd.

[trebor]

This is what I';ve got so far :-

/*--------------------------       MANDATORY configurable parameters      ----------------------------------------------------*/
/*--------------------------       MANDATORY configurable parameters      ----------------------------------------------------*/

/********************       OSD HARDWARE settings      *********************/
//Choose ONLY ONE option:
#define MINIMOSD                    // Uncomment this if using standard MINIMOSD hardware (default for 95% of boards)
//#define WITESPYV1                 // Uncomment this if using Witespy V1.1 OSD, select this to correct for both swapped bat1/bat 2 and to also use alternative resistors / pinouts. 
//#define WITESPYMICRO              // Uncomment this if using Witespy Micro Minim OSD, select this to correct for swapped bat1/bat 2. 
//#define RUSHDUINO                 // Uncomment this if using Rushduino

// NOTE-some of the popular RTFQ/Witespy boards have swapped bat1/bat2 pins and alternative voltage measuring resistors
// If having difficulties, first select default MINIMOSD as above, then use the following to correct:
// #define SWAPVOLTAGEPINS          // For boards with batt voltage appearing on vid voltage
// #define ALTERNATEDIVIDERS        // For boards with voltage unable to be adjusted high enough


/********************       CONTROLLER SOFTWARE      *********************/
// Choose ONLY ONE option:-
// Note - choose carefully to ensure correct settings are written to flight controller.
// The first three are for convenience - they set the OSD for the latest FC version.
// IMPORTANT - remember to update MWOSD when updating FC software!!

// Choose ONLY ONE option from the following long list :-

// latest release...
//#define MULTIWII                  // Uncomment this if you are using latest MULTIWII version from repository (2.4 at time of this MWOSD release)
//#define BASEFLIGHT                // Uncomment this if you are using latest BASEFLIGHT version from repository (Stable 2015.08.27 at time of this MWOSD release)
//#define TAULABS        in .h            // Uncomment this if you are using the latest Tau Labs MSP Module
#define CLEANFLIGHT               // Uncomment this if you are using latest CLEANFLIGHT version from repository (1.11.0 at time of this MWOSD release)
//#define BETAFLIGHT                // Uncomment this if you are using BETAFLIGHT (same as CLEANFLIGHT t time of this MWOSD release)
//#define HARIKIRI                  // Uncomment this if you are using HARIKIRI (for BOXNAMES compatibility)
//#define NAZA                      // Uncomment this if you are using NAZA flight controller
//#define GPSOSD_UBLOX              // Uncomment this if you are using a UBLOX GPS module for a GPS based OSD
//#define GPSOSD_NMEA               // Uncomment this if you are using a NMEA compatible GPS module for a GPS based OSD
//#define GPSOSD_MTK                // Uncomment this if you are using a MTK module for a GPS based OSD
//#define NOCONTROLLER              // Uncomment this if you ahave nothing connected to the serial port - no controller or GPS module
// old releases supported...
//#define MULTIWII_V23              // Uncomment this if you are using MW versions 2.2/2.3 
//#define MULTIWII_V21              // Uncomment this if you are using MW versions 2.0/2.1  (for BOXNAMES compatibility)
//#define BASEFLIGHT20150327        // Uncomment this if you are using BASEFLIGHT up to and including version Stable 2015.03.27
//#define CLEANFLIGHT172            // Uncomment this if you are using CLEANFLIGHT versions up to and including 1.7.2
//#define CLEANFLIGHT180            // Uncomment this if you are using CLEANFLIGHT versions 1.8.0 & 1.8.1



/********************       AIRCRAFT/INSTALLATION TYPE settings      *********************/
//Choose ONLY ONE option:
#define ROTORCRAFT                  // Default for multirotors etc.
//#define FIXEDWING                 // Uncomment this if you are using fixed wing MultiWii or Baseflight

What are those mandatory parameters for though ?

[robocog]

Yep looks like mine did as far as I can remember
so click compile
It will give the low memory warning

then click the right hand arrow next to the compile button (looks like a tick) to get it uploaded and wait till it says it has uploaded!

It took me a few goes to get it all working
DTR wire needs to be connected for the flashing (but not required once it has flashed)
The right board and com port needs to be selected (arduino pro or pro mini 5v 16mhz)

When done don';t forget to upload the fonts once connected to the MWOSD
It takes a while (it does show a counter)

Regards
Rob

[trebor]

At the bottom it comes up with ( done uploading ) cannot see ( uploaded ) anywhere !

[trebor]

Well I opened my Guiiiiii and the display is there with a choice of different font sizes. They seem to work but I will have to wait for new terminal ends for my Molex plugs before I can wire it back onto the quad to see if it works correctly.

[Gandhi]

Cool, glad you got it working.

Osd';s are a nightmare sometimes. I only have one on one of my 6 multis and that';s only cos it';s the one with kiss 24a esc';s and flight controller so the used shows cool stuff like ma consumed, total amp draw and motor speed :)