eLinux.org - User contributions [en]

EBC Exercise 27 BusyBox

2012-11-06T18:17:07Z

Correlbn: /* Running a Web Server */

[[Category:ECE497]]
[[Category:BeagleBoard]]
{{YoderHead}}

== Getting BusyBox ==
=== downloading ===

Get the busybox sources from the busybox site

host$ '''git clone git://busybox.net/busybox.git'''
host$ '''cd busybox'''

=== compiling ===
host$ '''source ~/.oe/crossCompileEnv.sh'''
host$ '''make help'''
host$ '''make defconfig'''
host$ '''make -j9''' # use -j''X'' for ''X-1'' cores

=== configuring ===

You can now configure BusyBox.

host$ '''make gconfig'''

After saving the configuration changes to update the .config file, it is a simple matter of running make.

host$ '''make -j9'''

My make took about 1.5 minutes to compile (25 seconds with make -j8!).

=== installing ===
Copy it to your Beagle and test it out. Just typing '''busybox''' will tell you what commands it knows. Try some of them.
host$ '''scp busybox root@beagle:.'''
beagle$ '''busybox'''
beagle$ '''busybox ls'''

Try some other commands...

== Playing with BusyBox ==

=== shrinking ===

How big is the '''busybox''' file? The default configuration for busybox has it many things (some 400). Reconfigure it to do just the commands you use. How big is it now? How big is it if you just have ''ls''? How much bigger is it when you add httpd? Try your own combinations. Report your findings in your status report.

=== Static Linking ===

Some embedded systems are so small they don't have shared libraries. Recompile busybox to be statically linked. (Hint: look in configuration) How big it is? Does it still work?

=== Running a Web Server ===

Configure busybox to be a web server. Look under '''Networking Utilites''', select '''httpd'''. How much more space does it take?

beagle$ '''busybox httpd'''

Yup, you are now running a web server. Your task is to figure out where to put the web pages it is serving. If you get something interesting going, post your Beagle's address here. Hint: find httpd.c.

{{YoderFoot}}

ECE497 BeagleBone PRU

2012-11-06T16:50:55Z

Correlbn: /* Work Breakdown */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[user:Correlbn|Bryan Correll]], [[user:Millerap|Andrew Miller]], [[user:Ngop|Peter Ngo]], [[user:Popenhjc|James Popenhagen]]

