It is this repository that actually pulls in the oe-layersetup project to perform the Linux EZSDK builds for TI’s entire suite of ARM CortextA chips. In this document we are only concerned with the oe-layersetup project.

Overview of the meta-embedian Yocto Layer

The supplied meta-embedian Yocto compliant layer has the following organization:

Notes on meta-embedian layer content

conf/machine/*

This folder contains the machine definitions for the smarct335x platform. These select the associated kernel, kernel config, u-boot, u-boot config, and UBI image settings.

recipes-bsp/u-boot/*

This folder contains recipes used to build DAS U-boot for smarct335x platform.

recipes-connectivity/lftp/*

This folder adds lftp ftp client utility for smarct335x platform.

recipes-core/busybox/*

This recipe modifies TI’s BusyBox configuration to remove telnet from the image.

recipes-core/images/*

These recipes are used to create the final target images for the devices. When you run Bitbake one of these recipes would be specified. For example, to build the root file system for the smarct335x platform:

This recipe is used to amend TI’s initialization scripts for the platform.

This recipe is used to amend TI’s network configuration data for the platform.

recipes-core/sysvinit/*

This recipe is used to amend TI’s console debug port configuration from ttyO0 to ttyO3 for the platform.

recipes-devtools/nodejs/*

These recipes build the Node.js Javascript server execution environment.

recipes-graphics/libgles/*

This recipe is to add smarct335xevm machine id when loads sgx module in SMARC T3354.

recipes-kernel/linux/*

Contains the recipes needed to build the smarct335x Linux kernels.

recipes-multimedia/amsdk-av-files/*

This recipe is to add smarct335x compatible machine for the platform.

recipes-support/boost/*

Adds Boost to the images. Boost provides various C++ libraries that encourage cross-platform development.

recipes-support/ntp/*

Network time protocol support.

Setting Up the Tools and Build Environment

To build the latest TI am335x 6.0 EZSDK you first need an Unbuntu Linux 12.04LTS installation (preferably 32bit). Since bitbake does not accept building images using root privileges, please do not login as a root user when performing the instructions in this section. Only Yocto version 1.6 supports Ubuntu 14.04 LTS. TI SDK6 is based on Yocto 1.5 and if your host PC is Ubuntu 14.04 LTS, please use SDK7 instead.

Once you have Ubuntu 12.04 LTS running, install the additional required support packages using the following console command:

If you are using a 64-bit Linux, then you'd also need to install 32-bit support libraries, needed by the pre-built Linaro toolchain and other binary tools.

You’ll also need to change the default shell to bash from Ubuntu’s default dash shell (select the <No> option):

 To build TI’s am335x SDK you will need to install the Linaro arm compiler that TI used for the release:

Writing Bitbake Recipes

In order to package your application and include it in the root filesystem image, you must write a BitBake recipe for it.

When starting from scratch, it is easiest to learn by example from existing recipes. 

Example HelloWorld recipe using autotools

For software that uses autotools (./configure; make; make install), writing recipes can be very simple:

SRC_URI specifies the location to download the source from. It can take the form of any standard URL using http://, ftp://, etc. It can also fetch from SCM systems, such as git in the example above.

PR is the package revision variable. Any time a recipe is updated that should require the package to be rebuilt, this variable should be incremented.

inherit autotools brings in support for the package to be built using autotools, and thus no other instructions on how to compile and install the software are needed unless something needs to be customized.

S is the source directory variable. This specifies where the source code will exist after it is fetched from SRC_URI and unpacked. The default value is ${WORKDIR}/${PN}-${PV}, where PN is the package name and PV is the package version. Both PN and PV are set by default using the filename of the recipe, where the filename has the format PN_PV.bb.

Example HelloWorld recipe using a single source file

This example shows a simple case of building a helloworld.c file directly using the default compiler (gcc). Since it isn’t using autotools or make, we have to tell BitBake how to build it explicitly.

In this case, SRC_URI specifies a file that must exist locally with the recipe. Since there is no code to download and unpack, we set S to WORKDIR since that is where helloworld.c will be copied to before it is built.

WORKDIR is located at ${OETREE}/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-vfp-neon-3.2-oe-linux-gnueabi/<package name and version> for most packages. If the package is machine-specific (rather than generic for the armv7ahf architecture), it may be located in the smarct335x-oe-linux-gnueabi subdirectory depending on your hardware (this applies to kernel packages, images, etc).

do_compile defines how to compile the source. In this case, we just call gcc directly. If it isn’t defined, do_compile runs make in the source directory by default.

do_install defines how to install the application. This example runs install to create a bin directory where the application will be copied to and then copies the application there with permissions set to 755.

D is the destination directory where the application is installed to before it is packaged.

${bindir} is the directory where most binary applications are installed, typically /usr/bin.

For a more in-depth explanation of BitBake recipes, syntax, and variables, see the Recipe Chapter of the OpenEmbedded User Manual.

Setup eMMC

Setting up eMMC usually is the last step at development stage after the development work is done at your SD card or NFS environments. From software point of view, eMMC is nothing but a non-removable SD card on board. When booting from eMMC and SD card is present, SD card is emulated as /dev/mmcblk0 and eMMC is emulated as /dev/mmcblk1. On the other hand, when booting from eMMC and SD card is absent, eMMC will be emulated as /dev/mmcblk0 now. eMMC could be /dev/mmcblk0 or /dev/mmcblk1 depending on if SD card is inserted and the boot device become dynamic when booting from eMMC.

Initramfs is the successor of initrd and has many advantages over initrd. Linux kernel here will mount it as a temperately rootfs and starts the init process from here. The init script will check if the partition 2 of eMMC is exist and them mount the real rootfs.

This section gives a step-by-step procedure to setup eMMC flash. Users can write a shell script your own at production to simplify the steps.

Get initramfs (assuming the home directory is /home/developer here)

Note: The above initramfs is obtained by the following steps:

You will find smarct335x-initramfs-image-smarct335x.tar.gz file under ~/oe-layersetup/build/arago-tmp-external-linaro-toolchain/deploy/images/

Extract this tarball and add your own init script. Users can use Embedian's init script for references.

Prepare for initramfs zImage

Select

General setup --> 

     [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support

     ()    Initramfs source file(s)

Enter the directory where your initramfs is. In this example

/home/developer/initramfs

Save the kernel config and build again.

Prepare for eMMC binaries from SD card (or NFS):

Insert SD card into your Linux PC. For these instructions, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.

For these instruction, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.

Mount Partitions:

On some systems, these partitions may be auto-mounted...

Copy MLO to rootfs partition:

Copy u-boot.img to rootfs partition:

Copy initramfs zImage to rootfs partition:

Copy uEnv.txt to rootfs partition:

Copy and paste the following contents to /media/rootfs/home/root ($ sudo vim /media/rootfs/home/root/uEnv.txt)

     For kernel v3.2:

Copy real rootfs to rootfs partition:

Remove SD card:

Insert this SD card into your SMARC T335X device.

Now it will be almost the same as you did when setup your SD card, but the eMMC device descriptor is /dev/mmcblk1 now.

Erase SD card:

Create Partition Layout:

In SDK6, Arago rootfs will mount partition2 as /media/mmcblk1p2 automatically after executing the above command. Umount the partition first.

Format Partitions:

Mount Partitions:

Install binaries for partition 1

Copy MLO/u-boot.img/uEnv.txt/zImage to the boot partition

Install Root File System

version 1.0b, 1/13/2014

Last updated 2015-12-07