CM-T3530: Linux: Building images
The run-time Linux image for CM-T3530 was created using OpenEmbedded framework. The OpenEmbedded framework can be used for creation of custom Linux images for CM-T3530.
OpenEmbedded setup
Creation of custom Linux images for CM-T3530 requires installation of OpenEmbedded framework. Getting Started section of OpenEmbedded User Manual describes the framework installation process.
Here we assume that you followed the Getting Started instructions, that you have the same directory structure and all the tools installed.
The OpenEmbedded framework should be configured in order to build images for CM-T3530. Example configuration for creation of Angstrom Linux image for CM-T3530 can be found in oe/local.conf file in CM-T3530 Linux package. To use it copy the oe/local.conf file to ${OEBASE}/build/conf directory:
cp /path/to/t3530-linux/oe/local.conf ${OEBASE}/build/conf
CM-T3530 is supported by OpenEmbedded and it is possible to build Linux images either with mainline OpenEmbedded or using baseline commit 33497aded7af7c5e6191e98d3083072da14c5945 in OpenEmbedded git tree with CM-T3530 patches. If you intend to use mainline OpenEmbedded, please skip the Applying Patches section.
Applying Patches
- Create a branch for CM-T3530 development. CM-T3530 patches are generated vs. commit 33497aded7af7c5e6191e98d3083072da14c5945 in org.openembedded.dev branch of the OpenEmbedded git tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
cd {$OEBASE}/oe/openembedded
git branch cm-t35-dev 33497aded7af7c5e6191e98d3083072da14c5945
git checkout cm-t35-dev
- Apply CM-T3530 patches
git apply /path/to/t3530-linux/oe/cm-t35.patch
Creating Angstrom Linux images
- Setup environment variables
export OEBASE=/path/to/oe cd $OEBASE export PATH=$OEBASE/bitbake/bin:$PATH export BBPATH=$OEBASE/build:$OEBASE/openembedded export BB_ENV_EXTRAWHITE="OEBASE"
- Build Angstrom Linux image
bitbake beagleboard-demo-image
Once bitbake is finished, the image will be created and put into ${OEBASE}/build/arm/tmp/deploy/glibc/images/cm-t35 directory. Default configuration creates two types of images: tar.bz2, and ubi. The ubi image can be copied to the CM-T3530 on-board NAND flash. The tar.bz2 archive can be extracted to a directory on the host workstation. This directory may be used as networked root filesystem for the device.
