{"id":995,"date":"2019-09-23T18:14:02","date_gmt":"2019-09-23T17:14:02","guid":{"rendered":"https:\/\/mightydevices.com\/?p=995"},"modified":"2019-09-24T09:23:21","modified_gmt":"2019-09-24T08:23:21","slug":"building-bare-metal-stm32l4-firmware-using-clang-llvm","status":"publish","type":"post","link":"https:\/\/mightydevices.com\/index.php\/2019\/09\/building-bare-metal-stm32l4-firmware-using-clang-llvm\/","title":{"rendered":"Building bare-metal STM32L4 firmware using Clang\/LLVM"},"content":{"rendered":"\n

In this tutorial I’ll show you how to build a basic bare-metal application for Cortex-M4F micro-controller using LLVM without having to resort to building the LLVM toolchain itself which can be tedious and time consuming. All in all LLVM is recognized for it’s ability to compile for different architectures (a.k.a cross-compile) so we should be good even using the most default<\/em> of packages.<\/p>\n\n\n\n

The following steps were done on Alpine Linux image using Windows -hosted Docker (image alpine:latest<\/code>) but all of it shall be applicable to other operating systems.<\/p>\n\n\n\n

From this point on I’ll assume that you have Docker installed and ready. So let’s begin by building the image with all tools necessary for development. Get the Dockerfile that I’ve prepared for this tutorial from here: https:\/\/github.com\/MightyDevices\/docker-llvm-arm-none-eabi-builder<\/a> Open up the command prompt in the directory where you’ve put the Dockerfile and type in the following command to build the image:<\/p>\n\n\n\n

docker build -t arm-build .<\/code><\/pre>\n\n\n\n
Image will go by the name arm-build<\/code>. This process may take a while as couple of things needs to be done. Firstly clang\/llvm toolchain is installed which is followed by GNU make installation. Then we download the arm-none-eabi<\/code> toolchain so that we have libraries (like libm<\/code> for math) for our projects.<\/p>\n\n\n\n
After the image build is done we can start the container in interactive mode with \/bin\/sh interpreter running. Docker also allows us to use a directory that will be shared between the Host OS (In my case: Windows) and Guest OS (Alpine) so let’s have that one as well and use it to store the project files. The command for all of that should look like this:<\/p>\n\n\n\n
mkdir share\ndocker run -it -v\"%cd%\/share\":\/share arm-build sh<\/code><\/pre>\n\n\n\n
Here I’ve used the Windows magical %cd%<\/code> in order to get the full path to the current directory. Docker on Windows has a hard time with relative paths. After executing the command you’ll be left with the Alpine Linux shell.<\/p>\n\n\n\n
Let’s now get the source files for the test project and try to adapt them to this build environment. How about we use something simple, like this one:  https:\/\/github.com\/MightyDevices\/startup-stm32l433<\/a>. Let’s clone it into the ‘share’ directory. In the Alpine Shell type in following commands<\/p>\n\n\n\n
cd \/share\ngit clone https:\/\/github.com\/MightyDevices\/startup-stm32l433\ncd startup-stm32l433<\/code><\/pre>\n\n\n\n
This project was prepared to be build either with GCC or with LLVM. In order to build with LLVM Toolchain one needs to use the following command:<\/p>\n\n\n\n
make TOOLCHAIN=llvm<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
If you do that you’ll notice an error that is caused by the lack of include files\/ libraries. The LLVM is a great for cross-compiling but it comes with no prebuild libraries and header files, and since we want to avoid the need of building these let’s use the libraries from the official ARM GCC Toolchain.<\/p>\n\n\n\n
In the project’s Makefile look for the lines that contain the INC_DIRS<\/code> and LIB_DIRS<\/code>.  Since the docker image build process took care of downloading the  ARM GCC Toolchain let’s now point the Clang to proper directories that contain all the necessary files. For the includes append the following:<\/p>\n\n\n\n
INC_DIRS += \/gcc-arm-none-eabi-8-2019-q3-update\/arm-none-eabi\/include\nINC_DIRS += \/gcc-arm-none-eabi-8-2019-q3-update\/lib\/gcc\/arm-none-eabi\/8.3.1\/include<\/code><\/pre>\n\n\n\n
and for the libraries use the paths below:<\/p>\n\n\n\n
LIB_DIRS += \/gcc-arm-none-eabi-8-2019-q3-update\/arm-none-eabi\/lib\/thumb\/v7e-m+fp\/hard\/\nLIB_DIRS += \/gcc-arm-none-eabi-8-2019-q3-update\/lib\/gcc\/arm-none-eabi\/8.3.1\/thumb\/v7e-m+fp\/hard\/<\/code><\/pre>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
This complex path name comes from the fact that we use a Cortex-M4F micro-controller which has the armv7e-m<\/code> core with hardware floating point unit (FPU), hence the hard<\/code>at the end of the path. If you were to build a project for different core\/FPU these would need to be altered accordingly. After all that you should end up with a working binary image, again, by issuing the make<\/code> command<\/p>\n\n\n\n
make TOOLCHAIN=llvm<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In this tutorial I’ll show you how to build a basic bare-metal application for Cortex-M4F micro-controller using LLVM without having to resort to building the LLVM toolchain itself which can be tedious and time consuming. All in all LLVM is recognized for it’s ability to compile for different architectures (a.k.a cross-compile) so we should be…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[6,5],"_links":{"self":[{"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/posts\/995"}],"collection":[{"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/comments?post=995"}],"version-history":[{"count":15,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/posts\/995\/revisions"}],"predecessor-version":[{"id":1016,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/posts\/995\/revisions\/1016"}],"wp:attachment":[{"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/media?parent=995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/categories?post=995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mightydevices.com\/index.php\/wp-json\/wp\/v2\/tags?post=995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}