Look what the mailman brought: It’s a shiny (or maybe matte?) BeagleBone Black, freshly arrived (actually it’s been over a month, but time sure flies…) from Newark element14! I’ve been doing Raspberry Pi related hacking for a while, but especially when the Pi was still fresh and new, I did from time to time consider if the grass would be greener on other side of the fence. Or blacker, in this case, as I mean BeagleBone Black.
BeagleBone was long very much more powerful than Raspberry Pi, but now that Pi2 has come out, price and specification-wise they are closer than ever. A quick personal comparison chart:
||Raspberry Pi 2 (B)
||46 € (Element14)
||32 € (Element14)
||1GHz single-core Cortex-A8
||0.9GHz quad-core Cortex-A7
||USB host, USB device, micro-HDMI
||4x USB, HDMI, 3.5mm Audio/analog video
||2x 46 pin headers (65 digital I/O)
||40 GPIO pins (26 digital I/O)
||4GB integrated flash, works as USB device
||camera and display interface on board
When Pi1 was out, the BeagleBone Black with the more modern Cortex-A8 chip and higher clockrate was definitely the more powerful, but now with 4-core Pi2, the tables have somewhat turned. Still, the clockrate is higher and there’s more GPIO. And speaking of GPIO, my Raspberry Pi vs. Pi2 GPIO benchmark has gotten a lot of interest, so I thought the best way to take this black beauty for a test drive would be to benchmark BeagleBone Black GPIO in a similar way.
The test subject is the most recent revision C of BeagleBone Black. I followed the (a bit lacking in detail and readability) Getting Started guide and downloaded the latest Debian Jessie image (8.3, 2016-01-24), flashed it to card and ran
apt-get update and
apt-get dist-upgrade (2016-04-14).
Continue reading BeagleBone Black GPIO Benchmark
Tux logo by Larry Ewing, Simon Budig, Anja Gerwinski
I’ve been a big fan of Picotech’s USB connected PC oscilloscopes ever since I purchased my first PicoScope 2204 almost two years ago. I liked the compact form factor on my desk a lot, and the powerful Picoscope software for Windows – Picotech makes only one version of this software so you get the same functionality with a £159 ($260) 2204 scope as a £5,995 ($9,900) PicoScope 6407 user would – although of course the scope features would be wildly different.
Now Picoscope is a great piece of Windows software and as I generally use Win7 to avoid reboots every time I want to use Photoshop or play a session of Mass Effect, it’s been perfect for me. However, quite a few of electronics enthusiasts are also big advocates of open software movement, and while Picotech has had drivers and SDK for Linux for a while to implement things like my realtime composite decoder, the fact that there is no Linux version of the oscilloscope software has been unfortunate. So when I noticed in the latest Picotech newsletter that there is now a beta of Picoscope for Linux, I knew I had to take it for a spin.
Installing Picoscope on Linux Mint 15
Picotech’s installation process is built on
apt packaging system, so a Debian-based Linux distro is the easiest installation target. This includes the wildly popular Ubuntu and Linux Mint distros, which means mainstream Linux users are well catered to. In Picotech forums, the beta thread had at least one user who extracted necessary stuff from the .deb packages and installed the software for Fedora, too.
In Debian-based Mint, the installation went without any hiccups just by following the instructions at Picotech’s Linux Drivers page. Note that
sudo apt-get install picoscope also installs all drivers so you don’t need to install your model-specific driver separately. Essentially the installation is just:
sudo echo deb http://labs.picotech.com/debian picoscope main >> /etc/apt/sources.list
wget -O - http://labs.picotech.com/debian/dists/picoscope/Release.gpg.key | sudo apt-key add -
sudo apt-get update
sudo apt-get install picoscope
Continue reading Picoscope Beta for Linux
A rather long wait ended today, when DHL dropped this little package off at work in the morning. I had placed my Raspberry Pi order in the first 24 hours when they started taking orders (or actually, registrations of interest) from RS Components, but it took about two months for me to receive the invitation to order, and three more weeks for the order to arrive.
Opening up the box, I was greeted with a very small computer, and two small leaflets, a quick start guide and a regulatory and safety pamphlet. The board is really quite small, just a few millimeters larger than a credit card. Two USB slots, HDMI, coaxial and stereo audio plugs and micro-USB for power, plus an ethernet jack.
I ran a quick test to see if everything worked. Initially, there was flicker on my projector (the only device with native HDMI input I currently have), but that turned out to be incompatibility with the HDMI switch I had – without it it worked just fine. I used the premade Debian image on a SD card and it worked perfectly.
Continue reading Raspberry Pi arrived today!
Just a brief revelation to share with any readers (perhaps they stumble here through Google, or by some horrible accident :).
I’ve had an Abit IP35-E motherboard in my HTPC setup for six months now, and while a great overclocking board, stable and packed with nice features (yeah, right, this is the budget version), I haven’t been able to coerce my Debian Lenny installation copied from previous IDE hard drive, or any Linux Live-CD to properly recognize my 500GB Samsung SATA hard drive.
Because booting to Linux rebooted with USB keyboard on, and IRQ options sometimes seemed to work their magic and temporarily get me to login prompt, I figured there was some IRQ conflict at work. I searched for the fix just half a year ago with no luck, but after 5 months of complete Linux abstince (spelled that wrong, I did), I stumbled upon an article in (now defunct) Fatwallet.
Turns out all I needed was to swap SATA cable from SATA1 port to SATA5 to avoid IRQ conflicts. Voila, now everything works great, no IRQ conflicts there (only SATA1-SATA4 ports conflict with USB controller).
Hope this helps someone!