How to cross-compile with the Developer Package

Revision as of 12:46, 22 January 2019 by Frq08988 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)




1 Article purpose[edit]

This article provides simple examples for the Developer Package of the OpenSTLinux distribution, that illustrate cross-compilation with the SDK:

  • modification of software elements delivered as source code (for example the Linux kernel)
  • addition of software (for example the Linux kernel module or user-space applications)

These examples also show how to deploy the results of the cross-compilation on the target, through a network connection to the host machine.

Info.png There are many ways to achieve the same result; this article aims to provide at least one solution per example. You are at liberty to explore other methods that are better adapted your development constraints.

2 Prerequisites[edit]

The prerequisites from the Cross-compile with OpenSTLinux SDK article must be executed, and the cross-compilation and deployment of any piece of software, as explained in that article, is known.

The board and the host machine are connected through an Ethernet link, and a remote terminal program is started on the host machine: see How to get Terminal.

The target is started, and its IP address (<board ip address>) is known.

Info.png If you encounter a problem with any of the commands in this article, remember that the README.HOW_TO.txt helper files, from the Linux kernel, U-Boot and TF-A installation directories, are the build references.

3 Modifying the Linux kernel configuration[edit]

3.1 Preamble[edit]

Warning.png Please read carefully and pay attention to the following point before modifying the Linux kernel configuration

The Linux kernel configuration option that you want to modify might be used by external out-of-tree Linux kernel modules (for example the GPU kernel driver), and these should then be recompiled. These modules are, by definition, outside the kernel tree structure, and are not delivered in the Developer Package source code; it is not possible to recompile them with the Developer Package. Consequently, if the Linux kernel is reconfigured and recompiled with this option then deployed on the board, the external out-of-tree Linux kernel modules might no longer be loaded.

There are two possible situations:

  • This is not a problem for the use cases on which you are currently working. In this case you can use the Developer Package to modify and recompile the Linux kernel.
  • This is a problem for the use cases on which you are currently working. In this case you need to switch on the STM32MP1 Distribution Package, and after having modified the Linux kernel configuration, use it to rebuild the whole image (that is, not only the Linux kernel but also the external out-of-tree Linux kernel modules).

Example:

  • Let's assume that the FUNCTION_TRACER and FUNCTION_GRAPH_TRACER options are activated to install the ftrace Linux kernel feature
  • This feature is used to add tracers in the whole kernel, including the external out-of-tree Linux kernel modules
  1. The Developer Package is used to reconfigure and recompile the Linux kernel, and to deploy it on the board
    1. The external out-of-tree Linux kernel modules are not recompiled. This is the case for the GPU kernel driver
    2. Consequently, the Linux kernel fails to load the GPU kernel driver module. However, even if the display no longer works, the Linux kernel boot succeeds, and the setup is sufficient, for example, to debug use cases involving an Ethernet or USB connection
  2. The Distribution Package is used to reconfigure the Linux kernel, and to rebuild and deploy the whole image on the board
    1. The external out-of-tree Linux kernel modules are recompiled, including the GPU kernel driver
    2. Consequently, the Linux kernel succeeds in loading the GPU kernel driver module. The display is available.

3.2 STM32MP157 Evaluation boards[edit]

This simple example modifies the value defined for the contiguous memory area (CMA) size.

  • Get the current value of the CMA size (128 Mbytes here) through the analysis of the target boot log
Board $> dmesg | grep -i cma
[    0.000000] cma: Reserved 128 MiB at 0xf0000000
  • Go to the <Linux kernel build directory>
PC $> cd <Linux kernel build directory>
  • Navigate to "Device Drivers - Generic Driver Options"
    • select "Size in Megabytes"
    • modify its value to 256
    • exit and save the new configuration
  • Check that the configuration file (.config) has been modified
PC $> grep -i CONFIG_CMA_SIZE_MBYTES .config
CONFIG_CMA_SIZE_MBYTES=256
  • Get the new value of the CMA size (256 Mbytes) through the analysis of the target boot log
