Difference between revisions of "EBC Exercise 05 Getting Exercise Support Materials"

From eLinux.org
Jump to: navigation, search
m (Get the Files)
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
[[Category:ECE497]]
 
[[Category:ECE497]]
 
{{YoderHead}}
 
{{YoderHead}}
Many of the following exercises require some extra files on the BeagleBoard.  These files are stored in a '''git''' repository.  We'll learn more about using git later.  Here I'll just show you how to get the files.
 
  
== Set Up Git ==
+
You need to download some reference manuals and set up your Beagle with some extra files.  Here's what to do.
  
Go to [http://help.github.com/set-up-git-redirect github] and follow the directions for installing and setting up git. No need to set up your own repository right now (unless you want to).
+
== Download Reference Manuals ==
 +
There are two important hardware reference manuals you need to have, the '''System Reference Manual''' (SRM) and the '''Technical Reference Manual''' (TRM) for the ARM processor. Here's where to find them.
 +
# The official SRM is kept [https://github.com/beagleboard/BeagleBone-Black here on github]. Here you will find a pdf file with the SRM.  Download it.
 +
# Finding the TRM if for the am335x and is on [http://www.ti.com/lit/pdf/spruh73 TI's site].
  
I suggest you do this for both your host computer and your Beagle. On the Beagle use
+
Keep both of these in an easy to find place, we'll reference them now and then.
  
beagle$ '''opkg update'''
+
== Set Up Git ==
beagle$ '''opkg install git'''
 
beagle$ '''opkg install openssh-keygen'''
 
 
 
The last opkg installs <code>ssh-keygen</code> which is needed to work with github.
 
 
 
On my host computer I had to run
 
  
  host$ '''ssh-add id_rsa'''
+
Many of the following exercises require some extra files on the BeagleBoard which you should have loaded on your host computer eariler. These files are stored in a '''git''' repository.  We'll learn more about using git later. Here I'll just show you how to get the files.
 
 
after running <code>ssh-keygen</code> to get <code>ssh -T git@github.com</code> to work.
 
  
 
== Get the Files ==
 
== Get the Files ==
Line 25: Line 19:
 
It only takes one command to pull down all the files.
 
It only takes one command to pull down all the files.
  
  beagle$ '''git clone git@github.com:MarkAYoder/BeagleBoard-exercises.git exercises'''
+
  bone$ '''git clone https://github.com/MarkAYoder/BeagleBoard-exercises.git exercises --depth=1'''
 +
(The whole repo is some 550M.  Using '''--depth=1''' you only get the recent history and it only takes 190M.)
  
This will take a while since it's getting all the course files, including pdf files of the course PowerPoint.  You only have to clone once for each computer.  I suggest you do the same on your host computer.
+
This will take a while since it's getting all the course files, including pdf files of the course PowerPoint.  You only have to clone once for each computer.  I suggest you do the same on your host computer if you have done so already.
  
  host$ '''git clone git@github.com:MarkAYoder/BeagleBoard-exercises.git exercises'''
+
  host$ '''git clone https://github.com/MarkAYoder/BeagleBoard-exercises.git exercises --depth=1'''
  
 
Now take a look at what you got.
 
Now take a look at what you got.
  
  beagle$ '''cd exercises'''
+
  bone$ '''cd exercises'''
  beagle$ '''ls'''
+
  bone$ '''ls'''
  beagle$ '''cd pptx'''
+
  bone$ '''cd pptx'''
  beagle$ '''ls'''
+
  bone$ '''ls'''
  
 
Later exercises will tell you which files to use from here.
 
Later exercises will tell you which files to use from here.
Line 42: Line 37:
 
If it's been a while since you did the clone it's a good idea to do a '''pull'''.  This will make sure all the files are up to date.
 
If it's been a while since you did the clone it's a good idea to do a '''pull'''.  This will make sure all the files are up to date.
  
  beagle$ '''git pull'''
+
  bone$ '''git pull'''
 +
 
 +
=== P8 and P9 Header Files ===
 +
The BeagleBone Black has two headers, P8 and P9, that have lots of IO. There are two [http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/ pdf files] that have lots of information about the headers in this git repository.  Here's how to get them
 +
host$ '''git clone git://github.com/derekmolloy/boneDeviceTree.git'''
 +
host$ '''cd boneDeviceTree/docs'''
 +
host$ '''ls'''
 +
BeagleboneBlackP8HeaderTable.pdf  BeagleboneBlackP9HeaderTable.pdf
 +
Put these where you can find them again.
  
 
{{YoderFoot}}
 
{{YoderFoot}}

Revision as of 10:17, 7 September 2016

thumb‎ Embedded Linux Class by Mark A. Yoder


You need to download some reference manuals and set up your Beagle with some extra files. Here's what to do.

Download Reference Manuals

There are two important hardware reference manuals you need to have, the System Reference Manual (SRM) and the Technical Reference Manual (TRM) for the ARM processor. Here's where to find them.

  1. The official SRM is kept here on github. Here you will find a pdf file with the SRM. Download it.
  2. Finding the TRM if for the am335x and is on TI's site.

Keep both of these in an easy to find place, we'll reference them now and then.

Set Up Git

Many of the following exercises require some extra files on the BeagleBoard which you should have loaded on your host computer eariler. These files are stored in a git repository. We'll learn more about using git later. Here I'll just show you how to get the files.

Get the Files

It only takes one command to pull down all the files.

bone$ git clone https://github.com/MarkAYoder/BeagleBoard-exercises.git exercises --depth=1

(The whole repo is some 550M. Using --depth=1 you only get the recent history and it only takes 190M.)

This will take a while since it's getting all the course files, including pdf files of the course PowerPoint. You only have to clone once for each computer. I suggest you do the same on your host computer if you have done so already.

host$ git clone https://github.com/MarkAYoder/BeagleBoard-exercises.git exercises --depth=1

Now take a look at what you got.

bone$ cd exercises
bone$ ls
bone$ cd pptx
bone$ ls

Later exercises will tell you which files to use from here.

If it's been a while since you did the clone it's a good idea to do a pull. This will make sure all the files are up to date.

bone$ git pull

P8 and P9 Header Files

The BeagleBone Black has two headers, P8 and P9, that have lots of IO. There are two pdf files that have lots of information about the headers in this git repository. Here's how to get them

host$ git clone git://github.com/derekmolloy/boneDeviceTree.git
host$ cd boneDeviceTree/docs
host$ ls
BeagleboneBlackP8HeaderTable.pdf  BeagleboneBlackP9HeaderTable.pdf

Put these where you can find them again.




thumb‎ Embedded Linux Class by Mark A. Yoder