ArmadeusWiki - User contributions [en]

Buildroot Mainline integration

2013-08-29T19:53:06Z

FrancoisG:

{{Under Construction}}

==Changes since BR version used in armadeus 3.x==
===default packages===
* uClibc: 0.9.29 -> 0.9.30 -> 0.9.33.2
* gcc: 4.2.1-> 4.4.5 -> 4.7.2
* busybox: 1.6.2 -> 1.20.2 -> 1.21
* U-Boot: 2012.10 -> 2013.04

===build directories===
* ''build_arm_xxx/'' ''project_build_xxx/'' ''toolchain_build_arm_xxx/'' have been removed and replaced by ''output/'':
<pre class="host">
build host images stamps target toolchain
</pre>

===configs===
* buildroot default configs are now stored in ''buildroot/configs/apfxx_defconfig'' and no more in ''buildroot/target/device/armadeus/apfxx/apfxx_defconfig''
* uClibc config should be named with version number to not overwrite the old one -->
''buildroot/target/device/armadeus/apf27/uClibc-0.9.30.config.arm''
* idem for U-Boot config:
''buildroot/target/device/armadeus/apf27/apf27-u-boot-2010.03.h''

==Changes since BR version used in armadeus 4.x==
* TBDL

==How to use new BR in armadeus==
* checkout a recent clean GIT view and before any other command edit the main Makefile to change the BUILDROOT_VERSION flag from 2012.02 to 20121030
** comment line 29
** uncomment the line 30
* then you can use it as old BR:
<pre class="host">
$ make apf27_defconfig
$ make
</pre>
* new patches dirrectory:
patches/buildroot/2012.11/

==Patches that can be sent to BR==
(Some will require some cleanup)
===Instructions===
* Patches to port: ''patches/buildroot/2010.11''
* when working on a patch mark it with:
** <nowiki> ** '''In progress''' ~~~~ </nowiki>
** '''-->''' '''In progress''' [[User:JulienB|JulienB]] 14:14, 9 November 2010 (UTC)
* Strike the one that are no more needed:
** <strike> 000-xxxxxxx.patch </strike>
* Write OK in bold green and your name (automatic with 4x'~') when corresponding patch has been ported:
** <nowiki> ** '''OK''' ~~~~ </nowiki>
** '''-->''' 000-xxxxxxx.patch: '''OK''' [[User:JulienB|JulienB]] 07:06, 21 October 2010 (UTC)
* How to:
** get a BR git
** try to apply patch with ''patch -p1 --dry-run < patch_name.patch''
** when it applies remove ''--dry-run'', commit, generates patch with [[GIT]] and send it to BR

===001 -> 059===
* 001-add_armadeus_device.patch -- armadeus specific
* 002-add_armadeus_specific_packages.patch -- armadeus specific
* 003-armadeus-ltrace-fix-download-url.patch
* 004-gilliland-ti-utils-fix-github-tarball-to-use-commit-id.patch
* 005-armadeus-gpsd-add-options-setting-in-menuconfig.patch
* 006-lcd4linux.patch -- broken
* 018-allegro.patch -- broken
* 021-sdl-water-config.patch -- broken
* 034-slideshow.patch -- broken
* 043-mesa-add_packages.patch -- broken
* 045-openssh-add_passwd_expire.patch
* 050-U-Boot-add_support_for_custom_configuration_file.patch
* 051-U-Boot-add_support_for_custom_binary_file_format.patch -- will be present in BR next release
* 052-U-Boot-add_support_for_Safe_Boot_file_format.patch

===060 -> 085===
* 072-xenomai-package.patch
* 081-adds_quake_package.patch ( 2nd priority package to push on the BR mainline )
* 083-pygame-armadeus_addons.patch
* 085-adds_gpm_package.patch -- broken

===095 -> 119===
* 097-adds_flite_package.patch (to push on the BR mainline - need some refactoring )
** '''In progress''' [[User:SamuelM|SamuelM]] 20:25, 3 December 2012 (UTC)
* 099-mplayer-add_patch_for_pld_asm_instruction_on_non_armv5_arch.patch
* 101-mplayer-add_patch_for_recent_alsa_compatibility.patch
* 107-games-add_wolf4sdl.patch -- broken
* 110-bluez-add_package.patch
** bluez-utils-4.x (currently 4.101) already in BR (since 2011.08) with bluez3 compat knob -- [[User:SamuelM|SamuelM]] 10:49, 1 November 2012 (UTC)
* 111-bluez-hacks.patch
** bluez-utils-4.x (currently 4.101) already in BR (since 2011.08) with bluez3 compat knob -- [[User:SamuelM|SamuelM]] 10:49, 1 November 2012 (UTC)
* 118-snes9x-add_package.patch -- broken

