The official repository for the GSoC-2016 project - BeagleScope. An introductory video to the project - video.
Note - The developed software has been tested on kernel version 4.4.12-ti-r31 and is expected to work on kernel version later than and equal to 4.4.12-ti-r31.
Poject has examples to explain use of remoteproc drivers and RPMSG framework for the PRUs. :https://github.com/ZeekHuge/BeagleScope/tree/port_to_4.4.12-ti-r31%2B/examples
(Just a side note - You'll probably like https://www.zeekhuge.me)
The project, as the part of GSoC-2016, aims to provide with software support to deploy the PRUSS subsystem on AM33xx processors, as a fast and parallel data acquisition units. The project is a good example of using generic PRU-remoteproc drivers and the RPMSG framework for PRUs. The PRU cores being highly optimized for I/O operations and single cycle instruction execution (mostly), are an appropriate choice for bit-banging and offloading tasks. BeagleScope uses this very feature of PRUs to offload the parallel data transactions and fast data acquisition. This project provides:
- Kernel support : Kernel support will be in the form of an offload subsystem and a kernel module that will expose PRUs as 'parallel I/O bus'. The subsystem would manage all the transactions of the I/O unit, while the parallel bus unit will manage communication with the PRU core.
- Firmware : The firmware will be the code for PRUs. The firmware would manage the communication on the PRU side and all the data I/O that PRU need to do.
The overall software stack would allow developers to use PRUs for many cool applications. One of such applications is an Oscilloscope. This can be achieved using a fast ADC along with the developed software. This project will also try to develop a 20MHz oscilloscope as a test for the developed code.
This is the main branch for now. In kernel version 4.4.12-ti-r31, the RPMsg framework used ARM INTC in place of Mailboxes to generate kicks from, and to PRUs. This was a significant change and the code needed to be modified to work with this new RPMsg framework. This branch has the code that works with kernel later than 4.4.12-ti-r31. To get examples for older version, checkout the master branch.
-
The direcotry contains the documents and notes that have been used or created along the main development process.
-
The directory contains all the kernel linux related code for the main project. It contains following driver source
- parallel_interface
- pi-bus
- beaglescope_driver
-
The directory contains the source for the device tree overlays that need to be loaded for the software stack to work correctly.
-
Directory that contains the examples that have been developed while learning PRU programming.
-
The directory contains the PRU firmware that needs to be compiled and installed to booted onto the PRUs to serve as a parallel interfacing bus.
-
Clone this repo.
$ git clone https://github.com/ZeekHuge/BeagleScope.git -
Install linux header files
$ suod apt-get install linux-headers-$(uname -r) -
Enter into BeagleScope directory
$ cd BeagleScope-
To compile firmwae, enter into 'firmware' directory
$ cd firmware-
To compile the firmware
$ make -
To boot the PRUs with this firmware
$ make install
-
-
To compiel drivers, enter into the 'driver' directory
$ cd driver-
To compile the drivers
$ make -
To load the drivers
$ make load
-
-
To compile the device tree overlay, enter into the 'dtc' directory
$ cd dtc-
To compile the dts
$ dtc -O dtb /lib/firmware/PI-TEST-00A0.dtbo -b 0 -@ PI-TEST-00A0.dts -
To overlay the dts once its compiled '$ echo PI-TEST > /sys/devices/platform/bone_capemgr/slots'
-
-
If you want to cross compile the source, rather than compiling it on the board itself, most of the things remain same and you can use the 'Kernel Development' section of this post for the setup part.
To use a release you will have to compile its source.
- Release v0.1
-
Clone this repo.
$ git clone https://github.com/ZeekHuge/BeagleScope.git -
Enter into the
BeagleScopedirectory.$ cd BeagleScope -
Create a new branch using tag v0.1.
$ git checkout v0.1 -b use_branch -
Ignore the README of that branch and compile the source using following make targets.
-
To compile firmware on the beaglebone black/green itself:
$ cd firmware$ make- To compile the firmware.$ make install- To compile as well as install the firmware.
-
To comiple the driver on the beaglebone black/green itslef:
$ cd driver$ make- To compile the driver.$ make load- To compile as well as load the driver.
-
-
If you want to cross compile the source, rather than compiling it on the board itself, most of the things remain same and you can use the 'Kernel Development' section of this post for the setup part.
See the Quickstart to get started quickly and contribute to the project.
The kernel code is released under the GPLv2 license.