Board $> dmesg | grep -i cma
[    0.000000] cma: Reserved 256 MiB at 0xe0000000

4 Modifying the Linux kernel device tree[edit]

This simple example modifies the default status of a user LED.

4.1 STM32MP157 Evaluation boards[edit]

  • With the board started; check that the user LED (LD3) is disabled
  • Go to the <Linux kernel source directory>
PC $> cd <Linux kernel source directory>
  • Edit the arch/arm/boot/dts/stm32mp157c-ed1.dts device tree source file
  • Change the status of the "stm32mp:green:user" led to "okay", and set its default state to "on"
	led {
		compatible = "gpio-leds";
		blue {
			label = "heartbeat";
			gpios = <&gpiod 9 GPIO_ACTIVE_HIGH>;
			linux,default-trigger = "heartbeat";
			default-state = "off";
		};
 		green {
 			label = "stm32mp:green:user";
 			gpios = <&gpioa 14 GPIO_ACTIVE_LOW>;
 			default-state = "on";
  		};
	};
  • Go to the <Linux kernel build directory>
PC $> cd <Linux kernel build directory>
  • Generate the device tree blobs (*.dtb)
PC $> make dtbs
PC $> cp arch/arm/boot/dts/stm32mp157*.dtb install_artifact/boot/
  • Update the device tree blobs on the board
PC $> scp install_artifact/boot/stm32mp157*.dtb root@<board ip address>:/boot/
Info.png If the /boot mounting point doesn't exist yet, please see how to create a mounting point
  • Reboot the board
Board $> reboot
  • Check that the user LED (LD3) is enabled (green)

5 Modifying a built-in Linux kernel device driver[edit]

This simple example adds unconditional log information when the display driver is probed.

  • Check that there's no log information when the display driver is probed
Board $> dmesg | grep -i stm_drm_platform_probe
Board $>
  • Go to the <Linux kernel source directory>
PC $> cd <Linux kernel source directory>
  • Edit the ./drivers/gpu/drm/stm/drv.c source file
  • Add a log information in the stm_drm_platform_probe function
static int stm_drm_platform_probe(struct platform_device *pdev)
{
	struct device *dev = &pdev->dev;
	struct drm_device *ddev;
	int ret;
	[...]

	DRM_INFO("Simple example - %s\n", __func__);

	return 0;
	[...]
}
  • Go to the <Linux kernel build directory>
PC $> cd <Linux kernel build directory>
  • Cross-compile the Linux kernel (please check the load address in the README.HOW_TO.txt helper file)
PC $> make uImage LOADADDR=0xC2000040
PC $> cp arch/arm/boot/uImage install_artifact/boot/
  • Update the Linux kernel image on board
PC $> scp install_artifact/boot/uImage root@<board ip address>:/boot/
Info.png If the /boot mounting point doesn't exist yet, please see how to create a mounting point
  • Reboot the board
Board $> reboot
  • Check that there is now log information when the display driver is probed
Board $> dmesg | grep -i stm_drm_platform_probe
[    5.005833] [drm] Simple example - stm_drm_platform_probe

6 Modifying/adding an external Linux kernel module[edit]

Most device drivers (modules) in the Linux kernel can be compiled either into the kernel itself (built-in/internal module) or as Loadable Kernel Modules (LKM/external module) that need to be placed in the root file system under the /lib/modules directory. An external module can be in-tree (in the kernel tree structure), or out-of-tree (outside the kernel tree structure).

6.1 Modifying an external in-tree Linux kernel module[edit]

This simple example adds an unconditional log information when the virtual video test driver (vivid) kernel module is probed or removed.

  • Go to the <Linux kernel source directory>
PC $> cd <Linux kernel source directory>
  • Edit the ./drivers/media/platform/vivid/vivid-core.c source file
  • Add log information in the vivid_probe and vivid_remove functions
