ECE497 Notes on DSP via c6run

Revision as of 14:31, 28 April 2011 by Yoder (Talk | contribs)

Jump to: navigation, search

Here are some notes on how to get c6run going on the BeagleBoard. This has been modified to add detail (4/27/2011) for the ECE4356 class.


There are some 350M of files that need to be downloaded and installed to use c6run. The good news is you don't have to install anything else. The bad news is, if this is being used with a class, 350M * number_of_students can strain a campus internet connection. Therefore we have two options, loading from the internet (works for everyone), and loading from your campus (works if someone on your campus has already downloaded for you).

The files you need to download are:

  • C6run_m_yoder.tgz
  • ti_cgt_c6000_7.0.4_setup_linux_x86.bin
  • angstrom-2010.4-test-20100422-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.2.tar.bz2
  • bios_setuplinux_5_41_09_34.bin

C6run_m_yoder.tgz contains the following:

  1. /lib/modules from target FS
  2. uImage itself
  3. C6Run package prebuilt for the above
  4. C6Run target software
    1. Kernel modules for TI components
    2. and
    3. pre-compiled test and and example applications

Pick your method of getting them.

From the Internet

  • Media:C6run_m_yoder.tgz comes from the eLinux site.
  • Download the TI C6000 v7.0.4 code generation tools for Linux from here
  • Download the angstrom ARM toolchain from here
  • Download the DSP/Bios package from here

From your Campus

Go to your campus site and look for the files listed above. The following schools have the files:

The class dfs site
EE4356 web site

Instructions for Host Setup and Build

Now that you have downloaded the above files, here is how to install them. It's assumed that the downloaded files are in your ~/Download directory (note ~ is /home/beagle below).

Now we create the toolchains directory and populate it

  • Install the codegen tools to ~/toolchains/TI_CGT_C6000_7.04 (you implicitly accept a EULA when doing this)
    host$ mkdir ~/toolchains
    host$ cd ~/Downloads
    host$ chmod +x ti_cgt_c6000_7.0.4_setup_linux_x86.bin
    host$ ls -l ! Look for an x by ti_... to verify it is executable
    host$ ./ti_cgt_c6000_7.0.4_setup_linux_x86.bin --installto ~/toolchains --mode silent
  • Install the ARM toolchain
    host$ tar -C ~/toolchains -xjf angstrom-2010.4-test-20100422-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.2.tar.bz2

The ARM toolchain will be in ~/toolchains/usr/local/angstrom/arm/

  • Install the DSP/Bios package (you implicitly accept a EULA when doing this)
    host$ chmod +x bios_setuplinux_5_41_09_34.bin
    host$ ./bios_setuplinux_5_41_09_34.bin --mode silent --prefix ~/toolchains  
  • Install the pre-built C6Run package. To do this you must first untar the c6run_m_yoder.tgz file
    host$ tar -xvfz c6run_m_yoder.tgz
    host$ cd c6run_m_yoder
    host$ tar -C ~/toolchains -xzf c6run_0_95_02_02_beagleboard.tar.gz
  • Edit the c6run environment settings to correctly point to the location of the components on your host PC (replace ${HOME} with the absolute path)
    host$ cd ~/toolchains/c6run_0_95_02_02_beagleboard
    host$ vi
    /* the following command in vi would make the substitution on all cases */
  • We now want to set up our environment variables. But first we will check to see what they are currently.
    host$ printenv ! Prints all the environment variables, note too many to see
    host$ printenv | more  ! Prints out a page at a time, hit space bar to advance
    host$ printenv | grep ARM ! Only prints lines that have “ARM” in them
    host$ printenv | grep C6 ! Only prints lines that have “C6” in them
  • The above commands, unless you ran the command previously, should show no environment variables with ARM or C6 in them
  • Source the environment variables and rerun the checks
    host$ source
    host$ printenv | grep ARM ! Only prints lines that have “ARM” in them
    host$ printenv | grep C6 ! Only prints lines that have “C6” in them

The preceding checks should now show that the following FOUR environment variables are set: ARM_TOOLCHAIN_PREFIX, ARM_TOOLCHAIN_PATH, CFLAGS, and C6RUN_TOOLCHAIN_PATH. At this point the environment and components are all setup to build the examples and test cases included in the the C6Run package. The compilation scripts (c6runlib and c6runapp scripts) rely on these and the other variables from the file.

It is suggested that the test and example makefiles be used as a template for any builds done for your own code.

  • Run make to compile the example code
    host$ cd example ! You should be in /home/beagle/toolchains/c6run_0_95_02_02_beagleboard/examples
    host$ make
  • Look at the output to make sure that no errors occurred. If errors occur then either correct them or seek instructor help
  • Go into the sub directories to see the compiled code
    host$ cd c6runapp/emqbit
    host$ ls
  • You should see in the directory listing the files bench_arm and bench_dsp (among others).

Target Preparation

  • Setup the beagleboard to boot using the included kernel image (uImage binary file). This should just require replacing the uImage file on your SD card with the provided one (rename the file to be just 'uImage'). This step can be accomplished with the following commands, after the SD card which has the Angstrom linux system has been put into the card reader and mounted on the host system.
    host$ df ! Verify that /media/BEAGLE and /media/ANGSTROM file systems are available
    host$ cd /media/BEAGLE ! Or whichever file system has the uImage file
    host$ mv uImage uImage.bak ! Save a copy in case you mess up
    host$ cd ~/Downloads/C6run_m_yoder
    host$ cp uImage /media/BEAGLE
  • Copy the the contents of the provided /lib/modules to the target's /lib/modules path. I (Yoder) found I didn't need to do this. I (Usevitch) concur.
  • Copy the contents of c6run_target.tar.gz to the target file system. I placed it in /opt. It contains the kernel modules from the TI components and the script which should be used to install them. The pre-built examples and test cases are also included in this archive. However, we also want to see if our compiled example code will work. Therefore we will copy over our examples directory.
    host$ mkdir /media/ANGSTROM/opt
    host$ cp c6run_target.tar.gz /media/ANGSTROM/opt
    host$ cd /media/ANGSTROM/opt
    host$ tar -xvf c6run_target.tgz ! This can be done on the host or on the beagleboard when linux boots
    host$ cp -R ~/toolchains/c6run_0_95_02_02_beagleboard/examples .  ! copy our examples directory onto the SD card
    host$ cd ! can't unmount a file system in use
    host$ umount /media/ANGSTROM
    host$ umount /media/BEAGLE

Target Running

  • Remove the SD card, place it into the beagleboard, and boot Angstrom linux.
  • Before running any c6run based application, make sure you run the script to load the needed kernel modules.
   beagle$ cd /opt/home/daniel/c6run_target
   beagle$ ./  ! sometimes modules are left over and need to be removed
   beagle$ ./ 
  • Now we will run our compiled fft benchmark examples
   beagle$ cd /opt/examples/c6runapp/emqbit
   beagle$ ./bench_arm
   beagle$ ./bench_dsp