ArmadeusWiki - User contributions [en]

GSM/GPRS

2012-06-12T09:32:34Z

SergioB: /* Sending AT commands "manually" */

This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).

==Introduction==
GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.
* GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].
* GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.
Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]

==Linux configuration (APF27Dev only)==
* Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:
<pre class="host">
$ make linux26-menuconfig
</pre>
<pre class="config">
System Type --->
Freescale MXC Implementations --->
...
Extension board (Wireless (APW)) --->
[*] GSM/GPRS Modem (NEW)
[ ] Bluetooth & WiFi module (NEW)
[ ] CSI (Camera) pass-through (NEW)
[ ] GPS module (NEW)
</pre>

<pre class="host">
$ make linux26
</pre>
* reflash you Linux kernel

==Configure serial port==
====APF27====
<pre class="apf">
# export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

====APF51Dev====

* Don't forget to put "Wireless" jumper J42 on your [[APF51Dev]] (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding jumper J39).
* On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).
<pre class="apf">
# load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin
</pre>
* Once firmware loaded, drivers related to FPGA can be used :
<pre class="apf">
# modprobe irq_ocore
# modprobe 8250
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
# modprobe twin_uarts_irq_mng
# modprobe twin_uarts_16750
serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750
serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750
</pre>
* Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):
<pre class="apf">
# modprobe wm831x-gpio
# echo 245 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio245/direction
# echo 1 > /sys/class/gpio/gpio245/value
</pre>
* Configure serial port:
<pre class="apf">
# ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
</pre>

* If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :
<pre class="apf">
# mknod /dev/ttyS0 c 4 64
# mknod /dev/ttyS1 c 4 65
</pre>
Then :
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

==Basic Usage==
===Sending AT commands "manually"===
* Sending AT commands with ''cu'' utility (be sure to [[cu/uucp|have installed it before]]):
<pre class="apf">
# cu -l $GSM_DEVICE
</pre>
( To exit ''cu'' you will have to type '''~.''' )
* Check module presence:
<pre class="apf">
ATI3
SAGEM HiC,A.005.00

OK
</pre>

{{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:
<pre class="apf">
ATE1
</pre>
}}

{{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):
<pre class="apf">
AT+IPR=115200
</pre>
}}

* Get constructor name:
<pre class="apf">
AT+CGMI
SAGEM

OK
</pre>
* Get model name:
<pre class="apf">
AT+CGMM
HILO GPRS

OK
</pre>
* Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''
<pre class="apf">
AT+CPIN="0000"

OK
</pre>
* Check PIN code status:
<pre class="apf">
AT+CPIN?
+CPIN: READY

OK
</pre>
{{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}

* Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):
<pre class="apf">
AT+CPAS
+CPAS: 0

OK
</pre>
* Get Indicator control (<battchg>[0-4],<signal>[0-4],<service>0/1,<message>0/1,<call>0/1,<smsfull>0/1):
<pre class="apf">
AT+CIND?
+CIND: 0,4,1,0,0,0,1

OK
</pre>
* Get signal quality (should be better than 12/99):
<pre class="apf">
AT+CSQ
+CSQ: 24,99

OK
</pre>
* Voice call "123456789" (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)
<pre class="apf">
ATD"123456789";
OK
</pre>
* Terminate current call:
<pre class="apf">
ATH
OK
</pre>

===Sending AT commands in shell scripts===

<source lang="bash">
GSM_DEVICE=/dev/ttyXXX
send_at_cmd()
{
echo -e -n "$1\015" > $GSM_DEVICE
sleep 1 # Adjustable ! (usleep)
}

send_at_cmd AT
</source>

* See ''target/test/test_gsm.sh'' for more details

==Sending SMS==
* Supposing you are already connected to the modem with cu
* Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))
<pre class="apf">
AT+CMGF=?
</pre>
* If OK, switch to SMS sending mode:
<pre class="apf">
AT+CMGF=1
</pre>
* Write a message for 0661234567 phone number:
<pre class="apf">
AT+CMGW="0661326109"