static int vivid_probe(struct platform_device *pdev)
{
	const struct font_desc *font = find_font("VGA8x16");
	int ret = 0, i;
	[...]

	/* n_devs will reflect the actual number of allocated devices */
	n_devs = i;

	pr_info("Simple example - %s\n", __func__);

	return ret;
}
static int vivid_remove(struct platform_device *pdev)
{
	struct vivid_dev *dev;
	unsigned int i, j;
	[...]

	pr_info("Simple example - %s\n", __func__);

	return 0;
}
  • Go to the <Linux kernel build directory>
PC $> cd <Linux kernel build directory>

  • Cross-compile the Linux kernel modules
PC $> make modules
PC $> make INSTALL_MOD_PATH="$PWD/../<Linux kernel build directory>/install_artifact" modules_install
  • Update the vivid kernel module on the board (please check the kernel version <kernel version>)
PC $> scp install_artifact/lib/modules/<kernel version>/kernel/drivers/media/platform/vivid/vivid.ko root@<board ip address>:/lib/modules/<kernel version>/kernel/drivers/media/platform/vivid/

OR

PC $> scp -r install_artifact/lib/modules/* root@<board ip address>:/lib/modules/
  • Update dependency descriptions for loadable kernel modules, and synchronize the data on disk with memory
Board $> /sbin/depmod -a
Board $> sync
  • Insert the vivid kernel module into the Linux kernel
Board $> modprobe vivid                   
[...]
[ 3412.784638] Simple example - vivid_probe
  • Remove the vivid kernel module from the Linux kernel
Board $> rmmod vivid
[...]
[ 3423.708517] Simple example - vivid_remove

6.2 Adding an external out-of-tree Linux kernel module[edit]

This simple example adds a "Hello World" external out-of-tree Linux kernel module to the Linux kernel.

  • Prerequisite: the Linux source code is installed, and the Linux kernel has been cross-compiled
  • Go to the working directory that contains all the source code (that is, the directory that contains the Linux kernel, U-Boot and TF-A source code directories)
PC $> cd <tag>/sources/arm-<distro>-linux-gnueabi
  • Export to KERNEL_SRC_PATH the path to the Linux kernel build directory that contains both the Linux kernel source code and the configuration file (.config)
PC $> export KERNEL_SRC_PATH=$PWD/<Linux kernel build directory>/
Example:
PC $> export KERNEL_SRC_PATH=$PWD/linux-stm32mp-4.14/build
  • Create a directory for this kernel module example
PC $> mkdir kernel_module_example
PC $> cd kernel_module_example
  • Create the source code file for this kernel module example: kernel_module_example.c
// SPDX-identifier: GPL-2.0
/*
 * Copyright (C) STMicroelectronics SA 2018
 *
 * Authors: Jean-Christophe Trotin <jean-christophe.trotin@st.com>
 *
 */

#include <linux/module.h>    /* for all kernel modules */
#include <linux/kernel.h>    /* for KERN_INFO */
#include <linux/init.h>      /* for __init and __exit macros */

static int __init kernel_module_example_init(void)
{
	printk(KERN_INFO "Kernel module example: hello world from STMicroelectronics\n");
	return 0;
}

static void __exit kernel_module_example_exit(void)
{
	printk(KERN_INFO "Kernel module example: goodbye from STMicroelectronics\n");
}

module_init(kernel_module_example_init);
module_exit(kernel_module_example_exit);

MODULE_DESCRIPTION("STMicroelectronics simple external out-of-tree Linux kernel module example");
MODULE_AUTHOR("Jean-Christophe Trotin <jean-christophe.trotin@st.com>");
MODULE_LICENSE("GPL v2");
  • Create the makefile for this kernel module example: Makefile
Info.png All the indentations in a makefile are tabulations
# Makefile for simple external out-of-tree Linux kernel module example

# Object file(s) to be built
obj-m := kernel_module_example.o

# Path to the directory that contains the Linux kernel source code
# and the configuration file (.config)
KERNEL_DIR ?= <Linux kernel path>

