ECE497 Notes on Installing Angstrom via Narcissus - Revision history

Yoder at 16:00, 18 May 2013

2013-05-18T16:00:34Z

Yoder: Added Notes tag

2012-07-18T14:26:21Z

Added Notes tag

Yoder: /* ETC 2011 image */ Added

2012-03-09T15:36:27Z

‎ETC 2011 image: Added

Rpjday: Update link to Narcissus.

2012-02-28T22:59:22Z

Update link to Narcissus.

Yoder: moved ECE497 Lab01 Installing Angstrom via Narcissus to ECE497 Notes on Installing Angstrom via Narcissus

2012-02-28T21:57:35Z

moved ECE497 Lab01 Installing Angstrom via Narcissus to ECE497 Notes on Installing Angstrom via Narcissus

Yoder: /* FIE 2011 image */ Added

2012-01-02T13:39:17Z

‎FIE 2011 image: Added

Yoder: /* Get ready for DSP Development */

2011-06-21T20:48:11Z

‎Get ready for DSP Development

Yoder: /* ICASSP 2011 image */ Cleaning up things.

2011-06-21T20:31:25Z

‎ICASSP 2011 image: Cleaning up things.

Yoder: Created page with "Category:ECE497 Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the i..."

2011-06-21T20:27:26Z

Created page with "Category:ECE497 Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the i..."

New page

[[Category:ECE497]]

Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.

=== ICASSP 2011 image ===

This is the image that Daniel Allred at TI created to support c6run.

