The BeagleBone Black is a low-cost, high-performance embedded platform for hobbyists and other uses. It is based upon a TI AM335x 1GHz ARM® Cortex-A8. Features (from the product website) include:
Processor: AM335x 1GHz ARM® Cortex-A8
Connectivity
The board comes pre-loaded with and Ångström Linux distirubtion and many other options can be considered for development and operating the device. It is a very powerful device with a large number of peripherals built in making it well-suited for a number of soft real-time applications.
To support demanding hard-real time constraints or to off load processes from the main CPU, the processor chip includes two programmable real-time (PRU) cores. These are reasonably high speed, 32-bit RISC cores where every instruction takes a deterministic 5 ns to complete. The devices have dedicated peripherals, access to the main system's peripherals, and ability to communicate with the main processor through interrupts, shared memory or DMA.
These devices can be used to create programmable real-time peripherals and subsystems. The downside is that they are specialized and need low-level (assembly) programming (at least until someone develops a compiler) and configuration.
The goal is to experiment with the PRU devices and modify a small program to send a burst of bits at a given rate. The ARM processor should query the user for a 32-bit hexadecimal number and transmit it out serially on a GPIO pin LSB first. The period of transmission for each bit in microseconds should also be sent by the ARM to the PRU. A small program based on the TI examples has been provided to show two methods of sharing memory with the PRU and ARM as well as for using the PRU timer (you can also rely on the 5 ns instruction timing but then become more sensitive to code changes).
Not the TI examples are not production quality code but samples for demonstration.
Familiarize yourself with the sample code and with the PRU assembly language. We will not be writing much code so you do not need to become expert but should be able to read the sample program and make modest changes.
Plan modifications to accomplish the goals above and prepare your code for the lab.
As well as you demonstration you should submit a brief lab report. For the lab report submit your code, documenting the changes, and the answers to the questions above using the prism submit command.