This is the Raspberry Pi board, an ARM based GNU-Linux computer. We’ve heard a little bit about it, but it recently garnered our attention when the machine was shown running XBMC at 1080p. That’s a lot of decoding to be done with the small package, and it’s taken care of at the hardware level.

Regular readers will know we’re fans of the XBMC project and have been looking for a small form factor that can be stuck on the back of a television. We had hoped it would be the BeagleBaord but that never really came to fruition. But this really looks like it has potential, and with a price tag of $35 (that’s for the larger 256MB RAM option) it’s a no-brainer.

Now there’s still a lot of rumors out there. We came across one thread that speculated the device will not decode video formats other than h.264 very well since it uses hardware decoding for that codec only. We’ll reserve judgement until there’s more reliable info. But you can dig through this forum thread where the XMBC dev who’s been working with the hardware is participating in the discussion.

Don’t forget to peek at the demo clip after the break too.

[via Reddit]

[Scot Kornak] got his hands on the new STM32 Discovery Board. He got his as a free giveaway, but at only $18 he probably would have picked one up anyway. His one complaint about the device is that he dual pin-headers which break out the ARM processor’s pins are not the most convenient for hooking up external components. He decided to make his own breakout board which would give him a more robust solution for the components he uses all the time.

The protoboard that he chose as a base is quite interesting. It’s made for interfacing DIL pin headers just like the ones on the STM32F4 Discovery board. Each row of the dual header is carried down the board perpendicular to those headers. [Scot] cut the traces underneath the STM32 board to isolate the right and left sides. He then added RS232 hardware to one side, while including another pair of DIL headers to break out the rest of the unused pins.

This is all he’s got so far, but there’s plenty of room on the base board to add more as the need arises.

The beta version of Pyxis 3 is now available. Skewworks continues to develop the ARM operating system, and with the transition to version 3 they’ve given it a new name: Gadgetos. One big difference from Pyxis 2 is that the new kernal is closed source. But they’ve taken steps to ensure that the OS is still hardware independent. This is done by reworking the kernel to allow driver loading at run time from an SD card.

The user interface has also changed a bit. Gadgetos relies entirely on a context-based menu system. The minimum input hardware requires a touchscreen LCD and one tactile button. By holding that button, a menu pops up in the center of the screen. This menu is different based on where it is called (this is where context comes in). If you’re at the desktop screen, you get options to load programs, etc. If you pull up the menu while running an application you’ll see the options available for that app. To see more about the new navigation system check out the video after the break.

We find it interesting that PIC and AVR programming is very common in hobby electronics but ARM doesn’t have nearly the same foothold. This is partly because there’s a knowledge barrier involved with making the transition (the other part is probably the lack of DIP packaged chips). But if you’ve worked with 8-bit microcontrollers you can certainly make the jump into the 32-bit realm. Here’s a great opportunity to get your feet wet. This guide will show you how to get the USART on an STM32 Discovery Board working, which makes it easy to get feedback about what’s going on in your program.

One difference you’ll notice when moving to ARM microcontrollers is that there is almost always a library bundle available from the manufacturer which includes all of the functions you need for hardware control (USART, USB, Ethernet, ADC, etc.). That’s the case here, so simply including the USART library makes it a snap to finish the rest of the program. Once you hook up your communications hardware (an FTDI cable in this case) just use the library initialization functions, followed by the send and receive commands and you’ll be pushing messages to a computer terminal in no time.

If you’re trying to use the STM32 Discovery Board with a Linux box here’s a shove in the right direction.

Want that 70″ LCD television in your living room to be an Android device? This little guy can make it happen. With an HDMI port on one end, and a USB plug on the other for power, just plug in FXI Technologies’ Cotton Candy dongle to create a 1080p Android television.

The price isn’t set for the device, but it’s expected to be available at less than $200. Considering what’s inside that’s pretty reasonable. There’s a dual-core 1.2 GHz ARM processor, 1 gig of RAM, 64 gigs of storage, Bluetooth, WiFi, and a microSD card slot. Wow!

So is it hackable? Absolutely. Well, kind of? The company doesn’t intend to bring Cotton Candy to the retail market. Instead, they will sell the device to developers who may do what they wish. From there, said developers have the option to license the technology for their own products. This begs the question, will the development kit come in under $200? Hard to say.

