Difference between revisions of "BeagleBone/PrussDemoSubmission"
(→Design) |
(→Design) |
||
| Line 9: | Line 9: | ||
*** Example will have be one driving the display and another incrementing the clock (in seconds). | *** Example will have be one driving the display and another incrementing the clock (in seconds). | ||
* Userspace can also talk to the PRUSS to update data in almost real time. | * Userspace can also talk to the PRUSS to update data in almost real time. | ||
| − | * Explaining why SPI transfers, GPIO bit banging doesn't work with applications like these. | + | * Explaining why SPI transfers, and GPIO bit banging doesn't work with applications like these. |
== Software == | == Software == | ||
Revision as of 22:38, 22 December 2012
Contents
Design
Using the PRUSS functionality of AM335x core for driving an vacuum fluorescent display using a shift register in realtime.
This proposal will have the following:
- Having PRU control everything once loaded
- Multiple PRU cores utilized.
- Example will have be one driving the display and another incrementing the clock (in seconds).
- Multiple PRU cores utilized.
- Userspace can also talk to the PRUSS to update data in almost real time.
- Explaining why SPI transfers, and GPIO bit banging doesn't work with applications like these.
Software
All PRU source is available on GitHub[1]
Currently the userspace utility code exists but final demo will have the clock being ran completely from PRUSS and not touching outside of it at all.
Multimedia
- Videos
- Beaglebone PRUSS Demo