# Path to the directory that contains the generated objects
DESTDIR ?= $(KERNEL_DIR)/install_artifact

# Path to the directory that contains the source file(s) to compile
PWD := $(shell pwd) 
  
default:
	$(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules

install:
	$(MAKE) -C $(KERNEL_DIR) M=$(PWD) INSTALL_MOD_PATH=$(DESTDIR) modules_install

clean:
	$(MAKE) -C $(KERNEL_DIR) M=$(PWD) clean
  • Cross-compile the kernel module example
PC $> make clean
PC $> make
PC $> make install
  • Go to the <Linux kernel build directory>
PC $> cd <Linux kernel build directory>
  • The generated kernel module example is in: install_artifact/lib/modules/<kernel version>/extra/kernel_module_example.ko
  • Push this kernel module example on board (please check the kernel version <kernel version>)
PC $> ssh root@<board ip address> mkdir -p /lib/modules/<kernel version>/extra
PC $> scp install_artifact/lib/modules/<kernel version>/extra/kernel_module_example.ko root@<board ip address>:/lib/modules/<kernel version>/extra

OR

PC $> scp -r install_artifact/lib/modules/* root@<board ip address>:/lib/modules/
  • Update dependency descriptions for loadable kernel modules, and synchronize the data on disk with memory
Board $> /sbin/depmod -a
Board $> sync
  • Insert the kernel module example into the Linux kernel
Board $> modprobe kernel_module_example
[18167.821725] Kernel module example: hello world from STMicroelectronics
  • Remove the kernel module example from the Linux kernel
Board $> rmmod kernel_module_example
[18180.086722] Kernel module example: goodbye from STMicroelectronics

7 Modifying the U-Boot[edit]

This simple example adds unconditional log information when U-Boot starts. Within the scope of the trusted boot chain, U-Boot is used as second stage boot loader (SSBL).

7.1 STM32MP157 Evaluation boards[edit]

  • Have a look at the U-Boot log information when the board reboots
Board $> reboot
[...]
U-Boot <U-Boot version>

CPU: STM32MP1 rev1.0
Model: STMicroelectronics STM32MP157C [...]
Board: stm32mp1 in trusted mode
[...]
  • Go to the <U-Boot source directory>
PC $> cd <U-Boot source directory>
Example:
PC $> cd u-boot-trusted-stm32mp-<U-Boot version>-AUTOINC+<U-Boot SHA1>/git
  • Edit the ./board/st/stm32mp1/stm32mp1.c source file
  • Add a log information in the checkboard function
int checkboard(void)
{
	char *mode;

	[...]

	printf("Board: stm32mp1 in %s mode\n", mode);
	printf("U-Boot simple example\n");

	return 0;
}
  • Get the list of supported configurations
PC $> make -f $PWD/../Makefile.sdk help
Configured U-Boot config(s):
  stm32mp15_basic_defconfig config (basic type) for u-boot.img binary
    with device tree: stm32mp157a-dk1
    with device tree: stm32mp157c-dk2
    with device tree: stm32mp157c-ed1
    with device tree: stm32mp157c-ev1
  stm32mp15_trusted_defconfig config (trusted type) for u-boot.stm32 binary
    with device tree: stm32mp157a-dk1
    with device tree: stm32mp157c-dk2
    with device tree: stm32mp157c-ed1
    with device tree: stm32mp157c-ev1
  stm32mp15_optee_defconfig config (optee type) for u-boot.stm32 binary
    with device tree: stm32mp157a-dk1
    with device tree: stm32mp157c-dk2
    with device tree: stm32mp157c-ed1
    with device tree: stm32mp157c-ev1

Available targets:
  all   : build U-Boot binaries for defined config(s)
  clean : clean build directories from generated files
  • Cross-compile the U-Boot: trusted boot for STM32MP157 Evaluation board
PC $> make -f $PWD/../Makefile.sdk all UBOOT_CONFIGS=stm32mp15_trusted_defconfig,trusted,u-boot.stm32 DEVICE_TREE="stm32mp157c-ev1"
  • Go to the directory in which the compilation results are stored
PC $> cd build-trusted/
  • Reboot the board, and hit any key to stop in the U-boot shell
Board $> reboot
[...]
Hit any key to stop autoboot:  0 
STM32MP> 
  • Connect a USB cable between the host machine and the board via the USB OTG ports
  • In the U-Boot shell, call the USB mass storage function
STM32MP> ums 0 mmc 0
Info.png For more information about the usage of U-Boot UMS functionality, see How to use USB mass storage in U-Boot
  • On the host machine, check the partition associated with the secondary stage boot loader (ssbl): sdc3 here
PC $> ls -l /dev/disk/by-partlabel/
total 0
lrwxrwxrwx 1 root root 10 Jan 17 18:05 bootfs -> ../../sdc4
lrwxrwxrwx 1 root root 10 Jan 17 18:05 fsbl1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jan 17 18:05 fsbl2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jan 17 18:05 rootfs -> ../../sdc5
lrwxrwxrwx 1 root root 10 Jan 17 18:05 ssbl -> ../../sdc3
lrwxrwxrwx 1 root root 10 Jan 17 18:05 userfs -> ../../sdc6
  • Copy the binary (u-boot.stm32) to the dedicated partition
PC $> dd if=u-boot.stm32 of=/dev/sdc3 bs=1M conv=fdatasync
  • Reset the U-Boot shell
STM32MP> reset
  • Have a look at the new U-Boot log information when the board reboots
[...]
U-Boot <U-Boot version>

CPU: STM32MP1 rev1.0
Model: STMicroelectronics STM32MP157C [...]
Board: stm32mp1 in trusted mode
U-Boot simple example
[...]

8 Modifying the TF-A[edit]

This simple example adds unconditional log information when the TF-A starts. Within the scope of the trusted boot chain, TF-A is used as first stage boot loader (FSBL).

8.1 STM32MP157 Evaluation boards[edit]

  • Have a look at the TF-A log information when the board reboots
Board $> reboot
[...]
INFO:      System reset generated by MPU (MPSYSRST)
INFO:    Using SDMMC
[...]
  • Go to the <TF-A source directory>
PC $> cd <TF-A source directory>
 Example:
 PC $> cd tf-a-stm32mp-<TF-A version>-AUTOINC+<TF-A SHA1>/git
  • Edit the ./plat/st/stm32mp1/bl2_io_storage.c source file
  • Add a log information in the stm32mp1_io_setup function
void stm32mp1_io_setup(void)
{
	int io_result;
	[...]
 
	/* Add a trace about reset reason */
	print_reset_reason();

	INFO("TF-A simple example");

	[...]
}
  • Get the list of supported configurations
