I’ve been working with Ruby on embedded systems for a couple of weeks now. The final pieces have fallen into place and I’d like to share them with you. From the beginning of the project, my goal have been to turn some LEDs on and off from a web page.
Getting down to the metal
Any embedded software application has to eventually control some interesting hardware. My ARM board had two LEDs wired up, so I thought I’d try to control them. The control for the ports that control those LEDs are in memory mapped registers.
Ruby really never let's us see the memory that we are working with, and even if it did, we are working in a virtual memory environment, so we wouldn't be able to access the specific memory address where the register is located. So it was time to learn how to write Ruby extensions.
I was surprised how easy this ended up being. Ruby has a great little module
makes Makefiles for you. The API
for defining ruby modules was also pretty straight forward and explained well in
I put the module I wrote up on git hub, so take a look there if you are interested. The extension allows you to just read from or write to any physical address on the device. To set a bit in a register, you might do something like this.
Ahh…0x, hex numbers, addresses. It's nice to be back.
To get the module into my Ruby environment, I created an
directory in the
ext directory of the Ruby source and dropped in
the source files. I didn't have to change any makefiles, I just created an
extconf.rb and the ruby build system took care of the rest.
It would certainly be possible to build the module separate from the rest of the Ruby source, but since I already had the source tree configure to cross-compile, the path of least resistance was to just include this extension in the source tree.
I posted my extension to the ruby-core mailing list to see if there was any wider interested in it. It turns out there is a memory mapper extension already written. I took a quick look and it isn’t exactly the same thing that I did. My interface is much more basic (and simple), but I think the mmap extension could be made to do the same thing I am doing.
The Promised Land
With a way to control the hardware from Ruby, I had finally arrived where I had wanted to be. The entire thesis behind this little experiment was that Ruby could make embedded application development fast and fun. I found both to be true.
This entire application came together in just a couple of hours. I was able to make use of a ruby gem that did a bunch of the work for me. I called the application weblink. You are free to interpret the name however you would like (We Blink, Web Blink, Web link). The source is on git hub.
When test-driving an embedded system, you'll save yourself a bundle of time by doing as much of the development as you can on your host computer. The download, restart, test cycle can really add up when you are working in quick TDD cycles.
On my particular system, the files system is still being hosted remotely, and the language is interpreted (no compile) so this overhead is not that bad. Still I wanted my application to run on my development machine, and I didn't think it wise to overwrite some random address in my Mac's memory, so I needed an abstraction.
When developing these kinds of environments in a C++ system, I would traditionally build a pure-virtual interface and implement it twice, once for the target hardware and once for the simulated, or development environment. In C you can do a similar thing with the linker.
You write two functions, one for each platform and just link in the correct one when building for that platform. With Ruby’s ducktyping, there is no need for a defined interface, but the concept is very similar. I wrote two Led classes both with ‘on’, ‘off’, and ‘on?’ methods.
I did not want the real Led class to have the platform specific knowledge about which LEDs were in which register, so I used the Factory Pattern to create the Led objects. The factory method is called ‘find.’ The MockLed file implements this same method that returns MockLed objects in the development environment.
The tricky part of this is switching between the two Led classes. For this, I chose to use Sinatra's environment configuration scheme. The production environment is used when running the app on the target, and the development environment runs on my Mac.
To celebrate the 170th anniversary of the first demonstration of the telegraph, I decided to turn the application into a visual telegraph, beeping out little messages. The ideas is that you enter a message in the web page, and the LED blinks out your morse code.
Here is where I saw the great power of not only Ruby, but also the community who uses it. I discovered right away that there is a Morse Code Gem already written. You give it a string and It gives you back a series of dits, dashes, and spaces. Thanks Ben!
See it for yourself
Okay, so enough talking, let me show it to you. Enjoy.
So I know that the response that I will get from embedded developers is “Great, but it's slow and big, it can't be used in a real system.” I'm going to do some profiling and optimization on this system to get some hard performance data.
Initial results (just looking at 'top') shows that the ruby process with Sinatra, Webrick, the morse gem, and my code loaded up is taking up about 12% of the system memory. That mean about 6 or 7 MB. What nice is that you only pay for what you use. If you don't require it, it won't load into memory. As far as clock cycles go, the ruby processes peaks out at about 20% of the 400 MHz processor when serving HTTP requests.
While blinking the LEDs, only a fraction of a percent of the processor’s cycles are being consumed. I’m not happy with the performance of Webrick (no one ever claimed it was fast anyway) and I am going to try to get Sinatra running with ‘Thin’ instead.
Synchronization: I fork a new ruby process to blink out the messages. If you got both LEDs blinking at the same time, they could step on each other's toes and cause incorrect values to be written to the LED. I need to stick a mutex in to protect that register.
I remember early in my career, Kevin Moore and I had started using Ruby to run our embedded builds. We used the Win32 API to drive the automation interface of Metrowerks and we wrote lots of little tools to do the annoying parts of building a flash image for us.
I remember at the time, Kevin and I having a conversation that went something like:
“Wouldn't it be cool if we could write the entire app in Ruby?” Well Kevin, now we can.