===120 -> 179===
* 120-cwiid-add_package.patch (to push on the BR mainline - need some refactoring to be more generic)
** '''In progress''' [[User:SamuelM|SamuelM]] 12:11, 1 November 2012 (UTC)
* 121-target-arm926t_is_arm926ej-s.patch
* 123-pywebradio-add_package.patch -- broken
* 124-e-uae-add_package.patch
* 125-opentyrian-add_package.patch -- broken
* 130-lbreakout-add_package.patch -- broken ( 2nd priority package to push on the BR mainline )
** '''In progress''' [[User:JulienB|JulienB]] 21:36, 20 December 2010 (UTC)
* 131-ltetris-add_package.patch -- broken
* 132-qt-full_integration_with_cross_compiling.patch
* 134-jffs2-add_board_name_to_binary_rootfs_name.patch -- armadeus specific
* 142-ncurses-fix_compilation_with_old_hosts.patch
* 146-busybox-disable_ip_busybox_if_iproute2_buildroot.patch
* 150-alsa-utils-fix_installation_bug_on_some_host_systems.patch
* 152-<strike>uclibc-add_times_syscall_patches.patch</strike>
* 157-buildroot-allow_generic_device_selection_even_when_custom_rootfs_is_chosen.patch
* 158-setserial-bump_version.patch
* 168-libcanfestival-add_package.patch (to push on the BR mainline )
** '''In progress''' [[User:SamuelM|SamuelM]] 19:42, 1 November 2012 (UTC)
* 172-gsmmux-add_package.patch
* 174-imx-lib-add_package.patch
** partially included in BR
* 176-imx-test-add_package.patch
* 178-uboot-add-missing-UBOOT_CLEAN_CMDS.patch
* 179-e2fsprog-allow_e4defrag_build_against_old_kernel_headers.patch
===180 -> end===
* 181-qtcreator-add_package.patch
* 182-uclibc-add_accept4_declaration_fix.patch
* 183-openwrt-uclibc-add-kernel_long-declaration.patch
* 184-fsl-mm-codeclib-add_package.patch
* 186-uboot-tools-2011.03-Ignore-env_sectors-on-NOR-and-SPI-dataflash.patch
* 188-marble-add_package.patch -- broken
* 189-dbus-fix_installation.patch
* 191-madplay-requires_libintl.patch -- to fix : the legacy libintl is not supported anymore
* 196-python-crc16-add_package.patch (to push on the BR mainline )
** '''In progress''' [[User:SamuelM|SamuelM]] 20:18, 3 December 2012 (UTC)
* 197-cunit-add_package.patch (to push on the BR mainline )
** '''In progress''' [[User:SamuelM|SamuelM]] 20:18, 3 December 2012 (UTC)
* 201-armadeus-add_gnokii.patch
* 203-armadeus-add_sms_server_tools_3_package.patch
* 204-busybox-fix-snapshot.patch
* 204-wpa-supplicant-add-option-ieee80211w.patch
* 205-busybox-coreutils-stty-add-rs485-config-options.patch
* 206-joe-add_package.patch
* 207-armadeus-add_python_pyro_3.14.patch
* 208-armadeus-add_beremiz.patch
* 209-armadeus-add_matiec.patch

==How to send patches to BR==

