Difference between revisions of "ECE434 Project - BBIO in Python Project"

From eLinux.org
Jump to: navigation, search
(Work Breakdown)
m (Work Breakdown)
Line 74: Line 74:
 
== Work Breakdown ==
 
== Work Breakdown ==
  
Joshua Key and Eric Morse did pair-programming and worked the entire project and all modules together.
+
Joshua Key and Eric Morse did pair-programming.  We worked the entire project and all modules together.
 
We completed all GPIO functionality of GPIOD, including event detection.
 
We completed all GPIO functionality of GPIOD, including event detection.
 
We completed all UART functionality of GPIOD.
 
We completed all UART functionality of GPIOD.

Revision as of 14:08, 12 November 2020

thumb‎ Embedded Linux Class by Mark A. Yoder


Team members: Eric Morse Joshua Key

Grading Template

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

09 Executive Summary
09 Packaging
09 Installation Instructions 
09 User Instructions
09 Highlights
09 Theory of Operation
09 Work Breakdown
09 Future Work/Conclusions
09 Hackster.io
09 Demo/Poster
00 Late
Comments: Have a good day.

Score:  90/100

(Inline Comment)

Executive Summary

Picture that summarizes the project.

BBIO are a group of library files for GPIOD that are written in C that uses Python wrappers to run it in Python. Our project is to rewrite the Python to be fully in Python rather than using wrappers.

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.

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 your code if using C.
  • Include any additional packages installed via apt. Include install.sh and setup.sh files.
  • 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.

Consider making it autostart for full credit.

Highlights

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

Include a YouTube demo the audio description.

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

Joshua Key and Eric Morse did pair-programming. We worked the entire project and all modules together. We completed all GPIO functionality of GPIOD, including event detection. We completed all UART functionality of GPIOD. We also completed all PinMux and ADC (Analog to Digital Conversion) of GPIOD.

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