GNU Arm Embedded Toolchain

GNUARM: Linux, Windows and outdated Mac OS X builds of GCC+Newlib+GDB Zylin.com GCC+GDB binaries for arm-elf, cortex, xscale, mips-elf, powerpc-eabi targets, platforms, hosted on Windows MinGW, Crossbuild Windows hosted from Debian, Cygwin,Linux,Mac x86 or Mac PowerPC. The next time you want to check out pre-defined macros supported by GCC on a platform, run the preprocessor with the flag -dM. It'll list out all the predefined macros available on the system. It'll list out all the predefined macros available on the system. Gcc-arm-linux-gnueabi free download. Arm Mbed OS Arm Mbed OS is an open source embedded operating system specifically designed for the Internet of Th.

Pre-built GNU bare-metal toolchain for 32-bit Arm processors

The GNU Arm Embedded toolchain contains integrated and validated packages featuring the GCC compiler, libraries, and other tools necessary for bare-metal software development. These toolchains target devices that are based on 32-bit Arm Cortex-A, Cortex-R and Cortex-M processors.

The toolchains are available for cross-compilation on Microsoft Windows (x86 32/64bit), Linux (x86_64 and 64-bit Arm), and Mac OS X host operating systems.

These toolchains are based on the Free Software Foundation (FSF) GNU open source tools and newlib.

Wanting to compile a small program I’d written in Rust to run on my home router, I found this guide to cross compilation of Rust code. The router is a Netgear R7000 with an ARM processor, running FreshTomato, a distribution of Linux for ARM and MIPS architecture consumer routers. The top of that guide shows an example of installing the cross-compilation toolchain for ARM on Ubuntu, but it required some work to adapt to Mac OS High Sierra, my desktop environment.

The guide suggests rustup can be used to install extra cross compilation targets. I already have rustup which I’ve used to install Rust for Mac OS and keep it up-to-date, so that’s handy. So I ran “rustup target list” to list all the installable targets:

Arm Linux Gcc Ubuntu

That’s a lot of possible targets. It looks like in the ARM space, there’s AArch64, arm-unknown, armebv7r, armv5te and armv7(r?) architectures of various variants. So, let’s google to see what kind of CPU the router has.

According to the OpenWRT wiki it’s a Broadcom BCM4709A0. So, what kind of architecture is that? Googling for “BCM4709A0” brought me to Wikidevi, which says it’s an ARM Cortex-A9. Looking at Wikipedia for the Cortex-A9 tells me:

Arm-linux-gnueabi-gcc Macos

• It’s a 32-bit architecture, so not AArch64
• It’s an ARMv7-A architecture

So I’d guess one of the armv7 targets is the best one. It’s probably not armv7-apple-ios or armv7-linux-androideabi, since this isn’t an iOS or Android OS. That leaves armv7-unknown-linux-gnueabihf, armv7-unknown-linux-musleabihf, armv7r-none-eabi and armv7r-none-eabihf. I know the router runs Linux, so let’s try the first two. I installed the armv7-unknown-linux-gnueabihf target with:

OK, let’s try compiling a “hello world” Rust application with that target:

That failed with a message “error: linking with cc failed: exit code: 1” and then a note showing the entire cc command, and a note saying:

OK, so I guess this is clang giving that error. Clang is the native C compiler for Mac OS, but I expect it can’t link an ARM executable in the way Rust wants. So, it looks like we need a linker for ARM. Reading the guide seems to suggest that Rust doesn’t have its own linker for Linux targets – it uses the linker from a C toolchain, for example the GNU C compiler. So we need to install a C toolchain targeting ARM.

My first stop when looking to install open source tools on Mac OS is Homebrew, and indeed there’s a formula on there for arm-linux-gnueabihf-binutils – it looks like that could be what we need to get a linker targeting ARM Linux. So let’s install that with:

That installs a set of tools named arm-linux-gnueabihf-addr2line, arm-linux-gnueabihf-ar and so on. I know the linker is normally invoked as “ld”, and cross-compilation toolchains by convention prefix their tool names with the target name, so the ARM Linux linker should be arm-linux-gnueabihf-ld. I know from the guide that this needs to go in ~/.cargo/config in a section like this:

But the Homebrew formula didn’t install arm-linux-gnueabihf-gcc – it only has arm-linux-gnueabihf-ld. Well, let’s try that instead, so the config is:

OK, let’s try compiling again…

This is more promising, but it looks like the linker can’t find all of those libraries to link with. Those look like parts of the GNU C library and other system libraries for Linux, which the Homebrew package arm-linux-gnueabihf-binutils doesn’t seem to include. These would normally be installed on a Linux system, but on Mac OS we don’t have them.

It seemed like I might need to install a more complete Linux toolchain that includes those libraries, but before trying that, let’s look at the other Rust target – armv7-unknown-linux-musleabihf. The “musl” in the name refers to the musl C library, a small C library that can be statically linked with Rust programs instead of the GNU C library. This sounds promising as it removes the need to link against libpthread, etc, which we had problems with earlier.

Let’s put the same linker configuration in ~/.cargo/config for the armv7-unknown-linux-musleabihf target:

And try compiling our Rust program with this target:

It built, so let’s copy the executable to the router:

And then SSH on to the router and run it:

Great, it works! Using the musl C library and statically linking everything is somewhat less optimal than linking against the C library that’s already installed on Linux, as it means the built executable size is larger, but it’s good enough for a simple Rust program.