CM-T3530: Linux: Building images - Revision history

Grinberg: /* Building Graphics SDK outside of OE */

2013-10-28T12:13:51Z

‎Building Graphics SDK outside of OE

Show changes

Ilya: /* Applying Patches */

2012-08-16T07:13:58Z

‎Applying Patches

Mike: 1 revision(s)

2010-02-24T12:22:44Z

1 revision(s)

Mike at 12:20, 24 February 2010

2010-02-24T12:20:30Z

Mike at 14:20, 23 December 2009

2009-12-23T14:20:52Z

New page

The run-time Linux image for CM-T3530 was created using [http://www.openembedded.org 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. [http://docs.openembedded.org/usermanual/usermanual.html#chapter_getting_oe Getting Started] section of [http://docs.openembedded.org/usermanual/usermanual.htm OpenEmbedded User Manual] describes the framework installation process.

Here we assume that you followed the [http://docs.openembedded.org/usermanual/usermanual.html#chapter_getting_oe 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 {{filename|oe/local.conf}} file in [http://www.compulab.co.il/t3530/download/t3530-linux.zip CM-T3530 Linux package]. To use it copy the {{filename|oe/local.conf}} file to {{filename|${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 [[CM-T3530: Linux: Building images#Applying Patches|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
* 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 {{filename|${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.

== See also ==
* [[CM-T3530: Linux: Kernel|Linux Kernel for CM-T3530]]
* [[CM-T3530: Linux: Angstrom]]
* [[Linux Development for ARM modules]]
* [http://www.openembedded.org OpenEmbedded]

[[Category:Linux|Building images]]
[[Category:CM-T3530|Linux: Building images]]

@@ Line 7: / Line 7: @@
 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 {{filename|oe/local.conf}} file in [http://www.compulab.co.il/t3530/download/t3530-linux.zip CM-T3530 Linux package]. To use it copy the {{filename|oe/local.conf}} file to {{filename|${OEBASE}/build/conf}} directory:
+Example configuration for creation of Angstrom Linux image for CM-T3530 can be found in {{filename|oe/local.conf}} file in [http://compulab.co.il/products/computer-on-modules/cm-t3530/#devres Linux package for CM-T3530]. To use it copy the {{filename|oe/local.conf}} file to {{filename|${OEBASE}/build/conf}} directory:
   cp /path/to/t3530-linux/oe/local.conf ${OEBASE}/build/conf
@@ Line 14: / Line 14: @@
 === 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
+  cd $OEBASE/openembedded
   git branch cm-t35-dev 33497aded7af7c5e6191e98d3083072da14c5945
   git checkout cm-t35-dev

← Older revision	Revision as of 12:22, 24 February 2010
(No difference)

@@ Line 16: / Line 16: @@
   cd {$OEBASE}/oe/openembedded
   git branch cm-t35-dev 33497aded7af7c5e6191e98d3083072da14c5945
 * Apply CM-T3530 patches
   git apply /path/to/t3530-linux/oe/cm-t35.patch