Raspberry Pi vs BeagleBone Black

For those projects that an Uno can't quite reach. I have written a short comparison of these two boards.

Server not found


There is something strange going on with my DNS. Can anyone confirm this page is or isn't there?

Thanks, Si.

Works fine for me.

And thanks for sharing, by the way. I recently though about starting to explore theses platforms for some of my future projects.

Works for me :slight_smile:
Good reviews BTW
might be tempted to invest!

There is something strange going on with my DNS. Can anyone confirm this page is or isn't there?

Thanks, Si.

Its probably just your ISP trying to filter the geek hardware pron.

Thanks for the review, even though I already have a stack of Pi's i'm not using, I have been looking into the beaglebone black just for the sheer amount of IO.

EDIT: I'm not sure if you have seen it or not yet, but the new NOOBS installer for the raspberry Pi makes installing the OS very user friendly. You just drop the files on any SD card (no need to make an image or find out how to load it on the SD card).

EDIT EDIT: Theres something amusing about driving my 21" LCD monitor with a device that draws 320mA, considering its usually hooked up to a PC with a 1000W PSU.

Use Raspberry Pi. It's not a matter of hardware but community and online resources. I'd use Arduino over PIC (have to learn it first) for the same reasons. Beagle board forum sucks (really really sucks). They should do a real forum instead of some strange version of google group etc. Raspberry Pi's forum is much better although not as good as Arduino forum. You ask questions and you can get some answers back. Installing raspberry pi version of debian (raspbian) is very much GUI all the way. I did that before I learned how to use basic linux commands.

I would also caution against using GPIOs on either RPI or BBB. You could end up with an expensive coaster. Plus, there is little portability once you start to rely on these GPIOs. I would slave an arduino over serial port for the time-sensitive or not sensor jobs so that I can easily move among different linux boxes and single board computers without making any change of my code. I'm pretty sure more single board linux computers will be coming soon and project code portability will be most important to any of us with more than a few projects on our belts.

It's not a matter of hardware but community and online resources.

It is, and it takes time to get that. It also requires that (in the case of BeagleBone Black) the professional electronic engineers who start the project, let go as soon as they feasibly can and trust the enthusiasts take over. I think BBB is getting to that point. Once its stable enough they need to stop messing with it and let the community start churning out the equivalent of libraries and shields. Not to mention books and all the fantastic online project write-ups.

I also agree that there is nothing quite like this forum. A couple of years ago I used to contribute a lot. I occasionally try now, but invariably when I come to a question I could help someone with 3 people have already answered it well!


Thanks for these insights, liudr. About the GPIOs, what do you mean by low portability? Pin affectation is difficult to change?

If you use the pins on rpi, you need non-standard library support to do so. Then the code that calls the library usually need to be changed when you port it to BBB. If you instead use arduino, code is the same. No need to call any non-standard library using serial port. I porgeam on my debian box and my cnde can be copy and pasted to RPI and works just fine. If I used RPI GPUO, I will have to set up cross compiler and remote debug.