Difference between revisions of "(Changed to Running F17 on Beaglebone) Programming GPIO on Fedora"
Jiecheng Qiu (talk | contribs) |
(→Project Details) |
||
Line 39: | Line 39: | ||
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. --> | <!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. --> | ||
+ | |||
+ | |||
+ | Step 1: Look for libraries for the GPIO and I2C interfaces. | ||
+ | |||
+ | |||
+ | |||
+ | * Find libraries related to GIPO. Currently, we have the source package for the Raspberry PI GPIO. | ||
+ | |||
+ | * Get the hardware (Pandaboard device) | ||
+ | |||
+ | |||
+ | |||
+ | Step 2: Test the libraries with panda board. | ||
+ | |||
+ | |||
+ | |||
+ | Step 3: Write final documentation. | ||
== Project Plan == | == Project Plan == |
Revision as of 11:17, 15 October 2012
Contents
Programming GPIO on Fedora
Project Description
A guide and some simple projects that run on different boards on Fedora.
Package appropriate libraries and provide instructions on interfacing devices to the BeagleBoard/BeagleBone and PandaBoard devices using the GPIO/SPI/I2C interfaces.
Expected outcome: appropriate libraries for GPIO/SPI/I2C support will be present in Fedora, and documentation page will be available outlining how to use these features.
Skills required: packaging, testing, writing
Maximum number of participants: 2 (one per board)
Resources: Chris Tyler (ctyler), Peter Robinson (pbrobinson)
== Project Leader(s) ==
Jiecheng Qiu
Wiki Page: User: Jiecheng Qiu
IRC: Jie_Q
Luis Francisco Fuentes
Wiki Page: User: Luis Francisco Fuentes
IRC: Luis
Project Contributor(s)
Project Details
Step 1: Look for libraries for the GPIO and I2C interfaces.
* Find libraries related to GIPO. Currently, we have the source package for the Raspberry PI GPIO.
* Get the hardware (Pandaboard device)
Step 2: Test the libraries with panda board.
Step 3: Write final documentation.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
Goals for each release and plans for reaching those goals:
0.0 Plan
We are going to use the pandaboard device for the I2C/GPIO/SPI interfaces.
Luis Fuentes : Package appropriate libraries for I2C
Jiecheng Qiu : Package appropriate libraries for GPIO
- 0.1
- 0.2
- 0.3
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Here is a page that I've recently started writing about GPIO/Serial/I2C/SPI on the Pandaboard: http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Interfacing
This is an unfinished project started by a CDOT research assistant for interfacing a motion sensor to a Pandaboard: http://zenit.senecac.on.ca/wiki/index.php/Motion_Sensor_Interfacing_for_Panda_Board_based_Dash_Board_System
From Chris Tyler
Source Code Control
Blogs
Seneca Particpants
Non-Seneca Participants
Planets
Project News
==