> Hey ! How are you doing ??
> <-- Ctrl+z to end SMS here

+CMGW: 8
</pre>
* +CMGW give you the number of your SMS saved in SIM card or phone memory
* Then, at anytime, you can send your SMS with (pass previous number as parameter):
<pre class="apf">
AT+CMSS=8
</pre>

==Tools to look at==
* http://www.developershome.com/sms/freeLibForSMS.asp
* http://www.gnokii.org/
* http://www.alamin.org/en/index.html
* http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page
* http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html

==Data tranfers (EDGE/3G)==

===PPP installation (done by default on APF51)===
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
<M> PPP (point-to-point protocol) support
[ ] PPP multilink support (EXPERIMENTAL)
[ ] PPP filtering
<M> PPP support for async serial ports
< > PPP support for sync tty ports
< > PPP Deflate compression
< > PPP BSD-Compress compression
< > PPP MPPE compression (encryption) (EXPERIMENTAL)
< > PPP over Ethernet (EXPERIMENTAL)
</pre>

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

<pre class="config">
Package Selection for the target --->
Networking applications --->
[*] pppd
[ ] filtering
[ ] radius
</pre>

<pre class="host">
$ make linux26 && make
</pre>

* reflash kernel & rootfs

===PPP configuration===
{{Note|Following instructions are given for the French operator "Bouygtel" and may need to be ajusted accordingly, depending on your operator/country}}

* Create a "chat" script that will be used to initiate MODEM dialup (here we use the "cat > xxxx << EOF trick" to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):
<pre class="apf">
# mkdir -p /etc/chatscripts/
# cat > /etc/chatscripts/bouygtel <<EOF
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR
'' AT
OK AT+IPR=115200
OK AT+CPIN="0000"
OK AT+CFUN=1
OK AT+COPS?
OK AT+CSQ
OK 'AT+CGDCONT=1,"IP","ebouygtel.com","",0,0'
OK 'AT&FE0Q0V1'
OK 'ATD*99#'
CONNECT ""
EOF
</pre>
* Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor
* Don't forget to update "AT+CPIN=" with your real PIN code and "AT+CGDCONT" and "ATD*99#" with your operator parameters.
* If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:
<pre class="apf">
# /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel > $GSM_DEVICE < $GSM_DEVICE
</pre>
* If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.

====For '''APF51'''====
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttyS0
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttyS0 <<EOF
115200
EOF
</pre>

====For '''APF27'''====
{{Note| Check if /dev/ttySMX1 exists, if not create it with :
<pre class="apf">
mknod /dev/ttySMX1 c 204 42
</pre>
}}
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttySMX1
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttySMX1 <<EOF
115200
EOF
</pre>

===PPP Usage===
* Load PPP module:
<pre class="apf">
# modprobe ppp (APF27)
or
# modprobe ppp_async (APF51)
</pre>
* Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
or
# export GSM_DEVICE=/dev/ttySMX1
</pre>

* Launch the beast:
<pre class="apf">
# pppd $GSM_DEVICE 115200 call bouygtel
</pre>

===Test===
<pre class="apf">
# ping www.google.fr
</pre>

=== Troubleshots ===
* Might be needed after a successful IP setup:
<pre class="apf">
# cp /etc/ppp/resolv.conf /etc/resolv.conf
# route add default ppp0 (due to defaultroute option in ppp ?)
</pre>

* To see what happened after having launched ''pppd'' or ''chat'':
<pre class="apf">
# tail -f /var/log/messages
</pre>

==GSM Muxing==
===Why ?===
* By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.
* This can be done by a "GSM mux", if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).
===Build gsmmux===
* To build GSM mux (if not already done):
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] gsmmux
Version to use (sagem) --->
</pre>
<pre class="host">
$ make
</pre>

===Use it===
* If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):
<pre class="apf">
# gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx
</pre>
* Virtual serial ports will be created in ''/dev/pts/'':
<pre class="apf">
/dev/pts/0 /dev/pts/1 /dev/pts/2
</pre>
* to know how ''/dev/ptmx'' & ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]
* If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...

