Toolchain » History » Version 23
fixeria, 02/18/2024 01:57 PM
| 1 | 12 | fixeria | h1. Toolchain |
|---|---|---|---|
| 2 | 1 | tsaitgaist | |
| 3 | 23 | fixeria | {{>toc}} |
| 4 | |||
| 5 | 20 | fixeria | 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. |
| 6 | 5 | tsaitgaist | |
| 7 | 20 | fixeria | h3. Binary packages |
| 8 | 1 | tsaitgaist | |
| 9 | 12 | fixeria | You can use a pre-compiled toolchain provided by your GNU/Linux distribution. |
| 10 | 1 | tsaitgaist | |
| 11 | 12 | fixeria | For Debian based distributions (Ubuntu, Linux Mint, etc.), use the following command: |
| 12 | 1 | tsaitgaist | |
| 13 | 12 | fixeria | <pre> |
| 14 | $ sudo apt install gcc-arm-none-eabi |
||
| 15 | </pre> |
||
| 16 | 1 | tsaitgaist | |
| 17 | 12 | fixeria | For ArchLinux (https://www.archlinux.org/packages/community/x86_64/arm-none-eabi-gcc/): |
| 18 | 11 | tsaitgaist | |
| 19 | 12 | fixeria | <pre> |
| 20 | 19 | fixeria | $ sudo pacman -S arm-none-eabi-gcc arm-none-eabi-newlib |
| 21 | 12 | fixeria | </pre> |
| 22 | 1 | tsaitgaist | |
| 23 | 20 | fixeria | The following versions are confirmed to work: |
| 24 | 1 | tsaitgaist | |
| 25 | 20 | fixeria | <pre> |
| 26 | Name : arm-none-eabi-gcc |
||
| 27 | Version : 10.2.0-1 |
||
| 28 | --- |
||
| 29 | Name : arm-none-eabi-binutils |
||
| 30 | Version : 2.34-1 |
||
| 31 | --- |
||
| 32 | Name : arm-none-eabi-newlib |
||
| 33 | Version : 3.3.0-1 |
||
| 34 | </pre> |
||
| 35 | 17 | fixeria | |
| 36 | 20 | fixeria | h3. Building from source |
| 37 | |||
| 38 | If a pre-compiled toolchain provided by your distribution fails to produce working firmware images, you can build your own toolchain known to be working with [[OsmocomBB]], see here: [[GnuArmToolchain]]. |
||
| 39 | 17 | fixeria | |
| 40 | h3. Building old branches |
||
| 41 | |||
| 42 | 21 | fixeria | 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. |
| 43 | 1 | tsaitgaist | |
| 44 | 21 | fixeria | This combination is known to work: |
| 45 | |||
| 46 | * binutils 2.21.1a, |
||
| 47 | * newlib 1.19.0, |
||
| 48 | * gcc 4.8.2. |
||
| 49 | |||
| 50 | 22 | laforge | It can be compiled using our "Dockerfiles":https://gitea.osmocom.org/osmocom/docker-playground: |
| 51 | 21 | fixeria | |
| 52 | <pre> |
||
| 53 | 22 | laforge | $ git clone https://gitea.osmocom.org/osmocom/docker-playground |
| 54 | 21 | fixeria | $ cd docker-playground/arm-none-eabi-gcc-4.8.2 |
| 55 | $ make |
||
| 56 | </pre> |
||
| 57 | |||
| 58 | Usage example: |
||
| 59 | |||
| 60 | <pre> |
||
| 61 | $ cd osmocom-bb |
||
| 62 | $ docker run --user $(id -u) -v $(pwd):/data -it --rm root/arm-none-eabi-gcc-4.8.2 |
||
| 63 | # cd /data/src |
||
| 64 | # make firmware |
||
| 65 | </pre> |
||
| 66 | 17 | fixeria | |
| 67 | 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. |
||
| 68 | This issue has been fixed in master: http://cgit.osmocom.org/osmocom-bb/commit/?id=a903b3c1ee27047c79728b18ff6340d23d1aad2e. |
||
| 69 | |||
| 70 | 1 | tsaitgaist | h3. Mac OS X |
| 71 | |||
| 72 | 17 | fixeria | 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. |
