Difference between revisions of "ECE497 Lab10 gMake"

From eLinux.org
Jump to: navigation, search
m (Lab 08, Multithread)
(Delete, there's a newer page out there.)
 
(30 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Below are the details of the labs we'll be doing from the DaVinci workshop.  Get these files before doing the labs:
+
[[Category:ToDelete]]
  
* Go to the class [https://myrhit.rose-hulman.edu/class/ece597/default.aspx SharePoint Site] and get
+
See [[EBC Exercise 07a make]] instead.
** DaVinci-OMAP_Workshop_v2.0.pdf
+
** tto_workshop_labs_(v2.00).tar
+
** makefile_profile.mak
+
  
* Untar the labs file on your Linux host.  It will create two directories, '''workshop''' and '''solutions'''You will find the materials needed to do the labs below in the '''workshop''' directoryThe directions in '''DaVanci-OMAP_Workshop''' file will tell you which directory to use for each lab.
+
Texas Instruments' Technical Traning for students concerning the DaVinci/OMAP platforms including DM64xx, DM35x/36x, OMAP35x, OMAP-L1x, and AMxBelow are the details of the labs we'll be doing from the DaVinci workshop.   
  
These labs were originally done for the Digital Video Evaluation Module (DVEVM)We will be adapting them for the BeagleBoard as we go.
+
Note, the workshop calls these labs 6-8I'm renumbering them to fit our numbering scheme, so the mapping is:
  
== Lab 05, gMake ==
+
{| style="color:green; background-color:#ccffff;" cellpadding="10" cellspacing="0" border="1"
 +
! Our Lab Number !! TI Lab Number
 +
|-
 +
| 10
 +
| 5
 +
|-
 +
| 11
 +
| 6
 +
|-
 +
| 12
 +
| 7
 +
|-
 +
| 13
 +
| 8
 +
|}
  
Lab 05 is on pages 125-157 of the DaVinci-OMAP_Workshop_v2.0.pdf file. Work through this lab.  You'll learn how '''make''' works.  When you get to part D, compare my version of the make file ('''makefile_profile.mak.yoder''') to the one in the folder.  The workshop assumes you have NFS setup to share files between the DVEVM and the host computer.  Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing.  If you can at the NFS working, great!, otherwise use my setup.  
+
Labs 10/5 appears here the rest have their own pages.
  
== Lab 06, Using the OSS Driver ==
+
== Lab 10/5a - Installation ==
  
Lab 06 is on pages 171-186 of the DaVinci-OMAP_Workshop_v2.0.pdf file.  In doing this lab you will get audio from the line-in jack on the Beagle and sent it out the speaker jack.
+
* Go to the class dfs site and get
* Go to the class [https://myrhit.rose-hulman.edu/class/ece597/default.aspx SharePoint Site] and get
+
** DaVinci-OMAP_Workshop_v2.0.pdf
** setpaths.mak
+
** tto_workshop_labs_(v2.00).tar
** setpaths.sh
+
** makefile_profile.mak
  
* Move the '''setpaths''' files in the workshop directory to another location.
+
* Untar the labs file on your Linux host.  It will create two directories, '''workshop''' and '''solutions'''.  You will find the materials needed to do the labs below in the '''workshop''' directory. The finished product for each lab can be found in the '''solutions''' directory. The directions in '''DaVanci-OMAP_Workshop''' file will tell you which directory to use for each lab.
<pre>
+
host $ cd workshop
+
host $ mv setpaths.sh setpaths.sh.orig
+
host $ mv setpaths.mak setpaths.mak.orig
+
</pre>
+
* Copy the setpaths files you got from SharePoint into the workshop directory. In Lab 6 you will edit these files so they are correct.
+
  
== Lab 07, Using Video Drivers ==
+
These labs were originally done for the Digital Video Evaluation Module (DVEVM).  I've  adapted them for the BeagleBoard.
  
== Lab 08, Multithread ==
+
== Lab 10/5b - gMake ==
  
== Lab 09, Prebuilt Engine ==
+
Lab 10 is lab 5 on pages 125-157 of '''DaVinci-OMAP_Workshop_v2.0.pdf'''. Work through this lab.  You'll learn how '''make''' works.  Part C has an error in the solution, a workaround can be found [[User:Simonea|here]].  When you get to part D, compare my version of the make file ('''makefile_profile.mak.yoder''') to the one in the folder.  The workshop assumes you have NFS setup to share files between the DVEVM and the host computer.  Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing.  If you can get NFS working, great!, otherwise use my setup.
 +
 
 +
To get part '''d''' to compile correctly, you have to make sure all the path information is correct.  Make sure to edit '''setpaths.sh, setpaths.mak, and makefile_profile.mak'''.  Because Configure is stubborn, you will still need to link <code>arm_v5t_le-gcc</code> to <code>arm-nonearm-none-linux-gnueabi-gcc</code> if it is to compile.
 +
<pre>
 +
cd /home/user/CodeSourcery/Sourcery_G++_Lite/bin
 +
ln -s arm-none-linux-gnueabi-gcc arm_v5t_le-gcc
 +
</pre>

Latest revision as of 19:25, 9 December 2011


See EBC Exercise 07a make instead.

Texas Instruments' Technical Traning for students concerning the DaVinci/OMAP platforms including DM64xx, DM35x/36x, OMAP35x, OMAP-L1x, and AMx. Below are the details of the labs we'll be doing from the DaVinci workshop.

Note, the workshop calls these labs 6-8. I'm renumbering them to fit our numbering scheme, so the mapping is:

Our Lab Number TI Lab Number
10 5
11 6
12 7
13 8

Labs 10/5 appears here the rest have their own pages.

Lab 10/5a - Installation

  • Go to the class dfs site and get
    • DaVinci-OMAP_Workshop_v2.0.pdf
    • tto_workshop_labs_(v2.00).tar
    • makefile_profile.mak
  • Untar the labs file on your Linux host. It will create two directories, workshop and solutions. You will find the materials needed to do the labs below in the workshop directory. The finished product for each lab can be found in the solutions directory. The directions in DaVanci-OMAP_Workshop file will tell you which directory to use for each lab.

These labs were originally done for the Digital Video Evaluation Module (DVEVM). I've adapted them for the BeagleBoard.

Lab 10/5b - gMake

Lab 10 is lab 5 on pages 125-157 of DaVinci-OMAP_Workshop_v2.0.pdf. Work through this lab. You'll learn how make works. Part C has an error in the solution, a workaround can be found here. When you get to part D, compare my version of the make file (makefile_profile.mak.yoder) to the one in the folder. The workshop assumes you have NFS setup to share files between the DVEVM and the host computer. Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing. If you can get NFS working, great!, otherwise use my setup.

To get part d to compile correctly, you have to make sure all the path information is correct. Make sure to edit setpaths.sh, setpaths.mak, and makefile_profile.mak. Because Configure is stubborn, you will still need to link arm_v5t_le-gcc to arm-nonearm-none-linux-gnueabi-gcc if it is to compile.

cd /home/user/CodeSourcery/Sourcery_G++_Lite/bin
ln -s arm-none-linux-gnueabi-gcc arm_v5t_le-gcc