https://elinux.org/api.php?action=feedcontributions&user=Mrchapp&feedformat=atomeLinux.org - User contributions [en]2024-03-28T09:50:39ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=BeagleBoard/DSP_Howto&diff=21530BeagleBoard/DSP Howto2010-05-27T06:16:19Z<p>Mrchapp: correct version is L23.i3.3</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
<br />
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&amp;DCMP=OMAP_Feb27_2008&amp;HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] using the [[BeagleBoard/DSP_Clarification#dsp-bridge|bridge driver]] kernel module. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].<br />
<br />
DSP Bridge driver provides features to control and communicate with DSP enabling parallel processing for multimedia acceleration. It enables the applications running on MPU to offload the processing to DSP [http://omappedia.org/wiki/DSPBridge_Project#About_DSP_Bridge].<br />
<br />
Some of the key features of DSP Bridge are:<br />
<br />
* ''Messaging'': Ability to exchange fixed size control messages with DSP<br />
* ''Dynamic memory management'': Ability to dynamically map files to DSP address space<br />
* ''Dynamic loading'': Ability to dynamically load new nodes on DSP at run time<br />
* ''Power Management'': Static and dynamic power management for DSP<br />
<br />
<br />
= Setup =<br />
<br />
In order to enable the DSP in your OMAP3 the procedure is two-fold:<br />
<br />
* GPP side (ARM side): Enable the bridge driver kernel module.<br />
* DSP side: Set the required files in the filesystem. <br />
** Most of these files are, right now, TI's proprietary binaries.<br />
<br />
== Kernel driver ==<br />
<br />
In order to use the DSP you would need TI's [[BeagleBoard/DSP_Clarification#dsp-bridge|bridgedriver]] module on the kernel. You can use the linux-omap repository's branch at kernel.org:<br />
<br />
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git<br />
cd linux-omap-2.6<br />
git checkout -b dspbridge orgin/dspbridge<br />
<br />
Warning: '''This module currently is under heavy development'''. If you want be updated you should pull for changes weekly or so. Besides, this how-to could be already deprecated.<br />
<br />
The default configuration for the beagle board doesn't enable de bridgedriver. You should build you own using<br />
<br />
make menuconfig<br />
<br />
or fetching the one used in [http://gitorious.org/vjaquez-beagleboard/marmita marmita]: <br />
<br />
wget http://gitorious.org/vjaquez-beagleboard/marmita/blobs/raw/master/meta-marmita/linux/linux-omap-bridgedriver/defconfig -O .config<br />
<br />
If you want DSS2 support for the Beagleboard, you should apply this patch in your kernel code: https://patchwork.kernel.org/patch/94049/<br />
<br />
wget -q https://patchwork.kernel.org/patch/94049/mbox/ -O - | git am --3way<br />
<br />
Then build the '''uImage''' as usual and install the modules on your rootfs:<br />
<br />
make oldconfig<br />
make<br />
make uImage<br />
make INSTALL_MOD_PATH=/media/rootfs modules_install<br />
<br />
== TI's DSP binaries ==<br />
<br />
In order to get the DSP binaries for multimedia processing you need to download them from [http://omappedia.org/wiki/OpenMAX_Project TI's OpenMAX IL project]. The most important binary is <code>baseimage.dof</code>, which is the BIOS image to be loaded into the DSP.<br />
<br />
The latests release of these binaries for mainstream Linux is '''v3.09''' for L23.i3.3. <br />
<br />
Most of the public releases are published in TI's [https://gforge.ti.com/gf/project/openmax/frs/ gforge].<br />
<br />
=== v3.09 ===<br />
<br />
Download the binary package and extract its content:<br />
<br />
wget --no-check-certificate https://gforge.ti.com/gf/download/frsrelease/285/3260/DSPbinaries-3.09-Linux-x86-Install<br />
chmod +x ./DSPbinaries-3.09-Linux-x86-Install<br />
./DSPbinaries-3.09-Linux-x86-Install --mode console --prefix /tmp<br />
<br />
Then copy those binaries into the directory <code>lib/dsp</code> in your root filesystem (<code>/media/rootfs</code> is assumed here):<br />
<br />
mkdir /media/rootfs/lib/dsp<br />
cp /tmp/Binaries/* /media/rootfs/lib/dsp<br />
<br />
=== v0.3.5 ===<br />
<br />
wget --no-check-certificate https://gforge.ti.com/gf/download/frsrelease/170/1399/tiopenmax-0.3.5.tar.gz<br />
tar xvf ./tiopenmax-0.3.5.tar.gz<br />
cd tiopenmax-0.3.5<br />
./TI-OMX-Sample-Firmware-0.3.5-Linux-x86-Install<br />
<br />
Accept the license agreement and copy the binaries into the directory <code>lib/dsp</code> in your root filesystem:<br />
<br />
mkdir /media/rootfs/lib/dsp<br />
cp ./lib/dsp/* /media/rootfs/lib/dsp<br />
<br />
=== v0.3 ===<br />
<br />
wget --no-check-certificate https://gforge.ti.com/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz<br />
tar xvf ./tiopenmax-0.3.tar.gz<br />
cd tiopenmax-0.3<br />
./TI-OMX-Sample-Firmware-0.3-Linux-x86-Install<br />
<br />
Accept the license agreement and copy the binaries into the directory <code>lib/dsp</code> in your root filesystem:<br />
<br />
mkdir /media/rootfs/lib/dsp<br />
cp ./lib/dsp/* /media/rootfs/lib/dsp<br />
<br />
= Running =<br />
<br />
On the board use these commands to load the module:<br />
<br />
modprobe mailbox<br />
modprobe bridgedriver base_img=/lib/dsp/baseimage.dof<br />
<br />
== ping test ==<br />
<br />
If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package]. The package provide a set of already compiled tests, either for ARM-side and DSP-side.<br />
<br />
Installing shortcut:<br />
<br />
# ARM-side app<br />
wget "http://dev.omapzoom.org/?p=tidspbridge/userspace-dspbridge.git;a=blob_plain;f=binaries/ping.out;hb=HEAD" -O ping.out<br />
chmod +x ping.out<br />
cp ping.out /media/rootfs<br />
<br />
# DSP-side socket node<br />
wget "http://dev.omapzoom.org/?p=tidspbridge/userspace-dspbridge.git;a=blob_plain;f=binaries/pingdyn_3430.dll64P;hb=HEAD" -O pingdyn_3430.dll64P<br />
cp pingdyn_3430.dll64P /media/rootfs/lib/dsp <br />
<br />
In the board just:<br />
<br />
./ping.out<br />
<br />
If you get an error like:<br />
DSPNode_Allocate failed: 0x80008008<br />
<br />
Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:<br />
<br />
./dynreg.out -r pingdyn_3430.dll64P<br />
<br />
= Developing =<br />
<br />
There are two ways to compile your own DSP nodes:<br />
<br />
* The official one, which requires DSP/BIOS and RTSC/XDC tools<br />
* The simplified one (used by [[User:Felipec|Felipe Contreras]])<br />
<br />
But either way, you will need the TI's DSP toolchain: [https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm C6x compiler CGT 6.0.22] (Code Generation Tools). Please note that you might be required to register to gain access to those files.<br />
<br />
This HOWTO assumes that the DSP toolchain are installed under <code>/opt/dsp/cgt6x-6.0.22</code>.<br />
<br />
== Official ==<br />
<br />
These instructions are taken from [http://omappedia.org/wiki/DSPBridge_Project#Build_Userspace_Files DSPBridge project] wiki page at [http://omappedia.org/ omapedia].<br />
<br />
=== Install build dependencies ===<br />
<br />
* [http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/bios/index.html DSP/BIOS] 5.33.04<br />
* [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html RTSC/XDCtools] 3.10.02<br />
<br />
Also, here is assumed that those packages are installed in <code>/opt/dsp</code>.<br />
<br />
=== Building the user space binaries ===<br />
<br />
git clone git://dev.omapzoom.org/pub/scm/tidspbridge/userspace-dspbridge.git<br />
cd userpace-dspbridge<br />
<br />
Edit "product.mak" to match the version of your tools. <br />
<br />
<code><br />
# DSP BIOS<br />
SABIOS_VER = 5.33.04<br />
SABIOS_VER_2 = 5_33_04<br />
<br />
# CodeGen Tools<br />
CGT55_VER = 3.2.2<br />
CGT6X_VER = 6.0.22<br />
</code><br />
<br />
Then run:<br />
<br />
make .dsp DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp<br />
<br />
Other make options:<br />
<br />
make clean # clean all<br />
make all # clean, compile and install all<br />
make .api # clean, compile and install API only<br />
make .samples # clean, compile and install samples only<br />
make .dsp # clean, compile and install DSP binaires only<br />
<br />
The output will be installed under <code>userpace-dspbridge/source/target</code><br />
<br />
== Simplified ==<br />
<br />
In this mode we will only need the DSP toolchains and the doffbuild tools. In this case, the test C6x compiler version is '''v6.1.7''' or greater.<br />
<br />
=== doffbuild tools ===<br />
<br />
The only relevant tool is DLLcreate, which can be found in the userspace-dpsbridge repository, but we can only extract what we need in this way:<br />
<br />
mkdir -p /opt/doffbuild/bin<br />
cd /opt<br />
wget -q "http://dev.omapzoom.org/?p=tidspbridge/userspace-dspbridge.git;a=blob_plain;f=source/dsp/bdsptools/bridge-tools.tar;hb=HEAD" -O - \<br />
| tar xf - --strip-components 3 --wildcards ti/dspbridge/dsp/doffbuild/bin/*<br />
<br />
=== DSP nodes samples ===<br />
<br />
Here is a couple of [http://gitorious.org/vjaquez-beagleboard/dsp-samples DSP node samples] built using the simplified approach.<br />
<br />
* '''dummy''' passes buffers back and forth<br />
* '''ping''' sends messages and waits for replies<br />
<br />
git clone git://gitorious.org/vjaquez-beagleboard/dsp-samples.git<br />
make DSP_TOOLS=/opt/dsp/cgt6x-6.0.22 DSP_DOFFBUILD=/opt/doffbuild<br />
make install DESTDIR=/media/rootfs<br />
<br />
Now you can run the '''dummy''' and the '''ping''' test applications.<br />
<br />
= Further information = <br />
<br />
# [http://omappedia.org/wiki/DSPBridge_Project DSP Bridge wiki page at Omappedia]<br />
# [https://gforge.ti.com/gf/project/omapbridge/docman/?subdir=3 Official OMAP DSP Bridge documentation]<br />
<br />
= See also =<br />
<br />
* [[BeagleBoard/gst-openmax]]</div>Mrchapphttps://elinux.org/index.php?title=User:Mrchapp&diff=16935User:Mrchapp2010-01-30T16:37:22Z<p>Mrchapp: Created page with 'http://linux.mty.itesm.mx/~ddiaz/'</p>
<hr />
<div>http://linux.mty.itesm.mx/~ddiaz/</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=11898BeagleBoard/Poky2009-05-27T03:58:42Z<p>Mrchapp: update git repository location</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mrchapp/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom --track origin/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mrchapp/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom --track origin/gitomapzoom<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644 (the one saying "IA32 GNU/Linux TAR"), and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see the <tt>v2.6.28-felipec1</tt> tag here: http://github.com/felipec/linux-omap/tree/v2.6.28-felipec1.<br />
<br />
===Note===<br />
This kernel uses DSS2, which has been configured to use LCD output as default. To use DVI-D or S-Video output you can modify the bootargs to allow it. Example args for DVI output:<br />
omapdss.def_disp=dvi omapfb.mode=dvi:1024x768MR-24@60 omapfb.vram=0:4M,1:2M<br />
<br />
You can find more information about DSS2 in http://groups.google.com/group/beagleboard/browse_thread/thread/115867f718b52e4b/4c64b2c614622053.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used with TI's OpenMAX IL: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
To display video on the framebuffer (DSS2-based) use gst-omapfb. Its recipe is here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-omapfb/gst-omapfb_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=11562BeagleBoard/Poky2009-05-08T14:42:51Z<p>Mrchapp: add gst-omapfb</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644 (the one saying "IA32 GNU/Linux TAR"), and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see the <tt>v2.6.28-felipec1</tt> tag here: http://github.com/felipec/linux-omap/tree/v2.6.28-felipec1.<br />
<br />
===Note===<br />
This kernel uses DSS2, which has been configured to use LCD output as default. To use DVI-D or S-Video output you can modify the bootargs to allow it. Example args for DVI output:<br />
omapdss.def_disp=dvi omapfb.mode=dvi:1024x768MR-24@60 omapfb.vram=0:4M,1:2M<br />
<br />
You can find more information about DSS2 in http://groups.google.com/group/beagleboard/browse_thread/thread/115867f718b52e4b/4c64b2c614622053.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used with TI's OpenMAX IL: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
To display video on the framebuffer (DSS2-based) use gst-omapfb. Its recipe is here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-omapfb/gst-omapfb_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=11561BeagleBoard/Poky2009-05-08T14:36:46Z<p>Mrchapp: update kernel tag, bootargs</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644 (the one saying "IA32 GNU/Linux TAR"), and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see the <tt>v2.6.28-felipec1</tt> tag here: http://github.com/felipec/linux-omap/tree/v2.6.28-felipec1.<br />
<br />
===Note===<br />
This kernel uses DSS2, which has been configured to use LCD output as default. To use DVI-D or S-Video output you can modify the bootargs to allow it. Example args for DVI output:<br />
omapdss.def_disp=dvi omapfb.mode=dvi:1024x768MR-24@60 omapfb.vram=0:4M,1:2M<br />
<br />
You can find more information about DSS2 in http://groups.google.com/group/beagleboard/browse_thread/thread/115867f718b52e4b/4c64b2c614622053.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/DSP_Clarification&diff=11539BeagleBoard/DSP Clarification2009-05-07T23:20:04Z<p>Mrchapp: /* dsp-link */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different. An [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html thread] of interest<br />
<br />
== dsp-gateway ==<br />
<br />
[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.<br />
<br />
It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.<br />
<br />
It is maintained by Hiroshi DOYU.<br />
<br />
There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.<br />
<br />
== dsp-bridge ==<br />
<br />
[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, from TI and Nokia.<br />
<br />
It is stable and production ready (phone announced at 2009 CES), but it still doesn't meet Linux coding standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.<br />
<br />
TI and the community are working on how power management must be handled, all the effort is being focused on linux-omap-pm branch maintained by Kevin Hillman.<br />
<br />
It's under heavy code cleanup to be open source friendly. Originally maintained at omapzoom.org, Hiroshi DOYU started his tree at gitorious, but now Ameya Palande took over. <br />
<br />
There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space.<br />
<br />
There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.<br />
<br />
For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]<br />
<br />
== dsp-link ==<br />
<br />
A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.<br />
<br />
It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.<br />
<br />
It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.<br />
<br />
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/DSP_Clarification&diff=11538BeagleBoard/DSP Clarification2009-05-07T23:19:19Z<p>Mrchapp: /* dsp-bridge */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different. An [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html thread] of interest<br />
<br />
== dsp-gateway ==<br />
<br />
[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.<br />
<br />
It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.<br />
<br />
It is maintained by Hiroshi DOYU.<br />
<br />
There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.<br />
<br />
== dsp-bridge ==<br />
<br />
[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, from TI and Nokia.<br />
<br />
It is stable and production ready (phone announced at 2009 CES), but it still doesn't meet Linux coding standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.<br />
<br />
TI and the community are working on how power management must be handled, all the effort is being focused on linux-omap-pm branch maintained by Kevin Hillman.<br />
<br />
It's under heavy code cleanup to be open source friendly. Originally maintained at omapzoom.org, Hiroshi DOYU started his tree at gitorious, but now Ameya Palande took over. <br />
<br />
There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space.<br />
<br />
There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.<br />
<br />
For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]<br />
<br />
== dsp-link ==<br />
<br />
A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.<br />
<br />
It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.<br />
<br />
It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.<br />
<br />
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/DSP_Clarification&diff=11537BeagleBoard/DSP Clarification2009-05-07T23:17:01Z<p>Mrchapp: /* dsp-gateway */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different. An [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html thread] of interest<br />
<br />
== dsp-gateway ==<br />
<br />
[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.<br />
<br />
It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.<br />
<br />
It is maintained by Hiroshi DOYU.<br />
<br />
There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.<br />
<br />
== dsp-bridge ==<br />
<br />
[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, from TI and Nokia.<br />
<br />
It is stable and production ready (phone announced at 2009 CES), but it still doesn't meet linux coding standards although there has been a lot of progress. Only the ARM side is available as open source, unlike the dsp-gateway, the DSP side is completely closed.<br />
<br />
TI and the community are working on how power management must be handled, all the effort is being focused on linux-omap-pm branch maintained by Kevin Hillman.<br />
<br />
It's under heavy code cleanup to be open source friendly, originally maintained at omapzoom.org, Hiroshi DOYU started his tree at gitorious, but now Ameya Palande took over. <br />
<br />
There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space.<br />
<br />
There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.<br />
<br />
For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]<br />
<br />
== dsp-link ==<br />
<br />
A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.<br />
<br />
It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.<br />
<br />
It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.<br />
<br />
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/DSP_Clarification&diff=11536BeagleBoard/DSP Clarification2009-05-07T23:16:01Z<p>Mrchapp: /* dsp-bridge */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different. An [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html thread] of interest<br />
<br />
== dsp-gateway ==<br />
<br />
[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.<br />
<br />
It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.<br />
<br />
It is maintained by Hiroshi DOYU.<br />
<br />
There are a few user-space applications that use it. Essentially GStreamer Nokia DSP plugins and a few others developed by the Maemo community.<br />
<br />
== dsp-bridge ==<br />
<br />
[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, from TI and Nokia.<br />
<br />
It is stable and production ready (phone announced at 2009 CES), but it still doesn't meet linux coding standards although there has been a lot of progress. Only the ARM side is available as open source, unlike the dsp-gateway, the DSP side is completely closed.<br />
<br />
TI and the community are working on how power management must be handled, all the effort is being focused on linux-omap-pm branch maintained by Kevin Hillman.<br />
<br />
It's under heavy code cleanup to be open source friendly, originally maintained at omapzoom.org, Hiroshi DOYU started his tree at gitorious, but now Ameya Palande took over. <br />
<br />
There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space.<br />
<br />
There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.<br />
<br />
For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]<br />
<br />
== dsp-link ==<br />
<br />
A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.<br />
<br />
It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.<br />
<br />
It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.<br />
<br />
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/DSP_Clarification&diff=11518BeagleBoard/DSP Clarification2009-05-06T21:50:15Z<p>Mrchapp: /* dsp-bridge */</p>
<hr />
<div>This article tries to explain all the different Linux DSP systems for OMAP chips, how they are similar and different.<br />
<br />
== dsp-gateway ==<br />
<br />
DSP Gateway was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.<br />
<br />
[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ Link].<br />
<br />
It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.<br />
<br />
It is maintained by Hiroshi DOYU.<br />
<br />
There are a few user-space applications that use it. Essentially GStreamer Nokia DSP plugins and a few others developed by the Maemo community.<br />
<br />
== dsp-bridge ==<br />
<br />
tidspbridge originally developed by TI, but after being released as open source it has received many contributions, predominantly by Nokia.<br />
<br />
It's probably not production ready (at least I don't know of any released product using it), and it still doesn't meet linux standards although there has been a lot of progress. Only the ARM side is available as open source, unlike the dsp-gateway, the DSP side is completely closed.<br />
<br />
Unfortunately there's a disagreement between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom.<br />
<br />
It's under heavy development, originally maintained by Hiroshi DOYU, but now Ameya Palande took over.<br />
<br />
There is plans to share the mailbox and iommu that the dsp-gateway uses, but it's independent from it, as well as to move parts of it to user-space.<br />
<br />
There are slightly more user-space applications using it, including gst-openmax through TI's OpenMAX IL implementation which is also open source. and gst-goo.<br />
<br />
== dsp-link ==<br />
<br />
A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.<br />
<br />
It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.<br />
<br />
It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10650BeagleBoard/Poky2009-04-07T16:49:18Z<p>Mrchapp: download specific toolchain</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644 (the one saying "IA32 GNU/Linux TAR"), and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10488BeagleBoard/Poky2009-04-03T22:20:14Z<p>Mrchapp: move the toolchain step</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644, and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10410BeagleBoard/Poky2009-03-28T19:30:58Z<p>Mrchapp: add toolchain subsection</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Get a toolchain==<br />
This has been tested with CodeSourcery's G++ Lite 2008q3-72. Download it from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release644, and install it in <tt>/usr/local/csl/arm-2008q3</tt>:<br />
<pre><br />
$ ls -l /usr/local/csl/arm-2008q3/<br />
total 24<br />
drwxr-sr-x 6 root root 4096 2008-10-01 11:12 arm-none-linux-gnueabi<br />
drwxr-xr-x 2 root root 4096 2008-10-01 11:16 bin<br />
drwxr-sr-x 2 root root 4096 2008-10-01 10:33 include<br />
drwxr-sr-x 3 root root 4096 2008-10-01 11:16 lib<br />
drwxr-sr-x 4 root root 4096 2008-10-01 11:15 libexec<br />
drwxr-sr-x 3 root root 4096 2008-10-01 10:30 share<br />
</pre><br />
<br />
If you already have the toolchain somewhere else, or can't install it in /usr/local, then edit this file and make sure <tt>EXTERNAL_TOOLCHAIN</tt> points to the toolchain: <tt>$POKY/meta-texasinstruments/conf/distro/include/poky-external-csl2008q3.inc</tt>.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10409BeagleBoard/Poky2009-03-28T19:11:44Z<p>Mrchapp: cd into path before checking out branch</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
cd meta-texasinstruments<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10408BeagleBoard/Poky2009-03-28T19:09:11Z<p>Mrchapp: correct path for configuration file</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/conf/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build/conf<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10407BeagleBoard/Poky2009-03-28T19:01:11Z<p>Mrchapp: checkout branch properly</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout -b gitomapzoom origin/ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10406BeagleBoard/Poky2009-03-28T16:51:42Z<p>Mrchapp: add directory listing</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
This page is about how to use [http://www.pokylinux.org/about/ Poky] for [[BeagleBoard]] development.<br />
=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
<pre><br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
total 181056<br />
3452 modules-2.6.28-omap1-beagleboard.tgz<br />
33320 omap-image-min-gst-beagleboard-20090327064222.rootfs.jffs2<br />
27168 omap-image-min-gst-beagleboard-20090327064222.rootfs.tar.gz<br />
0 omap-image-min-gst-beagleboard.jffs2<br />
0 omap-image-min-gst-beagleboard.tar.gz<br />
63300 omap-image-sato-beagleboard-20090327162651.rootfs.jffs2<br />
51884 omap-image-sato-beagleboard-20090327162651.rootfs.tar.gz<br />
0 omap-image-sato-beagleboard.jffs2<br />
0 omap-image-sato-beagleboard.tar.gz<br />
148 u-boot-beagleboard-2008.10-rc2+r2+gitdcae48d0df9dd0367172677f8154eb2683de0865-r2.bin<br />
4 u-boot-beagleboard.bin<br />
1776 uImage-2.6.28-omap1+r0+git1764d8eef033d40c623e9a9a0dde455e59ac2149-beagleboard-20090327164249.bin<br />
4 uImage-beagleboard.bin<br />
</pre><br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10390BeagleBoard/Poky2009-03-27T23:45:49Z<p>Mrchapp: missing character</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/build/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10389BeagleBoard/Poky2009-03-27T23:45:28Z<p>Mrchapp: correct location of local.conf</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf $POKY/buil/local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10388BeagleBoard/Poky2009-03-27T23:44:33Z<p>Mrchapp: add gstreamer and more recipes</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image, though YMMV:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
==GStreamer plug-ins==<br />
Two sets of plug-ins can be used: gst-openmax and gst-goo. Both are included in the GStreamer task. Recipes for these are located here:<br />
* <tt>$POKY/meta-texasinstruments/packages/gst-goo/gst-goo_5.14.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/gst-openmax/gst-openmax_git.bb</tt><br />
<br />
==Other==<br />
Some other important recipes would be the following:<br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-min-gst.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/images/omap-image-sato.bb</tt><br />
* <tt>$POKY/meta-texasinstruments/packages/tasks/task-omap-gst.bb</tt></div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10387BeagleBoard/Poky2009-03-27T23:35:41Z<p>Mrchapp: add bridge and openmax recipes</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/tree/tidspbridge-stable/.<br />
<br />
==Bridge library==<br />
The API for accessing the Bridge driver is provided by this recipe: <tt>$POKY/meta-texasinstruments/packages/tidspbridge/tidspbridge-lib_git.bb</tt>. The code is taken from this GIT repository: http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git. Of course, it requires the DSP Bridge driver, which is provided by the kernel.<br />
<br />
==TI's OpenMAX IL==<br />
The recipe for building TI's OpenMAX IL is located here: <tt>$POKY//meta-texasinstruments/packages/tiopenmax/tiopenmax_0.3.5.bb</tt>. This code is rather old. The goal is to use this GIT repository for OpenMAX: http://git.omapzoom.org/?p=platform/hardware/ti/omx.git, but that'll be later.<br />
<br />
* GStreamer plug-ins</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10386BeagleBoard/Poky2009-03-27T23:23:54Z<p>Mrchapp: add recipes section</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.<br />
<br />
=Recipes=<br />
What are the most important recipes around here? Here's a list of them.<br />
<br />
==U-boot==<br />
A recipe for u-boot can be found here: <tt>$POKY/meta/packages/uboot/u-boot-omap3_git.bb</tt>. This comes from Poky. You can try with another recipe for u-boot as long as it works on the Beagle. See <tt>$POKY/meta-texasinstruments/conf/machine/beagleboard.conf</tt> if you want to change it.<br />
<br />
==Kernel==<br />
Kernel recipe is <tt>$POKY/meta-texasinstruments/packages/linux/linux-beagle_git.bb</tt>. This kernel, kindly forked by Felipec, is currently based on 2.6.28-omap1, with dspbridge patches on them. This is the GIT repository for it, see under the tidspbridge-stable branch: http://github.com/felipec/linux-omap/.<br />
<br />
<br />
* Bridge library<br />
* TI's OpenMAX IL<br />
* GStreamer plug-ins</div>Mrchapphttps://elinux.org/index.php?title=BeagleBoard/Poky&diff=10385BeagleBoard/Poky2009-03-27T23:12:05Z<p>Mrchapp: initial version</p>
<hr />
<div>=Quick Start=<br />
<pre><br />
# Get Poky<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky; export POKY=`pwd`<br />
<br />
# Get TI's overlay<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
# Copy configuration<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
<br />
# Build!<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
</pre><br />
<br />
=Step by step=<br />
==Download Poky==<br />
Get Poky.<br />
svn co -r5728 http://svn.o-hand.com/repos/poky/trunk poky<br />
cd poky<br />
export POKY=`pwd`<br />
<br />
Why SVN if Poky already moved to GIT, you may ask. Well, we feel fond of that revision because we know it to work. Feel free try Poky's GIT or a newer SVN revision. In fact, you might want to take a look at [http://github.com/mturquette/pokyomap Poky OMAP] too.<br />
<br />
==Add Texas Instruments' overlay==<br />
cd $POKY<br />
git clone git://github.com/mturquette/meta-texasinstruments.git<br />
git checkout ddiaz/gitomapzoom<br />
<br />
==Configure==<br />
cd $POKY/build<br />
cp -p $POKY/meta-texasinstruments/conf/misc/local.conf local.conf<br />
Review the above file.<br />
<br />
==Fine tune==<br />
With newer kernels exmap complains about missing headers. For now, you can have the rest of the profiling tools by taking <tt>exmap-console</tt> and <tt>exmap-server</tt> out of "<tt>RDEPENDS_task-poky-tools-profile</tt>" in <tt>$POKY/meta/packages/tasks/task-poky-tools.bb</tt>. This is needed for a Sato image.<br />
<br />
==Build==<br />
cd $POKY<br />
source poky-init-build-env<br />
bitbake omap-image-min-gst<br />
<br />
Alternatively, you can build a complete Poky Sato image:<br />
bitbake omap-image-sato<br />
<br />
==Deploy==<br />
You can find your binaries here: <tt>$POKY/build/tmp/deploy/images/</tt>.<br />
cd $POKY/build/tmp/deploy/images/<br />
ls -1s<br />
[ADD DIR LISTING HERE]<br />
The kernel and u-boot can be copied to the boot partition on your MMC/SD card. Take the image tarball and untar it in the root partition of your MMC/SD card; also, untar the modules tarball on the root of your file system.</div>Mrchapp