You will need to use a recent Armadeus release (with Buildroot > 2011.05) to use the following instructions.

==Building common toolchains with Buildroot==
* create directory where toolchain will be put:
<pre class="host">
$ sudo mkdir -p /usr/local/armadeus
$ sudo chown $USER:$USER /usr/local/armadeus
</pre>

<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Build options ---->
() Host dir
</pre>

==Using already built Toolchains==

<pre class="config">
Toolchain ---->
Toolchain type (External toolchain) --->
Toolchain (Custom toolchain) --->
(/path/to/staging/usr/) Toolchain path
</pre>

Then, set the properties of the toolchain accordingly.

==Using a recent Buildroot to build rootfs for an Armadeus board==

This may be useful if you need some packages that have been integrated
in Buildroot after the release used in the latest release (or git head)
of the Armadeus SDK.

It allows to build new rootfs or images for the APF boards, keeping
support for the specific hardware.

The method uses:
* an Armadeus SDK providing the cross-toolchain and Armadeus specific hardware support;
* a recent Buildroot (from a tarball or a clone of the repository).

There are several ways of getting things done, but at the end, the main
difference will be the location of the full target directory; you can choose to install everything:
# either in the Armadeus target directory;
# or in the Buildroot one;
# ...

===Setting up the environment===

The 1st way is based on the <code>make O=/PATH_TO_ARMADEUS/buildroot/output/target</code> usage in the buildroot
tree (for more information, refer to the
[http://www.buildroot.net/downloads/buildroot.html#building_out_of_tree out-of-tree build section of the Buildroot documentation]).

The following explains the 2nd way (the way I use ;-)).

{{Note| In the following, '''from step 2''', you should ''run both the Armadeus SDK menuconfig and the Buildroot one at the same time''.

Despite the some differences, that makes the configuration of Buildroot easier and quicker!
}}

: 1. Build a minimal target for your board using the Armadeus SDK; what <code>make apfXXX_defconfig</code> sets is sufficient.
:: Linux kernel and programs provided by the recent Buildroot are not mandatory.
: 2. Get a recent Buildroot (tarball or head of Buildroot repository) and set the Armadeus cross-toolchain as its ''external toolchain'' (cf. [[#Using already built Toolchains|Using already built Toolchains]]).
: 3. Set the System configuration (of the recent Buildroot) pointing to the Armadeus target directory.
:: This way ensures that things only provided by the Armadeus SDK will be copied in the target:
<pre class="config">
System configuration ---->
Root FS skeleton (custom target skeleton) --->
(/PATH_TO_ARMADEUS/buildroot/output/target) custom target skeleton path
</pre>
: 4. Set the Filesystem images according to your wish (certainly similar to the Armadeus one).
: 5. Disable any bootloader.
:: The current u-boot version used in the Armadeus SDK (u-boot 1.3.4) is no longer available in recent Buildroot. However, some people are working on porting u-boot 2010-03, and maybe barebox too.
: 6. The kernel configuration depends on which, from the Armadeus SDK or Buildroot, will provide (build and install) the kernel image and its modules:
::: 1. If you have enabled the kernel in the Armadeus SDK, then your should probably not enable it in Buildroot. Misconfigurations may result in unconsistencies between the kernel image and its modules installed in the rootfs.
::: 2. If you have disabled the kernel in the Armadeus SDK, you should build it in Buildroot, but use patch set provided by the Armadeus SDK to keep specific hardware support.
<pre class="config">
Kernel ---->
[*] Linux Kernel
Kernel version (Custom version) --->
(2.6.38.1) Kernel version
(/PATH_TO_ARMADEUS/target/device/armadeus//linux/kernel-patches/$(BR2_LINUX26_VERSION)) Custom kernel patch
Kernel configuration (Using a custom config file) --->
(/PATH_TO_ARMADEUS/target/device/armadeus/BOARD_NAME/BOARD_NAME-linux-$(BR2_LINUX_KERNEL_VERSION).config) Configuration file path
Kernel binary format (uImage) --->
</pre>

Lastly, build and try the freshly built image (shall I recommend usage
of nfs-root for that kind of experiments ...).

{{Warning| '''Take care when enabling/disabling packages''' from one or the other side.

* '''Some hardware may not work properly without these patches.'''

:: Some packages have been patched in the Armadeus SDK, that Buildroot's ones does not patch (yet).

* '''Override some packages''' (ie. enabling a package in both the Armadeus SDK and Buildroot), '''may result in an unconsistent/unstable system'''.

:: This mainly targets the ''busybox'' and its potential broken symlinks.
}}

==Links==
* [http://www.buildroot.net/downloads/buildroot.html#external_toolchain Buildroot's documentation about External Toolchains]

External Toolchains

2011-08-07T19:44:43Z

SamuelM: /* Using already built Toolchains */

User:SamuelM

2011-08-07T16:54:01Z

SamuelM: /* A colored (and useful) prompt */

[[MemberList | << Member list]]

[[Special:UserList | << User list]]

== whoami ==

* Name:
:: Samuel MARTIN

* Background:
:: <s>Student at [http://www.eseo.fr/ ESEO] (French engineering school), specialised in Embedded systeme and Automation /</s>
:: <s>Master student at l'[http://www.plymouth.ac.uk/ University of Plymouth] (UK), in [http://www.plymouth.ac.uk/courses/postgraduate/taught/2558/MSc+Robotics Robotics].</s>
:: Embedded and System Engineer (Paris, France)

== Interests ==
* Robotics
* Computer Vision
* Image & signal processing
* Linux

== Objectives ==
''or, what I wanna do with the APF board (APF27 + Devfull)''
* '''Have fun!'''
* Improve my skills in:
** Hardware development (FPGA)
** System and embedded OS
** Electronic development
** Software development for embedded (tiny) target
* Share my experiments

== Contributions ==
[[OpenCV|Cross-compile OpenCV for your APF]]

[[CMake]]

== Tips ==
=== A colored (and useful) prompt ===
''zsh and [http://www.ctaf.free.fr/dokuwiki/doku.php?id=ctafconf ctafconf] users won't be lost'' ;-)
<source lang="bash">
##
## ~/.profile
##
source /etc/profile

## Enhanced promt
if [ -t 0 ]; then
bldblk='\033[1;30m' # Black - Bold
bldred='\033[1;31m' # Red
bldgrn='\033[1;32m' # Green
bldylw='\033[1;33m' # Yellow
bldblu='\033[1;34m' # Blue
bldpur='\033[1;35m' # Purple
bldcyn='\033[1;36m' # Cyan
bldwht='\033[1;37m' # White
txtrst='\033[0m' # Text Reset
undred='\033[4;31m' # Red - Underlined
bgdred='\033[1;41m' # Red - Background
bgdblu='\033[1;44m' # Blue - Background
fi;
if [ $(id -u) -eq 0 ]; then
userbgd="${bgdred}"
else
userbgd="${bgdblu}"
fi

export PS1="${userbgd}\u${bldylw}@${bldgrn}\h${txtrst} ${bldpur}[\$(eval \"res=\$?\"; [ \${res} -eq 0 ] && echo -en \"\${bldwht}\${res}\" || echo -en \"\${bldred}err \${res}\")${bldpur}] [${bldblu}\w${bldpur}] ${txtrst}\n\${SHELL:5}${bldgrn}\$${txtrst} "
</source>

=== u-boot configuration ===

# ''nfs-boot'' (kernel and rootfs), if the nfs server is alive
# ''boot from the NAND flash'', otherwise

==== u-boot environment ====

<pre class="apf">
BIOS> setenv nfsboot 'setenv bootargs ${console} ${mtdparts}; \
run addnfsargs addipargs; \
setenv autostart yes; \
nfs ${loadaddr} {serverip}:${rootpath}/${board_name}-linux.bin; \
bootm'
BIOS> setenv addnfsargs 'setenv bootargs ${bootargs} root=/dev/nfs rw nfsroot=${serverip}:${rootpath}'
BIOS> setenv addipargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off'
BIOS> setenv bootcmd 'if ping ${serverip}; then \
echo; \
echo Boot over NFS; \
echo; \
run nfsboot; \
else \
echo; \
echo Boot from the board; \
run jffsboot; \
fi'
BIOS> setenv board_name apf27
BIOS> setenv netmask 255.255.255.0
BIOS> setenv serverip 192.168.10.2
BIOS> setenv gatewayip 192.168.10.1
BIOS> setenv ipaddr 192.168.10.10
BIOS> setenv rootpath /path/to/where/you/untar/your/rootfs
BIOS> saveenv
BIOS> boot
</pre>

Adjust the <tt>bootdelay</tt> if needed.

Next boot will automatically try to boot over NFS, then fallback on the NAND flash

{{Warning|

If the '''NFS server is alive''', but neither the '''linux kernel image nor the rootfs'''
are '''NOT at the expected location''': ''/path/to/where/you/untar/your/rootfs'',

the boot will hang up, so '''booting will fail''' !}}

==== NFS server configuration ====

Refer to the [[Network File System configuration|NFS wiki page]] to setting the NFS server up.

Then:

* untar the rootfs tarball in ''/path/to/where/you/untar/your/rootfs''
* copy the linux kernel image to ''/path/to/where/you/untar/your/rootfs''

<pre class="host">
sudo tar xvf apf27-rootfs.tar -C /path/to/where/you/untar/your/rootfs
sudo -fv cp apf27-linux.bin /path/to/where/you/untar/your/rootfs
</pre>

MemberList

2011-07-24T15:33:19Z

SamuelM:

==Here is the list of the (active) members and their skills==

This list is maintained by the users themself.

*0: Novice
*1: Notions. At least one successfull experiment
*2: Confirmed
 

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! '''Name / IRC Nickname''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain / Salocin]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot / Artemys]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer / JiBee]] || 2 || 1 || 1 || 1 || robotics
|----------------
|[[User:NicolasA|Nicolas Aguirre]] || 2 || 0 || 1 || 1 || multimedia
|----------------
|[[User:BenoitC|Benoît Canet]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:SonZerro|Sonzerro]] || 0 || 0 || 1 || 2 || domotics
|----------------
|[[User:HenriG|Henri Geist]] || 1 || 1 || 0 || 1 || robotics
|----------------
|[[User:BorredonB|Bernard Borredon]] || 2 || 1 || 0 || 1 || domotics
|----------------
|[[User:ThomasB|Thomas Bores]] || 2 || 0 || 0 || 1 || Entertainment
|----------------
|[[User:FabriceM|Fabrice Mousset / KroMignon]] || 1 || 1 || 2 || 1 || Domotics & multimedia
|----------------
|[[User:AmineH|Amine EL HEDADI]] || 2 || 2 || 0 || 0 || domotics & robotics
|----------------
|[[User:PhilippeM|Philippe Monteil]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:CedricZ|Cédric Zmyj]] || 0 || 0 || 0 || 0 || domotics & robotics
|----------------
|[[User:JeanMichelN|Jean Michel Naimo / jeanmi12 ]] || 2 || 1 || 1 || 1 || Domotics & entertainment
|----------------
|[[User:OlivierC|Olivier Coutanceau]] || 1 || 0 || 0 || 0 || multimedia
|----------------
|[[User:ArnaudC|Arnaud COFFINET]] || 0 || 0 || 1 || 2 || multimedia & domotics
|----------------
|[[User:SylvainP|Sylvain PARRINO]] || 2 || 1 || 0 || 0 || robotics
|----------------
|[[User:AurelienH|Aurélien HIRON]] || 2 || 0 || 0 || 1 || robotics
|----------------
|[[User:GuillaumeT|Guillaume TRANNOY]] || 0 || 0 || 0 || 2 || domotics & robotics
|----------------
|[[User:JulienN|Julien NICOLAS / jujun]] || 2 || 1 || 0 || 1 || multimedia & network
|----------------
|[[User:StephaneF|Stéphane Falck]] || 0 || 0 || 0 || 0 || multimedia & robotics & domotics
|----------------
|[[User:GillesD|Gilles DUSSIN/ Sellig]] || 1 || 0 || 1 || 1 || robotics
|----------------
|[[User:MaximeL|Maxime Liron]] || 0 || 0 || 0 || 0 || domotics, robotics & multimedia
|----------------
|[[User:NicolasC|Nicolas CHARLERY/ realniko]] || 2 || 0 || 0 || 0 || electronic
|----------------
|[[User:BenoitJ|Benoit JESTER]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:FabienM|Fabien MARTEAU/ FabM]] || 1 || 2 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|[[User:JeanBaptisteMa| Jean-Baptiste Maillet]] || 2 || 1 || 0 || 0 || system
|----------------
|[[User:JeanFrancoisR| Jean-François Rousval]] || 2 || 1 || 0 || 1 ||
|----------------
|[[User:JulienPeeters| Julien Peeters]] || 2 || 1 || 0 || 0 || domotics, real-time, entertainment, network
|----------------
|[[User:YoannC| Yoann Congal / Alpheb]] || 0 || 0 || 0 || 1 || robotics
|----------------
|[[User:MatthieuT| Matthieu Texier / weeber]] || 1 || 0 || 1 || 0 || robotics, real-time
|----------------
|[[User:MartialG| Martial Guex]] || 2 || 1 || 1 || 2 || transceiver RF, real-time, wireless
|----------------
|[[User:NicolasL| Nicolas Lantz]] || 2 || 2 || 1 || 1 ||
|----------------
|[[User:GuillaumeD| Guillaume DELVIT]] || 1 || 1 || 1 || 1 || system, asynchronous CPU
|----------------
|[[User:BernardR|Bernard REMOND ]] || x || x || x || x ||
|----------------
|[[User:SamirH| Samir HAMNACHE]] || 0 || 0 || 0 || 1 || électronique
|----------------
|[[User:OlivierT|Olivier TARDIEU]] || 0 || 0 || 0 || 1 || électronique,robotics,domotics
|----------------
|[[User:ThibautR|Thibault Rétornaz]] || 1 || 1 || 1 || 0 || bio-med, électronique
|----------------
|[[User:FrancoisM|Francois Minaud]] || 1 || 1 || 1 || 0 || domotics, real-time, network
|----------------
|[[User:BrunoS|Bruno Suarez]] || 2 || 0 || 0 || 0 || électronique, Network
|----------------
|[[User:guillaumeDe|Guillaume Denis]] || 0 || 0 || 2 || 1 || Electronique numérique, FPGA
|----------------
|[[User:KevinP|Kévin PETIT]] || 1 || 0 || 1 || 1 || Multimedia
|----------------
|[[User:PierreBa|Pierre Baudemont / b4ud3]] || 2 || 0 || 1 || 0 || domotics, robotics
|----------------
|[[User:BrunoL|Bruno Landré]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:AntonioMB|Antonio Meléndez]] || 0 || 0 || 1 || 2 || domotics, robotics, eletcronics
|----------------
|[[User:MichelTe|Michel Le Mer]] || 0 || 0 || 2 || 2 || electronics, software
|----------------
|[[User:JulienBa|Julien Baley]] || 0 || 0 || 0 || 0 ||
|----------------
|[[User:FrankA|Frank ANJEAUX]] || 1 || 0 || 0 || 1 || software,robotics, domotics, electronics
|----------------
|[[User:JulienViaud|Julien viaud/polric]] || 2 || 0 || 1 || 1 ||
|----------------
|[[User:NicolasCa|Nicolas CARTIER]] || 1 || 1 || 0 || 2 || domotics & robotics
|----------------
|[[User:PierreAlexandreS|Pierre Alexandre SCHEMBRI]] || 2 || 1 || 2 || 2 || electronics, board design, embedded software, FPGA, robotics, low power
|----------------
|[[User:AlexG|Alex GONZALEZ]] || 2 || 2 || 0 || 1 || telecommunications, network & multimedia
|----------------
|[[User:JulienL|Julien Lefrique / apapi]] || 1 || 0 || 1 || 1 ||
|----------------
|[[User:PaoloB|Paolo Bernini / nihil84]] || 2 || 1 || 0 || 0 || robotics, real-time
|----------------
|[[User:MichielE|Michiel Ettema]] || 0 || 0 || 0 || 1 || telecommunications, networking
|----------------
|[[User:NicolasD|Nicolas Duclos]] || 2 || 1 || 0 || 0 || telecommunications, domotics and funs
|----------------
|[[User:SebastienP|Sebastien Philippe]] || 1 || 2 || 1 || 2 || electronics, board design, embedded linux
|----------------
|[[User:PaulM|Paul MONSINJON]] || 1 || 1 || 2 || 1 || robotics, fpga, embedded linux
|----------------
|[[User:OlivierR|Olivier REYNET]] || 1 || 0 || 0 || 0 || robotics, linux, networking
|----------------
|[[User:HugoP|Hugo Petit]] || 0 || 0 || 1 || 2 || electronics, automotive, board design, embedded software
|----------------
|[[User:PhilippeL|Philippe Leduc]] || 1 || 0 || 1 || 1 || robotics, real-time, embedded software, domotic
|----------------
|[[User:PierreDe|Pierre Delarboulas]] || 1 || 1 || 0 || 0 || robotics, domotic
|----------------
|[[User:WilliamB|William Benharbone]] || 0 || 0 || 1 || 1 || electronics, board design and funs
|----------------
|[[User:JeanJacquesP|JeanJacques Pitrolle]] || 2 || 1 || 0 || 0 || embedded software, robotics
|----------------
|[[User:SebastienVC|Sébastien Van Cauwenberghe]] || 2 || 2 || 2 || 0 || Power Electronics, Embedded Systems, FPGA's
|----------------
|[[User:PhilBB|Phil Bergeron-Burns]] || 0 || 0 || 2 || 0 || bio-medical
|----------------
|[[User:JaumeF|Jaume Figueras i Jové]] || 0 || 0 || 2 || 0 || academic, mapping
|----------------
|[[User:MathieuB|Mathieu Boucher]] || 1 || 2 || 1 || 0 ||
|----------------
|[[User:SamuelM|Samuel Martin / smartin]] || 2 || 0 || 1 || 1 || embedded systems, real-time, robotics, multimedia
|----------------
|[[User:GaelV|Gaël Vanderbruggen]] || 1 || 0 || 0 || 0 || bio-medical, robotics, multimedia
|----------------
|[[User:JeanMarcM| pieddemamouth/Jean-Marc Montanier]] || 1 || 0 || 0 || 1 || robotics
|----------------
|[[User:ChaoyiH| Chaoyi HU]] || 1 || 0 || 0 || 2 || entertainement, telecommunications, electronic
|}

==Links==
* [[Members | Geographical position of the members]]

[[Category:Association]]

User:SamuelM

2011-07-24T11:08:40Z

SamuelM: /* u-boot configuration */

[[MemberList | << Member list]]

[[Special:UserList | << User list]]

== whoami ==

* Name:
:: Samuel MARTIN

* Background:
:: <s>Student at [http://www.eseo.fr/ ESEO] (French engineering school), specialised in Embedded systeme and Automation /</s>
:: <s>Master student at l'[http://www.plymouth.ac.uk/ University of Plymouth] (UK), in [http://www.plymouth.ac.uk/courses/postgraduate/taught/2558/MSc+Robotics Robotics].</s>
:: Embedded and System Engineer (Paris, France)

== Interests ==
* Robotics
* Computer Vision
* Image & signal processing
* Linux

== Objectives ==
''or, what I wanna do with the APF board (APF27 + Devfull)''
* '''Have fun!'''
* Improve my skills in:
** Hardware development (FPGA)
** System and embedded OS
** Electronic development
** Software development for embedded (tiny) target
* Share my experiments

== Contributions ==
[[OpenCV|Cross-compile OpenCV for your APF]]

[[CMake]]

== Tips ==
=== A colored (and useful) prompt ===
''zsh and [http://www.ctaf.free.fr/dokuwiki/doku.php?id=ctafconf ctafconf] users won't be lost'' ;-)
<source lang="bash">
##
## ~/.profile
##
source /etc/profile

## Enhanced promt
if [ -t 0 ]; then
bldblk='\033[1;30m' # Black - Bold
bldred='\033[1;31m' # Red
bldgrn='\033[1;32m' # Green
bldylw='\033[1;33m' # Yellow
bldblu='\033[1;34m' # Blue
bldpur='\033[1;35m' # Purple
bldcyn='\033[1;36m' # Cyan
bldwht='\033[1;37m' # White
txtrst='\033[0m' # Text Reset
undred='\033[4;31m' # Red - Underlined
bgdred='\033[1;41m' # Red - Background
bgdblu='\033[1;44m' # Blue - Background
fi;
if [ $(id -u) -eq 0 ]; then
userbgd="${bgdred}"
else
userbgd="${bgdblu}"
fi

export PS1="${userbgd}\u${bldylw}@${bldgrn}\h${txtrst} ${bldpur}[\$(eval \"res=\$?\"; [ \${res}$
</source>

=== u-boot configuration ===

# ''nfs-boot'' (kernel and rootfs), if the nfs server is alive
# ''boot from the NAND flash'', otherwise

==== u-boot environment ====

<pre class="apf">
BIOS> setenv nfsboot 'setenv bootargs ${console} ${mtdparts}; \
run addnfsargs addipargs; \
setenv autostart yes; \
nfs ${loadaddr} {serverip}:${rootpath}/${board_name}-linux.bin; \
bootm'
BIOS> setenv addnfsargs 'setenv bootargs ${bootargs} root=/dev/nfs rw nfsroot=${serverip}:${rootpath}'
BIOS> setenv addipargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off'
BIOS> setenv bootcmd 'if ping ${serverip}; then \
echo; \
echo Boot over NFS; \
echo; \
run nfsboot; \
else \
echo; \
echo Boot from the board; \
run jffsboot; \
fi'
BIOS> setenv board_name apf27
BIOS> setenv netmask 255.255.255.0
BIOS> setenv serverip 192.168.10.2
BIOS> setenv gatewayip 192.168.10.1
BIOS> setenv ipaddr 192.168.10.10
BIOS> setenv rootpath /path/to/where/you/untar/your/rootfs
BIOS> saveenv
BIOS> boot
</pre>

Adjust the <tt>bootdelay</tt> if needed.

Next boot will automatically try to boot over NFS, then fallback on the NAND flash

{{Warning|

If the '''NFS server is alive''', but neither the '''linux kernel image nor the rootfs'''
are '''NOT at the expected location''': ''/path/to/where/you/untar/your/rootfs'',

the boot will hang up, so '''booting will fail''' !}}

==== NFS server configuration ====

Refer to the [[Network File System configuration|NFS wiki page]] to setting the NFS server up.

Then:

* untar the rootfs tarball in ''/path/to/where/you/untar/your/rootfs''
* copy the linux kernel image to ''/path/to/where/you/untar/your/rootfs''

<pre class="host">
sudo tar xvf apf27-rootfs.tar -C /path/to/where/you/untar/your/rootfs
sudo -fv cp apf27-linux.bin /path/to/where/you/untar/your/rootfs
</pre>

User:SamuelM

2011-07-24T10:23:25Z

SamuelM: tips: fix prompt, add my u-boot config

[[MemberList | << Member list]]

[[Special:UserList | << User list]]

== whoami ==

* Name:
:: Samuel MARTIN

* Background:
:: <s>Student at [http://www.eseo.fr/ ESEO] (French engineering school), specialised in Embedded systeme and Automation /</s>
:: <s>Master student at l'[http://www.plymouth.ac.uk/ University of Plymouth] (UK), in [http://www.plymouth.ac.uk/courses/postgraduate/taught/2558/MSc+Robotics Robotics].</s>
:: Embedded and System Engineer (Paris, France)

== Interests ==
* Robotics
* Computer Vision
* Image & signal processing
* Linux

== Objectives ==
''or, what I wanna do with the APF board (APF27 + Devfull)''
* '''Have fun!'''
* Improve my skills in:
** Hardware development (FPGA)
** System and embedded OS
** Electronic development
** Software development for embedded (tiny) target
* Share my experiments

== Contributions ==
[[OpenCV|Cross-compile OpenCV for your APF]]

[[CMake]]

== Tips ==
=== A colored (and useful) prompt ===
''zsh and [http://www.ctaf.free.fr/dokuwiki/doku.php?id=ctafconf ctafconf] users won't be lost'' ;-)
<source lang="bash">
##
## ~/.profile
##
source /etc/profile

## Enhanced promt
if [ -t 0 ]; then
bldblk='\033[1;30m' # Black - Bold
bldred='\033[1;31m' # Red
bldgrn='\033[1;32m' # Green
bldylw='\033[1;33m' # Yellow
bldblu='\033[1;34m' # Blue
bldpur='\033[1;35m' # Purple
bldcyn='\033[1;36m' # Cyan
bldwht='\033[1;37m' # White
txtrst='\033[0m' # Text Reset
undred='\033[4;31m' # Red - Underlined
bgdred='\033[1;41m' # Red - Background
bgdblu='\033[1;44m' # Blue - Background
fi;
if [ $(id -u) -eq 0 ]; then
userbgd="${bgdred}"
else
userbgd="${bgdblu}"
fi

export PS1="${userbgd}\u${bldylw}@${bldgrn}\h${txtrst} ${bldpur}[\$(eval \"res=\$?\"; [ \${res}$
</source>

=== u-boot configuration ===

# ''nfs-boot'' (kernel and rootfs), if the nfs server is alive
# ''boot from the NAND flash'', otherwise

==== u-boot environment ====

<pre class="apf">
BIOS> setenv nfsboot 'setenv bootargs ${console} ${mtdparts}; \
run addnfsargs addipargs; \
setenv autostart yes; \
nfs ${loadaddr} {serverip}:${rootpath}/${board_name}-linux.bin; \
bootm'
BIOS> setenv addnfsargs 'setenv bootargs ${bootargs} root=/dev/nfs rw nfsroot=${serverip}:${rootpath}'
BIOS> setenv addipargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off'
BIOS> setenv bootcmd 'if ping ${serverip}; then \
echo; \
echo Boot over NFS; \
echo; \
run nfsboot; \
else \
echo; \
echo Boot from the board; \
run jffsboot; \
fi'
BIOS> setenv board_name apf27
BIOS> setenv netmask 255.255.255.0
BIOS> setenv serverip 192.168.10.2
BIOS> setenv gatewayip 192.168.10.1
BIOS> setenv ipaddr 192.168.10.10
BIOS> setenv rootpath /path/to/where/you/untar/your/rootfs
BIOS> saveenv
BIOS> boot
</pre>

Adjust the <tt>bootdelay</tt> if needed.

Next boot will automatically try to boot over NFS, then fallback on the NAND flash

{{Warning|

If the '''NFS server is alive''', but neither the '''linux kernel image nor the rootfs'''
are '''NOT at the expected location''' (<tt>/path/to/where/you/untar/your/rootfs</tt>),

the boot will hang up, '''booting will fail''' !}}

==== NFS server configuration ====

Refer to the [[Network File System configuration|NFS wiki page]] to setting the NFS server up.

Then:

* untar the rootfs tarball in <tt>/path/to/where/you/untar/your/rootfs</tt>
* copy the linux kernel image to <tt>/path/to/where/you/untar/your/rootfs</tt>

<pre class="host">
sudo tar xvf apf27-rootfs.tar -C /path/to/where/you/untar/your/rootfs
sudo -fv cp apf27-linux.bin /path/to/where/you/untar/your/rootfs
</pre>

Buildroot Mainline integration

2011-03-12T10:58:57Z

SamuelM: /* Patches that can be sent to BR */

User:SamuelM

2010-12-05T18:40:34Z

SamuelM: /* A colored (and useful) prompt */

User:SamuelM

2010-11-11T13:36:49Z

SamuelM: /* whoami */

OpenCV

2010-06-07T23:49:30Z

SamuelM: fix links

{{Under_Construction}}
== Forewords ==
This page explains how to (cross-)compile [http://opencv.willowgarage.com/wiki OpenCV 2.1.0] for your APF-board.

== Pre-requisite ==
You need to have [[CMake]] >=2.6 installed on your system.

== Build OpenCV ==
# Edit your [[CMake#The_toolchain_file| toolchain.cmake file]]
# Create source and build directories <source lang="bash">
mkdir -pv opencv-on-armadeus/{src,build}
</source>
# Grab the source archive <source lang="bash">
cd opencv-on-armadeus/src && wget http://sourceforge.net/projects/opencvlibrary/files/opencv-unix/2.1/OpenCV-2.1.0.tar.bz2/dowload && tar xvvjf OpenCV-2.1.0.tar.bz2
</source>
# Here, you'll have to apply [[#OpenCV-2.1.0.patch| this patch]] to avoid compilation failed: <source lang="bash">
patch -p0 < OpenCV-2.1.0.patch
</source>
# Run CMake (generate Makefiles)
## <source lang="bash">
cd ~/opencv-on-armadeus/build && cmake -DCMAKE_TOOLCHAIN_FILE:PATH=/path/to/toolchain.cmake ../src/OpenCV-2.1.0
</source>
##It will certainly complain about unfound libraries and some other things, so adjust these things running:<source lang="bash">
cmake-gui
</source>
# Compile OpenCV libraries <source lang="bash">
VERBOSE=1 make
</source>

{{Note|'''cmake-gui'''

* Click twice on ''Configure'' when you change something.
* When configuring exit without any error, click on ''Generate'' to generate Makefiles.
* If your configuration is too messy, reset it by deleting the cache (File/Delete Cache) or remove the ''CMakeCache.txt'' file in the build directory. Don't hesitate to do so if something (eg. paths) is wrong ;)
* To see the ''cmake-command'' that corresponds to the configuration you have just set in cmake-gui: Tools/Show my changes
}}

=== Available features ===
CMake looks for all required tool in the path specified in [[CMake#The_toolchain_file| toolchain.cmake file]] toolchain.cmake file; therefore, some options, targets, libraries, ... are not available:

* Build:
** Latex Doc : Not available in Buildroot
** New Python support : Not available (require Python >=2.6, Buildroot provides Python 2.4)
** Swing Python support : Not available (require Python >=2.6, Buildroot provides Python 2.4)
** Octave support : Not available in Buildroot
* Python
** Executable : Not found (require Python >=2.6, Buildroot provides Python 2.4)
** Include dirs. : Found
** Library : Not found (require Python >=2.6, Buildroot provides Python 2.4)
* With
** V4L : Disable it (Buildroot provides it, but linker failed)
* OpenCV
** 3rd party libs. : You can enable it.

{{Note|You may need to enable some packages in your Armadeus configuration to get some libraries (libjpeg, libpng and libtiff) found by CMake.}}

== Run OpenCV applications on your APF-board ==
# In the ''build'' directory, you should find a ''bin'' and a ''lib'' sub-directories. Copy them (at least the ''lib'' directory) on your target.
# <source lang="bash">
export LD_LIBRARY_PATH=/path/to/the/OpenCVlibdir
</source>
# Run your application. You can try ''cvtest'' (some tests may fail because of missing resources), it will take a while... a long while ;)

== See also ==
* [http://opencv.willowgarage.com/wiki/InstallGuide OpenCV install guide]

== Appendices ==
=== OpenCV-2.1.0.patch ===
<source lang="diff">
--- OpenCV-2.1.0/3rdparty/flann/constants.h.origin 2010-06-08 01:14:22.171416516 +0200
+++ OpenCV-2.1.0/3rdparty/flann/constants.h 2010-06-08 01:15:06.912417891 +0200
@@ -41,7 +41,7 @@ enum flann_algorithm_t {
KMEANS = 2,
COMPOSITE = 3,
SAVED = 254,
- AUTOTUNED = 255,
+ AUTOTUNED = 255
};

enum flann_centers_init_t {
--- OpenCV-2.1.0/3rdparty/flann/flann.h.origin 2010-06-08 01:14:32.588443815 +0200
+++ OpenCV-2.1.0/3rdparty/flann/flann.h 2010-06-08 01:15:06.912417891 +0200
@@ -267,7 +267,7 @@ LIBSPEC int flann_compute_cluster_center

#ifdef __cplusplus
-};
+}

#include "flann.hpp"
--- OpenCV-2.1.0/3rdparty/include/flann/constants.h.origin 2010-06-08 01:14:54.503416676 +0200
+++ OpenCV-2.1.0/3rdparty/include/flann/constants.h 2010-06-08 01:15:06.912417891 +0200
@@ -41,7 +41,7 @@ enum flann_algorithm_t {
KMEANS = 2,
COMPOSITE = 3,
SAVED = 254,
- AUTOTUNED = 255,
+ AUTOTUNED = 255
};

enum flann_centers_init_t {
--- OpenCV-2.1.0/3rdparty/include/flann/flann.h.origin 2010-06-08 01:14:44.672417690 +0200
+++ OpenCV-2.1.0/3rdparty/include/flann/flann.h 2010-06-08 01:15:06.912417891 +0200
@@ -267,7 +267,7 @@ LIBSPEC int flann_compute_cluster_center

#ifdef __cplusplus
-};
+}

#include "flann.hpp"
</source>

[[Category: Software]]
[[Category: Video]]

CMake

2010-06-07T23:45:37Z

SamuelM: fix links

{{Under_Construction}}
== Forewords ==
Cmake is a utility that generate Makefile for your projects. Therefore, it does not need to be cross-compiled.

== Configure a project using CMake ==

=== The toolchain file ===
This file describes the (cross-)toolchain required to compile projects managed with CMake.

Copy-paste the following lines in a *.cmake file and set the variables of
"Armadeus subsection" accordingly to your configuration.

<source lang="bash">
##
## toolchain.cmake
##

## ==== Settings Section ====

## ---- Armadeus subsection ----
# set the Armadeus board (comments/uncomment according to your board)
set(ARMADEUS_BOARD "APF27")
# set(ARMADEUS_BOARD "APF9328")

# set the uClibc version
set(ARMADEUS_UCLIBC_VERSION "0.9.29")

# set the Armadeus root path
set(ARMADEUS_ROOT "/path/to/your/armadeus/sdk")

## ---- CMake subsection ----
# this one is important
set(CMAKE_SYSTEM_NAME "Linux")
# this one not so much
set(CMAKE_SYSTEM_VERSION "1")

## ==== CMake Variables ====

if(ARMADEUS_BOARD STREQUAL "APF27")
set(ARMADEUS_MARCH "armv5te")
elseif(ARMADEUS_BOARD STREQUAL "APF9328")
set(ARMADEUS_MARCH "armv4t")
else(ARMADEUS_BOARD STREQUAL "APF27")
message("\n"
"===========================================================\n"
"= Cannot determine the target =\n"
"===========================================================\n"
)
endif(ARMADEUS_BOARD STREQUAL "APF27")

set(ARMADEUS_ROOT_BR ${ARMADEUS_ROOT}/buildroot)
set(ARMADEUS_ROOT_CTC ${ARMADEUS_ROOT_BR}/build_${ARMADEUS_MARCH}/staging_dir)
set(ARMADEUS_ROOT_CTC_BINDIR ${ARMADEUS_ROOT_CTC}/usr/bin)
set(ARMADEUS_CTC_PREFIX "arm-linux-")

# specify the cross-toolchain (compiler, header and library directories)
set(CMAKE_C_COMPILER ${ARMADEUS_ROOT_CTC_BINDIR}/${ARMADEUS_CTC_PREFIX}gcc)
set(CMAKE_CXX_COMPILER ${ARMADEUS_ROOT_CTC_BINDIR}/${ARMADEUS_CTC_PREFIX}g++)
set(CMAKE_INCLUDE_PATH ${ARMADEUS_ROOT_BR}/toolchain_build_${ARMADEUS_MARCH}/uClibc-${ARMADEUS_UCLIBC_VERSION}/include)
set(CMAKE_LIBRARY_PATH ${ARMADEUS_ROOT_CTC})

set(CMAKE_FIND_ROOT_PATH ${ARMADEUS_ROOT_CTC} ${CMAKE_INCLUDE_PATH})

# search for programs in the build host directories
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY)
# for libraries and headers in the target directories
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
</source>

This file should be generated by Buildroot at the time of the Armadeus SDK setup.

=== Run CMake ===
TODO

Goto [[OpenCV#Build_OpenCV| here]] for an example (step #5)

== Use CMake in your a project ==
TODO

Goto [https://code.ros.org/trac/opencv/browser/tags/2.1/opencv/samples/c/example_cmake here] for an example

== See also ==
* [http://www.cmake.org/cmake/help/documentation.html Cmake documentation]
* Examples provided by existing projects ([https://code.ros.org/trac/opencv/browser/tags/2.1/opencv/samples/c/example_cmake example from OpenCV])

== Thanks ==
Thanks to Ctaf42 for his help about CMake.

[[Category: Software]]
[[Category: Toolchain]]

OpenCV

2010-06-07T23:37:27Z

SamuelM: Add OpenCV patch and runtime details

{{Under_Construction}}
== Forewords ==
This page explains how to (cross-)compile [http://opencv.willowgarage.com/wiki| OpenCV 2.1.0] for your APF-board.

== Pre-requisite ==
You need to have [[CMake]] >=2.6 installed on your system.

== Build OpenCV ==
# Edit your [[CMake#The_toolchain_file| toolchain.cmake file]]
# Create source and build directories <source lang="bash">
mkdir -pv opencv-on-armadeus/{src,build}
</source>
# Grab the source archive <source lang="bash">
cd opencv-on-armadeus/src && wget http://sourceforge.net/projects/opencvlibrary/files/opencv-unix/2.1/OpenCV-2.1.0.tar.bz2/dowload && tar xvvjf OpenCV-2.1.0.tar.bz2
</source>
# Here, you'll have to apply [[#OpenCV-2.1.0.patch| this patch]] to avoid compilation failed: <source lang="bash">
patch -p0 < OpenCV-2.1.0.patch
</source>
# Run CMake (generate Makefiles)
## <source lang="bash">
cd ~/opencv-on-armadeus/build && cmake -DCMAKE_TOOLCHAIN_FILE:PATH=/path/to/toolchain.cmake ../src/OpenCV-2.1.0
</source>
##It will certainly complain about unfound libraries and some other things, so adjust these things running:<source lang="bash">
cmake-gui
</source>
# Compile OpenCV libraries <source lang="bash">
VERBOSE=1 make
</source>

{{Note|'''cmake-gui'''

* Click twice on ''Configure'' when you change something.
* When configuring exit without any error, click on ''Generate'' to generate Makefiles.
* If your configuration is too messy, reset it by deleting the cache (File/Delete Cache) or remove the ''CMakeCache.txt'' file in the build directory. Don't hesitate to do so if something (eg. paths) is wrong ;)
* To see the ''cmake-command'' that corresponds to the configuration you have just set in cmake-gui: Tools/Show my changes
}}

=== Available features ===
CMake looks for all required tool in the path specified in [[CMake#The_toolchain_file| toolchain.cmake file]] toolchain.cmake file; therefore, some options, targets, libraries, ... are not available:

* Build:
** Latex Doc : Not available in Buildroot
** New Python support : Not available (require Python >=2.6, Buildroot provides Python 2.4)
** Swing Python support : Not available (require Python >=2.6, Buildroot provides Python 2.4)
** Octave support : Not available in Buildroot
* Python
** Executable : Not found (require Python >=2.6, Buildroot provides Python 2.4)
** Include dirs. : Found
** Library : Not found (require Python >=2.6, Buildroot provides Python 2.4)
* With
** V4L : Disable it (Buildroot provides it, but linker failed)
* OpenCV
** 3rd party libs. : You can enable it.

{{Note|You may need to enable some packages in your Armadeus configuration to get some libraries (libjpeg, libpng and libtiff) found by CMake.}}

== Run OpenCV applications on your APF-board ==
# In the ''build'' directory, you should find a ''bin'' and a ''lib'' sub-directories. Copy them (at least the ''lib'' directory) on your target.
# <source lang="bash">
export LD_LIBRARY_PATH=/path/to/the/OpenCVlibdir
</source>
# Run your application. You can try ''cvtest'' (some tests may fail because of missing resources), it will take a while... a long while ;)

== See also ==
* [http://opencv.willowgarage.com/wiki/InstallGuide| OpenCV install guide]

== Appendices ==
=== OpenCV-2.1.0.patch ===
<source lang="diff">
--- OpenCV-2.1.0/3rdparty/flann/constants.h.origin 2010-06-08 01:14:22.171416516 +0200
+++ OpenCV-2.1.0/3rdparty/flann/constants.h 2010-06-08 01:15:06.912417891 +0200
@@ -41,7 +41,7 @@ enum flann_algorithm_t {
KMEANS = 2,
COMPOSITE = 3,
SAVED = 254,
- AUTOTUNED = 255,
+ AUTOTUNED = 255
};

enum flann_centers_init_t {
--- OpenCV-2.1.0/3rdparty/flann/flann.h.origin 2010-06-08 01:14:32.588443815 +0200
+++ OpenCV-2.1.0/3rdparty/flann/flann.h 2010-06-08 01:15:06.912417891 +0200
@@ -267,7 +267,7 @@ LIBSPEC int flann_compute_cluster_center

#ifdef __cplusplus
-};
+}

#include "flann.hpp"
--- OpenCV-2.1.0/3rdparty/include/flann/constants.h.origin 2010-06-08 01:14:54.503416676 +0200
+++ OpenCV-2.1.0/3rdparty/include/flann/constants.h 2010-06-08 01:15:06.912417891 +0200
@@ -41,7 +41,7 @@ enum flann_algorithm_t {
KMEANS = 2,
COMPOSITE = 3,
SAVED = 254,
- AUTOTUNED = 255,
+ AUTOTUNED = 255
};

enum flann_centers_init_t {
--- OpenCV-2.1.0/3rdparty/include/flann/flann.h.origin 2010-06-08 01:14:44.672417690 +0200
+++ OpenCV-2.1.0/3rdparty/include/flann/flann.h 2010-06-08 01:15:06.912417891 +0200
@@ -267,7 +267,7 @@ LIBSPEC int flann_compute_cluster_center

#ifdef __cplusplus
-};
+}

#include "flann.hpp"
</source>

[[Category: Software]]
[[Category: Video]]

User:SamuelM

2010-06-07T20:35:04Z

SamuelM:

OpenCV

2010-06-04T23:30:03Z

SamuelM: Adjust links

CMake

2010-06-04T23:27:31Z

SamuelM: Create page

{{Under_Construction}}
== Forewords ==
Cmake is a utility that generate Makefile for your projects. Therefore, it does not need to be cross-compiled.

== Configure a project using CMake ==

=== The toolchain file ===
This file describes the (cross-)toolchain required to compile projects managed with CMake.

Copy-paste the following lines in a *.cmake file and set the variables of
"Armadeus subsection" accordingly to your configuration.

<source lang="bash">
##
## toolchain.cmake
##

## ==== Settings Section ====

## ---- Armadeus subsection ----
# set the Armadeus board (comments/uncomment according to your board)
set(ARMADEUS_BOARD "APF27")
# set(ARMADEUS_BOARD "APF9328")

# set the uClibc version
set(ARMADEUS_UCLIBC_VERSION "0.9.29")

# set the Armadeus root path
set(ARMADEUS_ROOT "/path/to/your/armadeus/sdk")

## ---- CMake subsection ----
# this one is important
set(CMAKE_SYSTEM_NAME "Linux")
# this one not so much
set(CMAKE_SYSTEM_VERSION "1")

## ==== CMake Variables ====

if(ARMADEUS_BOARD STREQUAL "APF27")
set(ARMADEUS_MARCH "armv5te")
elseif(ARMADEUS_BOARD STREQUAL "APF9328")
set(ARMADEUS_MARCH "armv4t")
else(ARMADEUS_BOARD STREQUAL "APF27")
message("\n"
"===========================================================\n"
"= Cannot determine the target =\n"
"===========================================================\n"
)
endif(ARMADEUS_BOARD STREQUAL "APF27")

set(ARMADEUS_ROOT_BR ${ARMADEUS_ROOT}/buildroot)
set(ARMADEUS_ROOT_CTC ${ARMADEUS_ROOT_BR}/build_${ARMADEUS_MARCH}/staging_dir)
set(ARMADEUS_ROOT_CTC_BINDIR ${ARMADEUS_ROOT_CTC}/usr/bin)
set(ARMADEUS_CTC_PREFIX "arm-linux-")

# specify the cross-toolchain (compiler, header and library directories)
set(CMAKE_C_COMPILER ${ARMADEUS_ROOT_CTC_BINDIR}/${ARMADEUS_CTC_PREFIX}gcc)
set(CMAKE_CXX_COMPILER ${ARMADEUS_ROOT_CTC_BINDIR}/${ARMADEUS_CTC_PREFIX}g++)
set(CMAKE_INCLUDE_PATH ${ARMADEUS_ROOT_BR}/toolchain_build_${ARMADEUS_MARCH}/uClibc-${ARMADEUS_UCLIBC_VERSION}/include)
set(CMAKE_LIBRARY_PATH ${ARMADEUS_ROOT_CTC})

set(CMAKE_FIND_ROOT_PATH ${ARMADEUS_ROOT_CTC} ${CMAKE_INCLUDE_PATH})

# search for programs in the build host directories
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY)
# for libraries and headers in the target directories
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
</source>

This file should be generated by Buildroot at the time of the Armadeus SDK setup.

=== Run CMake ===
TODO

Goto [[OpenCV#Build_OpenCV| here]] for an example

== Use CMake in your a project ==
TODO

Goto [https://code.ros.org/trac/opencv/browser/tags/2.1/opencv/samples/c/example_cmake| here] for an example

== See also ==
* [[http://www.cmake.org/cmake/help/documentation.html| Cmake documentation]]
* Examples provided by existing projects ([https://code.ros.org/trac/opencv/browser/tags/2.1/opencv/samples/c/example_cmake| example from OpenCV])

== Thanks ==
Thanks to Ctaf42 for his help about CMake.

OpenCV

2010-06-04T23:04:47Z

SamuelM: Create page

2009-07-21T19:41:18Z

SamuelM:

= Identité =

* Nom:
:: Samuel MARTIN

* Profession:
:: Etudiant en dernière année d'école d'ingénieur à l'[http://www.eseo.fr/ ESEO], spécialité Systèmes embarqués et Automatisme /
:: Master student à l'[http://www.plymouth.ac.uk/ University of Plymouth] (UK), section [http://www.plymouth.ac.uk/courses/postgraduate/taught/2558/MSc+Robotics Robotics].

= Centre d'intérêts =
* Robotique
* Computer Vision
* Image & signal processing
* Linux

= Objectifs =
''(ou ce que je souhaite faire avec l'APF)''
# Acquérir une APF asap
* '''Have fun!'''
* Développer mes compétences:
** Développement hardware (FPGA)
** Systèmes et OS embarqués
** Développement électronique
* Apporter ma ''petite'' contribution à l'ARMadeus Project dans la mesure de mes ''faible'' moyens

User:SamuelM

2009-07-21T19:39:36Z

SamuelM: Création userpage

= Identité =

* Nom:
:: Samuel MARTIN

* Profession:
:: Etudiant en dernière année d'école d'ingénieur à l'[http://www.eseo.fr/ ESEO], spécialité Systèmes embarqués et Automatisme /
:: Master student à l'[http://www.plymouth.ac.uk/ University of Plymouth] (UK), section [http://www.plymouth.ac.uk/courses/postgraduate/taught/2558/MSc+Robotics Robotics].

= Centre d'intérêts =
* Robotique
* Computer Vision
* Image & signal processing
* Linux

= Objectifs (ou ce que je souhaite faire avec l'APF) =
# Acquérir une APF asap
* '''Have fun!'''
* Développer mes compétences:
** Développement hardware (FPGA)
** Systèmes et OS embarqués
** Développement électronique
* Apporter ma ''petite'' contribution à l'ARMadeus Project dans la mesure de mes ''faible'' moyens