PC $> make -f $PWD/../Makefile.sdk help
Available targets:
  all   : build TF-A binaries for defined config(s)
  clean : clean build directories from generated files

TF-A configuration:
  TF_A_CONFIG = trusted optee
  TFA_DEVICETREE = stm32mp157a-dk1 stm32mp157c-dk2   stm32mp157c-ed1   stm32mp157c-ev1 
  ELF_DEBUG_ENABLE = '1' ('1' to export elf files)
  • Cross-compile the TF-A: trusted boot for STM32MP157 Evaluation board
PC $> make -f $PWD/../Makefile.sdk all TF_A_CONFIG=trusted TFA_DEVICETREE=stm32mp157c-ev1
  • Go to the directory in which the compilation results are stored
PC $> cd ../build/trusted
  • Reboot the board, and hit any key to stop in the U-boot shell
Board $> reboot
[...]
Hit any key to stop autoboot:  0 
STM32MP> 
  • Connect a USB cable between the host machine and the board via the USB OTG ports
  • In the U-Boot shell, call the USB mass storage function
STM32MP> ums 0 mmc 0
Info.png For more information about the usage of U-Boot UMS functionality, see How to use USB mass storage in U-Boot
  • On the host machine, check the partition associated with the first stage boot loader (fsbl1 and fsbl2 as backup): sdc1 and sdc2 (as backup) here
