3 ms·
The BeagleBone suffers from the same exact issues the Raspberry Pi does, namely that there are only two real ways to run the peripherals: The horribly, horribly
by fake-name 10y ago
The BeagleBone suffers from the same exact issues the Raspberry Pi does, namely that there are only two real ways to run the peripherals: The horribly, horribly slow filesystem interface, and "Open /dev/mem RW! YOLO! Run Apache as root for your crappy internet of shit project!".
There are basically no actual sane drivers for doing anything fast.
At one point, I spent a while looking at writing my own driver, but apparently I'm not a good enough hacker to write kernel drivers.
- snops 10y agoExcept the BeagleBone has PRUs, which are two 32 bit microcontrollers on the same silicon that can also access the GPIO peripherals. They share memory with the main processor but can be exclusively dedicated to your needs, and so peripheral access can be very fast indeed. Here is someone who has used them to turn the BeagleBone into a 100MHz Logic Analyser: http://theembeddedkitchen.net/beaglelogic-building-a-logic-analyzer-with-the-prus-part-1/449 http://theembeddedkitchen.net/beaglelogic-building-a-logic-a...
- amboar 10y agoIf your running relatively recent kernels on the board there's now a character device interface for gpios: https://patchwork.ozlabs.org/patch/580307/ https://patchwork.ozlabs.org/patch/580307/
- bsder 10y agoDid you try this reference: https://groups.google.com/forum/#!topic/beagleboard/dyuax5415dc https://groups.google.com/forum/#!topic/beagleboard/dyuax541... I found it quite invaluable for understanding how to write a kernel driver for things like the RaspberryPi or the BeagleBone. The fact that so many things about embedded hardware are so poorly documented is a real problem. Unfortunately, there just aren't that many of us hacking these at a kernel level.