This repo is a fork of kuhlix/avr32-toolchain which is a fork of a fork of the original jsnyder/avr32-toolchain: Makefile & supporting patches/scripts to build an AVR32 toolchain.
This repo contains a Makefile that builds an AVR32 toolchain with the latest patches released by Atmel (now Microchip). The patches are pretty old (from 2013) and so is the resulting gcc compiler and toolchain (gcc 4.4.7, from 2012).
The Makefile downloads, builds and installs everything.
The only two additions to this repo, compared to kuhlix/avr32-toolchain, are:
- Possibility to execute the build in a container (using
ubuntu-avr32-builder/Dockerfile) - Addition of alternative Makefile
Makefile.newlib-gs-1.16.mkwhich uses thenewlibof the GomSpace/avr32-newlib repo
The build-in-container bash script creates a container image with the
required build tools and then executes the build inside the docker container.
It is not required to use the containerized build, although it might
prove useful in the distant future.
Execute the build with:
./build-in-container
Then wait approximately 10 minutes and the output will be in the ./avr32-toolchain
folder (unless you changed it to something else)
The released tarball has name/version: 4.4.7+Atmel3.4.2build1 denoting gcc-4.4.7 with Atmel v3.4.2 patches. The build1 suffix means first build.
This avr32 toolchain uses newlib v1.19 (released 2011-12-19).
The Gomspace version of newlib is v1.16.0 (released 2007-12-19) and with some backports from 2.2.0. The repo is GomSpace/avr32-newlib: Fork of embecosm/avr32-newlib with GomSpace modifications
You can build the avr32 toolchain with either version of newlib.
If you want to build with the Gomspace newlib version then use the
Makefile.newlib-gs-1.16.mk makefile instead of Makefile.
To do this, you can use:
./build-in-container -gs
Tip: If you onlt want to build newlib, use the Make target: install-newlib
== AVR32 Toolchain Builder ==
This is a early implementation of a Makefile for an AVR32 toolchain builder for Mac OS X & Linux, and it has not been extensively tested. That said the patches are taken directly from Atmel, and basic testing is done with some more complicated builds (i.e.: link:http://eluaproject.net[eLua] in float and integer mode) to ensure that that at least these work after toolchain modifications.
Note: If you have previously built a toolchain of another version, out of the same builder directory, make sure to do the following first before building with newer sources:
=== Requirements (OS X) ===
You will need to have GCC, make and binutils on your machine to compile all of this. You can get all of these on Mac OS X, by just installing the Apple link:http://developer.apple.com/technologies/tools/[Developer Tools]. You should be able to download free versions of 3.x from the ADC website, install from the OS X install disc that came with your machine, or download XCode 4 from the App Store (now free again for all registered users).
You will also need gmp, mpfr and mpc first. I recommend installing these from link:https://github.com/mxcl/homebrew[homebrew] for now. I'll add these to the Makefile once I have a consistent configuration that can be used for both Linux & OS X.
If you would like to build dfu-programmer, also install libusb:
=== Requirements (Ubuntu) ===
These instructions should now also work on Ubuntu Linux, provided the following packages have been installed prior to attempting the build:
sudo apt-get install curl flex bison libgmp3-dev libmpfr-dev autoconf build-essential libncurses5-dev libmpc-dev unzip git
If you would like to build dfu-programmer, also install libusb:
=== Main Build Instructions ===
Next build the toolchain:
You should be able to also specify a specific install/prefix location by building using the following type of invokation:
If you do this, make sure you have permissions to create a directory at this location and/or to create directories within this location if the directory already exists.
NOTE: If you're running Mac OS X Lion or XCode 4.1 you may find that you're unable to bootstrap GCC. To work around this until the issue is fixed in Apple's distribution of llvm-gcc, use the following command instead of the above to build.
This should build the compiler, newlib, gdb, etc.. and install them all into a directory called arm-cs-tools in your home directory. If you want to install to another location, feel free to change the export lines and to adjust the definitions at the top of the Makefile.
Keep in mind that the Makefile does install at the end of each build.
Once you’re done, the makefile should notify you of the install location, which will be based on the git revision if you cloned the repository or the current date if you grabbed a tarball and/or you don't have the git binary. The message should look like the following:
====== INSTALLATION NOTE ====== Your tools have now been installed at the following prefix: /Users/jsnyder/avr32-tools-bd2485b
Please be sure to add something similar to the following to your .bash_profile, .zshrc, etc: export PATH=/Users/jsnyder/avr32-tools-bd2485b/bin:$PATH
If it uses the date instead the the git short revision will bve replaced with a date number like: 20110726.
If you also would like dfu-programmer installed intalled (make sure you have previously installed libusb as described in requirements):
=== Special Thanks ===
Special thanks to Rob Emanuele for the basis of this Makefile: http://elua-development.2368040.n2.nabble.com/Building-GCC-for-Cortex-td2421927.html