PC $> ls -l /dev/disk/by-partlabel/
total 0
lrwxrwxrwx 1 root root 10 Jan 17 18:05 bootfs -> ../../sdc4
lrwxrwxrwx 1 root root 10 Jan 17 18:05 sfsbl1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jan 17 18:05 sfsbl2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jan 17 18:05 rootfs -> ../../sdc5
lrwxrwxrwx 1 root root 10 Jan 17 18:05 ssbl -> ../../sdc3
lrwxrwxrwx 1 root root 10 Jan 17 18:05 userfs -> ../../sdc6
  • Copy the binary (tf-a-stm32mp157c-ev1-trusted.stm32) to the dedicated partition; to test the new TF-A binary, it might be useful to keep the old TF-A binary in the backup FSBL (fsbl2)
PC $> dd if=tf-a-stm32mp157c-ev1-trusted.stm32 of=/dev/sdc1 bs=1M conv=fdatasync
  • Reset the U-Boot shell
STM32MP> reset
  • Have a look at the new TF-A log information when the board reboots
[...]
INFO:      System reset generated by MPU (MPSYSRST)
INFO:    TF-A simple example
INFO:    Using SDMMC
[...]

9 Adding a "hello world" user space example[edit]

Thanks to the OpenSTLinux SDK, it is easy to develop a project outside of the OpenEmbedded build system. This chapter shows how to compile and execute a simple "hello world" example.

9.1 Source code file[edit]

  • Go to the working directory that contains all the source codes (i.e. directory that contains the Linux kernel, U-Boot and TF-A source code directories)
PC $> cd <tag>/sources/arm-<distro>-linux-gnueabi
  • Create a directory for this user space example
PC $> mkdir hello_world_example
PC $> cd hello_world_example
  • Create the source code file for this user space example: hello_world_example.c
// SPDX-identifier: GPL-2.0
/*
 * Copyright (C) STMicroelectronics SA 2018
 *
 * Authors: Jean-Christophe Trotin <jean-christophe.trotin@st.com>
 *
 */

#include <stdio.h>
#include <unistd.h>

int main(int argc, char **argv)
{
	int i =11;

	printf("\nUser space example: hello world from STMicroelectronics\n");
	setbuf(stdout,NULL);
	while (i--) {
		printf("%i ", i);
		sleep(1);
	}
	printf("\nUser space example: goodbye from STMicroelectronics\n");

	return(0);
}

9.2 Cross-compilation[edit]

Three ways to use the OpenSTLinux SDK to cross-compile this user space example are proposed below: (1) command line (2) makefile-based project (3) autotools-based project.

9.2.1 Command line[edit]

