Compiling and Installing Firmware

From Speeduino
Jump to: navigation, search

With the goal of maximum simplicity in mind, the process of compiling and installing the firmware is reasonably straightforward.


Downloading the firmware

There are two methods for obtaining the Speeduino firmware:

  1. Regular, stable code drops are produced, typically on the last day of each month. Details of the latest code drop are below
  2. If you want the latest and greatest (And occasionally flakiest) code, the git repository can be cloned and updated. See

Latest Stable Firmware

Older firmware releases

If required, older firmware releases and details can be found at Firmware History

Compiling the firmware

  • Start the IDE, select File > Open, navigate to the location you downloaded Speeduino to and open the speeduino.ino file.
  • Set the board type: Tools > Board > Arduino Mega 2560 or Mega ADK (This is the only board currently supported)
  • Click the Verify icon in the top left corner (Looks like a tick)

At this point you should have a compiled firmware! If you experienced a problem during the compile, see the Troubleshooting section below.

This video walks through the whole process of installing the firmware on your Arduino from scratch:

Optional (But recommended)

There is an option available for changing the compiler optimization level, which can improve . By default, the IDE uses the -Os compile option, which focuses on producing small binaries. As the size of the Speeduino code is not an issue but speed is a consideration, changing this to -O3 produces better results (Approximately 20% faster, with a 40% larger sketch size) To do this, you need to edit the platform.txt file:

  • Make sure the Arduino IDE isn't running
  • Open the platform.txt file which is in the following locations:
    • On Windows: c:\Program Files\Arduino\hardware\arduino\avr
    • On Mac: /Applications/Arduino/Contents/Resources/Java/hardware/arduino/avr/
    • On Linux:
  • On the following 3 entries, change the Os to be O3:
    • compiler.c.flags
    • compiler.c.elf.flags
    • compiler.cpp.flags
  • Save the file and restart the Arduino IDE

Note: This is NOT required if using PlatformIO, the above optimisation is applied automatically there


Once you've successfully compiled the firmware, installation on the board is trivial.

  • Plug in your Mega 2560 to a free USB port
  • If you're running Windows and this is the first time you've used an Arduino, you may need to install drivers for the Arduino serial chip. All official boards, and many non-official ones, use the ATMega16U2 or 8U2, whereasmany of the cheaper 2560 based boards utilise the CH340G IC. The serial chips can generally be identified by appearance:

ATMega16U (square IC) - drivers included in Windows, MacOS and linux:


WCH CH340G (Rectangular IC) - drivers from WCH:

  • Select the serial port to upload to: Tools > Serial Port
  • Hit the Upload button from the top left corner (Looks like an arrow point to the right)

Assuming all goes well, you should see the IDE message that avrdude is done, similar to this:

Verifying Firmware

The firmware is now loaded onto your board and you are now able to move onto Connecting to TunerStudio.

Optionally, you may perform a verification of the firmware by using the Arduino IDE's Serial Monitor. This can be started by selecting 'Serial Monitor' from the Tools menu.

In the window that appears, enter a capital "S" (no quotes) and press Enter. The Mega should respond with the year and month of the code version installed (xxxx.xx):

Speeduino 2017.03

NOTE: Ensure the baud rate is set to 115200

You can also enter "?" for a list of queries from your Mega:

=== Command Help ===

All commands are single character and are concatenated with their parameters 
without spaces. Some parameters are binary and cannot be entered through this 
prompt by conventional means. 
Syntax:  <command>+<parameter1>+<parameter2>+<parameterN>

=== List of Commands ===

A - Displays 31 bytes of currentStatus values in binary (live data)
B - Burn current map and configPage values to eeprom
C - Test COM port.  Used by Tunerstudio to see whether an ECU is on a given serial 
    port. Returns a binary number.
L - Displays map page (aka table) or configPage values.  Use P to change page (not 
    every page is a map)
N - Print new line.
P - Set current page.  Syntax:  P+<pageNumber>
R - Same as A command
S - Display signature number
Q - Same as S command
V - Display map or configPage values in binary
W - Set one byte in map or configPage.  Expects binary parameters. 
    Syntax:  W+<offset>+<newbyte>
t - Set calibration values.  Expects binary parameters.  Table index is either 0, 
    1, or 2.  Syntax:  t+<tble_idx>+<newValue1>+<newValue2>+<newValueN>
Z - Display calibration values
T - Displays 256 tooth log entries in binary
r - Displays 256 tooth log entries
? - Displays this help page

You can now test your new Speeduino code by starting TunerStudio and attempting to connect. See Connecting to TunerStudio for more details


Incorrect Arduino board selected

If you see the following (or similar) errors when trying to compile the firmware and the solutions:

scheduler.ino:317:7: error: ‘OCR4A’ was not declared in this scope
scheduler.ino:323:8: error: ‘TIMSK5’ was not declared in this scope 
scheduler.ino:323:25: error: ‘OCIE4A’ was not declared in this scope 

You may have the wrong kind of Arduino board selected. Set the board type by selecting Tools > Board > Arduino Mega 2560 or Mega ADK

Entire Speeduino project is not opened

The following can occur if you have only opened the speeduino.ino file rather than the whole project.

speeduino.ino:27:21: fatal error: globals.h: No such file or directory

Make sure all the files are contained within the same directory, then select File->Open and find the speeduino.ino file. If you have opened the project correctly, you should have multiple tabs along the top: