Difference between revisions of "BeagleBone/PrussDemoSubmission"
(→Design) |
m |
||
(9 intermediate revisions by 2 users not shown) | |||
Line 5: | Line 5: | ||
This proposal will have the following: | This proposal will have the following: | ||
− | * Having PRU control everything once loaded. | + | * Having PRU control everything once loaded |
− | * Userspace can also talk to the | + | ** Multiple PRU cores utilized. |
− | * | + | *** 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. | |
− | + | * Explaining why SPI transfers, and GPIO bit banging doesn't work with applications like these. | |
− | |||
− | |||
− | |||
− | |||
== Multimedia == | == Multimedia == | ||
− | + | [[File:Nixie_Breadboard.jpg|center|thumb|450px|Breadboard PRUS Demo Picture]] | |
− | + | [[Category:BeagleBone]] | |
− | |||
− |
Latest revision as of 03:14, 28 November 2019
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.