Scratchbox-2 version 2.0 released !

April 2, 2009 at 14:38 | Posted in Uncategorized | 2 Comments
Tags: ,

On April Fools’ Day (1.4.2009) Scratchbox-2 version 2.0 was released. We are going to use this version in the next maemo SDK+ release that we are planning to release on week 15/2009. Scratchbox-2 is one of the core components of maemo SDK+ development environment.

SB2 home page:

Maemo SDK+ home page:

Video: Maemo 5 alpha on BeagleBoard

March 31, 2009 at 12:24 | Posted in hardware, sdk | 6 Comments
Tags: , , , , ,

Here’s a quick video I put together while learning to use the video cam (you’ll notice that pretty soon) :-) This is just a basic demonstration of how the Maemo 5 alpha SDK runs on the BeagleBoard. Sorry about the video quality, I’ll make a better one from the eventual Maemo 5 Beta release.. promise!

Check out the Maemo on BeagleBoard site for more information.



Maemo 5 alpha on BeagleBoard

March 13, 2009 at 19:11 | Posted in hardware, sdk | 9 Comments
Tags: , , , , ,

After the release of the Maemo 5 alpha SDK, I’ve been working between my other duties on getting it running on the BeagleBoard. The Maemo on BeagleBoard project site has today been updated to include instructions for anyone to do the same.

BeagleBoard running the Maemo 5 alpha Application manager

BeagleBoard running the Maemo 5 alpha Application manager

The alpha SDK has released some content in the form of closed binaries. You are required to accept an EULA to gain access to the closed content and that means a ready-made rootfilesystem cannot be offered as a part of this project.

Instead a full set of instructions on how to build your own rootfilesystem using the Scratchbox1 based SDK is provided. The kernel image and modules are available for download and the kernel build process is documented. I’m not entirely happy with not providing a ready-made rootfs, but the closed binaries prohibit me from doing so. I hope you can understand this.

The provided kernel is buildable from the Maemo 5 alpha kernel sources (2.6.28) plus a sizeable patch which reimplements the display subsystem for BeagleBoard. The dss2 patches originate from the Ångström distribution‘s efforts available in the OpenEmbedded git, but within this project they are provided as one file.

The project’s default kernel configuration includes modules for USB HID, USB ethernet devices and USB mass storage devices. This means that you can use a mouse,  a keyboard, a USB-Ethernet plug or even a USB hard disk with your Maemo powered BeagleBoard — if you also have a powered USB hub, that is.

I was able to install packages from the Fremantle extras-devel repository directly to the BeagleBoard using apt-get. Someone had already uploaded a fun puzzle game Hex-a-Hop and it runs perfectly on this setup :-)



Chinook SDK Tools

November 15, 2007 at 1:34 | Posted in tools | Leave a comment
Tags: , ,

I wanted to write a few words about the tools released last week with the Chinook SDK.

The Chinook SDK is a collection of libraries, tools and resources that enables you to develop new applications and port existing ones to the IT OS2008.

With the SDK we wanted to release tools that are known to work and that are also used internally for software development in order to provide a verified set of utilities for you developers in the maemo community.

The tools and the SDK are now in the same repository and this has created a situation where the omission of certain library -dev packages has raised some eyebrows. The reason for this omission is that those libraries are only needed as a run-time dependency for one or more of the tools that are in the same repository. It is also an indication that if your application needs to use that library, you need to make sure it’s available for the non-developers from some other repository than the SDK, preferably from the Chinook extras repository. Your application should not depend on something that’s only available in the SDK repository.

There’s a plan to provide a separate tools repository the next time we publish an SDK. This will hopefully make the separation of the tools and the SDK more clear. This will also make it safer to activate just the tools repository on the device without having to worry about all the ‘noise’ the SDK repository creates in the Application Manager.

From Bora to Chinook

In Bora SDK the included tools were a small collection of standard Linux tools. This time with Chinook we’ve released more well known tools and also some that were developed internally and haven’t been available to the open source community before.

Oprofile is now available accompanied with a graphical user interface. Valgrind has been updated to a new version along with gdb in order to better support glibc2.5.

Most of the internally developed tools and helper scripts are in packages named “sp-something”. These utilities help in tasks like simulating different kinds of system load or collecting and analyzing debugging data or just provide help in starting up the various other debug tools correctly. The main goal of these “sp-tools” is to offer a variety of utilities to help you increase the quality of your applications by facilitating easier and more powerful testing.

The tools documentation pages were updated and the tools were categorized by task to help new developers easily see what’s available. Each tool that got categorized has its own subpage with a description, usage examples and links to other sources of information.

The new main page for the tools is

There are still some pending “sp-tools” in the Chinook pipeline. These will be available for you from the SDK repository in the near future. I’ll be sure to advertize them when the time comes.

Your friendly tools guy signing off. Happy hacking!


Blog at | The Pool Theme.
Entries and comments feeds.


Get every new post delivered to your Inbox.