Re: Cheap slow CPU that runs Orocos?

Willy Lambert <[email protected]>
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <CAKvQZ_2mKpykGqxKQYFY04myLbMivvjUY1vPZ4NpB9-nAQt50Q@mail.gmail.com>
2012/11/27 Philippe Hamelin <[email protected]>:
> 2012/11/27 Paul Chavent <[email protected]>
>>
>> On 11/21/2012 11:17 PM, Willy Lambert wrote:
>> > 2012/11/21 Paul Chavent <[email protected]>
>> >> I manage a custom gnu/linux based system that fit on 20Mb with
>> >> everything
>> >> for running orocos and our software (kernel + glibc + omniorb + orocos
>> >> +
>> >> opencv + lua + other misc packages)
>> >>
>> >> I can give you more information if you need.
>> >>
>> >>
>> > Yes please, I'm very curious about this.
>> >
>>
>> I'm currently use a custom build infrastructure ( http://gitorious.org/bif
>> ). This infrastructure is just a collection of shell functions that allow to
>> ease the development of recipes ( here is the orocos recipe
>> http://gitorious.org/bif/bif/blobs/master/framework/packages/orocos-rtt/orocos-rtt.sh
>> ).
>>
>> Nothing really new here, just an automated way of compiling orocos (like
>> the bitbake recipes of OE, or Makefile of buildroot), and crosscompile
>> capabilities.
>>
>
> I successfuly used Buildroot 2011.05 in a previous project using Orocos
> 2.3.1 on an ARM Cortex-A9 board. I patched buildroot to support the required
> packages (boost, omniorb, orocos-log4cpp, orocos-rtt, orocos-ocl, etc.). You
> can find the patched version in the "2011.05-sm" branch available on my
> github account (https://github.com/phamelin/buildroot/tree/2011.05-sm). You
> will have to modify the scripts since the source packages were retrieved
> from a private server. As I remember, the whole operating system including
> Orocos was fitting on a 32 Mb SD card.
>
> Philippe
>

I confirm that with a simple configuration you can build a minimal
linux with a "minimal" Orocos in something less than 50Mb (I currently
have 34M, but I'm not chasing size, and all option of orocs are not
activated).

Note that this is only the system/framework files. My application
binaries will take some place over this. It's around 10 times ligther
than a default minimal Debian installation. But this minimal system is
not equivalent in term of functionnalities.

FYI, my experience of all this (Debian base+custom dfistribution, or
Buildroot from scratch system) told me that you gain a lot in size and
boot time (this is the good indirect news), but it'll cost much more
to setup the first system or to integrate new stuff (first is just an
apt-get install, second is a package creation if it doesn't exists
yet).

When my application will be working on my minimal system I'll try in
qemu to lower the CPU/Memory available to see what's happening.
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.