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, [] or [ 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 ==
== Project Plan == 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:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<s><!-- 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. -->
Oct 6, 2012. Group Meeting.<br /><br />
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 we did some research on the library and drivers, here is the google doc link for sharing the information within group member:
We are going to use the Beaglebone/Beagleboard device for the GPIO interfaces.<br /><br />
Luis Fuentes : Package appropriate libraries for Beagleboard GPIO <br />
Jiecheng Qiu : Package appropriate libraries for Beaglebone GPIO <br />
<br /><br />
Oct 15, 2012 Update Project Home Page.<br /><br />
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.
== Project Plan ==
Tracking mechanism (bugzilla, trac, github, ...):
<!-- 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.0 Plan<br /><br />
We are going to use the Pandaboard device for the I2C/GPIO/SPI interfaces.<br /><br />
Luis Fuentes : Package appropriate libraries for I2C <br />
Jiecheng Qiu : Package appropriate libraries for GPIO <br />
* 0.1 Research the library of GPIO/I2C and package it on Pandaboard with Fedora System<br /><br />
* 0.2 Test it and make it done<br /><br />
* 0.3 Finalize the package release and finish the documentation<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:
From Chris Tyler
=== Source Code Control ===
=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
Jiecheng Qiu's Blog:
Luis Fuentes:

Navigation menu