Make a beagleboard boot image and SDK image from [http://www.angstrom-distribution.org/narcissus Narcissus]. These steps are more or less in line from those taken [http://groups.google.com/group/beagleboard/browse_thread/thread/6b57d7dc2dbce7c3 here].

* Select '''beagleboard''' as the machine
* Select a unique name (or use the random one provided)
* Select '''advanced''' for options
** Select '''stable 2011.03''' for base of rootfs
** Select '''regular''' base system
** Select '''udev''' for /dev manager
** Select '''sysvinit''' for init manager
** Select '''OMAP SD image''' for image type
** Software manifest is '''no''' (really it doesn't matter unless you plan to redistribute this stuff)
** Set SDK type as '''Full SDK for generated filesystem''' and select the appropriate '''32bit Intel''' for host (our Ubuntu install is 32-bit)
* Select '''X11''' for the user environment
* For the X11 desktop environment, ok to leave it blank

* For ''Additional packages'':
** Under ''Development packages'' select:
*** Perl
*** Toolchain
*** Native (on-target) SDK
*** Native (on-target) Qt Embedded SDK
*** Native (on-target) Qt X11 SDK Development
** Under ''Network related packages'' select:
*** Dropbear SSH server
*** NTPdate
** Under ''Platform specific packages'':
*** ''Texas Instruments OMAP3x/AM3x family'' select:
**** Matrix GUI for QT/X11
**** PowerVR SGX demos for X11
**** PowerVR SGX gfxdriver plugin for QT/X11
**** TI texture streaming demo for X11
*** ''Texas Instruments OMAP3x/DaVinci/OMAPL family (using DSP)'' select:
**** TI DSPLINK Example Applications
**** TI Codec Engine Example Applications
**** Texas Instruments Gstreamer plugins
*** ''Various demonstration configs'' select:
**** Beagleboard validation GNOME image

Now click '''Build Me!''' This will take some time.

The result of the build will be several files. (''MM''=month of creation, ''XXXX''=unique name you provided)
* Angstrom-2011.''MM''-narcissus-beagleboard-i686-''XXXX''-image-sdk.tar.gz image with the SDK
* ''XXXX''-image-beagleboard.tar.gz image with the file system contents.
* ''XXXX''-image-beagleboard-sd-1GiB.img.gz is a 1GB SD card image.
* ''XXXX''-image-beagleboard-sd-4GiB.img.gz is a 4GB SD card image.

Now we need to install the SDK image
<pre>
tar -C ~/toolchains -xzf Angstrom-2011.MM-narcissus-beagleboard-i686-XXXX-image-sdk.tar.gz
</pre>
(again, ''MM''=month of creation)

This will install the toolchain to <code>~/toolchains/usr/local/angstrom/arm</code>. This is a little long so let's move it
<pre>
mv ~/toolchains/usr/local/angstrom/arm ~/toolchains/arm-angstrom
rm -Rf ~/toolchains/usr
</pre>
So now we have the ARM compiler ready to be used. We will use the SD card image later.

==== More Setup notes ====

<pre>
1. Install VirtualBox
2. Install Ubuntu 10.04.2 from ISO file.
3. We assume you are on a laptop with wired Ethernet port and WiFi capability
4. Setup the Network adapters for connection to both board and the internet
Setup proxy for getting stuff, accessing the internet, etc.

Part 2 - Get ready for DSP Development

5. Download the latest C6Run release package from https://gforge.ti.com/gf/project/dspeasy/frs/

6. Unzip the C6Run package
tar -xzf ~/Downloads/C6Run_X_YY_ZZ_WW.tar.gz

This will create a directory C6Run_X_YY_ZZ_WW in the current directory (I just use my home directory)

7. Download the Texas Instruments C6000 Compiler tools (version 7.2.2 or later) from https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm
Note that this requires you to have a login with my.ti.com. This is a little annoying.

8. Install the DSP compiler to $(HOME)/toolchains
mkdir -p ~/toolchains
chmod +x ~/Downloads/ti_cgt_c6000_7.2.2_setup_linux_x86.bin
~/Downloads/ti_cgt_c6000_7.2.2_setup_linux_x86.bin --mode silent --installto ~/toolchains

This takes a minute and installs silently (you are implicitly agreeing to some EULA when you do this).
The DSP toolchain will be in ~/toolchains/TI_CGT_C6000_7.2.2.

8. Now we need to get an ARM compiler, and we are actually going to do this as part of getting a boot image for the Beagleboard
</pre>
These steps are detailed above...
<pre>

9. Let's setup up C6Run so we can build DSP code.
A. Edit the Rules.mak to point to the right ARM and DSP toolchains:
CODEGEN_INSTALL_DIR ?= $(HOME)/toolchains/TI_CGT_C6000_7.2.2
ARM_TOOLCHAIN_PATH ?= $(HOME)/toolchains/arm-angstrom
ARM_TOOLCHAIN_PREFIX ?= arm-angstrom-linux-gnueabi-

It also appears that we need to make sure that the LINUXUTILS_VERSION is set to 2_25_05_11.
Without this, any application built with C6Run won't work on the current 2011.03 build generated by Narcissus
since the kernel module inlcuded is based on the older LinuxUtils

B. Now get all dependent components to build back-end libararies. The fetching and install may take some time
cd ~/C6Run_X_YY_ZZ_WW
make get_components

C. Edit the file plaftorms/beagleboard-xM/platform.mak and get rid of the redefines of the ARM_TOOLCHAIN_PATH and ARM_TOOLCHAIN_PREFIX (since we want
to use the version we just set above in Rules.mak)

D. Select beagleboard-xM config
make beagleboard-xM_config

E. build the back-end libraries
make gpp_libs dsp_libs

F. Source the environment for the C6Run tools
source environment.sh

G. Build all the examples and test cases to make sure things work
make examples tests

If that all worked, then C6Run is ready to be used to build DSP code for use with ARM programs

10. Now we can get the Beagle up and running. We will use the XXXX-image-beagleboard-sd-4GiB.img.gz file generated by Narcissus.

</pre>

=== Older 2010 image ===

# Go to [http://narcissus.angstrom-distribution.org/ here]
# Under '''Select the machine you want to build your rootfs image for:''' select '''beagleboard'''

There are many configurations you can try. For starts try

# Scroll to almost the bottom and select '''Platform specific packages:'''
# Again scroll to near the bottom and select '''Linuxtag 2010 beagleboard demo'''
# Click '''Build me!''' and wait
# Once the image is created, follow the instructions to download the image. It's big so it will take a while

Once the image is build you will have two files to download. One is a disk image of the CD card and the other is the root file system.

# Download both of these
# Run <code>host$ sudo zcat XXX | dd of=/dev/of/your/sd bs=8225280</code>. This will partition and format the SD card and install the files needed to boot Linux. It took me about 3 minutes.
# run <code>host$ sync</sync> to be sure all the files have been written.
# Next, uncompress the root file system image on the CD card. <code>host$ cd /media/rootfs</code>
# <code>host$ tar -xvf ~/Documents/....</code>
# <code>host$ sync</code>

Eject the SD and plug it in your Beagle and power it up.

← Older revision		Revision as of 16:00, 18 May 2013
Line 1:		Line 1:
−	[[Category:~~ECE497~~ \|~~Notes~~]]	+	[[Category:ECE497Notes \|N ]]

	Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.		Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.

← Older revision		Revision as of 14:26, 18 July 2012
Line 1:		Line 1:
−	[[Category:ECE497]]	+	[[Category:ECE497 \|Notes]]

	Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.		Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.

← Older revision		Revision as of 15:36, 9 March 2012
Line 2:		Line 2:

	Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.		Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.
		+
		+	== ETC 2011 image ==
		+
		+	The ETC image is pretty much the same as the FIE image, but with a couple of things cleaned up. I moved to using git for managing the exercises folder. There some gpio and pwm examples.

	== FIE 2011 image ==		== FIE 2011 image ==

← Older revision		Revision as of 13:39, 2 January 2012
Line 2:		Line 2:

	Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.		Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image. The first listed creates the image used for the ICASSP 2011 tutorial/workshop. The second one does an older image.
		+
		+	== FIE 2011 image ==
		+
		+	The FIE image is pretty much the same as the ICASSP image, but with a couple of things cleaned up.

	== ICASSP 2011 image ==		== ICASSP 2011 image ==

@@ Line 11: / Line 11: @@
 This is the image that Daniel Allred at TI created to support c6run.
-Make a beagleboard boot image and SDK image from [http://www.angstrom-distribution.org/narcissus Narcissus]. These steps are more or less in line from those taken [http://groups.google.com/group/beagleboard/browse_thread/thread/6b57d7dc2dbce7c3 here].
+Make a beagleboard boot image and SDK image from [http://narcissus.angstrom-distribution.org/ Narcissus]. These steps are more or less in line from those taken [http://groups.google.com/group/beagleboard/browse_thread/thread/6b57d7dc2dbce7c3 here].
 * Select '''beagleboard''' as the machine

@@ Line 68: / Line 68: @@
 == Get ready for DSP Development ==
-. Download the latest C6Run release package from [[https://gforge.ti.com/gf/project/dspeasy/frs/ here]].
+* Download the latest C6Run release package from [https://gforge.ti.com/gf/project/dspeasy/frs/ here].
-. Unzip the C6Run package
+* Unzip the C6Run package
-    tar -xzf ~/Downloads/C6Run_X_YY_ZZ_WW.tar.gz
+<pre>
+$ tar -xzf ~/Downloads/C6Run_X_YY_ZZ_WW.tar.gz
-   This will create a directory C6Run_X_YY_ZZ_WW in the current directory (I just use my home directory)
+</pre>
-. Download the Texas Instruments C6000 Compiler tools (version 7.2.2 or later) from https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm
+* Download the Texas Instruments C6000 Compiler tools (version 7.2.2 or later) from [https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm here].
-   Note that this requires you to have a login with my.ti.com.  This is a little annoying.
+Note that this requires you to have a login with [http://my.ti.com my.ti.com]. This is a little annoying.
-. Install the DSP compiler to $(HOME)/toolchains
+*Install the DSP compiler to $(HOME)/toolchains
-   mkdir -p ~/toolchains
-   chmod +x ~/Downloads/ti_cgt_c6000_7.2.2_setup_linux_x86.bin
-   ~/Downloads/ti_cgt_c6000_7.2.2_setup_linux_x86.bin --mode silent --installto ~/toolchains
-−
-   This takes a minute and installs silently (you are implicitly agreeing to some EULA when you do this).
-   The DSP toolchain will be in ~/toolchains/TI_CGT_C6000_7.2.2.
-−
-. Now we need to get an ARM compiler, and we are actually going to do this as part of getting a boot image for the Beagleboard
-</pre>
-These steps are detailed above...
 <pre>
-. Let's setup up C6Run so we can build DSP code.
+* Let's setup up c6Run so we can build DSP code.
-    A. Edit the Rules.mak to point to the right ARM and DSP toolchains:
+** Edit the '''Rules.mak''' to point to the right ARM and DSP toolchains:
-      CODEGEN_INSTALL_DIR     ?= $(HOME)/toolchains/TI_CGT_C6000_7.2.2
+<pre>
-      ARM_TOOLCHAIN_PATH      ?= $(HOME)/toolchains/arm-angstrom
+CODEGEN_INSTALL_DIR     ?= $(HOME)/toolchains/TI_CGT_C6000_7.2.2
-      ARM_TOOLCHAIN_PREFIX    ?= arm-angstrom-linux-gnueabi-
+ARM_TOOLCHAIN_PATH      ?= $(HOME)/toolchains/arm-angstrom
 ARM_TOOLCHAIN_PREFIX    ?= arm-angstrom-linux-gnueabi-
-      It also appears that we need to make sure that the LINUXUTILS_VERSION is set to 2_25_05_11.
+</pre>
-      Without this, any application built with C6Run won't work on the current 2011.03 build generated by Narcissus
-      since the kernel module inlcuded is based on the older LinuxUtils
-    B. Now get all dependent components to build back-end libararies. The fetching and install may take some time
+It also appears that we need to make sure that the '''LINUXUTILS_VERSION''' is set to '''2_25_05_11'''. Without this, any application built with C6Run won't work on the current 2011.03 build generated by Narcissus since the kernel module inlcuded is based on the older LinuxUtils.
-      cd ~/C6Run_X_YY_ZZ_WW
-      make get_components
+** Now get all dependent components to build back-end libararies. The fetching and install may take some time
+<pre>
-    C. Edit the file plaftorms/beagleboard-xM/platform.mak and get rid of the redefines of the ARM_TOOLCHAIN_PATH and ARM_TOOLCHAIN_PREFIX (since we want
+$ cd ~/C6Run_X_YY_ZZ_WW
-       to use the version we just set above in Rules.mak)
+$ make get_components
-    D. Select beagleboard-xM config
+** Select beagleboard-xM config
-      make beagleboard-xM_config
+<pre>
+$ make beagleboard-xM_config
-    E. build the back-end libraries
+</pre>
-      make gpp_libs dsp_libs
-    F. Source the environment for the C6Run tools
+** Source the environment for the C6Run tools
-      source environment.sh
+<pre>
+$ source environment.sh
-    G. Build all the examples and test cases to make sure things work
+</pre>
-      make examples tests
-−
-−
-  If that all worked, then C6Run is ready to be used to build DSP code for use with ARM programs
-−
-−
-. Now we can get the Beagle up and running.  We will use the XXXX-image-beagleboard-sd-4GiB.img.gz file generated by Narcissus.
 </pre>
 === Older 2010 image ===

@@ Line 3: / Line 3: @@
 Here's another precompiled approach that creates a complete disk image, but gives you some control over what is in the image.  The first listed creates the image used for the ICASSP 2011 tutorial/workshop.  The second one does an older image.
-=== ICASSP 2011 image ===
+== ICASSP 2011 image ==
 This is the image that Daniel Allred at TI created to support c6run.
@@ Line 66: / Line 66: @@
 So now we have the ARM compiler ready to be used.  We will use the SD card image later.
-==== More Setup notes ====
+== Get ready for DSP Development ==
-−
-<pre>
-. Install VirtualBox
-. Install Ubuntu 10.04.2 from ISO file.
-. We assume you are on a laptop with wired Ethernet port and WiFi capability
-. Setup the Network adapters for connection to both board and the internet
-    Setup proxy for getting stuff, accessing the internet, etc.
-−
-Part 2 - Get ready for DSP Development
-. Download the latest C6Run release package from https://gforge.ti.com/gf/project/dspeasy/frs/
+. Download the latest C6Run release package from [[https://gforge.ti.com/gf/project/dspeasy/frs/ here]].
 . Unzip the C6Run package