Need help with tamago?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

1.1K Stars 33 Forks BSD 3-Clause "New" or "Revised" License 628 Commits 0 Opened issues


TamaGo - bare metal Go for ARM SoCs

Services available


Need anything else?

Contributors list

TamaGo - bare metal Go for ARM SoCs

tamago |

Copyright (c) F-Secure Corporation

TamaGo gopher


Andrea Barisani
[email protected] | [email protected]

Andrej Rosano
[email protected] | [email protected]


TamaGo is a framework that enables compilation and execution of unencumbered Go applications on bare metal ARM System-on-Chip (SoC) components.

The projects spawns from the desire of reducing the attack surface of embedded systems firmware by removing any runtime dependency on C code and Operating Systems.

The TamaGo framework consists of the following components:

  • A modified Go distribution which extends

    support to the
    target, allowing bare metal execution.
  • Go packages for SoC driver support.

  • Go packages for board support.

The modifications are meant to be minimal for both the Go distribution (< ~4000 LOC changed) and the target application (one import required), with a clean separation from other architectures.

Strong emphasis is placed on code re-use from existing architectures already included within the standard Go runtime, see Internals.

Both aspects are motivated by the desire of providing a framework that allows secure Go firmware development on embedded systems.

Current release level

GitHub release Build Status

The current release for the TamaGo modified Go distribution is tamago1.17.3, which adds

support to go1.17.3.

Binary releases for amd64 and armv7l Linux hosts are available.


The main documentation can be found on the project wiki.

The package API documentation can be found on

Supported hardware

The following table summarizes currently supported SoCs and boards.

| SoC | Board | SoC package | Board package | |---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| | NXP i.MX6ULZ | USB armory Mk II | imx6 | usbarmory/mark-two | | NXP i.MX6ULL | MCIMX6ULL-EVK | imx6 | mx6ullevk | | BCM2835 | Raspberry Pi Zero | bcm2835 | pi/pizero | | BCM2835 | Raspberry Pi 1 Model A+ | bcm2835 | pi/pi1 | | BCM2835 | Raspberry Pi 1 Model B+ | bcm2835 | pi/pi1 | | BCM2836 | Raspberry Pi 2 Model B | bcm2835 | pi/pi2 |


Go applications are simply required to import, the relevant board package to ensure that hardware initialization and runtime support takes place:

import (
    // Example for USB armory Mk II
    _ ""

Build the TamaGo compiler (or use the latest binary release):

cd tamago-go-latest/src && ./all.bash
cd ../bin && export TAMAGO=`pwd`/go

Go applications can be compiled with the compiler built in the previous step, with the addition of a few flags/variables:

# Example for USB armory Mk II
  ${TAMAGO} build -ldflags "-T 0x80010000  -E _rt0_arm_tamago -R 0x1000"

See the respective board package README file for compilation information for each specific target.

Executing and debugging

See the respective board package README file for execution and debugging information for each specific target (real or emulated).

The example application provides sample driver usage and instructions for native as well as emulated execution.


tamago |
Copyright (c) F-Secure Corporation

These source files are distributed under the BSD-style license found in the LICENSE file.

The TamaGo logo is adapted from the Go gopher designed by Renee French and licensed under the Creative Commons 3.0 Attributions license. Go Gopher vector illustration by Hugo Arganda.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.