(see the [http://elinux.org/Buildroot_how_to_contribute Buildroot - How to contribute] page)

* GIT should be installed and configured on your PC like stated [[GIT|here]]
* clone buildroot GIT:
<pre class="host">
$ git clone xxxxx buildroot_git_dev/ (TBDL)
$ cd buildroot_git_dev/
</pre>
* take patch from armadeus:
<pre class="host">
$ cp /path_to_armadeus_bsp/patches/buildroot/2011.05/0xx-name.patch .
</pre>
* create a branch to work (here ''my_work''):
<pre class="host">
$ git branch my_work
$ git checkout my_work
Switched to branch 'my_work'
$ git branch
master
* my_work
</pre>
* try patch:
<pre class="host">
$ patch -p1 --dry-run < 0xx-name.patch
</pre>
* if it works, apply it for real:
<pre class="host">
$ patch -p1 < 0xx-name.patch
</pre>
* list changes:
<pre class="host">
$ git status
</pre>
* do some more changes if needed and then save them:
<pre class="host">
... do changes ...
$ git add files_changed
... test changes ...
$ git commit -m "Summary of your work"
</pre>
* generate patch to send to BR:
<pre class="host">
$ git format-patch -M master..my_work -s
</pre>
* this will give:
<pre class="host">
0001-Summary_of_your_work.patch
</pre>
* send patch to BR:
<pre class="host">
$ git send-email --from=xxx.xxx@xxx.xx --to=buildroot@busybox.net --smtp-server=smtp.xxx.xx 0001-Summary_of_your_work.patch
</pre>
* depending on the feedbacks from BR, modify your patch:
<pre class="host">
... do changes ...
$ git diff
$ git add files_changed
$ git commit --amend
$ git format-patch -M master..my_work -s
</pre>
* adds version inside [PATCH] ex: [PATCH v2]
* adds comments after ---, ex:
<pre class="host">
From a2413db058ac3c515337102690ba12a746831f7e Mon Sep 17 00:00:00 2001
From: Julien Boibessot <julien.boibessot@armadeus.com>
Date: Wed, 19 Oct 2011 10:39:26 +0200
Subject: [PATCH v2] Add libmodbus package

Signed-off-by: Julien Boibessot <julien.boibessot@armadeus.com>
---
Changes since v1:
- Took Yegor Yefremov remarks about "call AUTOTARGETS' into account.

Based on previous work of Marek Belisko and comments of Thomas Petazzoni.

package/Config.in | 1 +
package/libmodbus/Config.in | 8 ++++++++
package/libmodbus/libmodbus.mk | 11 +++++++++++
3 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 package/libmodbus/Config.in
create mode 100644 package/libmodbus/libmodbus.mk

diff --git a/package/Config.in b/package/Config.in
......
</pre>
* retry ;-)

====After patch has been accepted====
* Delete branch & co:
<pre class="host">
$ rm xxxx.patch
$ git checkout master
$ git branch -D my_work

$ git branch
* master
</pre>

==Links==
* [http://buildroot.org/downloads/manual/manual.html BR online doc]

Uboot FPGA firmware update from Linux

2013-01-20T16:10:46Z

FrancoisG:

The U-Boot FPGA firmware can be updated by means of U-Boot ([[Target_Software_Installation#FPGA_firmware_installation]]) or directly from Linux as described herewith.

Under Linux:

* At first download your FPGA firmware:
<pre class="apf">
# tftp -g -r my_firmware.bit 192.168.0.2
</pre>

* Then, determine which partition in the flash is the firmware partition:
<pre class="apf">
# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00080000 00020000 "env"
mtd2: 00080000 00020000 "env2"
mtd3: 00100000 00020000 "firmware"
mtd4: 00080000 00020000 "dtb"
mtd5: 00080000 00020000 "splash"
mtd6: 00800000 00020000 "kernel"
mtd7: 1f400000 00020000 "rootfs"
</pre>
The example above is taken from an APF51 running Armadeus version 5.2 and we can see that mtd3 is the firmware partition. If yours is different, then replace mtd3 by what you found out to be the right one in the following commands.

* Once done, the U-Boot Firmware partition has to be erased:
<pre class="apf">
# flash_eraseall /dev/mtd3/
</pre>

* Then your FPGA .bit file can be written:
<pre class="apf">
# nandwrite -p /dev/mtd3 my_firmware.bit
</pre>

That's all !

Debian on APF

2012-01-13T19:46:52Z

FrancoisG:

{{Under_Construction}}

This page details how to install Debian on an APF51.

==Requirements==
* an APF51 board
* a development PC running linux
* the debootstrap program installed on the development PC
* the qemu-user ARM statically linked on the development PC
* about an hour of free time

==Preparing the development PC==
* In this tutorial, we have used Ubuntu 11.10 on the development PC. Any other distribution can be used with some adjustments but of course, Debian based distributions are recommended.

* Let's first install all the packages that will be used :
<pre class="host">
$ sudo apt-get install debootstrap qemu-user-static
</pre>

* then get in a root shell and prepare a work folder:
<pre class="host">
$ sudo su
# mkdir /root/apf51_debian
# cd /root/apf51_debian
</pre>

==Bootstrapping the Debian filesystem==

* The debootstrap command is generating a base debian filesystem by downloading all debian base packages and unpacking them in a folder, in order to build a fresh debian root filesystem.
* Installing deb packages is not only extracting archive files, it also consists in running scripts after unpacking the files. Running these scripts is handled by the script interpreters that have been unpacked in the generated folders. Therefore generating an ARM debian filesystem on an x86 based computer requires to do this in two steps.
* Let's run the first step. That one consists in downloading all the deb packages and unpacking the files, but without running the scripts :
<pre class="host">
# debootstrap --foreign --arch=armel squeeze rootfs http://ftp.debian.org/debian
</pre>
* The foreign option makes debootstrap stop right after unpacking. The arch option specifies the architecture we want to make a rootfs for, armel is the name of the ARM port of debian. Then in order we have squeeze, which is the name of the debian version we want to get, currently squeeze is the stable version. Then rootfs is the name of the subfolder where debootstrap will work. Finally the URL of the debian mirror we want to use (you can use another one which sits in your country, to make it faster).
* This process takes a while, it will download all the debian base packages from the mirror and unpack them in the rootfs folder.
* The next step is to run the second stage of debootstrap. That stage consists in finalizing the installation of the package by running the scripts I mentionned. Since these scripts will be executed using the interpreter who is in the new filesystem, and not by the interpreter from your development PC, we are now facing a problem : The interpreter in that new filesystem is an ARM program, and won't run on an x86 system. To overcome this, we will make use of qemu, who allows to run foreign architecture linux programs by doing emulation.
* First, we need to copy the qemu binary into the new filesystem :
<pre class="host">
# cp /usr/bin/qemu-arm-static rootfs/usr/bin
</pre>
* Then we can launch the second stage of debootstrap, qemu will automatically let it run the ARM binaries through qemu :
<pre class="host">
# DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true LC_ALL=C LANGUAGE=C LANG=C chroot rootfs debootstrap/debootstrap --second-stage
</pre>
* This process also takes a while, it will run the scripts of each package, in order to finalize the packages installation.
==Tweaking the filesystem==

* After the filesystem has been generated by debootstrap, some adjustments need to be done.
* First, we need to have debian run a getty on the console serial port (ttymxc2), otherwise no login prompt will be available on the console port :
<pre class="host">
# echo 'T0:23:respawn:/sbin/getty -L ttymxc2 115200 vt100' >> rootfs/etc/inittab
</pre>

* The debian mirror also has to be specified in the APT configuration, in order to install new debian packages later :
<pre class="host">
# echo 'deb http://ftp.debian.org/debian squeeze main' > rootfs/etc/apt/sources.list
</pre>

* The hostname of the debian system has to be set properly:
<pre class="host">
# echo 'apf51' > rootfs/etc/hostname
# echo '127.0.1.1 apf51' >> rootfs/etc/hosts
</pre>

* Finally we can clean the APT cache. We no longer need the deb files, and that will save quite some disk space :
<pre class="host">
# rm rootfs/var/cache/apt/archives/*.deb
</pre>

==Copying the filesystem on the APF==
* Now that the debian filesystem is ready, it must be transferred to the APF51.

* This tutorial will describe a method that will allow to keep the original Armadeus system on the board, and that will permit to choose which system to boot very easily. It is not the only way to run Debian on the APF, but it is quite convinient.

* You need to have an APF51 running the Buildroot based original system.

* The first step is to pack the debian filesystem that has been created on the development PC:
<pre class="host">
# tar cvf debian_arm_rootfs.tar rootfs
</pre>

* Then this file should be transfered to the APF51 board. You can use tftp for example. Put the file in /root on the APF51.

* Now, on the APF51, the archive should be extracted. Don't forget the p option of tar, which is required to properly extract permissions on files :
<pre class="host">
# cd /root
# tar xvpf debian_arm_rootfs.tar
</pre>

* We will boot this distribution using chroot. We need to write a script that will be run by the kernel on startup and that will do the chroot at an early stage of the boot process, so that nothing from the original armadeus system is started when we want to boot debian. To do this, create a file called /debinit that contains the following lines :
<pre class="host">
#!/bin/sh
mount -t proc none /root/rootfs/proc
exec chroot /root/rootfs /sbin/init
</pre>

* This script needs to be executable :
<pre class="host">
#chmod 755 /debinit
</pre>

* Kernel modules and firmware files need to be copied from the Armadeus system to the debian filesystem :
<pre class="host">
#cp -r /lib/modules/* /root/rootfs/lib/modules
#cp -r /lib/firmware /rot/rootfs/lib/firmware
#chroot /root/rootfs /sbin/depmod -a
</pre>

* Finally, we need to configure U-Boot so it tells the kernel to use that script on bootup. Reboot your board, press a key to interrupt the automatic boot in U-Boot, then do :
<pre class="host">
BIOS>setenv debboot 'setenv addubifsargs ${addubifsargs} init=/debinit; run ubifsboot'
BIOS>saveenv
</pre>

* That's all. Now you board will keep booting the original system but if you want to boot debian instead, you can interrupt the autoboot of U-Boot and run the command :

<pre class="host">
BIOS>run debboot
</pre>

* In case you want the board to boot debian automatically, you can do so by running :
<pre class="host">
BIOS>setenv bootcmd run debboot
BIOS>saveenv
</pre>

* You can then switch back to the original Armadeus system by running :
<pre class="host">
BIOS>setenv bootcmd run ubifsboot
BIOS>saveenv
</pre>

==Known issues==
* There's a kernel oops during the boot process. This is related to the SPI driver.
* Booting takes quite some time because udev has an issue with the SPI port and it takes some time before it timeouts and continues the boot.

==Misc==
[[Category:Distribution]]

* http://free-electrons.com/blog/embdebian-with-multistrap/

Debian on APF

2012-01-13T19:46:00Z

FrancoisG:

{{Under_Construction}}

This page details how to install Debian on an APF51.

==Requirements==
* an APF51 board
* a development PC running linux
* the debootstrap program installed on the development PC
* the qemu-user ARM statically linked on the development PC
* about an hour of free time

==Preparing the development PC==
* In this tutorial, we have used Ubuntu 11.10 on the development PC. Any other distribution can be used with some adjustments but of course, Debian based distributions are recommended.

* Let's first install all the packages that will be used :
<pre class="host">
$ sudo apt-get install debootstrap qemu-user-static
</pre>

* then get in a root shell and prepare a work folder:
<pre class="host">
$ sudo su
# mkdir /root/apf51_debian
# cd /root/apf51_debian
</pre>

==Bootstrapping the Debian filesystem==

* The debootstrap command is generating a base debian filesystem by downloading all debian base packages and unpacking them in a folder, in order to build a fresh debian root filesystem.
* Installing deb packages is not only extracting archive files, it also consists in running scripts after unpacking the files. Running these scripts is handled by the script interpreters that have been unpacked in the generated folders. Therefore generating an ARM debian filesystem on an x86 based computer requires to do this in two steps.
* Let's run the first step. That one consists in downloading all the deb packages and unpacking the files, but without running the scripts :
<pre class="host">
# debootstrap --foreign --arch=armel squeeze rootfs http://ftp.debian.org/debian
</pre>
* The foreign option makes debootstrap stop right after unpacking. The arch option specifies the architecture we want to make a rootfs for, armel is the name of the ARM port of debian. Then in order we have squeeze, which is the name of the debian version we want to get, currently squeeze is the stable version. Then rootfs is the name of the subfolder where debootstrap will work. Finally the URL of the debian mirror we want to use (you can use another one which sits in your country, to make it faster).
* This process takes a while, it will download all the debian base packages from the mirror and unpack them in the rootfs folder.
* The next step is to run the second stage of debootstrap. That stage consists in finalizing the installation of the package by running the scripts I mentionned. Since these scripts will be executed using the interpreter who is in the new filesystem, and not by the interpreter from your development PC, we are now facing a problem : The interpreter in that new filesystem is an ARM program, and won't run on an x86 system. To overcome this, we will make use of qemu, who allows to run foreign architecture linux programs by doing emulation.
* First, we need to copy the qemu binary into the new filesystem :
<pre class="host">
# cp /usr/bin/qemu-arm-static rootfs/usr/bin
</pre>
* Then we can launch the second stage of debootstrap, qemu will automatically let it run the ARM binaries through qemu :
<pre class="host">
# DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true LC_ALL=C LANGUAGE=C LANG=C chroot rootfs debootstrap/debootstrap --second-stage
</pre>
* This process also takes a while, it will run the scripts of each package, in order to finalize the packages installation.
==Tweaking the filesystem==

* After the filesystem has been generated by debootstrap, some adjustments need to be done.
* First, we need to have debian run a getty on the console serial port (ttymxc2), otherwise no login prompt will be available on the console port :
<pre class="host">
# echo 'T0:23:respawn:/sbin/getty -L ttymxc2 115200 vt100' >> rootfs/etc/inittab
</pre>

* The debian mirror also has to be specified in the APT configuration, in order to install new debian packages later :
<pre class="host">
# echo 'deb http://ftp.debian.org/debian squeeze main' > rootfs/etc/apt/sources.list
</pre>

* The hostname of the debian system has to be set properly:
<pre class="host">
# echo 'apf51' > rootfs/etc/hostname
# echo '127.0.1.1 apf51' >> rootfs/etc/hosts
</pre>

* Finally we can clean the APT cache. We no longer need the deb files, and that will save quite some disk space :
<pre class="host">
# rm rootfs/var/cache/apt/archives/*.deb
</pre>

==Copying the filesystem on the APF==
* Now that the debian filesystem is ready, it must be transferred to the APF51.

* This tutorial will describe a method that will allow to keep the original Armadeus system on the board, and that will permit to choose which system to boot very easily. It is not the only way to run Debian on the APF, but it is quite convinient.

* You need to have an APF51 running the Buildroot based original system.

* The first step is to pack the debian filesystem that has been created on the development PC:
<pre class="host">
# tar cvf debian_arm_rootfs.tar rootfs
</pre>

* Then this file should be transfered to the APF51 board. You can use tftp for example. Put the file in /root on the APF51.

* Now, on the APF51, the archive should be extracted. Don't forget the p option of tar, which is required to properly extract permissions on files :
<pre class="host">
# cd /root
# tar xvpf debian_arm_rootfs.tar
</pre>

* We will boot this distribution using chroot. We need to write a script that will be run by the kernel on startup and that will do the chroot at an early stage of the boot process, so that nothing from the original armadeus system is started when we want to boot debian. To do this, create a file called /debinit that contains the following lines :
<pre class="host">
#!/bin/sh
mount -t proc none /root/rootfs/proc
exec chroot /root/rootfs /sbin/init
</pre>

* This script needs to be executable :
<pre class="host">
#chmod 755 /debinit
</pre>

* Kernel modules and firmware files need to be copied from the Armadeus system to the debian filesystem :
<pre class="host">
#cp -r /lib/modules/* /root/rootfs/lib/modules
#cp -r /lib/firmware /rot/rootfs/lib/firmware
#chroot /root/rootfs /sbin/depmod -a
</pre>

* Finally, we need to configure U-Boot so it tells the kernel to use that script on bootup. Reboot your board, press a key to interrupt the automatic boot in U-Boot, then do :
<pre class="host">
BIOS>setenv debboot 'setenv addubifsargs ${addubifsargs} init=/debinit; run ubifsboot'
BIOS>saveenv
</pre>

* That's all. Now you board will keep booting the original system but if you want to boot debian instead, you can interrupt the autoboot of U-Boot and run the command :

<pre class="host">
BIOS>run debboot
</pre>

* In case you want the board to boot debian automatically, you can do so by running :
<pre class="host">
BIOS>setenv bootcmd run debboot
BIOS>saveenv
</pre>

* You can then switch back to the original Armadeus system by running :
<pre class="host">
BIOS>setenv bootcmd run ubifsboot
BIOS>saveenv
</pre>

==Known issues==
* There's a kernel oops during the boot process. This is related to the SPI driver.
* Booting takes quite some time because udev has an issue with the SPI port and it takes some time before it timeouts and continues the boot.

[[Category:Distribution]]

* http://free-electrons.com/blog/embdebian-with-multistrap/

Debian on APF

2012-01-13T19:41:32Z

FrancoisG: /* Copying the filesystem on the APF */

{{Under_Construction}}

* http://free-electrons.com/blog/embdebian-with-multistrap/

This page details how to install Debian on an APF51.

==Requirements==
* an APF51 board
* a development PC running linux
* the debootstrap program installed on the development PC
* the qemu-user ARM statically linked on the development PC
* about an hour of free time

==Preparing the development PC==
* In this tutorial, we have used Ubuntu 11.10 on the development PC. Any other distribution can be used with some adjustments but of course, Debian based distributions are recommended.

* Let's first install all the packages that will be used :
<pre class="host">
$ sudo apt-get install debootstrap qemu-user-static
</pre>

* then get in a root shell and prepare a work folder:
<pre class="host">
$ sudo su
# mkdir /root/apf51_debian
# cd /root/apf51_debian
</pre>

==Bootstrapping the Debian filesystem==

* The debootstrap command is generating a base debian filesystem by downloading all debian base packages and unpacking them in a folder, in order to build a fresh debian root filesystem.
* Installing deb packages is not only extracting archive files, it also consists in running scripts after unpacking the files. Running these scripts is handled by the script interpreters that have been unpacked in the generated folders. Therefore generating an ARM debian filesystem on an x86 based computer requires to do this in two steps.
* Let's run the first step. That one consists in downloading all the deb packages and unpacking the files, but without running the scripts :
<pre class="host">
# debootstrap --foreign --arch=armel squeeze rootfs http://ftp.debian.org/debian
</pre>
* The foreign option makes debootstrap stop right after unpacking. The arch option specifies the architecture we want to make a rootfs for, armel is the name of the ARM port of debian. Then in order we have squeeze, which is the name of the debian version we want to get, currently squeeze is the stable version. Then rootfs is the name of the subfolder where debootstrap will work. Finally the URL of the debian mirror we want to use (you can use another one which sits in your country, to make it faster).
* This process takes a while, it will download all the debian base packages from the mirror and unpack them in the rootfs folder.
* The next step is to run the second stage of debootstrap. That stage consists in finalizing the installation of the package by running the scripts I mentionned. Since these scripts will be executed using the interpreter who is in the new filesystem, and not by the interpreter from your development PC, we are now facing a problem : The interpreter in that new filesystem is an ARM program, and won't run on an x86 system. To overcome this, we will make use of qemu, who allows to run foreign architecture linux programs by doing emulation.
* First, we need to copy the qemu binary into the new filesystem :
<pre class="host">
# cp /usr/bin/qemu-arm-static rootfs/usr/bin
</pre>
* Then we can launch the second stage of debootstrap, qemu will automatically let it run the ARM binaries through qemu :
<pre class="host">
# DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true LC_ALL=C LANGUAGE=C LANG=C chroot rootfs debootstrap/debootstrap --second-stage
</pre>
* This process also takes a while, it will run the scripts of each package, in order to finalize the packages installation.
==Tweaking the filesystem==

* After the filesystem has been generated by debootstrap, some adjustments need to be done.
* First, we need to have debian run a getty on the console serial port (ttymxc2), otherwise no login prompt will be available on the console port :
<pre class="host">
# echo 'T0:23:respawn:/sbin/getty -L ttymxc2 115200 vt100' >> rootfs/etc/inittab
</pre>

* The debian mirror also has to be specified in the APT configuration, in order to install new debian packages later :
<pre class="host">
# echo 'deb http://ftp.debian.org/debian squeeze main' > rootfs/etc/apt/sources.list
</pre>

* The hostname of the debian system has to be set properly:
<pre class="host">
# echo 'apf51' > rootfs/etc/hostname
# echo '127.0.1.1 apf51' >> rootfs/etc/hosts
</pre>

* Finally we can clean the APT cache. We no longer need the deb files, and that will save quite some disk space :
<pre class="host">
# rm rootfs/var/cache/apt/archives/*.deb
</pre>

==Copying the filesystem on the APF==
* Now that the debian filesystem is ready, it must be transferred to the APF51.

* This tutorial will describe a method that will allow to keep the original Armadeus system on the board, and that will permit to choose which system to boot very easily. It is not the only way to run Debian on the APF, but it is quite convinient.

* You need to have an APF51 running the Buildroot based original system.

* The first step is to pack the debian filesystem that has been created on the development PC:
<pre class="host">
# tar cvf debian_arm_rootfs.tar rootfs
</pre>

* Then this file should be transfered to the APF51 board. You can use tftp for example. Put the file in /root on the APF51.

* Now, on the APF51, the archive should be extracted. Don't forget the p option of tar, which is required to properly extract permissions on files :
<pre class="host">
# cd /root
# tar xvpf debian_arm_rootfs.tar
</pre>

* We will boot this distribution using chroot. We need to write a script that will be run by the kernel on startup and that will do the chroot at an early stage of the boot process, so that nothing from the original armadeus system is started when we want to boot debian. To do this, create a file called /debinit that contains the following lines :
<pre class="host">
#!/bin/sh
mount -t proc none /root/rootfs/proc
exec chroot /root/rootfs /sbin/init
</pre>

* This script needs to be executable :
<pre class="host">
#chmod 755 /debinit
</pre>

* Kernel modules and firmware files need to be copied from the Armadeus system to the debian filesystem :
<pre class="host">
#cp -r /lib/modules/* /root/rootfs/lib/modules
#cp -r /lib/firmware /rot/rootfs/lib/firmware
</pre>

* Finally, we need to configure U-Boot so it tells the kernel to use that script on bootup. Reboot your board, press a key to interrupt the automatic boot in U-Boot, then do :
<pre class="host">
BIOS>setenv debboot 'setenv addubifsargs ${addubifsargs} init=/debinit; run ubifsboot'
BIOS>saveenv
</pre>

* That's all. Now you board will keep booting the original system but if you want to boot debian instead, you can interrupt the autoboot of U-Boot and run the command :

<pre class="host">
BIOS>run debboot
</pre>

* In case you want the board to boot debian automatically, you can do so by running :
<pre class="host">
BIOS>setenv bootcmd run debboot
BIOS>saveenv
</pre>

* You can then switch back to the original Armadeus system by running :
<pre class="host">
BIOS>setenv bootcmd run ubifsboot
BIOS>saveenv
</pre>

[[Category:Distribution]]

Debian on APF

2012-01-13T19:33:38Z

FrancoisG:

{{Under_Construction}}

* http://free-electrons.com/blog/embdebian-with-multistrap/

This page details how to install Debian on an APF51.

==Requirements==
* an APF51 board
* a development PC running linux
* the debootstrap program installed on the development PC
* the qemu-user ARM statically linked on the development PC
* about an hour of free time

==Preparing the development PC==
* In this tutorial, we have used Ubuntu 11.10 on the development PC. Any other distribution can be used with some adjustments but of course, Debian based distributions are recommended.

* Let's first install all the packages that will be used :
<pre class="host">
$ sudo apt-get install debootstrap qemu-user-static
</pre>

* then get in a root shell and prepare a work folder:
<pre class="host">
$ sudo su
# mkdir /root/apf51_debian
# cd /root/apf51_debian
</pre>

==Bootstrapping the Debian filesystem==

* The debootstrap command is generating a base debian filesystem by downloading all debian base packages and unpacking them in a folder, in order to build a fresh debian root filesystem.
* Installing deb packages is not only extracting archive files, it also consists in running scripts after unpacking the files. Running these scripts is handled by the script interpreters that have been unpacked in the generated folders. Therefore generating an ARM debian filesystem on an x86 based computer requires to do this in two steps.
* Let's run the first step. That one consists in downloading all the deb packages and unpacking the files, but without running the scripts :
<pre class="host">
# debootstrap --foreign --arch=armel squeeze rootfs http://ftp.debian.org/debian
</pre>
* The foreign option makes debootstrap stop right after unpacking. The arch option specifies the architecture we want to make a rootfs for, armel is the name of the ARM port of debian. Then in order we have squeeze, which is the name of the debian version we want to get, currently squeeze is the stable version. Then rootfs is the name of the subfolder where debootstrap will work. Finally the URL of the debian mirror we want to use (you can use another one which sits in your country, to make it faster).
* This process takes a while, it will download all the debian base packages from the mirror and unpack them in the rootfs folder.
* The next step is to run the second stage of debootstrap. That stage consists in finalizing the installation of the package by running the scripts I mentionned. Since these scripts will be executed using the interpreter who is in the new filesystem, and not by the interpreter from your development PC, we are now facing a problem : The interpreter in that new filesystem is an ARM program, and won't run on an x86 system. To overcome this, we will make use of qemu, who allows to run foreign architecture linux programs by doing emulation.
* First, we need to copy the qemu binary into the new filesystem :
<pre class="host">
# cp /usr/bin/qemu-arm-static rootfs/usr/bin
</pre>
* Then we can launch the second stage of debootstrap, qemu will automatically let it run the ARM binaries through qemu :
<pre class="host">
# DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true LC_ALL=C LANGUAGE=C LANG=C chroot rootfs debootstrap/debootstrap --second-stage
</pre>
* This process also takes a while, it will run the scripts of each package, in order to finalize the packages installation.
==Tweaking the filesystem==

* After the filesystem has been generated by debootstrap, some adjustments need to be done.
* First, we need to have debian run a getty on the console serial port (ttymxc2), otherwise no login prompt will be available on the console port :
<pre class="host">
# echo 'T0:23:respawn:/sbin/getty -L ttymxc2 115200 vt100' >> rootfs/etc/inittab
</pre>

* The debian mirror also has to be specified in the APT configuration, in order to install new debian packages later :
<pre class="host">
# echo 'deb http://ftp.debian.org/debian squeeze main' > rootfs/etc/apt/sources.list
</pre>

* The hostname of the debian system has to be set properly:
<pre class="host">
# echo 'apf51' > rootfs/etc/hostname
# echo '127.0.1.1 apf51' >> rootfs/etc/hosts
</pre>

* Finally we can clean the APT cache. We no longer need the deb files, and that will save quite some disk space :
<pre class="host">
# rm rootfs/var/cache/apt/archives/*.deb
</pre>

==Copying the filesystem on the APF==
* Now that the debian filesystem is ready, it must be transferred to the APF51.

* This tutorial will describe a method that will allow to keep the original Armadeus system on the board, and that will permit to choose which system to boot very easily. It is not the only way to run Debian on the APF, but it is quite convinient.

* You need to have an APF51 running the Buildroot based original system.

* The first step is to pack the debian filesystem that has been created on the development PC:
<pre class="host">
# tar cvf debian_arm_rootfs.tar rootfs
</pre>

* Then this file should be transfered to the APF51 board. You can use tftp for example. Put the file in /root on the APF51.

* Now, on the APF51, the archive should be extracted. Don't forget the p option of tar, which is required to properly extract permissions on files :
<pre class="host">
# cd /root
# tar xvpf debian_arm_rootfs.tar
</pre>

* We will boot this distribution using chroot. We need to write a script that will be run by the kernel on startup and that will do the chroot at an early stage of the boot process, so that nothing from the original armadeus system is started when we want to boot debian. To do this, create a file called /debinit that contains the following lines :
<pre class="host">
#!/bin/sh
mount -t proc none /root/rootfs/proc
exec chroot /root/rootfs /sbin/init
</pre>

* This script needs to be executable :
<pre class="host">
#chmod 755 /debinit
</pre>

* Finally, we need to configure U-Boot so it tells the kernel to use that script on bootup. Reboot your board, press a key to interrupt the automatic boot in U-Boot, then do :
<pre class="host">
BIOS>setenv debboot 'setenv addubifsargs ${addubifsargs} init=/debinit; run ubifsboot'
BIOS>saveenv
</pre>

* That's all. Now you board will keep booting the original system but if you want to boot debian instead, you can interrupt the autoboot of U-Boot and run the command :

<pre class="host">
BIOS>run debboot
</pre>

* In case you want the board to boot debian automatically, you can do so by running :
<pre class="host">
BIOS>setenv bootcmd run debboot
BIOS>saveenv
</pre>

* You can then switch back to the original Armadeus system by running :
<pre class="host">
BIOS>setenv bootcmd run ubifsboot
BIOS>saveenv
</pre>

[[Category:Distribution]]

Debian on APF

2012-01-13T19:10:18Z

FrancoisG:

Debian on APF

2012-01-13T18:59:50Z

FrancoisG: /* Tweaking the filesystem */

Debian on APF

2012-01-13T18:44:31Z

FrancoisG:

User talk:FrancoisG

2012-01-13T18:05:04Z

FrancoisG:

[[DebianOnAPF]]

User talk:FrancoisG

2012-01-13T18:04:46Z

FrancoisG: New page: UbuntuOnAPF

[[UbuntuOnAPF]]

MemberList

2011-08-19T13:33:58Z

FrancoisG: /* Here is the list of the (active) members and their skills */

==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
|----------------
|[[User:FrancoisG| Francois Goudal / Fanfwe]] || 2 || 2 || 1 || 1 || robotics, telecommunications

|}

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

[[Category:Association]]

MemberList

2011-08-19T13:32:44Z

FrancoisG: /* Here is the list of the (active) members and their skills */

==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
|----------------
|[[User:FrancoisG| Francois Goudal]] || 2 || 2 || 1 || 1 || robotics, telecommunications

|}

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

[[Category:Association]]