This method allows quick cross-compilation of a single-source code file. It applies if the project has only one file.
The cross-development toolchain is associated with the sysroot that contains the header files and libraries needed for generating binaries that run on the target architecture (see SDK for OpenSTLinux distribution#Native and target sysroots).
The sysroot location is specified with the --sysroot option.

The sysroot location must be specified using the --sysroot option. The CC environment variable created by the SDK already includes the --sysroot option that points to the SDK sysroot location.

PC $> echo $CC
arm-openstlinux_weston-linux-gnueabi-gcc -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/local/SDK/2.4+openstlinux-4.14-rocko-mp1-18-07-03/sysroots/cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
  • Create the directory in which the generated binary is to be stored
PC $> mkdir -p install_artifact install_artifact/usr install_artifact/usr/local install_artifact/usr/local/bin
  • Cross-compile the single source code file for the user space example
PC $> $CC hello_world_example.c -o ./install_artifact/usr/local/bin/hello_world_example

9.2.2 Makefile-based project[edit]

For this method, the cross-toolchain environment variables established by running the cross-toolchain environment setup script are subject to general make rules.
For example, see the following environment variables:

PC $> echo $CC
arm-openstlinux_weston-linux-gnueabi-gcc -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/local/SDK/2.4+openstlinux-4.14-rocko-mp1-18-07-03/sysroots/cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
PC $> echo $CFLAGS
-O2 -pipe -g -feliminate-unused-debug-types
PC $> echo $LDFLAGS
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
PC $> echo $LD
arm-openstlinux_weston-linux-gnueabi-ld --sysroot=/local/SDK/2.4+openstlinux-4.14-rocko-mp1-18-07-03/sysroots/cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
  • Create the makefile for this user space example: Makefile
Info.png All the indentations in a makefile are tabulations
PROG = hello_world_example
SRCS = hello_world_example.c
OBJS = $(SRCS:.c=.o)

CLEANFILES = $(PROG)
INSTALL_DIR = ./install_artifact/usr/local/bin

# Add / change option in CFLAGS if needed
# CFLAGS += <new option>

$(PROG):  $(OBJS)
	$(CC) $(CFLAGS) -o $(PROG) $(OBJS)

.c.o:
	$(CC) $(CFLAGS) -c $< -o $@

all: $(PROG)
 
 
clean:
	rm -f $(CLEANFILES) $(patsubst %.c,%.o, $(SRCS)) *~

install: $(PROG)
	mkdir -p $(INSTALL_DIR)
	install $(PROG) $(INSTALL_DIR)
  • Cross-compile the project
PC $> make
PC $> make install

9.2.3 Autotools-based project[edit]

This method creates a project based on GNU autotools.

  • Create the makefile for this user space example: Makefile.am
bin_PROGRAMS = hello_world_example
hello_world_example_SOURCES = hello_world_example.c
  • Create the configuration file for this user space example: configure.ac
AC_INIT(hello_world_example,0.1)
AM_INIT_AUTOMAKE([foreign])
AC_PROG_CC
AC_PROG_INSTALL
AC_OUTPUT(Makefile)
  • Generate the local aclocal.m4 files and create the configure script
PC $> aclocal
PC $> autoconf
  • Generate the files needed by GNU coding standards (for compliance)
PC $> touch NEWS README AUTHORS ChangeLog
  • Generate the links towards SDK scripts
PC $> automake -a
                       
  • Cross-compile the project
PC $> ./configure ${CONFIGURE_FLAGS}
PC $> make
PC $> make install DESTDIR=./install_artifact

9.3 Deploy and execute on board[edit]

  • Check that the generated binary for this user space example is in: ./install_artifact/usr/local/bin/hello_world_example
  • Push this binary onto the board
PC $> scp -r install_artifact/* root@<board ip address>:/
  • Execute this user space example
Board $> cd /usr/local/bin
Board $> ./hello_world_example 

User space example: hello world from STMicroelectronics
10 9 8 7 6 5 4 3 2 1 0 
User space example: goodbye from STMicroelectronics

10 Tips[edit]

10.1 Creating a mounting point[edit]

The objective is to create a mounting point for the boot file system (bootfs partition)

  • Find the partition label associated with the boot file system
Board $> ls -l /dev/disk/by-partlabel/
total 0
lrwxrwxrwx 1 root root 15 Dec 13 12:31 bootfs -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Dec 13 12:31 fsbl1 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Dec 13 12:31 fsbl2 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Dec 13 12:31 rootfs -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Dec 13 12:31 ssbl -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Dec 13 12:31 userfs -> ../../mmcblk0p6
  • Attach the boot file system found under /dev/mmcblk0p4 in the directory /boot
Board $> mount /dev/mmcblk0p4 /boot

Trusted Firmware for Arm Cortex-A

Graphics Processing Units

Light-emitting diode

General-Purpose Input/Output

Direct Rendering Manager

Second Stage Boot Loader

Central processing unit

USB On-The-Go

User-space Mode Setting

First Stage Boot Loader

Microprocessor Unit

Software development kit

Attachments

Discussions