ECE497 Instructor's Guide - Revision history

Yoder: Added tag

2012-07-18T14:45:29Z

Added tag

2012-05-28T17:57:32Z

Added Header/Footer

2011-08-25T19:30:35Z

‎What Topics Should be Covered?: Moved topics to another page.

2011-08-25T18:55:52Z

Added categories

2011-08-25T18:10:17Z

‎Embedded Linux - Processing Audio and Video: Added Using the DSP

2011-08-24T12:46:55Z

‎Embedded Linux - Processing Audio and Video: Updated link

2011-08-23T20:34:31Z

Added Audio and Video processing

2011-08-22T16:50:55Z

Removed analytics

2011-08-22T15:36:00Z

‎Embedded Linux Kernel Topics

2011-08-22T15:35:49Z

‎Embedded Linux Development Topics

@@ Line 1: / Line 1: @@
-[[Category:ECE497]]
+[[Category:ECE497 | Instructor's]]
 [[Category:EmbeddedBeagleClass]]
 [[Category: BeagleBoard]]

@@ Line 2: / Line 2: @@
 [[Category:EmbeddedBeagleClass]]
 [[Category: BeagleBoard]]
 There are many choices that have to be made when designing a college course.  The open source world gives you even more choices.  The following takes you down the path I have chosen for my 32-bit embedded Linux course ([[ECE497 - 32-bit Embedded Linux, Rose-Hulman]]).  As we travel I'll point out what decisions needed to be made, what the options were and why I made my choice. Once you see where I've taken you, it should be easier for you to pick a path for your class.
@@ Line 76: / Line 77: @@
 ; Also, while there is significant open-source support, do we need Development Tools from TI to program/compile/debug the software on the board? If so, how can we obtain a license for this software?
 : Presently there are free ARM compilers; however if you use the DSP you need to get the 'C6x compiler from TI.  It's free, but you have to agree to their license.

@@ Line 55: / Line 55: @@
 == What Topics Should be Covered? ==
-When I first started planning for this course I was told "The hardest things about designing such a course is deciding what to leave out".  That is very true.  There is a huge range of topics that could be covered. They seem to fall in three broad categories:
+[[EBC_Embedded_Beagle_Class_Topics | Here]] is a list of topics that I've covered.  The list includes labs and exercises for nearly every topic.
-# Traditional embedded topics such as reading switches and flashing LEDs (general purpose I/O), UARTS, I2C, SPI, and A to D's.
-# Embedded Linux topics such as tools for code development and what happens when the kernel boots up, how to write device drivers, etc.
-# Advanced applications.  This includes open source projects such as processing streaming media with [http://gstreamer.freedesktop.org/ GStreamer] and computer vision with [http://opencv.willowgarage.com/wiki/ OpenCV]
-Here's what I have planned.
+=== Course Projects ===
 A major part of the course grade is based on a major project.  Here are some of the projects that have been done, or that I'm proposing:  [[ECE497 Project Ideas]]

← Older revision		Revision as of 18:55, 25 August 2011
Line 1:		Line 1:
	[[Category:ECE497]]		[[Category:ECE497]]
		+	[[Category:EmbeddedBeagleClass]]
	[[Category: BeagleBoard]]		[[Category: BeagleBoard]]

@@ Line 102: / Line 102: @@
 ; [[EBC_Exercise_08_Using_ALSA_for_Audio_Processing | Using ALSA for Audio Processing]]
 : This is a three part lab.  Part a shows how to use ALSA to input sounds and save them to a file.  Part b reads that file and plays the sound.  Both parts are inspection labs, i.e., you just look at them.  In part c you combine parts a and b to create a program that inputs a sound from the line in and outputs to the line out.
 === Embedded Linux - Kernel Topics ===

@@ Line 100: / Line 100: @@
 At this point in a traditional embedded class one starts working with more complex interfaces such at A2D's and D2a'a.  We do the same here, but differently.  In a traditional class you learn which registers to use to setup and run the A2D.  Here we learn to use ALSA (Advanced Linux Sound Architecture) a standard sound interface for Linux.  What is learned will also work on a Linux host computer.
-; [[ECE497_Lab11_Using_ALSA_for_Audio_Processing | Using ALSA for Audio Processing]]
+; [[EBC_Exercise_08_Using_ALSA_for_Audio_Processing | Using ALSA for Audio Processing]]
 : This is a three part lab.  Part a shows how to use ALSA to input sounds and save them to a file.  Part b reads that file and plays the sound.  Both parts are inspection labs, i.e., you just look at them.  In part c you combine parts a and b to create a program that inputs a sound from the line in and outputs to the line out.

@@ Line 95: / Line 95: @@
 ; [[EBC_Exercise_07b_make_with_variables | make with variables]]
 : In this part, we will add some user-defined variables and built-in variables to simplify and help the makefile more readable. You will also have a chance to build a “test’ rule to help debug your makefile.
 === Embedded Linux - Kernel Topics ===

@@ Line 97: / Line 97: @@
 : In this part, we will add some user-defined variables and built-in variables to simplify and help the makefile more readable. You will also have a chance to build a “test’ rule to help debug your makefile.
-=== Embedded Linux Kernel Topics ===
+=== Embedded Linux - Kernel Topics ===
 It's time to start looking into what the kernel does and how it does it. Here we move from completely Beagle-based development to setting up the host for cross-development.  Soon you'll be compiling your own kernel!

@@ Line 81: / Line 81: @@
 : There are a number of serial standards for processors to talk to peripherals.  I²C is a "two-wire interface" standard that is used to attach low-speed peripherals to an embedded system. In this exercise we wire up a couple of I²C temperature sensors (TC74) and learn how to read their values.
-=== Embedded Linux Development Topics ===
+=== Embedded Linux - Development Topics ===
 The following exercises start the transition to Linux based approaches.  They introduce Linux-based tools, but we're working with the kernel yet.