BeagleBone Black: A 1-GHz computer for $45
eetimes.com
eetimes.com
Something that sets these apart from the Raspberry Pi are that they full of easy access I/O, and two the Cloud9 IDE.
It is insanely fun to write javascript code in a browser talking to this thing wirelessly and have it do stuff. For me who likes to do mobile robots this is the really really great. I've got one of the old Rovio telepresence [1] things (its a mobile base with a Web cam and a WiFi link) and this board is going to be its new brain. The angstrom distro on it is very similar to the distro that the Chumby came with only a bit more stuff (Python, yay!).
The HDMI output is ok (its not 1080p so don't even think you're going to do XMBC on this thing) but nothing to write home about.
One USB port so get a hub, but on the plus side you can provide you own 5V power supply and that means you don't need a powered hub (unless you're trying to run high power peripherals). The Logitech Unifying receiver works well if you want to add a keyboard and mouse in one plug. (Now if that Unifying Reciever did WiFi it would kick butt)
All in all I think its a really good board. Nice mix of features. It will put pricing pressure on the Arduino Due I suspect.
[1] http://www.amazon.com/WowWee-Rovio-Enabled-Robotic-WebCam/dp...
never really understood the appeal of the arduino interface or cloud9. Well, for the arduino i can at least try to explain that, same with android, there are so many bad tutorials based on copy/past and boasting those IDE, that lots and lots of people start already thinking that is their only option.
No need for the negativity, can't blame those guys for wanting to get a larger userbase by making things easy. In the end the larger volume/bigger community is beneficial to everyone.
Once you get someone past the basics and into the 'advanced' mode setting them up with ssh, vim, and screen is a great way to be productive on a linux machine.
[1] Putty in this case being the terminal emulator for PC's which can also talk to serial ports.
I'm hoping that BBB's (3B's?) are going to take their place in the fall. They seem much more suited to tinkering than raspis. A very exciting platform!
I originally was attempting to use an MK802 android stick running ubuntu and interfacing it with an Arduino Micro.
However, for $45, it saves much time and "just works".
Also, like you said, it cannot do 1080p, so if you want that for XBMC get a Pi, but for a robot, this, to me, seems ideal.
1. Looks like it's been out for a while. If you were getting a similar thing today, would you stick with it or go for something else [1]?
2. When you drop the beaglebone into the Rovio, would you actually be replacing its OEM controller, or just interacting with it over WiFi?
[1] http://www.amazon.com/Rover-App-Controlled-Tank-Night-Vision...
The big hold-up is lack of access to (or maybe pure lack of) encoders on the wheels (we were using the wifi/web interface). It's impossible to move by dead reckoning. This was actually part of our class, to teach us how bad dead reckoning is and then we moved on to CV for tracking and control.
How so?
I thought RasPi has plenty of I/O, but I'm not familiar with BB.
Minor quibble: The lack of analog sound output. It shows that their mindset was not entirely focused on the robotics / DIY genre, but more on the miniature computer thing. You don't do sound output on a robot or controller from HDMI.
There are so many awesome kits coming down the pipeline:
http://www.kickstarter.com/projects/1106670630/mojo-digital-...
http://www.kickstarter.com/projects/adapteva/parallella-a-su...
- The default OS version had some issues that I was not able to ssh into the board. Once I downloaded and loaded the latest version available on the site, I was able to ssh as root.
- I was not able to connect serially (from my mac). Turns out that the FTDI driver they provide is 32 bit but (my) Mac needs a 64 bit. So you have to install the 32 bit, save the Info.plist, then install the 64 bit and copy it back and chmod permissions correctly.
- While trying to do a "opkg upgrade", be careful. Mine got into some issues installing a downloaded version half way through the process. But this also somehow broke the network connection. So no more updates. I almost thought I bricked my board. But I was able to again use my SD (from the previous downloaded latest version) to the rescue and bring it back to life again.
This board is a beautiful little piece of hardware. I'm really looking forward to tinkering around with it.
After reading this post, I thought I would be clever and just install the proper drivers, turns out, you do have to follow krishna2's instructions exactly.
Hopefully this saves others the slight headache, I went through:
- Install the HoRNDIS-rel4.pkg network drivers included on the board.
- Install the FTDI_Ser.dmg serial drivers included on the board. When I installed them, an error message popped up stating something about the OS being unable to use the driver.
- Download the 64-bit drivers here: http://www.ftdichip.com/Drivers/VCP.htm . As of this posting, this is the latest version: http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriv...
- Before installing the latest serial drivers: cp /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist /tmp
- Install the new drivers.
- cp /tmp/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist
- Enjoy!
Here's the error message, for SEO juice:
USBMSC Identifier (non-unique): 5A-1813BBBK0554 0x1d6b 0x104 0x308 HoRNDIS: init: HoRNDIS tethering driver for Snow Leopard+, by Joshua Wise 0 0 dgmdmcontrol: start - Failed to find the CDC driver HoRNDIS: rndisInit: their MTU 1486 HoRNDIS: init: starting up with MTU 1486 HoRNDISUSBInterface: Ethernet address c8:a0:30:ab:92:29 0 0 AppleUSBCDCACMData: start - allocateResources failed 0 1 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed 0 0 dgmdmcontrol: start - Failed to find the CDC driver 0 [Level 5] [com.apple.message.domain com.apple.commssw.cdc.device] [com.apple.message.driver AppleUSBCDCACMData] [com.apple.message.vendor_id 0x1D6B] [com.apple.message.product_id 0x104] AppleUSBCDCACMData: Version number - 4.1.23, Input buffers 8, Output buffers 16 HoRNDIS: rndisCommand: unsupported: RNDIS_MSG_INDICATE AppleUSBCDC: Version number - 4.1.23 Sandbox: sandboxd(36667) deny mach-lookup com.apple.coresymbolicationd Kext com.FTDI.driver.FTDIUSBSerialDriver not found for unload request. Kext com.FTDI.driver.FTDIUSBSerialDriver not found for unload request.
The power consumption is stupidly low, the colo company had to find a different meter to measure it from their normal server oriented one.
I use it as a DNS server, and SSH tunnel destination.
They gave me an IP address, subnet mask, and gateway, I preconfigured it, and posted them the board in a cheap case, plus the power supply with plug.
They invoice me annually for the power used including an amount of bandwidth which I never come near.
This is the PSU I use:
http://uk.farnell.com/jsp/search/productdetail.jsp?sku=17169...
with
http://uk.farnell.com/jsp/search/productdetail.jsp?SKU=17169...
I was going to use a RasPi, but I/O was too slow as it had to shove both the Ethernet and Disk through the same USB controller.
The other thing I'm using these things for (at least the RasPis) is a temporary fix for when someone's computer is busted -- it gets them back online with access to most of their daily routine, while I'm taking time to repair the PC. The BBB might have a bit more performance, so I might add that to the mix too.
But, I think it just takes one small project to get you started. I've noticed that this has a snowball effect as I start reading more and talking to more people about electronics and automation. Lots of fun! It's all about hacking, learning and having a good time!
Mine is currently a part time camera host for the (hot, young) chick cam, and rapidly getting the electronics and control programming to run the door on the coop. My long term plan is to have a few webcams in the coop and do some computer vision for chicken detection.
Pulling in the Shenzhen thread -- I wish I had the lab I had in HS 20 years back to do this: a bench full of scopes and power supplies, meters, and a parts room that was open for use. No paying retail + $10 shipping and waiting a week for parts.
I've finally got the last few parts to move it from breadboard to soldered pc board, so I'm hoping to get that done this weekend.
http://alvarop.com/2013/02/automation-progress-light-alarm-a...
And the nerd/hacker/enthusiast in me would gladly put down the cash to make it happen.
However, I also run into a wall when thinking of what to do with such a device. I'm not inspired by webcam+embedded linux. I don't want home automation. I already have devices hooked up to a TV. I work on the Kindles, which use Android (Fire) and embedded Linux (eink), so I can't argue buying a BeagleBoard for educational reasons.
Every time a product like this comes up, I get excited and start searching the TI website or BeagleBoard.org or Raspberry Pi or Arduino for lists of related components I could purchase to put together. Make my own weather station? I live in Seattle, the weather never changes :). What about a toiler paper roll sensor so I know if I need to buy more next time I'm at costco? (with a gf, this is hard problem!). I don't want this electronic staying in the bathroom around the moisture. What about getting a blue light star tracker and calculating celestial position like the old stealth fighters did? Cool, but kind of niche.
The closest idea I came up with is making an RC car. It would get me into the shop to make a frame, perhaps use a 3D printer for mold coverings, and be a fun demo with friends. When I start looking for motors, I get stuck finding a place to buy a motor. Take this page, for example:
http://www.ti.com/tool/dk-lm4f-drv8312
It's unclear to me if this page is a 'kit' for a large shop who want to try out this motor for a specific application. Or do I really need the huge controller board to operate this brushless motor?
Also, is it even possible to buy 4 or 8 of the motors? Or do I really need to put in an order of 1k or 10k units?!?!
Forgive the naive question, but where do other people go shopping for related components like a motor to wire together with these kits? What am I doing wrong?
https://cubieboard.myshopify.com/collections/frontpage/produ...
* the Cubieboard comes w/ male headers for its I/O pins. This is a lot less convenient from a practical perspective. There's an additional baseboard you can get but it's huge or I guess you can put your own blocks on.
* the Beaglebone comes w/ two PRUs if you need to do real-time work this is pretty sweet
* For general I/O, libraries like PyBBIO and Bonescript make the Beaglebone dead simple to program with. As far as I can tell, to access GPIO for the Cubieboard, there's a custom kernel module driver you'll need to install to access via /sys and no clear docs on PWM or other "basic" stuff.
Also looks like right now, the Cubieboard is a lot less mature and it's unclear what the timeline is for it to get better - for example, looking at the Google Groups threads, looks like there's the VPU/GPU acceleration is a bit finicky (the Cubieboard uses Mali-400, Beaglebone uses SGX530, both closed source/binary only drivers). There also seems to be a pretty active contingent of... less than helpful people on a lot of threads.
Cloud9 was fun to play with, and allowed quick access to all the functions you might want on the headers. Pretty easy to develop on, and requires very minimal setup or work to actually start programming in js.
Next, I put Ubuntu (Angstrom is very similar) on it and played around and was able to get familiar with where all of the pin input and output files lived, and how the muxing was put together in the OS. Once you explore a bit it's pretty quick. At that point, just pick a language and start writing whatever you want. I've written shell, C, and python for it for various projects this semester. It's super easy to run a web server on it to control the board from afar which makes for a killer demo at a hackathon or something. Also would be super easy to have it control things around your home from your smartphone.
Some notes / reminders: - X11 (Xming for PC) if you don't want to / can't use HDMI and you want a GUI (lxde). - Don't put a 5V data line into the UART pins (or most pins), classmates busted at least 5 A6's this way (new model may have improved).
I haven't used a Pi yet, and have a Model B coming my way now, but I'm absolutely grabbing a Black or two to see if it's any better. Would definitely recommend it!
Plugging the Raspberry Pi in and having it display immediately on the TV almost brought tears to my eyes. Maybe the situation is improved for the BeagleBone?
I have been playing w/ an MK802 stick and it has a few issues.
http://www.amazon.com/gp/offer-listing/B00ALSZNLW/ref=dp_olp...
PicUntu http://ubuntu.g8.net/ seems to got Ubuntu booted and running on the device.
I'm sorry, but that is NOT open source "when it comes to hardware". It's very cool, it's open source when it comes to software, but open source hardware is a completely different kettle of beagles, and I find it annoying that TI spokespeople would be trying to claim as much. It makes us "hackers" dis-trusting and TI look disengenuous.
Still think it's awesome! Just wish TI marketing would stop hitching a free ride.
EDIT: What is a "marketing engineer"?
What more do you want?
I don't think people realize how much stuff is in these chips and how much work and NRE it takes to make something like a $10 SoC happen. It's nice to see the advantages of scale being useful and -yay- we all get cheap XBMC players, but don't take it for granted.
I think their marketing has been just superb on this platform, and it's a huge turnaround from the days of $4,000 EVKs for their chips.
My definition of open source hardware is nicely outlined at http://en.wikipedia.org/wiki/Open-source_hardware .
Once again, I think the project is awesome, I think the marketing, despite good, is, well, marketing.
My main problem with the Pi is that it is very finicky... plug a USB device in, and it dies/connection drops and all kinds of weird things happen. I have seen none so far on the Black.
In fact technically RPi model B's official spec is that it requires 700mA. You can often get away with less, but you'll definitely start to hit 500mA+ under stress and with peripherals, which is above what USB can officially supply.
Your best bet is to get a nice solid cellphone wall-wart type charger, preferably rated 2A and up. With enough juice powering the Pi, all the issues relating to USB disconnects, freezing, and ethernet dropping stop happening.
Gonna guess that the stability you're seeing with the beaglebone is just from its much lower power requirement.
pi@raspberrypi ~ $ uptime
10:58:03 up 17 days, 13:45, 1 user, load average: 0.00, 0.01, 0.05
pi@raspberrypi ~ $Many USB devices don't work with the Pi. It's pretty picky.
pi@mia ~ $ uptime
15:40:15 up 94 days, 23:03, 1 user, load average: 0.00, 0.01, 0.05[1] http://circuitco.com/support/index.php?title=BeagleBoneBlack
http://arstechnica.com/gaming/2011/08/accuracy-takes-power-o...
But if you're just doing run-of-the-mill SNES emulation, it should be great.
The raspi does have analog video output, but it's composite. If you're an old school gaming purist you'd want something with analog RGB output.