Skip to content

Latest commit

 

History

History
190 lines (139 loc) · 6.34 KB

README.md

File metadata and controls

190 lines (139 loc) · 6.34 KB
Raw

Vision-Apps Library Build for Target Ubuntu/Debian

This build system covers building the Vision-Apps Linux library for Ubuntu/Debian systems running on TI's EdgeAI processors (TDA4VM, AM62A, AM67A, AM68A, and AM69A). Supported use cases include:

  • Case 1: Compiling with the native GCC in arm64v8 Ubuntu Docker container directly on aarch64 build machine
  • Case 2: Compiling with the native GCC in arm64v8 Ubuntu Docker container on x86_64 machine using QEMU
  • Case 3 (Experimental): Cross-compiling on x86_64 build machine in Ubuntu Docker container
Image 2
CASE 1 and CASE 2 with aarch64 Container 		Image 1
CASE 3 with x86_64 Container

Prerequisite

docker-pull the base Docker image

Pull the baseline Docker image needed. Assuming outside of a proxy network,

docker pull ubuntu:22.04
docker pull ubuntu:20.04
docker pull arm64v8/ubuntu:22.04
docker pull arm64v8/ubuntu:20.04
docker pull arm64v8/debian:12.5

repo tool

mkdir -p ~/bin
PATH="${HOME}/bin:${PATH}"
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+rx ~/bin/repo
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

Ensure that the following basic git configuration is complete, particularly for repo init to function as part of init_setup.sh.

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

edgeai-ti-proxy (only required to make the build system work in TI proxy network)

Set up edgeai-ti-proxy git repository (TI-internal only)

Before docker-build or docker-run, please make sure sourcing edgeai-ti-proxy/setup_proxy.sh, which will define the USE_PROXY env variable and all the proxy settings for the TI network.

CASE 1 & 2: Compiling with the native GCC in arm64v8 Ubuntu Docker container

Build systems:

  1. In arm64v8 Ubuntu Docker container using QEMU on x86_64 machine
  2. In arm64v8 Ubuntu Docker container on aarch64 target

Target for lib deployment:

  1. arm64v8 Ubuntu 20.04 Docker container
  2. arm64v8 Ubuntu 22.04 Docker container

initial setup: install source repos

Depending on the Ubuntu distro for the target docker container, run one of these:

ARCH=arm64 BASE_IMAGE=ubuntu:22.04 ./init_setup.sh
ARCH=arm64 BASE_IMAGE=ubuntu:20.04 ./init_setup.sh
ARCH=arm64 BASE_IMAGE=debian:12.5 ./init_setup.sh

Docker-build

(Only for CASE 2 - QEMU on x86_64 machine) to set up the QEMU (one-time after boot the build machine):

./qemu_init.sh

Depending on the Ubuntu distro for the target docker container, run one of these:

ARCH=arm64 BASE_IMAGE=ubuntu:22.04 ./docker_build.sh
ARCH=arm64 BASE_IMAGE=ubuntu:20.04 ./docker_build.sh
ARCH=arm64 BASE_IMAGE=debian:12.5 ./docker_build.sh

Docker-run

Depending on the Ubuntu distro for the target docker container, run one of these:

ARCH=arm64 BASE_IMAGE=ubuntu:22.04 ./docker_run.sh
ARCH=arm64 BASE_IMAGE=ubuntu:20.04 ./docker_run.sh
ARCH=arm64 BASE_IMAGE=debian:12.5 ./docker_run.sh

Build the vision-apps library in the container

If need to clean up any previous build, run SOC=<platform_name> make yocto_clean or SOC=<platform_name> make vision_apps_clean.

To build the vision-apps library in the container, run the following:

SOC=<platform_name> GCC_LINUX_ARM_ROOT=/usr CROSS_COMPILE_LINARO= LINUX_SYSROOT_ARM=/ LINUX_FS_PATH=/ TREAT_WARNINGS_AS_ERROR=0 make yocto_build

where platform_name=[j721e|j721s2|j722s|j784s4|am62a].

vision_apps.so location: workarea/vision_apps/out/${SOC}/A72/LINUX/release/libtivision_apps.so.${PSDK_VERSION}

Debian packaging (Exprimental) in the container

SOC=<platform_name> PKG_DIST=ubuntu22.04 make deb_package
SOC=<platform_name> PKG_DIST=ubuntu20.04 make deb_package
SOC=<platform_name> PKG_DIST=debian12.5 make deb_package

The resulting Debian package is located: workarea/vision_apps/out/${SOC}/A72/LINUX/release/libti-vision-apps-${SOC}_${PSDK_VERSION}-${PKG_DIST}.deb

CASE 3: Cross-compiling on x86_64 build machine in Ubuntu Docker container

Target for lib deployment: Yocto PSDK-Linux

This has the same goal as the PSDK-RTOS workarea build system except doing in Ubuntu Docker container.

initial setup: install source repos and compiler tools

ARCH=amd64 BASE_IMAGE=ubuntu:22.04 SOC=<platform_name> ./init_setup.sh

where platform_name=[j721e|j721s2|j722s|j784s4|am62a].

Docker-build

ARCH=amd64 BASE_IMAGE=ubuntu:22.04 ./docker_build.sh

Docker-run

ARCH=amd64 BASE_IMAGE=ubuntu:22.04 ./docker_run.sh

Build the vision-apps library in the container

SOC=<platform_name> make yocto_build

where platform_name=[j721e|j721s2|j722s|j784s4|am62a].

Workarounds and Fixes

setup_psdk_rtos.sh

From sdk_builder/scripts/setup_psdk_rtos.sh, all the apt packages are installed in Dockerfile and setup_tools_arm.sh scripts is extracted and used for CASE 3 during init_setup.sh.

AR Flags

With the default Concerto compiler settings, the following warning messages show up around every static .a library.

/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')

A workaround: rsyslog/rsyslog#1179 Update sdk_builder/concerto/compilers/gcc_linux_arm.mak to remove 'u' flag as follows:

$(_MODULE)_LINK_LIB   := $(AR) -rsc $($(_MODULE)_BIN) $($(_MODULE)_OBJS)

Configuration for aarch64 Ubuntu container

  • Following env variables are passed during docker-run: 
    GCC_LINUX_ARM_ROOT=/usr CROSS_COMPILE_LINARO= LINUX_SYSROOT_ARM=/ LINUX_FS_PATH=/ TREAT_WARNINGS_AS_ERROR=0
  • During docker-build:
    • ti-rpmsg-char is built and installed
    • apt-get install libGLESv2, libEGL, libgbm
  • Additional library and include paths are added. Please see patches/sdk_builder/concerto/compilers/gcc_linux_arm.mak
  • A few missing header files are copied from targetfs right after docker-run. Please see entrypoint.sh.