== Grading ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
09 Executive Summary (looks good)
05 Installation Instructions (Can't find uio_pruss)
05 User Instructions (Segmentation fault)
10 Highlights (Nice clean tone in 2nd video)
07 Theory of Operation (Good overview. I'd like to see more comment in your PRU code)
05 Work Breakdown (Need to include who did what)
10 Future Work
10 Conclusions
00 Demo (I want to hear the clean sine before filling this in)
10 Late
Comments:

Score: 00/100
</pre>

== Executive Summary ==

For this project, the objective is to explore the PRU, Programmable Realtime Unit, (DID THIS:Define PRU) of the BeagleBone, looking at both the limitations of implementation and how to implement tasks such as handling pulse width modulation. The PRU is a part of the processor that runs at 200MHz (5ns per instruction), and is separate from the operating system all together, making it more efficient at accessing I/O pins. The project is more research intensive, as opposed to implementation intensive, and serves to bring together all of the sources found on the BeagleBone's PRU into one abbreviated document with examples of how to use it and the potential for extra projects. The ultimate goal here is to walk through step by step leading to the representation of a sinusoidal wave using pulse width modulation accessed from PRU and play the produced wave through a speaker.

As of now we have gathered information about the PRU, found memory locations that can be edited on the PRU and in C so that we can interact with functions outside of the PRU's capabilities, and implemented code on the PRU that simulates a pulse width modulation on a GPIO pin. We were also able to produce an approximated sinusoidal output on the GPIO pin using pulse width modulation at a specific frequency. For each of these there is an example to follow describing how each part works, and listing any resources to look at to find out more.

We were hoping to potentially look into reading an analog input and producing it as an approximated output using the pulse width modulator, but this ended up being to optimistic of a goal. This would be an interesting thing to explore for a project that expands upon this.

== Installation Instructions ==

The Git Hub is on the following link:

*https://github.com/millerap/AM335x_PRU_BeagleBone
*Hardware: Some LEDs for messing with the GPIO pins and a speaker for listening to PWM approximated sine wave.

Note: When implementing the pulse width modulation, you may want to bias the wave around 0V instead of 1.65V. If this is the case, you may want to use a summing circuit which will require an Op-Amp, a 2kohm and 1kohm resistor, and 2 resistors of the same value (Higher values preferable for lower power consumption), which will need to be connected as shown where V1 is your pwm voltage, V2 is your -1.65V bias, and V3 is unused:

[[File:SummerCicuit.png|Non-Inverting Summer Circuit]]

Unless you desire a louder output than capable with simple I/O pins, there is no additional hardware needed.

== User Instructions ==

'''Always''' run the following before doing anything with the PRU:
beagle$ '''modprobe uio_pruss'''

This can be activated anywhere on the BeagleBone and activates the PRU module in the kernel so that its memory and all of its components are accessible.

Note: modprobe uio_pruss is BeagleBone specific and will not be found on a host computer. Also, if you do not do this instruction before following the rest of the instructions you may run into segmentation faults when trying to initialize the PRU.

DID THIS:Where is uio_pruss? (Not a specific location, can be accessed anywhere on the BeagleBone)

== Finding Where to Access Things ==

There are many locations in memory that are needed to access specific I/O pins on the BeagleBone. Some of these I/O pins can be found here:
*[http://www.ti.com/lit/ug/spruh73f/spruh73f.pdf SPRUH73f pdf]

The following are not found in the file, but are good addresses to know when accessing MUXs:

gpmc_a2:
memory location: gpmc_a2.gpio1_18 (0x44e10848/0x848 = 0x0027), b NA, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE7
signals: gpmc_a2 | gmii2_txd3 | rgmii2_td3 | mmc2_dat1 | gpmc_a18 | pr1_mii1_txd2 | ehrpwm1A | gpio1_18

gpmc_a3:
memory location: gpmc_a3.gpio1_19 (0x44e1084c/0x84c = 0x0027), b NA, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE7
signals: gpmc_a3 | gmii2_txd2 | rgmii2_td2 | mmc2_dat2 | gpmc_a19 | pr1_mii1_txd1 | ehrpwm1B | gpio1_19

gpmc_ad8:
memory location: gpmc_ad8.gpio0_22 (0x44e10820/0x820 = 0x0027), b NA, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE7
signals: gpmc_ad8 | lcd_data23 | mmc1_dat0 | mmc2_dat4 | ehrpwm2A | pr1_mii_mt0_clk | NA | gpio0_22

gpmc_ad9:
memory location: gpmc_ad9.gpio0_23 (0x44e10824/0x824 = 0x0027), b NA, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE7
signals: gpmc_ad9 | lcd_data22 | mmc1_dat1 | mmc2_dat5 | ehrpwm2B | pr1_mii0_col | NA | gpio0_23

== Building and Running the GPIO_PWM_PRU Example ==

This example is located in the GPIO_PWM_PRU directory in the AM335x_PRU_BeagleBone git repository, and can be pulled with the following:
beagle$ '''git clone git://github.com/millerap/AM335x_PRU_BeagleBone'''

This example uses the gpio and delay loops to approximate a PWM using the user LEDs on the BeagleBone. It is based on an example provided by Lyren Brown and documented by boxysean at
http://blog.boxysean.com/2012/08/12/first-steps-with-the-beaglebone-pru/

In GPIO_PWM_PRU all of the complicated Makefiles and directories used to make a multitude of examples at once have been stripped away to allow the user to compile one individual program that will run on the PRU.

The readme.txt file in the GPIO_PWM_PRU directory provides a walkthrough for compiling and running blinker on the BeagleBone.

The first step to compiling a program for the PRU is to make sure prussdrv.c is made and up to date. This is the file provided by TI that contains all of the C functions that allow for communication with the PRU. To do this, do the following:
beagle$ '''cd <directory>/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/interface'''
beagle$ '''export CROSS_COMPILE=""'''
beagle$ '''make'''

Make the rest follow the above format.

CROSS_COMPILE is specified as "" because this is running on the BeagleBone itself and the Makefile is setup to defaultly cross compile the code from another linux machine.

Once this is completed, the pasm_source must be set for the BeagleBone's linux operating system:
beagle$ '''cd ../utils/pasm_source'''
beagle$ '''./linuxbuild'''

'''Note: The above instructions need to be done for every time the BeagleBone boots up and these directories should be included with any code that you write for the PRU'''

Now, the BeagleBone is ready to compile the example code. Navigate to the example's root directory again:
beagle$ '''cd ../../'''
beagle$ '''make CROSS_COMPILE=""'''

This will compile the blinker.c file and output it to the bin folder. After this point, the assembly file needs to be compiled into a .bin file. This is done in the bin folder.
beagle$ '''cd bin'''
beagle$ '''make'''

Now, there should be a blinker.bin file in the folder. running the blinker executabile will put the blinker.bin file on the PRU and start it running. Use the following:
beagle$ '''./blinker'''

I get a Segmentation fault, but I think that's because I can't do the modprobe

== How the Assembly Code Works ==
(DID THIS:Note that this is /bin/blinker.p. WORKING ON THIS: Could you add
some comments to the file explaining things?)
//in the overview talk about the period being 5ns

In the assembly file blinker.p:

Registers r5 and r6 are the duty_cycle and period respectively. The duty_cycle is a number smaller than the period that the accumulator r4 counts up to before setting the output to zero. When the r4 = period, r4 resets and the output is set to 1. This gives the following for for OnTime and OffTime.

SecondsPerCycle = 5*10^-9
OnCycles = 2 + (duty_cycle)*3 + 2
OffCycles = 2 + (period - duty_cycle)*3 - 1 + 2
TotalCycles = 7 + (period)*3

These equations can be used to create a very exact PWM output by setting duty_cycle and period to the values you wish to use. The code that was compiled and run above has a period of about a second and a duty cycle of about 50%.

There are a few macros defined at the beginning of the program. These macros are the location of GPIO1's memory space, the location of its set registers and the location of its clear registers. The BeagleBone's GPIO pins must be turned off and on using these two different memory locations. Setting the set register to 0 does not turn off its respective GPIO pin.

r2 stores the value that is going to be written to either set or clear gpio. r3 stores the address that r2 will be written to. within the first 3 lines of PWM_ON these values are set such that r2 will turn on the user LEDs. The instruction that actually turns it on is SBBO. This takes the value of r2 and writes it to memory location r3 with an offset of 0.

Here is a complete guide to the [http://processors.wiki.ti.com/index.php/PRU_Assembly_Instructions PRU's Assembly Instructions] from TI

== How the C Code Works ==
DID THIS:This is an interesting section. Could you note here where in the manuals
you found your information?

The following information can be found on TI's PRU Linux Application Loader API Guide wiki:
*[http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader_API_Guide#prussdrv_map_prumem C PRU instructions]

This lays out every function that can be used in the C code as well as an explanation of its functionality.

The blinker.c file is a direct port of the PRU initialization code from TI. Putting the two side by side, the only difference between the two is the name of the bin file that is used for the exec function.

The code first initializes the PRUSS, Programmable Realtime Unit Subsystem or the entire system of two PRUs, an interrupt controller (INTC), and associated memory ([http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit_Subsystem PRUSS]),(DID THIS:What's the difference between PRUSS and PRU?) by allocating memory for it using the prussdrv_init() function. It then initializes memory mapping for the PRU using the prussdrv_open() function. All of the intc functions are used for interrupt communication between the ARM and the PRU. This code is not utilized by the examples in this page.

Similar to the exec function in C, the prussdrv_exec_program () function overlays the IRAM (Instruction RAM) portion of the PRUSS with the bin file that was created from blinker.p. The first field of prussdrv_exec_program needs a PRU number, which is either 0 or 1 depending on which PRU core is being used. In this case, PRU0 is executing blinker.bin. The second field is the path to the bin that will be put into the PRU's IRAM.

The next section waits on event 0 from the PRU to signal the C program that it has completed its execution. This, again, was not implemented, but writing the appropriate bit to the r31 register would cause the C program to continue. As it is, the program stalls at this point until SIGINT is received.

If the correct event were received, the next function is used to halt the PRU's execution then it would release the PRUSS clocks and disable the prussdrv module.

== Sending an array to the PRU ==

The initialization code provided by TI has a handy function for passing an array to the PRU. Each of the PRU cores have an 8kb data ram associated with them, and that data space can be populated from an external C program. The next example will make use of this function to pass different PWM duty cycles to the PRU. This will be largely based around the following function:

int prussdrv_pru_write_memory (unsigned int pru_ram_id, unsigned int wordoffset, unsigned int *memarea, unsigned int bytelength);

pru_ram_id can take on one of 4 values, and are as follows:

PRUSS0_PRU0_DATARAM
PRUSS0_PRU1_DATARAM
PRUSS0_PRU0_IRAM
PRUSS0_PRU1_IRAM

Here, each of the PRUs have both an Instruction RAM and a DATARAM section. DATARAM for PRU0 is found in the memory locations 0x0 - 0x2000, and DATARAM for PRU1 is found in the memory locations 0x2000 - 0x4000.

wordoffset is an offset in words (4 bytes) from the base memory location, pru_ram_id.

memarea is a pointer to an array of unsigned ints (also 4 bytes) that will be passed onto the PRU.

bytelength is the number of bytes to write to the PRU.

For more information on using C to initialize the PRU visit [http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader_API_Guide#prussdrv_map_prumem TI's PRU Linux Application Loader API Guide]
Thanks for the reference. It's a big help.)

== Building and Running the Sin_Approximation Example ==

This example uses a modified version of the GPIO_PWM_PRU example to change the duty cycle every period such that the average voltage approximates a sin wave. Navigate to the pwm_sin directory and take a look at the C code. Its nearly identical to the previous code except for a few small differences. The first difference is that it opens and edits two files to export GPIO0_7 and turn it into an output.

The next change is that the prussdrv_pru_write_memory command discussed above is used to push an array containing duty cycles onto the DRAM for PRU0. The duty cycles are approximated using a the sin function from the math.h header file. Here is why:
(VCC*(on_time)+0*(off_time))
---------------------------- = VCC*duty_percent
period
.
VCC*duty_percent = Va
.
Va = VCC*Sin(2*PI*f*t/fs)
.
VCC*duty_percent = VCC*sin(2*PI*f*t/fs)
.
duty_percent = sin(2*PI*f*t/fs)

Looking at the assembly code, we see a similar PWM control as before, but this time it is reading the duty cycles from memory. The coding to do this is a little more complicated due to precise measuring for the sampling frequency, but because this is being run on PRU0, DRAM starts at 0x0. If you feel that you need to change the sampling frequency at any point here's a bit on how to calculate the amount of instructions you need to delay in total.

sample_period = 1/sample_frequency
.
sample_period/(number_instructions_delay_loop*5ns) = total_number_instructions_to_delay_per_period
.
Then count the amount of instructions before or after the loop and nock off that many instructions to delay. This will of course
need to be accounted for in the duty cycle, and some sampling frequencies may not offer all duty_percentages.
.
duty_percent = number_on_instruction_delay/number_off_instruction_delay
.
number_on_instruction_delay + number_off_instruction_delay = total_number_instructions_to_delay_per_period
.
->(duty_percent + 1)*total_number_instruction_to_delay_per_period = number_on_instruction_delay

Of course a few other numbers will have to be adjusted, such as the number of samples to read from memory. Because it has to read in 4 bytes of data, this will end up being:
total_number_instructions_to_delay_per_period*4+4
This way the number will reset to 0 as soon as it goes over the limit of memory to be read.

To build this example, follow the same procedure as before, and wire GPIO7 (Pin 42) (Which header?) through a speaker to ground. The output produced will be start as a 367Hz approximation and can be changed by putting a number into the terminal (67 to 66000) and pressing enter (NOTE:Text may mess it up. So, DON'T use text!). All of the sampling for 133kHz sampling is now taken care of for any frequency wave mentioned in the previous sentence.

== Highlights ==

During the project we were able to get an approximated 880Hz sine wave to play by changing a pulse width modulation duty cycle to approximate a dc voltage output, as you would with an LED dimmer. You can view this in action along with a helpful tip in the youtube video:

*[http://www.youtube.com/watch?v=6ytju0bkkiQ&feature=youtu.be PWM Demo].
*[http://www.youtube.com/watch?v=aFep70xN2j4 PWM Sine Wave Approximation Example]

The first video sounds clipped, but the second one sound very clean! Good job.

== Theory of Operation ==

In the first examples, you can see that the GPIO can be toggled on and off simply by editing locations in memory from the PRU. You simply set how long you want the LED to be on and how long you want the LED to be off, and delay the time between on and off to create the desired latency.

In the following example, the premise changes slightly. The operation of our code is simple, the PRU offers precise instruction delay of 5ns per instruction. With this we were able to create a delay of instructions that would be a sampling frequency, and in between this delay of instructions we were able to have a set amount of instructions for which the GPIO was on, and a set amount where the GPIO was off. Also, memory could be set from a C program, and then read by the PRU. This came in handy when approximating the sine wave because C offers the math.h header file that has the sin function included and can give approximate numbers to send to the PRU. The amount of delay on and off could be set dynamically every time the loop began by reading the next bit of data stored in memory, thus creating an average voltage that approximated a playable sine wave.

Refer to How the C Code Works, How the Assembly Code Works, and Building and Running Sin_Approximation for more details.

== Work Breakdown ==

DID THIS:Also include who did what.

'''Milestones'''

10/22: We should have all research done. Update documentation with every Milestone.

10/26: We should be able to show something, an example or simple implementation.

10/29: Ability to send different lengths to turn on an LEDs.

10/31: Ability to send different lengths to multiple LEDs.

11/2: We should be able to demo our overall work, possibly have some things to fix before presentation.

11/4: Finalize presentation

11/6-11/9: Presentation

'''What was done and who did it'''

Research and Documentation: Andrew, Bryan, James, Peter

Simple Implementation of a blinking LED: Andrew, Bryan, James, Peter

PWM Implementation: Andrew

Sinusoidal Approximation: James

Wiki Editing and Organization: Andrew, Bryan, James, Peter

'''Research'''

Most of our research has come from internet resources listed below:
*[http://elinux.org/Ti_AM33XX_PRUSSv2 TI PRU Resources]
*[http://blog.boxysean.com/2012/08/12/first-steps-with-the-beaglebone-pru/ Example for Running Code on the PRU]
*[http://processors.wiki.ti.com/index.php/PRU_Assembly_Instructions PRU Assembly Instructions]
*[http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader_API_Guide#prussdrv_map_prumem Initializing PRU in C]
*[http://www.ti.com/lit/ds/symlink/am3358.pdf AM335X Datasheet]

== Future Work ==

For future work there are a few interesting features that we were not able to get to due to time limit and the amount of research needed to begin with. First, we found difficulty in accessing things such as the PWM and analog in ports. These could be further explored given the documents that we have dug up, and some exploration on Google. Second, we wanted to read audio from the analog input and adjust the duty_cycle of the PWM accordingly to have approximate audio output which is the next step to what we have done here. Third, we wanted to explore interrupts on the PRU, but were unable to find enough documentation to get an example working. (The 'C' code has this comment: /* Wait for event completion from PRU */. Does it wait for the PRU?)
So, PWM, analog in, audio capabilities, and interrupts are the possible things to look into. Also, any other time critical operations can be explored further with the BeagleBone PRU because it has a delay of exactly 5ns for every instruction.

== Conclusions ==

So, if you need precise timing, or more rapid access to a certain GPIO pin, this is a route you might want to look into. There are a few suggestions listed above that might be interesting to see come out of using the PRU. However, if you do not require precisely timed events or faster access to GPIO pins, you might want to consider just using C on the main processor. Much of the information needed to access certain parts of the PRU and the hardware from the PRU is either very vague, or very difficult to dig up, and because the PRU is not widely used, it is difficult to find people that can offer information on the topic.

{{YoderFoot}}

EBC Mini Project 02

2012-11-05T17:19:52Z

Correlbn: /* Adafruit */

[[Category:ECE497 |Mini02]]
{{YoderHead}}

Pick one of the senors from the [https://www.sparkfun.com/products/11016 SparkFun Sensor Kit] or from [http://adafruit.com Adafruit] and interface it to the Bone. Create a wiki page describing how to use the sensor.

Add your name next to the sensor/display you want to use and pick it up from me.

== Sparkfun ==

{|
! Name
! Sensor
! Description
|-
| Josh Dugan
| HMC5883L - Triple-Axis Magnetometer Breakout Board
| An accurate, simple-to-use digital magnetometer with an I2C interface.
|-
| Ross Hansen
| ADXL335 - Triple-Axis Accelerometer Breakout Board
| Senses acceleration along all three axes, with a range of up to ±3g. Fully analog interface. [[Sparkfun:_ADXL335,_three-axis_accelerometer]]
ITG-3200
|-
| Alex Drane
| ADXL345 - Accelerometer Breakout Board
|
|-
| Ruffin White
| Triple-Axis Gyro Breakout Board
| Senses angular velocity along three axes of rotation. Fully digital interface with a range of up to ±2000°/s. [[Sparkfun:_ITG-3200,Triple-Axis_Gyro]]
|-
| Kevin Geisler
| [[Large Piezo Vibration Sensor - With Mass]]
| A flexible film able to sense for vibration, touch, shock, etc. When the film moves back and forth an AC wave is created, with a voltage of up to ±90.
|-
| Mark A. Yoder
| Reed Switch
| Senses magnetic fields, makes for a great non-contact switch.
|-
| Mark A. Yoder
| 0.25" Magnet Square
| Plays nicely with the reed switch. Embed the magnet into stuffed animals or inside a box to create a hidden actuator to the reed switch.
|-
| Stephen Shinn
| [[Sparkfun: 0.5" Force Sensitive Resistor|0.5" Force Sensitive Resistor]]
| A force sensing resistor with a 0.5" diameter sensing area. Great for sensing pressure (i.e. if it's being squeezed).
|-
| Tom Atnip
| [[Sparkfun:_PIR_Motion_Sensor]]
| Easy-to-use motion detector with an analog interface. Power it with 5-12VDC, and you'll be alerted of any movement.
|-
|
| Ultrasonic Rangefinder - Maxbotix LV-EZ1
| Distance sensor with both analog and RS-232 interfaces, providing sonar range information from 6 to 254 inches.
|-
|
| HIH-4030 Humidity Sensor
| A high precision humidity sensor with an analog output.
|-
| Andrew Miller
| IR Receiver Breakout Board
| An analog interfaced IR receiver, sensitive to a wide range of IR waves. Great for 'listening' to TV remotes.
|-
| James Popenhagen
| [[Mini Photocell]]
| The photocell will vary its resistance based on how much light it's exposed to. Will vary from 1kΩ in the light to 10kΩ in the dark.
|-
| Peter Ngo & Bryan Correll
| Optical Detector/Phototransistor
| An all-in-one infrared emitter and detector. Ideal for sensing black-to-white transitions or can be used to detect nearby objects.
|-
| Jesse Brannon
| BMP085 Barometric Pressure Sensor
| Low power, high precision barometric pressure sensor with I2C output.
|-
| James Popenhagen
| [[Flex Sensor]]
| As the sensor is flexed, the resistance across the sensor increases. Useful for sensing motion or positioning
|-
| Chris Good
| SoftPot
| These are very thin variable potentiometers. By pressing on various positions along the strip, you vary the resistance
|}

== Adafruit ==

{|
! Name
! Device
! Description
|-
| Matthew Moravec & Yue Zhang
| [https://www.adafruit.com/products/512 Analog 2-axis Thumb Joystick]
| Analog 2-axis Thumb Joystick with Select Button + Breakout Board
|-
|
| [https://www.adafruit.com/products/377 Rotary Encoder]
| This rotary encoder is a high quality 24-pulse encoder, with detents and a nice feel. This encoder also has a push-button built into it so you can press onto the knob to close a separate switch. One side has a 3 pin connector (ground and two coding pins) and the other side has two pins for a normally-open switch.
|-
|
| [https://www.adafruit.com/products/333 Touch screen (Nintendo DSL digitizer)]
| This resistive touch screen can be used with a stylus or fingertip and is easy to use with a microcontroller.
600 ohms across X pins, 300 ohms across Y pins
4 wire resistive display, on a 0.5mm FPC connector
|-
|Xinyu Cheng
| [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
|
|-
|Mike Junge
|[https://www.adafruit.com/products/959 Mini 8x8 LED Matrix w/I2C - Blue]
|
|-
|Xia Li
|[https://www.adafruit.com/products/870 Mini 8x8 LED Matrix w/I2C - Red]
|
|-
|
|[[Bicolor LED Square Pixel Matrix]]
| The matrices use a driver chip that does all the heavy lifting for you: They have a built in clock so they multiplex the display. They use constant-current drivers for ultra-bright, consistent color, 1/16 step display dimming, all via a simple I2C interface.
|-
|
| [https://www.adafruit.com/products/812 Green 7-segment clock display]
| These displays are multiplexed, common-cathode. What that means it that you can use a 74HC595. Sorry, I didn't order the version with i2c.
|-
| Sean Richardson
| [https://www.adafruit.com/products/306 Digital Addressable RGB LED]
| These LED strips are fun and glowy. There are 32 RGB LEDs per meter, and you can control each LED individually! We have 5 meters worth!
|-
|
|-
|Greg Larmore
| [https://www.adafruit.com/products/555 16x24 Red LED Matrix Panel]
| These LED panels take care of all the work of making a big matrix display. Each panel has six 8x8 red matrix modules, for a 16x24 matrix. The panel has a HT1632C chip on the back with does all the multiplexing work for you and has a 3-pin SPI-like serial interface to talk to it and set LEDs on or off (you cannot set the LED to be individually dimmed, as in 'grayscale'). There's a few extras as well, such as being able to change the brightness of the entire display, or blink the entire display at 1 Hz. [[Adafruit: 16x24 Red LED Matrix Panel]]
|-
|
|-
|John Lobdell
| [https://www.adafruit.com/products/377 Rotary Encoder]
|These rotary encoders rotate all the way around continuously, and are divided up into 24 'segments'. Each segment has a click-y feeling to it, and each movement clockwise or counter-clockwise causes the two switches to open and close. There is no way to know what the current 'position' is - instead you would use a microcontroller to count how many 'clicks' left or right it has been turned. If you need to detect rotational 'position' a potentiometer would be a better choice. [[Adafruit: Rotary Encoder]]
|}

{{YoderFoot}}

EBC Mini Project 02

2012-11-05T17:19:30Z

Correlbn: /* Sparkfun */

[[Category:ECE497 |Mini02]]
{{YoderHead}}

Pick one of the senors from the [https://www.sparkfun.com/products/11016 SparkFun Sensor Kit] or from [http://adafruit.com Adafruit] and interface it to the Bone. Create a wiki page describing how to use the sensor.

Add your name next to the sensor/display you want to use and pick it up from me.

== Sparkfun ==

{|
! Name
! Sensor
! Description
|-
| Josh Dugan
| HMC5883L - Triple-Axis Magnetometer Breakout Board
| An accurate, simple-to-use digital magnetometer with an I2C interface.
|-
| Ross Hansen
| ADXL335 - Triple-Axis Accelerometer Breakout Board
| Senses acceleration along all three axes, with a range of up to ±3g. Fully analog interface. [[Sparkfun:_ADXL335,_three-axis_accelerometer]]
ITG-3200
|-
| Alex Drane
| ADXL345 - Accelerometer Breakout Board
|
|-
| Ruffin White
| Triple-Axis Gyro Breakout Board
| Senses angular velocity along three axes of rotation. Fully digital interface with a range of up to ±2000°/s. [[Sparkfun:_ITG-3200,Triple-Axis_Gyro]]
|-
| Kevin Geisler
| [[Large Piezo Vibration Sensor - With Mass]]
| A flexible film able to sense for vibration, touch, shock, etc. When the film moves back and forth an AC wave is created, with a voltage of up to ±90.
|-
| Mark A. Yoder
| Reed Switch
| Senses magnetic fields, makes for a great non-contact switch.
|-
| Mark A. Yoder
| 0.25" Magnet Square
| Plays nicely with the reed switch. Embed the magnet into stuffed animals or inside a box to create a hidden actuator to the reed switch.
|-
| Stephen Shinn
| [[Sparkfun: 0.5" Force Sensitive Resistor|0.5" Force Sensitive Resistor]]
| A force sensing resistor with a 0.5" diameter sensing area. Great for sensing pressure (i.e. if it's being squeezed).
|-
| Tom Atnip
| [[Sparkfun:_PIR_Motion_Sensor]]
| Easy-to-use motion detector with an analog interface. Power it with 5-12VDC, and you'll be alerted of any movement.
|-
|
| Ultrasonic Rangefinder - Maxbotix LV-EZ1
| Distance sensor with both analog and RS-232 interfaces, providing sonar range information from 6 to 254 inches.
|-
|
| HIH-4030 Humidity Sensor
| A high precision humidity sensor with an analog output.
|-
| Andrew Miller
| IR Receiver Breakout Board
| An analog interfaced IR receiver, sensitive to a wide range of IR waves. Great for 'listening' to TV remotes.
|-
| James Popenhagen
| [[Mini Photocell]]
| The photocell will vary its resistance based on how much light it's exposed to. Will vary from 1kΩ in the light to 10kΩ in the dark.
|-
| Peter Ngo & Bryan Correll
| Optical Detector/Phototransistor
| An all-in-one infrared emitter and detector. Ideal for sensing black-to-white transitions or can be used to detect nearby objects.
|-
| Jesse Brannon
| BMP085 Barometric Pressure Sensor
| Low power, high precision barometric pressure sensor with I2C output.
|-
| James Popenhagen
| [[Flex Sensor]]
| As the sensor is flexed, the resistance across the sensor increases. Useful for sensing motion or positioning
|-
| Chris Good
| SoftPot
| These are very thin variable potentiometers. By pressing on various positions along the strip, you vary the resistance
|}

== Adafruit ==

{|
! Name
! Device
! Description
|-
| Matthew Moravec & Yue Zhang
| [https://www.adafruit.com/products/512 Analog 2-axis Thumb Joystick]
| Analog 2-axis Thumb Joystick with Select Button + Breakout Board
|-
|
| [https://www.adafruit.com/products/377 Rotary Encoder]
| This rotary encoder is a high quality 24-pulse encoder, with detents and a nice feel. This encoder also has a push-button built into it so you can press onto the knob to close a separate switch. One side has a 3 pin connector (ground and two coding pins) and the other side has two pins for a normally-open switch.
|-
|
| [https://www.adafruit.com/products/333 Touch screen (Nintendo DSL digitizer)]
| This resistive touch screen can be used with a stylus or fingertip and is easy to use with a microcontroller.
600 ohms across X pins, 300 ohms across Y pins
4 wire resistive display, on a 0.5mm FPC connector
|-
|Xinyu Cheng
| [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
|
|-
|Mike Junge
|[https://www.adafruit.com/products/959 Mini 8x8 LED Matrix w/I2C - Blue]
|
|-
|Xia Li
|[https://www.adafruit.com/products/870 Mini 8x8 LED Matrix w/I2C - Red]
|
|-
|Peter Ngo & Bryan Correll
|[[Bicolor LED Square Pixel Matrix]]
| The matrices use a driver chip that does all the heavy lifting for you: They have a built in clock so they multiplex the display. They use constant-current drivers for ultra-bright, consistent color, 1/16 step display dimming, all via a simple I2C interface.
|-
|
| [https://www.adafruit.com/products/812 Green 7-segment clock display]
| These displays are multiplexed, common-cathode. What that means it that you can use a 74HC595. Sorry, I didn't order the version with i2c.
|-
| Sean Richardson
| [https://www.adafruit.com/products/306 Digital Addressable RGB LED]
| These LED strips are fun and glowy. There are 32 RGB LEDs per meter, and you can control each LED individually! We have 5 meters worth!
|-
|
|-
|Greg Larmore
| [https://www.adafruit.com/products/555 16x24 Red LED Matrix Panel]
| These LED panels take care of all the work of making a big matrix display. Each panel has six 8x8 red matrix modules, for a 16x24 matrix. The panel has a HT1632C chip on the back with does all the multiplexing work for you and has a 3-pin SPI-like serial interface to talk to it and set LEDs on or off (you cannot set the LED to be individually dimmed, as in 'grayscale'). There's a few extras as well, such as being able to change the brightness of the entire display, or blink the entire display at 1 Hz. [[Adafruit: 16x24 Red LED Matrix Panel]]
|-
|
|-
|John Lobdell
| [https://www.adafruit.com/products/377 Rotary Encoder]
|These rotary encoders rotate all the way around continuously, and are divided up into 24 'segments'. Each segment has a click-y feeling to it, and each movement clockwise or counter-clockwise causes the two switches to open and close. There is no way to know what the current 'position' is - instead you would use a microcontroller to count how many 'clicks' left or right it has been turned. If you need to detect rotational 'position' a potentiometer would be a better choice. [[Adafruit: Rotary Encoder]]
|}

{{YoderFoot}}

ECE497 BeagleBone PRU

2012-10-16T15:57:47Z

Correlbn:

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[user:Yoder|Mark A. Yoder]], [[user:Correlbn|Bryan Correll]], [[user:Millerap|Andrew Miller]], [[user:Ngop|Peter Ngo]], [[user:Popenhjc|James Popenhagen]]

== Executive Summary ==

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

== Installation Instructions ==

Give step by step instructions on how to install your project on the SPEd2 image.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-10-16T15:56:52Z

Correlbn: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/brannojs/ brannojs]
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 Project: Zigbee|Zigbee]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
| [[Special:Contributions/Chris.good|contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/goodca/ goodca]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 Project AutoPilot | AutoPilot]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 Project AutoPilot | AutoPilot]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
|
| [[ECE497 Project: Zigbee|Zigbee]]
|
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project: Beaglebone PRU|Beaglebone PRU]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| [[ECE497 Project: Zigbee|Zigbee]]
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
| [[User:Lobdeljt | John Lobdell]]
|
| [[ECE 497 lobdeljt Project | My Beagle Project]]
| [https://github.com/jtlobdell jtlobdell]
|-
|
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

EBC Mini Project 02

2012-09-27T03:06:52Z

Correlbn: /* Adafruit */

[[Category:ECE497 |Mini02]]
{{YoderHead}}

Pick one of the senors from the [https://www.sparkfun.com/products/11016 SparkFun Sensor Kit] or from [http://adafruit.com Adafruit] and interface it to the Bone. Create a wiki page describing how to use the sensor.

Add your name next to the sensor/display you want to use and pick it up from me.

== Sparkfun ==

{|
! Name
! Sensor
! Description
|-
| Josh Dugan
| HMC5883L - Triple-Axis Magnetometer Breakout Board
| An accurate, simple-to-use digital magnetometer with an I2C interface.
|-
| Ross Hansen
| ADXL335 - Triple-Axis Accelerometer Breakout Board
| Senses acceleration along all three axes, with a range of up to ±3g. Fully analog interface. [[Sparkfun:_ADXL335,_three-axis_accelerometer]]
ITG-3200
|-
| Ruffin White
| Triple-Axis Gyro Breakout Board
| Senses angular velocity along three axes of rotation. Fully digital interface with a range of up to ±2000°/s. [[Sparkfun:_ITG-3200,Triple-Axis_Gyro]]
|-
| Kevin Geisler
| [[Large Piezo Vibration Sensor - With Mass]]
| A flexible film able to sense for vibration, touch, shock, etc. When the film moves back and forth an AC wave is created, with a voltage of up to ±90.
|-
| Mark A. Yoder
| Reed Switch
| Senses magnetic fields, makes for a great non-contact switch.
|-
| Mark A. Yoder
| 0.25" Magnet Square
| Plays nicely with the reed switch. Embed the magnet into stuffed animals or inside a box to create a hidden actuator to the reed switch.
|-
| Stephen Shinn
| [[Sparkfun: 0.5" Force Sensitive Resistor|0.5" Force Sensitive Resistor]]
| A force sensing resistor with a 0.5" diameter sensing area. Great for sensing pressure (i.e. if it's being squeezed).
|-
| Tom Atnip
| [[Sparkfun:_PIR_Motion_Sensor]]
| Easy-to-use motion detector with an analog interface. Power it with 5-12VDC, and you'll be alerted of any movement.
|-
|
| Ultrasonic Rangefinder - Maxbotix LV-EZ1
| Distance sensor with both analog and RS-232 interfaces, providing sonar range information from 6 to 254 inches.
|-
|
| HIH-4030 Humidity Sensor
| A high precision humidity sensor with an analog output.
|-
| Andrew Miller
| IR Receiver Breakout Board
| An analog interfaced IR receiver, sensitive to a wide range of IR waves. Great for 'listening' to TV remotes.
|-
| James Popenhagen
| [[Mini Photocell]]
| The photocell will vary its resistance based on how much light it's exposed to. Will vary from 1kΩ in the light to 10kΩ in the dark.
|-
|
| Optical Detector/Phototransistor
| An all-in-one infrared emitter and detector. Ideal for sensing black-to-white transitions or can be used to detect nearby objects.
|-
| Jesse Brannon
| BMP085 Barometric Pressure Sensor
| Low power, high precision barometric pressure sensor with I2C output.
|-
| James Popenhagen
| [[Flex Sensor]]
| As the sensor is flexed, the resistance across the sensor increases. Useful for sensing motion or positioning
|-
| Chris Good
| SoftPot
| These are very thin variable potentiometers. By pressing on various positions along the strip, you vary the resistance
|}

== Adafruit ==

{|
! Name
! Device
! Description
|-
| Matthew Moravec & Yue Zhang
| [https://www.adafruit.com/products/512 Analog 2-axis Thumb Joystick]
| Analog 2-axis Thumb Joystick with Select Button + Breakout Board
|-
|
| [https://www.adafruit.com/products/377 Rotary Encoder]
| This rotary encoder is a high quality 24-pulse encoder, with detents and a nice feel. This encoder also has a push-button built into it so you can press onto the knob to close a separate switch. One side has a 3 pin connector (ground and two coding pins) and the other side has two pins for a normally-open switch.
|-
|
| [https://www.adafruit.com/products/333 Touch screen (Nintendo DSL digitizer)]
| This resistive touch screen can be used with a stylus or fingertip and is easy to use with a microcontroller.
600 ohms across X pins, 300 ohms across Y pins
4 wire resistive display, on a 0.5mm FPC connector
|-
|Xinyu Cheng
| [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
|
|-
|Mike Junge & Peter Ngo & Bryan Correll
|[https://www.adafruit.com/products/959 Mini 8x8 LED Matrix w/I2C - Blue]
|
|-
|Xia Li
|[https://www.adafruit.com/products/870 Mini 8x8 LED Matrix w/I2C - Red]
|
|-
|Alex Drane
|[[Bicolor LED Square Pixel Matrix]]
| The matrices use a driver chip that does all the heavy lifting for you: They have a built in clock so they multiplex the display. They use constant-current drivers for ultra-bright, consistent color, 1/16 step display dimming, all via a simple I2C interface.
|-
|
| [https://www.adafruit.com/products/812 Green 7-segment clock display]
| These displays are multiplexed, common-cathode. What that means it that you can use a 74HC595. Sorry, I didn't order the version with i2c.
|-
| Sean Richardson
| [https://www.adafruit.com/products/306 Digital Addressable RGB LED]
| These LED strips are fun and glowy. There are 32 RGB LEDs per meter, and you can control each LED individually! We have 5 meters worth!
|-
|
|-
|Greg Larmore
| [https://www.adafruit.com/products/555 16x24 Red LED Matrix Panel]
| These LED panels take care of all the work of making a big matrix display. Each panel has six 8x8 red matrix modules, for a 16x24 matrix. The panel has a HT1632C chip on the back with does all the multiplexing work for you and has a 3-pin SPI-like serial interface to talk to it and set LEDs on or off (you cannot set the LED to be individually dimmed, as in 'grayscale'). There's a few extras as well, such as being able to change the brightness of the entire display, or blink the entire display at 1 Hz. [[Adafruit: 16x24 Red LED Matrix Panel]]
|-
|
|-
|John Lobdell
| [https://www.adafruit.com/products/377 Rotary Encoder]
|These rotary encoders rotate all the way around continuously, and are divided up into 24 'segments'. Each segment has a click-y feeling to it, and each movement clockwise or counter-clockwise causes the two switches to open and close. There is no way to know what the current 'position' is - instead you would use a microcontroller to count how many 'clicks' left or right it has been turned. If you need to detect rotational 'position' a potentiometer would be a better choice.
|}

{{YoderFoot}}

ECE497 Correlbn Project

2012-09-10T15:25:57Z

Correlbn: Created page with "Project {{YoderHead}} Team members: Mark A. Yoder, (List all the team members here with link to their eLinux User page. Use my format. == E..."

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[user:Yoder|Mark A. Yoder]], (List all the team members here with link to their eLinux User page. Use my format.

== Executive Summary ==

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

== Installation Instructions ==

Give step by step instructions on how to install your project on the SPEd2 image.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-09-10T15:25:20Z

Correlbn: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[ECE497 Correlbn Project | My Beagle Project]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 duganje Project | My Beagle Project]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 hansenrl Project | My Beagle Project]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 jungeml Project | My Beagle Project]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
|
| [[ECE497 mmoravec Project | My Beagle Project]]
|
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project | My Beagle Project]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| Project TBD
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[ECE497 popenhjc Project | My Beagle Project]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-09-10T15:06:23Z

Correlbn: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[ECE497 Correlbn Project | My Beagle Project]]
| [https://github.com/correlbn/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 duganje Project | My Beagle Project]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 hansenrl Project | My Beagle Project]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 jungeml Project | My Beagle Project]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
|
| [[ECE497 mmoravec Project | My Beagle Project]]
|
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project | My Beagle Project]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| Project TBD
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[ECE497 popenhjc Project | My Beagle Project]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

User:Correlbn

2012-09-10T15:02:40Z

Correlbn:

[[Category:ECE497]]

ECE497 Contributions and Project Status

2012-09-10T15:01:48Z

Correlbn: /* Contributions */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
|
| [[ECE497 Project Template | My Beagle Project]]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 duganje Project | My Beagle Project]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 hansenrl Project | My Beagle Project]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 jungeml Project | My Beagle Project]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
|
| [[ECE497 mmoravec Project | My Beagle Project]]
|
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project | My Beagle Project]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| Project TBD
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[ECE497 popenhjc Project | My Beagle Project]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

User:Correlbn

2012-09-10T14:58:11Z

Correlbn: Created page with "Category: ECE497"

Category: ECE497

ECE497 Contributions and Project Status

2012-09-10T14:32:28Z

Correlbn: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
|
| [[ECE497 Project Template | My Beagle Project]]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 duganje Project | My Beagle Project]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
|
| [[ECE497 Project Template | My Beagle Project]]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 hansenrl Project | My Beagle Project]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 jungeml Project | My Beagle Project]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
|
| [[ECE497 mmoravec Project | My Beagle Project]]
|
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project | My Beagle Project]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| Project TBD
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[ECE497 popenhjc Project | My Beagle Project]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}