Check out the video after the break to hear an interview with the company’s CEO. It certainly sounds fascinating, and like the Chumby NeTV, we can’t wait to see what comes of this.

[Thanks Adam via RootzWiki]

[Andrew] is trying to buckle down and hammer out his PhD project but was surprised by the sorry state of the configuration options for his FPGA/ARM dev board. Using JTAG was painfully slow, so he studied the datasheet to see if there was another way. It turns out the Xilinx FPGA he’s using does have a slave serial mode so he came up with a way to push configuration from the ARM to the FPGA serially.

Four of the connects he needed were already mapped to PortC pins on the AT91SAM9260 ARM System on a Chip. He ended up using the EN_GSM pin on the FPGA, since there is no GSM module on this board; connecting it to the microcontroller with a piece of wire. Now he can SSH into the ARM processor, grabbing information on the FPGA from /dev/fpga0. When it comes time to program, it’s as easy as using the cat command on the binary file and redirecting the output to the same hook.

This man is strapped onto the business end of a huge robotic arm. If you’ve seen videos of industrial robots on automobile assembly lines and the like, you know how fast and strong these machines are. But this isn’t headed for the factory floor, it’s a new flight simulator built do train Australian fighter pilots.

Researchers at Deakin University were looking for a way to give a fighter pilot a more realistic simulator experience. What they ended up with is an apparatus that can spin continuously on two axes. This lets the pilot feel what it might be like to stall and have the aircraft spinning out of control.

The video after the break is not to be missed. You’ll see the test pilot (read: guinea pig) flung this way and that to the point that we almost decided this should be a “Real or Fake” post. But we’re confident that this actually exists. We expect that future renditions will include the front portion of the aircraft and be completely enclosed in a projection dome, just like the Lexus driving simulator.

Looks like the Lightweight USB Framework for AVRs (LUFA) has just been ported for ARM microcontrollers. NXP recently released a package for their LPC Cortex M3 family of ARM controllers. You won’t find a reference to LUFA on their nxpUSBlib description page (which we think is kind of sad), but if you grab a copy of the beta code the Version.h header file shows that it is indeed a port of the project. This is further backed up by the LUFA creator, [Dean Camera], who consulted with the NXP team doing the work.

The package provides an open-source USB stack that you can use in your projects as a USB host or USB device. We’re advocates of open source packages like this one as it makes it much easier for hobbyists to get help using the tools, and it allows the community to give back through bug fixes and feature additions.

We’ve highlighted a few LUFA projects, like this keyboard remapper and this AVR programmer. We’re looking to seeing the first set of NXP LUFA projects roll through!

[Thanks Johnny]

Small and more powerful… what more can you want? This is the newest BeagleBoard offering, called the BeagleBone. It’s packed with some pretty intriguing features, but let’s take a tour of the hardware first.

Like its predecessors, the BeagleBone sports an ARM processor. This time around it’s a TI AM3358 ARM Cortex-A8. It will ship with a 2 GB microSD card and has an Ethernet port and USB connection. The dual pin headers on either side of the board are designed to receive ‘Capes’ for expansion. Currently a DVI cape is in the works, with HDMI and others to follow.

Linux is running on board and one of the best features we see in the video after the break is the browser-based programming interface. When connected to a network, the BeagleBone serves HTML5 web pages. One of these is an IDE that lets you write and execute code directly from your browser.

Now, can we finally have our open-hardware set top box (hopefully running XBMC)?? At an MSRP of $89 this should be able to give AppleTV 2 a run for its money as an easy way to get your television some network connectivity.

[Thanks NsN via Linux for Devices]

Some hard work has gone into making it possible to develop for the STM32 Discovery board using a Linux system. The board boasts an ARM Cortex-M3 processor, which can be programmed via the mini-USB port on the side. But the company only supports development through their IDE’s which don’t run natively on Linux. The stlink project aims to solve this, providing a toolchain, and making it possible to flash the microcontroller via the USB connection.

The github project linked above also includes a tutorial to get you started (pdf). In addition to a walk through on compiling the software packages, it includes a simple blink program that you can use to test out your hardware. GDB, the familiar open-source debugger, is used to flash the chip. This is a bare-bones tutorial so if you end up posting about your experiences using this toolchain with the Discovery boards we’d love to hear about it.

