Changes

Jump to: navigation, search
Project Contributor(s)
== (Changed to Running F17 on Beaglebone) Programming GPIO on Fedora ==
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
Resources: Chris Tyler (ctyler), Peter Robinson (pbrobinson)
 
 
Update to
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
IRC: Jie_Q
'''Luis Francisco Fuentes'''<br />
Wiki Page: [[User: Luis Francisco Fuentes]]<br />
IRC: Luis
NOTE: only Project Leader(s) should add names here. You should not add your own name to the Contributor list. -->
 
Omarr Khattab -- Give me config files of Fedora 17 arm.
 
Max -- help me with change the mmc_root permission.
 
Gloria Ip -- help me with some sources link and reference info.
== Project Details ==
<!-- 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 Plan == Nov 10 Update to them. -->:
Step (1: Look for libraries for ) 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 GPIO 2nd partition, and I2C interfacesuntar a rootfs tarball onto that partition.
'''Find libraries related (2) If that works, try updating the kernel on partition 1 to GIPOthe F17 OMAP kernel. Currently, we have The kernel is the source package for 'uImage' file in the Raspberry PI GPIOfirst partion.
'''Get (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 hardware BeagleBoard (Pandaboard devicestep 1 above)could be used as your 0.1 release.
Step 2: Test the libraries with panda board.
Step 3: Write final documentation.
== Project Plan ==
Tracking mechanism (bugzilla, trac, github, ...):
Key contactsBelow it old project plan:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<s><!-- Add links 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 any mentors or key participants in the communitythem. -->
Goals for each release Oct 6, 2012. Group Meeting.<br /><br />We discussed about which hardware and plans for reaching those goals:<!-- Note: each contributor is expected interface we are going to have unique goalscontribute. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of And the state of the other students' workfinal decision is we are gonna use Pandaboard device. For example, under the umbrella of one project title, one student may I will work on packaging a piece of software and another may work on documentationthe GPIO interface, or one may work on solving one bug and another on solving another bug, but two students must not Luis will work on the same bug or depend on I2C interface. One of our member drop the other students' work in order to be able to complete their own project. --><br /><br />0course, so, that is all for now.0 Plan<br /><br />
We are going to use we did some research on the Pandaboard device library and drivers, here is the google doc link for sharing the I2Cinformation within group member: https:/GPIO/SPI interfacesdocs.google.<br com/document/d/><br 1TJQb7bEK91TNs3f2jqkOiQU3_ro8Z7BhKEbdtaCOoxc/>edit
Luis Fuentes : Package appropriate libraries We are going to use the Beaglebone/Beagleboard device for I2C the GPIO interfaces.<br />Jiecheng Qiu : Package appropriate libraries for GPIO <br />
Luis Fuentes : Package appropriate libraries for Beagleboard GPIO <br />
Jiecheng Qiu : Package appropriate libraries for Beaglebone GPIO <br />
*0<br /><br />Oct 15, 2012 Update Project Home Page.1 Research the library of GPIO<br /><br /I2C and package it on Pandaboard with Fedora System>
*0Today we update the Project Detail, Project Plan, and Blogs.2 Test it We will continue do some research on library, and make try to package it donesoon. And we will ask for loan some hardware.
Tracking mechanism (bugzilla, trac, github, ...):
*0Key contacts:<!-- Add links to any mentors or key participants in the community.3 Finalize the package release and finish the documentation-->
Goals for each release and plans for reaching those goals:
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
<br /><br />
0.1 release an initial version of our package <br /><br />
0.2 release a final version and get it into the Fedora package review process <br /><br />
0.3 the package has gone through the final release process and is available in Fedora <br /><br /></s>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
== Communication ==
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 ===
Jiecheng Qiu's Blog: http://jcqiu.wordpress.com

Navigation menu