Aseba on Raspberry PI

This page is dedicated to describing how to build ASEBA Studio on Raspberry PI, an ARM based SBC computer like Raspberry PI.

First of all some hints to be sure that your Raspberry is correctly configured and you can start working on it.

If you have also bought the SD card with the Raspberry Debian distro, note that it is often configured with partitions only for 2GB SD and RAM split for 256 MB in order to be compatible with the smallest Raspy configuration. Verifiy the size of your SD and the version of your Raspberry in order to be sure of these two sizes.

For the RAM you can find there how to check it.
You can modify the configuration of your Raspberry with the utility raspi-config.

Launch it and then first of all update it by choosing the menu item 'update'.
Once you are sure of having well configured your Raspy unchaining all its power by letting it see the total configured RAM, do the upgrade of the installed distribution

sudo apt-get upgrade

then shutdown the Raspberry and move the SD card to a more powerful platform on which to compile Aseba.

Currently the RAM and speed of Raspberry are not enough for some compiling tasks of ASEBA, so it is better to work with an emulator from a more powerful PC.
Follow the instructions of this forum topic in order to start a prompt on the Raspy file system, in emulation mode, by using qemu.
In order to run with quemu an image newer than ( 2012-12-16-wheezy-raspbian.img) you need to comment out the contents of the Raspberry file /etc/ and restart with chroot, otherwise by executing a command like apt-get you will get the error:

qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction (core dumped)

From there you can follow the normal Aseba build process described on the Aseba site.
When you have finished, move the SD card back to the Raspberry and then you can start to use Aseba on your Raspberry.
If you want to produce yourself the deb package you must still follow these hints:
The normal procedure is to package both Dashel and Enki as debian packages, and have them installed prior to building Aseba. In fact, they are as build dependency.
You can easily package Enki and Dashel, just download them and do the same procedure as for the Aseba package.

For creating a package issue the following command:

debuild -i -us -uc -b

Note that the -i option skips the .git directory, so that you can do
this directly from a cloned git repository. For running on PI it requires the package devscripts installed.
There you can find as an alternative the .deb package file already made for Raspbian.
In this case you have to download it on the Raspberry and install it with standard linux commands.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License