===Going further===
* In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm
* People wanting to do a "real" phone can take a look at [http://ofono.org/documentation ofono]

==Links==
* [http://support.sagemcom.com/site/modele_fax.php?page=produit&numero_type=22&produit=877 HiLo 3G documentation at Sagem]
* [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]
* [http://www.developershome.com/sms/ SMS tutorial]
* http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem
* [http://www.anotherurl.com/library/at_test.htm AT Test commands]
* http://www.gsm-modem.de/gsm-faq.html
* [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]

[[Category:Wireless]]

Target Software Installation

2012-02-29T10:09:34Z

SergioB: /* Linux kernel installation */

On this page you will learn how to flash new U-Boot, Linux and rootfs images on your APF module.

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
<pre class="apf">
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=
autoload=no
...
</pre>
The command '''setenv''' is used to change these variables. For example, to set the IP address (don't do it yet):
<pre class="apf">
BIOS> setenv ipaddr 192.168.0.10
</pre>
The command '''saveenv''' is used to save the state of your environment variables in FLASH memory; that way they will be available at next boot:
<pre class="apf">
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
</pre>

===Network configuration===
In order to use the U-Boot's network features, you have to set the network environment variables:
<pre class="apf">
BIOS> setenv netmask 255.255.255.0 (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.10
BIOS> setenv serverip 192.168.0.2 (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/apf9328-root" (to boot Linux over NFS)
</pre>
You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.
<pre class="apf">
BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.10
BIOS> setenv serverip 192.168.0.2
BIOS> saveenv
</pre>
Do not forget to save your changes in FLASH, to have them available at next power up:
<pre class="apf">
BIOS> saveenv
</pre>
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
<pre class="apf">
BIOS> run flash_reset_env
</pre>

==Linux kernel installation==
XX, in the following chapters, has to be replaced by your board name

* Check that your Armadeus kernel image size is smaller than the U-Boot partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/binaries/XX/
</pre>
* If yes, copy it to your TFTP server directory (here ''/tftpboot/''):
<pre class="host">
[armadeus]$ cp buildroot/binaries/XX/XX-linux.bin /tftpboot/
</pre>
* Load kernel image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} XX-linux.bin
</pre>
or with the serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
''Ctrl+Altgr+\+c to access kermit command line then:''
(/home/.../) C-Kermit>send /tftpboot/XX-linux.bin
''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size = 0x0013d0b0 = 1298608 Bytes
## Start Addr = 0x08000000
BIOS>
</pre>

----
{{Warning|If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS)}}
Check that transfered size value is less than the ones specified here [[#Flash_memory_partitions|Flash Memory Partitions]]
<pre class="apf">
Bytes transferred = 1313216 (1409c0 hex)
</pre>
----

* You can test your new kernel image without flashing it with; if so you will have to reload it again after test:
** '''Please note''': The ''bootm'' command is not supported by [[APF51]] boards yet; directly flash the kernel with the below commands instead
<pre class="apf">
BIOS> bootm ${loadaddr}
</pre>
* a U-Boot script exists to ease kernel image loading through Ethernet:
<pre class="apf">
BIOS> run download_kernel
</pre>
* After kernel image has been downloaded into RAM memory, you can flash it with:
<pre class="apf">
BIOS> run flash_kernel
</pre>
* To make it easier, you can use automatic scripts that will download the image and flash it in the same go. So next time you will only launch:
<pre class="apf">
BIOS> run update_kernel
</pre>
* To know what ''update_kernel'' script is doing you can display its content:
<pre class="apf">
BIOS> printenv update_kernel
</pre>
* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:
<pre class="apf">
BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm
(the kernel image you want to try must have been loaded at ${loadaddr})
</pre>

==rootfs installation==

* Check that your Armadeus rootfs image size is smaller than the rootfs partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/output/images/
...
[armadeus]$ cp buildroot/output/images/XX-rootfs.ubi /tftpboot/ (apf9328-rootfs.jffs2 on [[APF9328]]
</pre>
* Load rootfs image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} XX-rootfs.ubi (apf9328-rootfs.jffs2 on [[APF9328]]
</pre>
For large rootfs (bigger than the available RAM on your system) please use this method ('''not''' supported on the [[APF9328]]):
<pre class="apf">
BIOS> tftpboot ${rootfs_offset} XX-rootfs.ubi nand
</pre>

or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
''Ctrl+Altgr+\+c to access kermit command line then...''
(/home/.../) C-Kermit>send path_to_your_host_buildroot_dir/XX-rootfs.ubi
''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size = 0x........
## Start Addr = 0x........
BIOS>
</pre>

* Flash rootfs image with:
<pre class="apf">
BIOS> run flash_rootfs
</pre>
* Now you should be ready to test Linux:
<pre class="apf">
BIOS> boot
</pre>
* To make it easier, you can use U-Boot scripts we defined. So next time you will only launch:
<pre class="apf">
BIOS> run update_rootfs
</pre>

==FPGA firmware test==

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
apf_pkg BRAMTest bus_led led PS2 PS2_Opencore servo sram_test wishbone_example Xtools
You can make some trials with the ''firmware/PS2/ps2_top.bin'' file. 
 

{{Warning| for the APF9328, Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!}}
{{Note | For the APF51 only binary file format work ('''.bin'''). Do not use '''.bit''' format}}

* Load FPGA firmware image file with U-Boot through: 
Ethernet:
<pre class="apf">
BIOS> tftpboot ${loadaddr} fpgafirmware.bin
</pre>
''fpgafirmware.bin'' is of course the name of your bitfile stored in your TFTP shared directory (''/tftpboot/'')

or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send path_to_your_tftp/fpgafirmware.bin
</pre>
then you can type the c command to reconnect to the terminal

* Test your new FPGA firmware's downloading:
<pre class="apf">
BIOS> fpga load 0 ${loadaddr} ${firmware_len}
</pre>

==FPGA firmware installation==

* Flash your firmware image with:
<pre class="apf">
BIOS> run flash_firmware
</pre>
* When you are '''satisfied with your firmware''', you can make it "autoloaded" at power up:
<pre class="apf">
BIOS> setenv firmware_autoload 1
BIOS> saveenv
</pre>

==Update U-Boot==

There are two steps to update U-Boot:
===Load the new U-Boot code in RAM===
You can use the following commands to download U-boot: 
*With Ethernet and a TFTP server:
<pre class="apf">
BIOS> tftpboot ${loadaddr} apf9328-u-boot.bin
</pre>
*With Ethernet and a NFS server:
<pre class="apf">
BIOS> nfs ${loadaddr} host_ip_addr:/nfs_path_to_buildroot/apf9328-u-boot.bin
</pre>
*With kermit and the serial/RS232 line
<pre class="apf">
BIOS> loadb ${loadaddr}
<CTRL><ALT GR>\
c
send path_to_buildroot/apf9328-u-boot.bin
c<ENTER>
</pre>

===Transfer code from RAM to Flash memory===
There is a simple U-Boot command/script to do that:
<pre class="apf">
BIOS> run flash_uboot
</pre>

Advanced informations can be found at the [[BootLoader]] wiki page.

==Flash memory partitions==
===APF9328 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF9328 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="40%" | Armadeus 2.x address range (index from FLASH physical @ 0x10000000) !! width="40%" | Armadeus 3 address range (index from FLASH physical @ 0x10000000) !! Type
|- align="center"
|0x000000 - 0x03FFFF ( 256KB )
|0x000000 - 0x03FFFF ( 256KB )
| U-Boot
|- align="center"
|0x040000 - 0x5FFFF ( 128KB )
|0x040000 - 0x5FFFF ( 128KB )
| U-Boot environment variables
|- align="center"
|0x060000 - 0x9FFFF ( 256KB )
|0x060000 - 0x9FFFF ( 256KB )
| FPGA bitfile
|- align="center"
|0x0A0000 - '''0x21FFFF ( 1.5MB )'''
|0x0A0000 - '''0x29FFFF ( 2MB )'''
| Linux kernel image
|- align="center"
|'''0x220000''' - End of FLASH ( ~6 MB or ~14MB )
|'''0x2A0000''' - End of FLASH ( ~5.5 MB or ~13.5MB )
| Root filesystem
|}
 

===APF27 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF27 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="80%" | NAND flash address range !! Type
|- align="center"
|0x00000000 - 0x0009FFFF (640KB, including NAND SPL and 384KB spare memory for bad blocks)
| U-Boot
|- align="center"
|0x000A0000 - 0x000FFFFF (384KB)
| U-Boot environment variables
|- align="center"
| 0x00100000 - 0x0017FFFF (512KB)
| FPGA bitfile
|- align="center"
| 0x00180000 - 0x0067FFFF (5MB)
| Linux kernel image
|- align="center"
| 0x00680000 - End of FLASH (>~250MB)
| Root filesystem
|}
 

===APF51 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF51 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="80%" | NAND flash address range !! Type
|- align="center"
|0x00000000 - 0x000fffff (1MB, including NAND SPL and spare memory for bad blocks)
| U-Boot
|- align="center"
|0x00100000 - 0x001fffff (1MB)
| U-Boot environment variables
|- align="center"
| 0x00200000 - 0x002fffff (1MB)
| FPGA bitfile
|- align="center"
| 0x00300000 - 0x00afffff (8MB)
| Linux kernel image
|- align="center"
| 0x00b00000 - End of FLASH (>~500MB)
| Root filesystem
|}

Target Software Installation

2012-02-29T10:07:00Z

SergioB: /* Linux kernel installation */

On this page you will learn how to flash new U-Boot, Linux and rootfs images on your APF module.

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
<pre class="apf">
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=
autoload=no
...
</pre>
The command '''setenv''' is used to change these variables. For example, to set the IP address (don't do it yet):
<pre class="apf">
BIOS> setenv ipaddr 192.168.0.10
</pre>
The command '''saveenv''' is used to save the state of your environment variables in FLASH memory; that way they will be available at next boot:
<pre class="apf">
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
</pre>

===Network configuration===
In order to use the U-Boot's network features, you have to set the network environment variables:
<pre class="apf">
BIOS> setenv netmask 255.255.255.0 (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.10
BIOS> setenv serverip 192.168.0.2 (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/apf9328-root" (to boot Linux over NFS)
</pre>
You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.
<pre class="apf">
BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.10
BIOS> setenv serverip 192.168.0.2
BIOS> saveenv
</pre>
Do not forget to save your changes in FLASH, to have them available at next power up:
<pre class="apf">
BIOS> saveenv
</pre>
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
<pre class="apf">
BIOS> run flash_reset_env
</pre>

==Linux kernel installation==
XX, in the following chapters, has to be replaced by your board name

* Check that your Armadeus kernel image size is smaller than the U-Boot partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/binaries/XX/
</pre>
* If yes, copy it to your TFTP server directory (here ''/tftpboot/''):
<pre class="host">
[armadeus]$ cp buildroot/binaries/XX/XX-linux.bin /tftpboot/
</pre>
* Load kernel image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} XX-linux.bin
</pre>
or with the serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
''Ctrl+Altgr+\+c to access kermit command line then:''
(/home/.../) C-Kermit>send /tftpboot/XX-linux.bin
''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size = 0x0013d0b0 = 1298608 Bytes
## Start Addr = 0x08000000
BIOS>
</pre>

----
{{Warning|If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS)}}
Check that transfered size value is less than the ones specified here [[#Flash_memory_partitions|Flash Memory Partitions]]
<pre class="apf">
Bytes transferred = 1313216 (1409c0 hex)
</pre>
----

* You can test your new kernel image without flashing it with; if so you will have to reload it again after test:
** '''Please note''': The ''bootm'' command is not supported on '''APF51''' boards yet; directly flash the kernel with the below commands instead
<pre class="apf">
BIOS> bootm ${loadaddr}
</pre>
* a U-Boot script exists to ease kernel image loading through Ethernet:
<pre class="apf">
BIOS> run download_kernel
</pre>
* After kernel image has been downloaded into RAM memory, you can flash it with:
<pre class="apf">
BIOS> run flash_kernel
</pre>
* To make it easier, you can use automatic scripts that will download the image and flash it in the same go. So next time you will only launch:
<pre class="apf">
BIOS> run update_kernel
</pre>
* To know what ''update_kernel'' script is doing you can display its content:
<pre class="apf">
BIOS> printenv update_kernel
</pre>
* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:
<pre class="apf">
BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm
(the kernel image you want to try must have been loaded at ${loadaddr})
</pre>

==rootfs installation==

* Check that your Armadeus rootfs image size is smaller than the rootfs partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/output/images/
...
[armadeus]$ cp buildroot/output/images/XX-rootfs.ubi /tftpboot/ (apf9328-rootfs.jffs2 on [[APF9328]]
</pre>
* Load rootfs image with U-Boot through network:
<pre class="apf">
BIOS> tftpboot ${loadaddr} XX-rootfs.ubi (apf9328-rootfs.jffs2 on [[APF9328]]
</pre>
For large rootfs (bigger than the available RAM on your system) please use this method ('''not''' supported on the [[APF9328]]):
<pre class="apf">
BIOS> tftpboot ${rootfs_offset} XX-rootfs.ubi nand
</pre>

or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
''Ctrl+Altgr+\+c to access kermit command line then...''
(/home/.../) C-Kermit>send path_to_your_host_buildroot_dir/XX-rootfs.ubi
''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size = 0x........
## Start Addr = 0x........
BIOS>
</pre>

* Flash rootfs image with:
<pre class="apf">
BIOS> run flash_rootfs
</pre>
* Now you should be ready to test Linux:
<pre class="apf">
BIOS> boot
</pre>
* To make it easier, you can use U-Boot scripts we defined. So next time you will only launch:
<pre class="apf">
BIOS> run update_rootfs
</pre>

==FPGA firmware test==

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
apf_pkg BRAMTest bus_led led PS2 PS2_Opencore servo sram_test wishbone_example Xtools
You can make some trials with the ''firmware/PS2/ps2_top.bin'' file. 
 

{{Warning| for the APF9328, Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!}}
{{Note | For the APF51 only binary file format work ('''.bin'''). Do not use '''.bit''' format}}

* Load FPGA firmware image file with U-Boot through: 
Ethernet:
<pre class="apf">
BIOS> tftpboot ${loadaddr} fpgafirmware.bin
</pre>
''fpgafirmware.bin'' is of course the name of your bitfile stored in your TFTP shared directory (''/tftpboot/'')

or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send path_to_your_tftp/fpgafirmware.bin
</pre>
then you can type the c command to reconnect to the terminal

* Test your new FPGA firmware's downloading:
<pre class="apf">
BIOS> fpga load 0 ${loadaddr} ${firmware_len}
</pre>

==FPGA firmware installation==

* Flash your firmware image with:
<pre class="apf">
BIOS> run flash_firmware
</pre>
* When you are '''satisfied with your firmware''', you can make it "autoloaded" at power up:
<pre class="apf">
BIOS> setenv firmware_autoload 1
BIOS> saveenv
</pre>

==Update U-Boot==

There are two steps to update U-Boot:
===Load the new U-Boot code in RAM===
You can use the following commands to download U-boot: 
*With Ethernet and a TFTP server:
<pre class="apf">
BIOS> tftpboot ${loadaddr} apf9328-u-boot.bin
</pre>
*With Ethernet and a NFS server:
<pre class="apf">
BIOS> nfs ${loadaddr} host_ip_addr:/nfs_path_to_buildroot/apf9328-u-boot.bin
</pre>
*With kermit and the serial/RS232 line
<pre class="apf">
BIOS> loadb ${loadaddr}
<CTRL><ALT GR>\
c
send path_to_buildroot/apf9328-u-boot.bin
c<ENTER>
</pre>

===Transfer code from RAM to Flash memory===
There is a simple U-Boot command/script to do that:
<pre class="apf">
BIOS> run flash_uboot
</pre>

Advanced informations can be found at the [[BootLoader]] wiki page.

==Flash memory partitions==
===APF9328 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF9328 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="40%" | Armadeus 2.x address range (index from FLASH physical @ 0x10000000) !! width="40%" | Armadeus 3 address range (index from FLASH physical @ 0x10000000) !! Type
|- align="center"
|0x000000 - 0x03FFFF ( 256KB )
|0x000000 - 0x03FFFF ( 256KB )
| U-Boot
|- align="center"
|0x040000 - 0x5FFFF ( 128KB )
|0x040000 - 0x5FFFF ( 128KB )
| U-Boot environment variables
|- align="center"
|0x060000 - 0x9FFFF ( 256KB )
|0x060000 - 0x9FFFF ( 256KB )
| FPGA bitfile
|- align="center"
|0x0A0000 - '''0x21FFFF ( 1.5MB )'''
|0x0A0000 - '''0x29FFFF ( 2MB )'''
| Linux kernel image
|- align="center"
|'''0x220000''' - End of FLASH ( ~6 MB or ~14MB )
|'''0x2A0000''' - End of FLASH ( ~5.5 MB or ~13.5MB )
| Root filesystem
|}
 

===APF27 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF27 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="80%" | NAND flash address range !! Type
|- align="center"
|0x00000000 - 0x0009FFFF (640KB, including NAND SPL and 384KB spare memory for bad blocks)
| U-Boot
|- align="center"
|0x000A0000 - 0x000FFFFF (384KB)
| U-Boot environment variables
|- align="center"
| 0x00100000 - 0x0017FFFF (512KB)
| FPGA bitfile
|- align="center"
| 0x00180000 - 0x0067FFFF (5MB)
| Linux kernel image
|- align="center"
| 0x00680000 - End of FLASH (>~250MB)
| Root filesystem
|}
 

===APF51 Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF51 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="80%" | NAND flash address range !! Type
|- align="center"
|0x00000000 - 0x000fffff (1MB, including NAND SPL and spare memory for bad blocks)
| U-Boot
|- align="center"
|0x00100000 - 0x001fffff (1MB)
| U-Boot environment variables
|- align="center"
| 0x00200000 - 0x002fffff (1MB)
| FPGA bitfile
|- align="center"
| 0x00300000 - 0x00afffff (8MB)
| Linux kernel image
|- align="center"
| 0x00b00000 - End of FLASH (>~500MB)
| Root filesystem
|}

MemberList

2012-02-29T09:59:28Z

SergioB: /* 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
|----------------
|[[User:PhilippeLe| Philippe Le Rhun]] || 1 || 0 || 0 || 2 || entertainement, robotics, domotic
|----------------
|[[User:JeremieG| Jeremie Girouard]] || 0 || 0 || 0 || 0 || expérimentations,learning, Embedded Systems
|----------------
|[[User:RafalK| Rafal Kapela]] || 2 || 0 || 2 || 0 || Multimedia, real-time video content processing
|----------------
|[[User:XavierB| Xavier Bruhière]] || 1 || 1 || 1 || 1 || Robotics, domotic, learning
|----------------
||[[User:HerveDa| Dang Hervé]] || 0 || 0 || 0 || 0 || Robotics, aeronautics...
|----------------
||[[User:SergioB| Sergio Borghese]] || 2 || 1 || 0 || 0 || Networking, cryptography, embedded
|----------------
||[[User:KennethM| Ken Cracraft]] || 2 || 1 || 2 || 0 || embedded systems, FPGA, telecommunications, linux, networking
|}

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

[[Category:Association]]