Difference between revisions of "ECE497 Project DotRun"

From eLinux.org
Jump to: navigation, search
Line 57: Line 57:
 
== User Instructions ==
 
== 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.
+
Use the two buttons to control the dot run up or down. If the dot hit the bars, game over. The longer you survive, the higher score you get.
 +
 
 
== Highlights ==
 
== Highlights ==
  

Revision as of 18:50, 18 November 2013

thumb‎ Embedded Linux Class by Mark A. Yoder


Team members: Yang Liu, Yuxuan Zeng

Grading Template

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

00 Executive Summary
00 Installation Instructions 
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments: I'm looking forward to seeing this.

Score:  10/100

(Inline Comment)

Executive Summary

We are building a game on BBB with a 16*24 LED matrix and two buttons. There is a dot in the central of matrix and bars coming from right or left side of matrix. You can make the dot to move up and down to dodge the bars by the buttons.

Give two sentences telling what works. The framework of software has been done.

Give two sentences telling what isn't working. The LED matrix circuit hasn't been built up yet.

End with a two sentence conclusion.

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

Packaging

If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.

Installation Instructions

Give step by step instructions on how to install your project.

  • Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
  • Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
  • Include a Makefile for you code.
  • 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

Use the two buttons to control the dot run up or down. If the dot hit the bars, game over. The longer you survive, the higher score you get.

Highlights

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

Include a 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.

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.




thumb‎ Embedded Linux Class by Mark A. Yoder