Difference between revisions of "(Changed to Running F17 on Beaglebone) Programming GPIO on Fedora"
m (moved Programming GPIO on Fedora to (Changed to Running F17 on Beaglebone) Programming GPIO on Fedora)
Revision as of 14:37, 17 November 2012
- 1 (Changed to Running F17 on Beaglebone) Programming GPIO on Fedora
- 2 Project Description
- 3 Project Contributor(s)
- 4 Project Details
- 5 Project Plan
- 6 Communication
- 7 Project News
(Changed to Running F17 on Beaglebone) Programming GPIO on Fedora
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) ==
Wiki Page: User: Jiecheng Qiu
Nov 10 Update to:
(1) Try to get F17 running by leaving partition 1 untouched (the boot files) and replace partition 2 with the F17 userspace ("rootfs"). The easiest way to do this is probably to mount an Angstrom card on a PC, erase the files on the 2nd partition, and untar a rootfs tarball onto that partition.
(2) If that works, try updating the kernel on partition 1 to the F17 OMAP kernel. The kernel is the 'uImage' file in the first partion.
(3) If that works, then try to create a full beaglebone image from the F7 components. (Let me know if you get to this step).
You can ask for help on any of these in #fedora-arm. Please keep be posted on how this goes. Based on what you find out, we can set up image creation for BeagleBone in Fedora-ARM. Getting the F17 userspace running on the BeagleBoard (step 1 above) could be used as your 0.1 release.
Below it old project plan:
Oct 6, 2012. Group Meeting.
We discussed about which hardware and interface we are going to contribute. And the final decision is we are gonna use Pandaboard device. I will work on the GPIO interface, and Luis will work on the I2C interface. One of our member drop the course, so, that is all for now.
we did some research on the library and drivers, here is the google doc link for sharing the information within group member: https://docs.google.com/document/d/1TJQb7bEK91TNs3f2jqkOiQU3_ro8Z7BhKEbdtaCOoxc/edit
We are going to use the Beaglebone/Beagleboard device for the GPIO interfaces.
Luis Fuentes : Package appropriate libraries for Beagleboard GPIO
Jiecheng Qiu : Package appropriate libraries for Beaglebone GPIO
Oct 15, 2012 Update Project Home Page.
Today we update the Project Detail, Project Plan, and Blogs. We will continue do some research on library, and try to package it soon. And we will ask for loan some hardware.
Tracking mechanism (bugzilla, trac, github, ...):
Goals for each release and plans for reaching those goals:
0.1 release an initial version of our package
0.2 release a final version and get it into the Fedora package review process
0.3 the package has gone through the final release process and is available in Fedora
Upsteam Wiki and Web
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
Information from Chris Tyler
Source Code Control
Jiecheng Qiu's Blog: http://jcqiu.wordpress.com