[Thanks Texane]

[Alejandro] and his friends recently finished a first prototype of scratch-built robotic arm. They’ve got some nice electronics bench equipment for use with a project like this, but for the actual fabrication work it’s off to the kitchen.

As you can see in the video after the break, they’re using PVC as the stock material in this build. Flat sheets are produced by slitting a PVC pipe down the middle, warming it in oven until soft, then compressing it between two floor tiles with a big jug of water used as a weight for the makeshift press. Mounting holes for the servo motors that make up the joints are drilled with a hand drill, and the assembly was affixed to an old CD as a base.

Once assembled they wired it to the control circuitry and build a set of sensors that you wear on your arm. Now your elbow, wrist, and pointer finger are in control of the servos. A demonstration of this functionality starts around two minutes into the video.

We’ve seen other examples of robot arms built without the use of machine tools. This arm made out of ShapeLock plastic is one of the most interesting examples.

The Arduino folks took advantage of Maker Faire New York to announce their new line of products. There’s several interesting new additions to their product line.

They’ve got a WiFi shield in the works that utilizes a module from H&D Wireless in conjunction with an AVR32 processor to take the workload off of the ATmega chip on the Arduino board. It even has room for you to run your own code on the shield’s processor.

Notable (but of less interest to us) is the 1.0 release of the IDE and the development of a new low-cost board. That hardware is intended to make USB device development easier for those already familiar with the Arduino platform.

But the big news that caught our eye is the announcement of an ARM Cortex-M3 Arduino called the Due (we already wish that had been named something different just for search term contrast to the Duemilanova). The hardware hasn’t been finalized yet, although you can see a prototype in the picture above. They want community input on the final touches, so get in there and give them a hand!

[Thanks Insapio and Tom]

Do you have a rooted Android device and a computer running Linux? If so, you’re already on your way to coding for Android in Assembly. Android devices use ARM processors, and [Vikram] makes the argument that ARM provides the least-complicated Assembly platform, making it a great choice for those new to Assembly programming. We think his eight-part tutorial does a great job of introducing the language and explaining how to get the development tools up and running. You’ll need to know some basic programming concepts, but from what we saw you don’t need any prior experience with ARM or Android.

So why learn Assembly at all? We took a stab at Assembly for AVR a few months ago and really learned a lot about the hardware that we just never needed to know writing in C. It’s a great way to optimise functions that waste too much time because of quirks with higher-level language compilers. That means you don’t need to write your entire application in Assembly. You can simply use it to streamline hairy parts of your code, then include those Assembly files at compile time.

If you’ve got an ARM development board gathering dust in the corner of your shop, perhaps you could repurpose it as an oscilloscope. [Arend-Paul Spijkerman] was able to use an mbed and LPCXpresso as the hardware end of an oscilloscope. He didn’t use a standalone screen as a display, instead opting to push the scope readings from the hardware to a computer for display. This was greatly simplified by using StampDock as a basis for the GUI.

His circuit diagrams calls for an RS-232 connection for the LPCXpresso but not for the mbed. We’re not quite familiar enough with the mbed to know why, but perhaps those in the know can clue us in by leaving a comment. The probe connections are quite simple, each made up of a voltage divider and a pair of diodes. But the breadboard above looks much busier because it has two oscilloscope circuits built on it, and there’s a 10 MHz clock and a 4040 ripple counter which were used to provide a test signal.

[BarsMonster] just challenged our conceptions of ARM development with his single-sided development board that’s loaded with an STM32F100 (PDF warning) ARM microcontroller. The board is remarkably simple – just a regulator, resistor and a few caps are necessary to get a $1 ARM μC up and running.

[BarsMonster] gave us a schematic of his board along with the Eagle .brd file of his build. Everything is an SMD component, so except for 9 through-holes, this board can be easily manufactured at home.

While we have seen a few single sided projects at Hack A Day, dev boards made with this technique have fallen by the wayside. This surprises us because single sided boards are easy to make with the various CNC mills we’ve seen.

There are a few great projects out there for the STM32 processor, like a web radio, but [BarsMonster] is having some trouble finding some good libraries for his MCU (specifically STM32 libraries for Eagle). If you know of anything he can do, drop a note in the comments or on his website.