To compile the target firmware for OsmocomBB or SIMtrace, you need a GNU toolchain for ARM. You can either use binary packages provided by your distribution (recommended), or build a toolchain from source code yourself. There are various pre-compiled toolchains available (e.g. Code Sourcery), but not all of them will produce working firmware. We're trying to support all these configurations, but it might take a while to identify the source of a problem. If you have persistent errors when compiling, try using a different package.
You can use a pre-compiled toolchain provided by your GNU/Linux distribution.
For Debian based distributions (Ubuntu, Linux Mint, etc.), use the following command:
$ sudo apt install gcc-arm-none-eabi
$ sudo pacman -S arm-none-eabi-gcc arm-none-eabi-newlib
The following versions are confirmed to work:
Name : arm-none-eabi-gcc Version : 10.2.0-1 --- Name : arm-none-eabi-binutils Version : 2.34-1 --- Name : arm-none-eabi-newlib Version : 3.3.0-1
Building from source¶
Building old branches¶
If you need to build the firmware from old unmaintained branches (sylvain/burst_ind, sylvain/testing, jolly/testing, etc.), an older version of toolchain is needed.
Please follow the build instructions at: https://github.com/axilirator/gnu-arm-installer/
When using toolchain with GCC >=4.8, the firmware can be compiled, but will hang as soon as you want to sync to an ARFCN.
This issue has been fixed in master: http://cgit.osmocom.org/osmocom-bb/commit/?id=a903b3c1ee27047c79728b18ff6340d23d1aad2e.
Mac OS X¶
Apparently the arm-elf-gcc 4.3.2 from ports for MacOS X can compile the firmware as well after symlinking /opt/local/bin/arm-elf-ranlib to /opt/local/bin/arm-elf-linux-ranlib and /opt/local/bin/arm-elf-strip to /opt/local/bin/arm-elf-linux-strip. If you omit the links, there will be unresolvable references to symbols in the libraries.