Building ARM Trusted Firmware for Axxia Overview Note that only the bl31 component is used by Axxia. No other targets are supported. The cross compilation tools should be in the PATH, CROSS_COMPILE should contain the proper prefix, and SYSROOT should point to the target root file system if required by the tools. ARCH should be set to arm64. For example, after installing the Yocto tools, set up the environment as follows. $ $ $ $

export export export export

PATH=/sysroots/x86_64-pokysdk-linux/usr/bin/aarch64-poky-linux:$ CROSS_COMPILE=aarch64-poky-linuxSYSROOT=/sysroots/aarch64-poky-linux ARCH=arm64

Steps 1 Clone the Axxia ARM Trusted Firmware repository. $ git clone https://github.com/axxia/axxia_atf.git 2 Checkout the “axxia-dev” branch. $ cd axxia_atf $ git checkout --track -b axxia-dev origin/axxia-dev 3 Build bl31. Add ‘PLAT=axxia USE_COHERENT_MEM=0 CRASH_REPORTING=1’, and optionally, ‘DEBUG=1’ to the make command line. If ‘DEBUG=1’ is added, there will be more output on the console, and more assertions in the code. $ make PLAT=axxia USE_COHERENT_MEM=0 CRASH_REPORTING=1 bl31 or $ make DEBUG=1 PLAT=axxia USE_COHERENT_MEM=0 CRASH_REPORTING=1 bl31

1

Prior to version atf_84091c4_axxia_1.7, build as follows. Note that earlier versions of the ATF will only work with versions of U-Boot up to 1.19. In addition to PLAT=axxia, include the following. Either AXM5600=1 or AXC6700=1 must be defined. Either EMULATION=1 or SIMULATION=1 may be defined. Optionally, DEBUG=1 can be defined to add console output as above. $ make PLAT=axxia bl31 4 Create an ELF object of the bl31 binary for inclusion in the SPL. $ ${CROSS_COMPILE}objcopy -I binary -O elf64-littleaarch64 -B aarch64 \ --rename-section .data=.monitor build/axxia/release/bl31.bin \ build/axxia/release/bl31.o Or, if using DEBUG=1, $ ${CROSS_COMPILE}objcopy -I binary -O elf64-littleaarch64 -B aarch64 \ --rename-section .data=.monitor build/axxia/debug/bl31.bin \ build/axxia/debug/bl31.o Copy bl31.o from above to the spl directory (you may need to create the spl directory!) in the U-Boot source tree after configuring U-Boot.

2