ArmadeusWiki - User contributions [en]

User:NicolasL

2010-09-22T12:06:49Z

NicolasL:

Bonjour,

Je m'appelle Nicolas Lantz, j'ai 29 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 6/7 ans.

J'habite à coté de Grenoble au milieu des montagnes. ;-)

== '''Différentes réalisations professionnelles:''' ==

-Outils de génération et d'installation de Debian embarqué ( < 16Mo) ou de système réduits (<4Mo avec buildroot). Avec utilisation de "kexec", boot sur usb, interface d'adminisatration web...

-Démonstrateur de réseaux de capteurs cognitifs (Atmega 2561 et chip RF CC1000) utilisant un noyau à composant du Framework THINK et permettant la reconfiguration dynamique (rechargement d'une partie du code en flash dynamiquement et sans reboot).

-Passerelle Zigbee Ethernet (carte de dev Atmel AT91SAM7-XC-EK, avec FreeRTOS, Framework THINK, et pile TCP/IP Lwip).

== '''Mes compétences :''' ==

Du copier coller de mon CV !

Environnements : GNU/Linux: Debian / Ubuntu
Noyaux en Embarqué : Construction de tout système, Linux (à partir de 2Mo)
et Open-sources (à partir de quelques kilo-octets pour le multi-taches):
Framework THINK (noyau à composant logiciel), FreeRTOS...
Microprocesseurs : ARM7, ARM9, i386, ATMEGA 8bit, NIOS 2...
Protocoles : TCP/ IP /UDP, DHCP, ftp, tftp, http, cgi, série, spi, zigbee...
Langages info. emb. : C, ShellScripts, Assembleur...
Outils sous Linux : Eclipse, SVN, gcc, gdb, make, ant, Buildroot, OpenOCD, Avarice...

== '''Objectifs :''' ==

Members

2008-11-27T15:23:32Z

NicolasL:

Members

2008-11-27T15:22:09Z

NicolasL:

How to make a VHDL design in Ubuntu/Debian

2008-10-29T22:09:15Z

NicolasL: /* Simulation */

[[Category: FPGA]]

This tutorial describes how to install all the necessary tools to develop simple designs under Ubuntu for the Armadeus Project.<br>
As Ubuntu is a Debian based distribution, all the informations on this page should work with Debian too.

== Editing VHDL ==

To edit VHDL code all standard editing softwares like Vim, Emacs or others can be used.
But Emacs has a really good [http://www.iis.ee.ethz.ch/~zimmi/emacs/vhdl-mode.html vhdl-mode] used by lots of designers. If you hate Emacs, you
can use the xilinx-embedded editor or vim with a [http://code.google.com/p/vim-vhdl/ VHDL-plugin] under development.

== Making a simple project ==

It's a good idea to make a clean project tree for your design, because different software are
used and each generates a large amount of files.

Here is an example of a VHDL project tree :

* '''MySimple_project/'''
**'''src/''' for all sources files (.vhd,.ucf,.xcf)
**'''testbench/''' VHDL sources files for testing your design
**'''ise/''' Xilinx web pack will work in this directory
**'''simu/''' All files generated by the simulator

== Simulation ==
To stay in the Free Software spirit, the best method to simulate is to use [http://ghdl.free.fr/ GHDL] (based on GCC).<br>
To install it on Ubuntu you just have to type :
$ sudo apt-get install ghdl

You can find a good tutorial for using GHDL [http://forum.ubuntu-fr.org/viewtopic.php?pid=1545563#p839075 here] and on [http://ghdl.free.fr/ghdl/Starting-with-GHDL.html#Starting-with-GHDL the official website]. It's supposed that the project tree
used is this one described previously.

Analysing files:
$ ghdl -i --ieee=synopsys --warn-no-vital-generic --workdir=simu --work=work src/*.vhdl testbench/testb_file.vhd
And compile:
$ ghdl -m --ieee=synopsys --warn-no-vital-generic --workdir=simu --work=work testb_file

After that a binary file named ''testb_file'' is created; to launch simulation we just have to:
$ ./testb_file --stop-time=500ns --vcdgz=testb_file.vcdgz
The stop time option sets the simulation time and the vcdgz option will generate a gunzip compressed wave file to visualize the result.

Visualizing the result can be done with gtkwave:
$ sudo apt-get install gtkwave

We can launch it with the following command :
$ gunzip --stdout testb_file.vcdgz | gtkwave --vcd

[[Image:gtkwave.png|700px]]

It can be a good idea to make a Makefile instead of typing all this commands, here is a little Makefile:

<code lang="makefile">

# project name
PROJECT=bus_led_top
# vhdl files
FILES = src/bus_led.vhd src/bus_led_top.vhd
# testbench
SIMTOP = led_top_tb
SIMFILES = testbench/led_top_tb.vhd
# Simu break condition
GHDL_SIM_OPT = --assert-level=error
#GHDL_SIM_OPT = --stop-time=500ns

SIMDIR = simu
SYNTHFILES = bin/bus_led_ise/netgen/synthesis

GHDL_CMD = ghdl
GHDL_FLAGS = --ieee=synopsys --warn-no-vital-generic

VIEW_CMD = /usr/bin/gtkwave

ghdl-compil :
mkdir -p simu
$(GHDL_CMD) -i $(GHDL_FLAGS) --workdir=simu --work=work $(SIMFILES) $(FILES)
$(GHDL_CMD) -m $(GHDL_FLAGS) --workdir=simu --work=work $(SIMTOP)
@mv $(SIMTOP) simu/$(SIMTOP)

ghdl-run :
@$(SIMDIR)/$(SIMTOP) $(GHDL_SIM_OPT) --vcdgz=$(SIMDIR)/$(SIMTOP).vcdgz

ghdl-view:
gunzip --stdout $(SIMDIR)/$(SIMTOP).vcdgz | $(VIEW_CMD) --vcd

ghdl-clean :
$(GHDL_CMD) --clean --workdir=simu
</code>

to use it, just write :
$ make ghdl-compil
to compile, then:
$ make ghdl-run
to run the design, then:
$ make ghdl-view
to launch gtkwave and visualize the results.

== Syntesis, place & route ==

=== GUI installation ===
To synthesize the design it is mandatory to use Xilinx tools (It's not exactly true, others tools can be used for synthesize like Mentor tools, but at the end to make the bitstream Xilinx tools are necessary), fortunately Xilinx provides his webpack for Linux [http://www.xilinx.com/support/download/i92linwp.htm here] (you have to register). You "just" have to download it (1.7Go).

Before launching the installer, some packages are needed:
sudo apt-get install libmotif3 libxp6 libcurl3 portmap

Then launch the installer
./Webpack_full.sh

To launch the floorplanner, DISPLAY has to be change :
export DISPLAY=:0

After this installation, ISE can be found in the directory ''$(Xilinx_root_dir)/bin/lin''.
To avoid retyping export, a little script ''launch_ise.sh'' can be made in ''bin/lin/'' directory:
#!/bin/bash
export DISPLAY=:0
~/Xilinx92i/bin/lin/ise
Then make launch click :

[[Image:lanceurise.png]]

There is a good tutorial on [http://harded.free.fr/site/?p=31 harded.free.fr].

=== Using Xilinx command line tools for shell syntesis ===

See [http://panteltje.com/panteltje/fpga/index.html Using Xilinx Webpack-8.1i on grml Linux in scripted mode, without GUI] for an introduction.

First of all, library files has to be copied in library directory :
sudo -s
mkdir /usr/local/lib/xilinx/
cp Xilinx_directory/bin/lin/*.so /usr/local/lib/xilinx/
echo /usr/local/lib/xilinx >> /etc/ld.so.conf
ldconfig

Then modify your .bashrc (add at the end):
PLATFORM=lin
XILINX=Xilinx_directory
export XILINX
PATH=Xilinx_directory/bin/lin:$PATH
export PATH

Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.html Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://armadeus.svn.sourceforge.net/viewvc/*checkout*/armadeus/trunk/firmware/bus_led/Makefile armadeus/firmware/bus_led/Makefile]. To use it modify the head and write the names of your files :

*General options

# project name
PROJECT=bus_led_top
# vhdl files
FILES = src/bus_led.vhd src/bus_led_top.vhd

* constraints for synthesis

# pin configuration
UCF_FILE = src/bus_led.ucf
# Synthesis constraints file
XCF_FILE =

*Testbench options

# testbench
SIMTOP = led_top_tb
SIMFILES = ../apf_pkg/apf_test_pkg.vhd testbench/led_top_tb.vhd

*Simulation can stop after a given time or after an assert error (end of test for example)

# Simu break condition
GHDL_SIM_OPT = --assert-level=error
#GHDL_SIM_OPT = --stop-time=500ns

PrBoom

2008-10-23T18:14:06Z

NicolasL: /* Troubleshots */

==PrBoom==
{{Game infos|name=PrBoom|type=FPS|web=http://|screenshot=Doom.jpg|status=Fully working|video=http://www.youtube.com/watch?v=256RY8DaoX0}}

===Infos===
Doom clone derived from original ID Software sources and enhanced (SDL support, bugs correction...). Doom is the sequel of Wolfenstein.
It is working quite well on 8bpp framebuffers; for 16bpp one, a bug has to be corrected in i.MX framebuffer (ongoing).<br>
PrBoom is integrated in Buildroot on latest SVN snapshots. It needs SDL, SDL_mixer & SDL_net. Currently there is no sound support on Armadeus boards. Video was taken on the new LCD. Runs at full speed in 320x240 with only ~40% CPU usage in 8bpp mode.

==Install==
* Launch Buildroot configuration:
$ make menuconfig
[[Image:Menuconfig_package.png]]<br>
<br>
[[Image:Menuconfig_package_graphics.png]]<br>
<br>
[[Image:Menuconfig_package_prboom.png]]

Activate PrBoom package (it will autoselect SDL, SDL_mixer and SDL_net). Then, exit and save your config. Re-Build your rootfs:
$ make

===APF9328 with only 8 MBytes of FLASH===
As the generated rootfs is too big to be put on the 8MBytes APF9328 FLASH, there are 2 solutions:
====1. put rootfs on a MMC/SD====
In Buildroot configure rootfs to be tar-ed:
'''Target filesystem options --->'''
[[Image:Menuconfig_tar_rootfs.png]]
and then:
[armadeus]$ sudo tar xvf /.../buildroot/binaries/armadeus/rootfs.arm.tar -C /media/usbdisk
[armadeus]$ sudo umount /media/usbdisk
in U-Boot then use (with MMC inserted):
BIOS> run mmcboot
After Linux boot on Target, launch the game.
====2. put games files on NFS export====
''armadeus/buildroot/build_arm_nofpu/root/usr/games/prboom'', ''armadeus/buildroot/project_build_arm/armadeus/root/usr/share/games/doom/prboom.wad'' and ''doom1.wad''.!! Files should be in the same directory !! Then cd in directory and launch the game:

==Launching==
# /usr/games/prboom -width 320 -height 240 &
or
# /mnt/nfs/usr/games/prboom -width 320 -height 240 &

==Troubleshots==
*If SDL is complaining because it can't find any mouse (''Unable to init SDL: Unable to open mouse'') then, before launching the game, do:
# export SDL_NOMOUSE=1

[[Category:Games]]
[[Category:SDL]]

PrBoom

2008-10-23T18:07:06Z

NicolasL: /* Troubleshots */

PrBoom

2008-10-23T18:05:57Z

NicolasL: /* Troubleshots */

PrBoom

2008-10-23T18:05:37Z

NicolasL: /* Troubleshots */

Members

2008-09-24T14:37:02Z

NicolasL: /* Google Map */

ISP1761

2008-06-25T14:53:51Z

NicolasL: /* UNDER CONSTRUCTION */

This chip is a USB 2.0 Host/OnTheGo controller from NXP (ex Philips).
It will be used on the DevFull board.

[[Image:Construction.png]]
==UNDER CONSTRUCTION==
see http://www.armadeus.com/wiki/index.php?title=ISP1761_Linux_driver

==Hardware connection==

==Drivers==
* [[ISP1761 Linux driver | Linux driver]]

==Links==
* [http://www.nxp.com/acrobat/applicationnotes/AN10042_2.pdf NXP Linux application not for this chip]
* [http://sourceforge.net/projects/isp176x-hcd NXP Open Source driver on SourceForge (x86 only)]
* [http://www.ucc.asn.au/~dagobah/isp1761/ Linux driver for PXA targets]

ISP1761

2008-06-25T14:53:42Z

NicolasL: /* UNDER CONSTRUCTION */

This chip is a USB 2.0 Host/OnTheGo controller from NXP (ex Philips).
It will be used on the DevFull board.

[[Image:Construction.png]]
==UNDER CONSTRUCTION==
see **http://www.armadeus.com/wiki/index.php?title=ISP1761_Linux_driver

==Hardware connection==

==Drivers==
* [[ISP1761 Linux driver | Linux driver]]

==Links==
* [http://www.nxp.com/acrobat/applicationnotes/AN10042_2.pdf NXP Linux application not for this chip]
* [http://sourceforge.net/projects/isp176x-hcd NXP Open Source driver on SourceForge (x86 only)]
* [http://www.ucc.asn.au/~dagobah/isp1761/ Linux driver for PXA targets]

User:NicolasL

2008-06-25T14:51:06Z

NicolasL: /* '''Mes compétences :''' */

Bonjour,

Je m'appelle Nicolas Lantz, j'ai 26 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 3 ans.

Sinon, j'habite à coté de grenoble au milieu des montagnes. (-;

== '''Différentes réalisations professionnelles:''' ==

-Outils de génération et d'installation de Debian embarqué ( < 16Mo) ou de système réduits (<4Mo avec buildroot). Avec utilisation de "kexec", boot sur usb, interface d'adminisatration web...

-Démonstrateur de réseaux de capteurs cognitifs (Atmega 2561 et chip RF CC1000) utilisant un noyau à composant du Framework THINK et permettant la reconfiguration dynamique (rechargement d'une partie du code en flash dynamiquement et sans reboot).

-Passerelle Zigbee Ethernet (carte de dev Atmel AT91SAM7-XC-EK, avec FreeRTOS, Framework THINK, et pile TCP/IP Lwip).

== '''Mes compétences :''' ==

Du copier coller de mon CV (-;

Environnements : GNU/Linux: Debian / Ubuntu
Noyaux en Embarqué : Construction de tout système, Linux (à partir de 2Mo)
et Open-sources (à partir de quelques kilo-octets pour le multi-taches):
Framework THINK (noyau à composant logiciel), FreeRTOS...
Microprocesseurs : ARM7, ARM9, i386, ATMEGA 8bit, NIOS 2...
Protocoles : TCP/ IP /UDP, DHCP, ftp, tftp, http, cgi, série, spi, zigbee...
Langages info. emb. : C, ShellScripts, Assembleur...
Outils sous Linux : Eclipse, SVN, gcc, gdb, make, ant, Buildroot, OpenOCD, Avarice...

== '''Objectifs :''' ==

User:NicolasL

2008-06-25T14:50:42Z

NicolasL: /* '''Mes compétences :''' */

User:NicolasL

2008-06-25T14:50:27Z

NicolasL: /* '''Mes compétences :''' */

Bonjour,

Je m'appelle Nicolas Lantz, j'ai 26 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 3 ans.

Sinon, j'habite à coté de grenoble au milieu des montagnes. (-;

== '''Différentes réalisations professionnelles:''' ==

-Outils de génération et d'installation de Debian embarqué ( < 16Mo) ou de système réduits (<4Mo avec buildroot). Avec utilisation de "kexec", boot sur usb, interface d'adminisatration web...

-Démonstrateur de réseaux de capteurs cognitifs (Atmega 2561 et chip RF CC1000) utilisant un noyau à composant du Framework THINK et permettant la reconfiguration dynamique (rechargement d'une partie du code en flash dynamiquement et sans reboot).

-Passerelle Zigbee Ethernet (carte de dev Atmel AT91SAM7-XC-EK, avec FreeRTOS, Framework THINK, et pile TCP/IP Lwip).

== '''Mes compétences :''' ==

Du copier coller de mon CV (-;

Environnements : GNU/Linux: Debian / Ubuntu
Noyaux en Embarqué : Construction de tout système, Linux (à partir de 2Mo)

et Open-sources (à partir de quelques kilo-octets pour le multi-taches):
Framework THINK (noyau à composant logiciel), FreeRTOS...
Microprocesseurs : ARM7, ARM9, i386, ATMEGA 8bit, NIOS 2...
Protocoles : TCP/ IP /UDP, DHCP, ftp, tftp, http, cgi, série, spi, zigbee...
Langages info. emb. : C, ShellScripts, Assembleur...
Outils sous Linux : Eclipse, SVN, gcc, gdb, make, ant, Buildroot, OpenOCD, Avarice...

== '''Objectifs :''' ==

User:NicolasL

2008-06-25T14:49:27Z

NicolasL: /* '''Différentes réalisations professionnel:''' */

Bonjour,

Je m'appelle Nicolas Lantz, j'ai 26 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 3 ans.

Sinon, j'habite à coté de grenoble au milieu des montagnes. (-;

== '''Différentes réalisations professionnelles:''' ==

-Outils de génération et d'installation de Debian embarqué ( < 16Mo) ou de système réduits (<4Mo avec buildroot). Avec utilisation de "kexec", boot sur usb, interface d'adminisatration web...

-Démonstrateur de réseaux de capteurs cognitifs (Atmega 2561 et chip RF CC1000) utilisant un noyau à composant du Framework THINK et permettant la reconfiguration dynamique (rechargement d'une partie du code en flash dynamiquement et sans reboot).

-Passerelle Zigbee Ethernet (carte de dev Atmel AT91SAM7-XC-EK, avec FreeRTOS, Framework THINK, et pile TCP/IP Lwip).

== '''Mes compétences :''' ==

Du copier coller de mon CV (-;

Environnements : GNU/Linux: Debian / Ubuntu
Noyaux en Embarqué : Construction de tout système, Linux (à partir de 2Mo) et Open-sources (à partir de quelques kilo-octets pour le multi-taches):
Framework THINK (noyau à composant logiciel), FreeRTOS...
Microprocesseurs : ARM7, ARM9, i386, ATMEGA 8bit, NIOS 2...
Protocoles : TCP/ IP /UDP, DHCP, ftp, tftp, http, cgi, série, spi, zigbee...
Langages info. emb. : C, ShellScripts, Assembleur...
Outils sous Linux : Eclipse, SVN, gcc, gdb, make, ant, Buildroot, OpenOCD, Avarice...

== '''Objectifs :''' ==

USB Host

2008-06-25T14:33:01Z

NicolasL: /* Controller */

How-To use the USB Host functionnality of Armadeus boards under Linux.

= Controller =
To use USB devices on your Armadeus board, you will need to have a USB Host controller on your development board. Currently, only the [[APF9328DevFull|DevFull]] has this functionnality. It is equipped with a USB 2.0 Host controller featuring three USB high speed ports.

[[ISP1761_Linux_driver | To know how to install USB Host Linux driver for the DevFull, go here.]]

= Using USB devices =

== USB keyboard/mouse (HID: Human Interface Device) ==
=== Driver installation ===
Adding USB keyboard support
$ make linux-menuconfig

select Device Drivers ---> [*] HID Devices ---> <*> Generic HID support (static)
select Device Drivers ---> [*] HID Devices ---> <M> USB Human Interface Device (full HID) support (module)

=== Starting the driver ===
# modprobe usbhid

===Plug the keyboard===
* you should see on console:
usb 1-1.1: new low speed USB device using isp1761 and address 3
usb 1-1.1: configuration #1 chosen from 1 choice
input: NOVATEK USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1
input: NOVATEK USB Keyboard as /class/input/input1
input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1

===Plug the mouse===
* you should see on console:
usb 1-1.2: new low speed USB device using isp1761 and address 6
usb 1-1.2: configuration #1 chosen from 1 choice
input: Logitech USB-PS/2 Optical Mouse as /class/input/input6
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2

== USB Flash memory / USB key ==
=== Driver installation ===
Adding USB Flash support
$ make linux-menuconfig

select Device Drivers ---> SCSI device support ---> <*> SCSI device support (static)
select Device Drivers ---> SCSI device support ---> [*] legacy /proc/scsi/ support (static)
select Device Drivers ---> SCSI device support ---> <*> SCSI disk support (static)

select Device Drivers ---> [*] USB support ---> [*] USB device filesystem (static)
select Device Drivers ---> [*] USB support ---> <*> USB Mass Storage support (static)

=== Starting the driver ===
* if sda1 has not been previoulsy created
# mknod /dev/sda1 b 8 1
* create a mount directory "memstick"
# mkdir -m 777 /mnt/memstick
* mount the USB Flash device
# mount -t vfat /dev/sda1 /mnt/memstick
* check what is present on the USB Flash device
# ls -al /mnt/memstick

= USB Performances =
A performance test has been performed by means of the usb_perf.sh script. <br>
A high speed USB stick (corsair memory flash voyager) has been used.
Test result (mean values): read -> 2980 kBytes/sec write -> 2095 kBytes/sec

The maximal bandwidth has been also measured by using a scope and by tranferring 4096 octets from the USBstick to a buffer of a kernel driver
Result: ~10Mo/sec

= Links =
* http://www.nxp.com/acrobat/datasheets/ISP1760_4.pdf
* http://www.nxp.com/acrobat_download/datasheets/ISP1761_4.pdf

[[Category:BoardConnectivity]]
[[Category:Linux drivers]]

USB Host

2008-06-25T14:32:41Z

NicolasL: /* Controller */

How-To use the USB Host functionnality of Armadeus boards under Linux.

= Controller =
To use USB devices on your Armadeus board, you will need to have a USB Host controller on your development board. Currently, only the [[APF9328DevFull|DevFull]] has this functionnality. It is equipped with a USB 2.0 Host controller featuring three USB high speed ports.
[[ISP1761_Linux_driver | To know how to install USB Host Linux driver for the DevFull, go here.]]

= Using USB devices =

== USB keyboard/mouse (HID: Human Interface Device) ==
=== Driver installation ===
Adding USB keyboard support
$ make linux-menuconfig

select Device Drivers ---> [*] HID Devices ---> <*> Generic HID support (static)
select Device Drivers ---> [*] HID Devices ---> <M> USB Human Interface Device (full HID) support (module)

=== Starting the driver ===
# modprobe usbhid

===Plug the keyboard===
* you should see on console:
usb 1-1.1: new low speed USB device using isp1761 and address 3
usb 1-1.1: configuration #1 chosen from 1 choice
input: NOVATEK USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-platform-1.1
input: NOVATEK USB Keyboard as /class/input/input1
input: USB HID v1.10 Mouse [NOVATEK USB Keyboard] on usb-platform-1.1

===Plug the mouse===
* you should see on console:
usb 1-1.2: new low speed USB device using isp1761 and address 6
usb 1-1.2: configuration #1 chosen from 1 choice
input: Logitech USB-PS/2 Optical Mouse as /class/input/input6
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-platform-1.2

== USB Flash memory / USB key ==
=== Driver installation ===
Adding USB Flash support
$ make linux-menuconfig

select Device Drivers ---> SCSI device support ---> <*> SCSI device support (static)
select Device Drivers ---> SCSI device support ---> [*] legacy /proc/scsi/ support (static)
select Device Drivers ---> SCSI device support ---> <*> SCSI disk support (static)

select Device Drivers ---> [*] USB support ---> [*] USB device filesystem (static)
select Device Drivers ---> [*] USB support ---> <*> USB Mass Storage support (static)

=== Starting the driver ===
* if sda1 has not been previoulsy created
# mknod /dev/sda1 b 8 1
* create a mount directory "memstick"
# mkdir -m 777 /mnt/memstick
* mount the USB Flash device
# mount -t vfat /dev/sda1 /mnt/memstick
* check what is present on the USB Flash device
# ls -al /mnt/memstick

= USB Performances =
A performance test has been performed by means of the usb_perf.sh script. <br>
A high speed USB stick (corsair memory flash voyager) has been used.
Test result (mean values): read -> 2980 kBytes/sec write -> 2095 kBytes/sec

The maximal bandwidth has been also measured by using a scope and by tranferring 4096 octets from the USBstick to a buffer of a kernel driver
Result: ~10Mo/sec

= Links =
* http://www.nxp.com/acrobat/datasheets/ISP1760_4.pdf
* http://www.nxp.com/acrobat_download/datasheets/ISP1761_4.pdf

[[Category:BoardConnectivity]]
[[Category:Linux drivers]]

ISP1761

2008-06-25T14:26:26Z

NicolasL: /* UNDER CONSTRUCTION */

Network File System configuration

2008-06-19T08:16:55Z

NicolasL: /* TFTP Server under Linux: */

==Introduction==

On this page, you will find usefull informations to configure your Host or Target network

==NFS server on your development Host==

===Installation===
* On Fedora, NFS is part of your distribution so you normally don't need to install it.
* On Ubuntu/Kubuntu:
$ sudo apt-get install nfs-user-server
or if you prefer:
$ sudo apt-get install nfs-kernel-server

===Configuration===
====/etc/exports====
You have to configure the directory where you will store the files you want to share accross the network.
For that you have to modify the '''/etc/exports''' file (for example):
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.0.0(ro,no_root_squash,sync)
(In that case your Host will authorize all client from the subnet 192.168.*.* to access /local/export in read only mode)

====Restart of NFS server====
* '''On Fedora:'''
# /sbin/service nfs restart
Next time you boot, you can check your NFS server status with:
# /sbin/service nfs status
and if not started then:
# /sbin/service nfs start

* '''On Ubuntu/Kubuntu:'''
$ sudo /etc/init.d/nfs-user-server restart
or
$ sudo /etc/init.d/nfs-kernel-server restart
Next time you boot, you can check your NFS server status with:
System Settings->System services

* '''On OpenSUSE'''
# /etc/init.d/nfsserver restart

==NFS usage on your Armadeus board==

===Mount the NFS partition manually ===

* create a mount point (for example):
# mkdir -p /mnt/host
* mount it (for example):
# mount -t nfs 192.168.0.2:/local/export /mnt/host
If 192.168.0.2 is your Host IP address and ''/local/export'' the name of your Host directory you want to mount.

===Mount the NFS partition automatically at each boot from FLASH===

* be sure to have the latest available software (>=armadeus2.0 or latest SVN)
* login to your Armadeus board as root
* open the '''/etc/fstab''' file and add this line:
<host-ip>:/<path-to-shared-folder> /mnt/<path-to-mount-folder> nfs hard,intr,rsize=8192,wsize=8192 0 0
example:
192.168.0.2:/local/export /mnt/host nfs hard,intr,rsize=8192,wsize=8192 0 0
* check your modification:
# mount /mnt/host
* reboot your board
# reboot
* and enjoy the result
# df
# ls /mnt/host
When you have a problem, verify that the NFS server is running on the host:
[host] $ /etc/init.d/nfs-kernel-server status
or
[host] $ /sbin/service nfs status

===Boot from NFS===

* in U-Boot set the ''rootpath'' envt variable accordingly (for example if your NFS export file is ''/local/export'' on your Host):
BIOS> setenv rootpath /local/export
* save it:
BIOS> saveenv
* then boot with:
BIOS> run nfsboot

===Summary of the required Packages:===
* portmap (buildroot)
* nfs (busybox)
* nfs support (Linux, activated by default in Armadeus configuration)

==Troubleshooting:==

*1] If nfsd and mountd daemon are not running on your Host, then you will get a message like:
# mount: RPC: Program not registered
In that case, restart the NFS service on your Host (see above)
*2] To successfully mount a NFS drive, portmap daemon should be running on your target, if not system will hang during some minutes when you launch the mount !!
To check if portmap is running, look at the running processes:
# ps faux
If portmap is not listed, then launch it manually:
# /etc/init.d/S14portmap

==TFTP Server:==
* On Ubuntu/Kubuntu:
http://doc.ubuntu-fr.org/tftpd

==TFTP Server under Windows:==
For those who want to transfer some files from Windows (kernel image / root fs), a small and FREE tftp server is available here:
http://tftpd32.jounin.net/

* To copy a file (test.png) from the host (192.168.0.3) to the target use this command:
# tftp -g -r test.png 192.168.0.3

==NFS Server under Windows:==
For those who want to use the NFS service on Windows, a small and FREE NFS server is available here:
http://www.freedownloadscenter.com/Utilities/Misc__Utilities/nfsAxe.html

==Links==

* http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.8.
* [[SSH]]

{{LanguageBar|Network_Configuration|Configuration_Réseau|Netzwerk_Konfiguration}}

[[Category:Network]]

Network File System configuration

2008-06-19T08:16:04Z

NicolasL:

==Introduction==

On this page, you will find usefull informations to configure your Host or Target network

==NFS server on your development Host==

===Installation===
* On Fedora, NFS is part of your distribution so you normally don't need to install it.
* On Ubuntu/Kubuntu:
$ sudo apt-get install nfs-user-server
or if you prefer:
$ sudo apt-get install nfs-kernel-server

===Configuration===
====/etc/exports====
You have to configure the directory where you will store the files you want to share accross the network.
For that you have to modify the '''/etc/exports''' file (for example):
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.0.0(ro,no_root_squash,sync)
(In that case your Host will authorize all client from the subnet 192.168.*.* to access /local/export in read only mode)

====Restart of NFS server====
* '''On Fedora:'''
# /sbin/service nfs restart
Next time you boot, you can check your NFS server status with:
# /sbin/service nfs status
and if not started then:
# /sbin/service nfs start

* '''On Ubuntu/Kubuntu:'''
$ sudo /etc/init.d/nfs-user-server restart
or
$ sudo /etc/init.d/nfs-kernel-server restart
Next time you boot, you can check your NFS server status with:
System Settings->System services

* '''On OpenSUSE'''
# /etc/init.d/nfsserver restart

==NFS usage on your Armadeus board==

===Mount the NFS partition manually ===

* create a mount point (for example):
# mkdir -p /mnt/host
* mount it (for example):
# mount -t nfs 192.168.0.2:/local/export /mnt/host
If 192.168.0.2 is your Host IP address and ''/local/export'' the name of your Host directory you want to mount.

===Mount the NFS partition automatically at each boot from FLASH===

* be sure to have the latest available software (>=armadeus2.0 or latest SVN)
* login to your Armadeus board as root
* open the '''/etc/fstab''' file and add this line:
<host-ip>:/<path-to-shared-folder> /mnt/<path-to-mount-folder> nfs hard,intr,rsize=8192,wsize=8192 0 0
example:
192.168.0.2:/local/export /mnt/host nfs hard,intr,rsize=8192,wsize=8192 0 0
* check your modification:
# mount /mnt/host
* reboot your board
# reboot
* and enjoy the result
# df
# ls /mnt/host
When you have a problem, verify that the NFS server is running on the host:
[host] $ /etc/init.d/nfs-kernel-server status
or
[host] $ /sbin/service nfs status

===Boot from NFS===

* in U-Boot set the ''rootpath'' envt variable accordingly (for example if your NFS export file is ''/local/export'' on your Host):
BIOS> setenv rootpath /local/export
* save it:
BIOS> saveenv
* then boot with:
BIOS> run nfsboot

===Summary of the required Packages:===
* portmap (buildroot)
* nfs (busybox)
* nfs support (Linux, activated by default in Armadeus configuration)

==Troubleshooting:==

*1] If nfsd and mountd daemon are not running on your Host, then you will get a message like:
# mount: RPC: Program not registered
In that case, restart the NFS service on your Host (see above)
*2] To successfully mount a NFS drive, portmap daemon should be running on your target, if not system will hang during some minutes when you launch the mount !!
To check if portmap is running, look at the running processes:
# ps faux
If portmap is not listed, then launch it manually:
# /etc/init.d/S14portmap

==TFTP Server under Linux:==
* On Ubuntu/Kubuntu:
http://doc.ubuntu-fr.org/tftpd

==TFTP Server under Windows:==
For those who want to transfer some files from Windows (kernel image / root fs), a small and FREE tftp server is available here:
http://tftpd32.jounin.net/

* To copy a file (test.png) from the host (192.168.0.3) to the target use this command:
# tftp -g -r test.png 192.168.0.3

==NFS Server under Windows:==
For those who want to use the NFS service on Windows, a small and FREE NFS server is available here:
http://www.freedownloadscenter.com/Utilities/Misc__Utilities/nfsAxe.html

==Links==

* http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.8.
* [[SSH]]

{{LanguageBar|Network_Configuration|Configuration_Réseau|Netzwerk_Konfiguration}}

[[Category:Network]]

Target Software Installation

2008-06-19T08:10:50Z

NicolasL: /* Linux RootFS installation */

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

==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:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=00:0E:32:00:00:01
autoload=no
...

Use the command '''setenv''' to change these variables. For example, to set the IP address:
BIOS> setenv ipaddr 192.168.0.3

Use the command '''saveenv''' to save the state of your environment variables in FLASH memory:
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

===Network configuration===
In order to use the U-Boot's network features, you have to set the network environment variables:
BIOS> setenv netmask 255.255.255.0 (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.3
BIOS> setenv serverip 192.168.0.5 (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/root" (to boot Linux over NFS)

You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.

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.3
BIOS> setenv serverip 192.168.0.5
BIOS> saveenv

Do not forget to save your changes in FLASH, to have them available at next power up:
BIOS> saveenv
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
BIOS> run flash_reset_env

===Linux kernel building and installation===

* configure your Linux kernel:
[armadeus]$ make linux-menuconfig

* save your configuration and then rebuild your kernel image:
[armadeus]$ make linux

* check that your Armadeus kernel image size is smaller than the U-Boot partition (1,5MB):
[armadeus]$ ls -al buildroot/binaries/armadeus/
...
[armadeus]$ cp buildroot/binaries/armadeus/linux-kernel-2.6.23.1-arm.bin /tftpboot/

* Load kernel image with U-Boot through network:
BIOS> tftp 08000000 /tftpboot/linux-kernel-2.6.23.1-arm.bin
or with the serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/linux-kernel-2.6.23.1-arm.bin
the you can type the c command to reconnect to the terminal
----
<span style="color:red">
'''!!! 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) !!!'''
</span><br>
Check that transfered size value is less than 1572864 (0x180000 hex)
Bytes transferred = 1313216 (1409c0 hex)
----

* You can test your new kernel image without flashing it with:
BIOS> bootm 08000000

----

* Flash kernel image with:
BIOS> run flash_kernel

* To make it easier next time, you can write a small U-Boot script:
BIOS> setenv kernel_img linux-kernel-2.6.23.1-arm.bin
BIOS> setenv update_kernel_tftp if tftp 08000000 \${kernel_img}\; then run flash_kernel\; fi
* So next time you will only launch:
BIOS> run update_kernel_tftp

* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:
BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm
(the kernel image you want to try must have been loaded at 0x08000000)

===Linux RootFS installation===

* check that your Armadeus RootFS image size is smaller than the RootFS partition :
[armadeus]$ ls -al buildroot/binaries/armadeus/
...
[armadeus]$ cp buildroot/binaries/armadeus/rootfs.arm.jffs2 /tftpboot/

* Load RootFS image with U-Boot through network:
BIOS> tftp 08000000 /tftpboot/rootfs.arm.jffs2
or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/rootfs.arm.jffs2
then you can type the c command to reconnect to the terminal

* Flash RootFS image with:
BIOS> run flash_rootfs

* Now you should be ready to test Linux:
BIOS> boot

* To make it easier next time, you can write a small U-Boot script:
BIOS> setenv rootfs_img rootfs.arm.jffs2
BIOS> setenv update_rootfs_tftp if tftp 08000000 \${rootfs_img}\; then run flash_rootfs\; fi
BIOS> saveenv

* So next time you will only launch:
BIOS> run update_rootfs_tftp

===FPGA firmware installation===

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
BRAMTest led PS2 PS2_Opencore sram_test
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file.<br>
<br>
----
'''!!! 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 !!!'''
----
<br>

* Load FPGA firmware image file with U-Boot through:<br>
Ethernet:
BIOS> tftp 08000000 fpgafirmware.bit
fpgafirmware.bit is of course the name of your bitfile stored in your TFTP shared directory (/tftpboot/)

or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send path_to_your_tftp/fpgafirmware.bit
then you can type the c command to reconnect to the terminal

* Flash your firmware image with:
BIOS> run flash_firmware

* Test your new FPGA firmware:
BIOS> fpga load 0 ${firmware_addr} ${firmware_len}

* When your are satisfied with your firmware you can make it "autoloaded" at power up:
BIOS> setenv firmware_autoload 1
BIOS> saveenv

==Update U-Boot==

There are two steps to update U-Boot:
*1] Load the new U-Boot code in RAM
You can use the following commands to download U-boot:<br>
With Ethernet and a TFTP server:
BIOS> tftp 08000000 /tftpboot_path_to_buildroot/u-boot.bin
With Ethernet and a NFS server:
BIOS> nfs 08000000 host_ip_addr:/nfs_path_to_buildroot/u-boot.bin
With the kermit and a serial line
BIOS> loadb 08000000
<CTRL><ALT GR>\
c
send path_to_buildroot/u_boot.bin
c

*2] Transfer code from RAM to Flash memory
There is a simple U-Boot command/script to do that:
BIOS> run flash_uboot

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

Target Software Installation

2008-06-19T07:52:27Z

NicolasL: /* Linux kernel building and installation */

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

==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:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=00:0E:32:00:00:01
autoload=no
...

Use the command '''setenv''' to change these variables. For example, to set the IP address:
BIOS> setenv ipaddr 192.168.0.3

Use the command '''saveenv''' to save the state of your environment variables in FLASH memory:
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

===Network configuration===
In order to use the U-Boot's network features, you have to set the network environment variables:
BIOS> setenv netmask 255.255.255.0 (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.3
BIOS> setenv serverip 192.168.0.5 (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/root" (to boot Linux over NFS)

You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.

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.3
BIOS> setenv serverip 192.168.0.5
BIOS> saveenv

Do not forget to save your changes in FLASH, to have them available at next power up:
BIOS> saveenv
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
BIOS> run flash_reset_env

===Linux kernel building and installation===

* configure your Linux kernel:
[armadeus]$ make linux-menuconfig

* save your configuration and then rebuild your kernel image:
[armadeus]$ make linux

* check that your Armadeus kernel image size is smaller than the U-Boot partition (1,5MB):
[armadeus]$ ls -al buildroot/binaries/armadeus/
...
[armadeus]$ cp buildroot/binaries/armadeus/linux-kernel-2.6.23.1-arm.bin /tftpboot/

* Load kernel image with U-Boot through network:
BIOS> tftp 08000000 /tftpboot/linux-kernel-2.6.23.1-arm.bin
or with the serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/linux-kernel-2.6.23.1-arm.bin
the you can type the c command to reconnect to the terminal
----
<span style="color:red">
'''!!! 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) !!!'''
</span><br>
Check that transfered size value is less than 1572864 (0x180000 hex)
Bytes transferred = 1313216 (1409c0 hex)
----

* You can test your new kernel image without flashing it with:
BIOS> bootm 08000000

----

* Flash kernel image with:
BIOS> run flash_kernel

* To make it easier next time, you can write a small U-Boot script:
BIOS> setenv kernel_img linux-kernel-2.6.23.1-arm.bin
BIOS> setenv update_kernel_tftp if tftp 08000000 \${kernel_img}\; then run flash_kernel\; fi
* So next time you will only launch:
BIOS> run update_kernel_tftp

* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:
BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm
(the kernel image you want to try must have been loaded at 0x08000000)

===Linux RootFS installation===
* Load RootFS image with U-Boot through network:
BIOS> tftp 08000000 pathtoyourhostedbuildrootdir/rootfs.arm.jffs2
or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/rootfs.arm.jffs2
then you can type the c command to reconnect to the terminal

* Flash RootFS image with:
BIOS> run flash_rootfs

* Now you should be ready to test Linux:
BIOS> boot

* To make it easier next time, you can write a small U-Boot script:
BIOS> setenv rootfs_img rootfs.arm.jffs2
BIOS> setenv update_rootfs_tftp if tftp 08000000 \${rootfs_img}\; then run flash_rootfs\; fi
BIOS> saveenv

* So next time you will only launch:
BIOS> run update_rootfs_tftp

===FPGA firmware installation===

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
BRAMTest led PS2 PS2_Opencore sram_test
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file.<br>
<br>
----
'''!!! 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 !!!'''
----
<br>

* Load FPGA firmware image file with U-Boot through:<br>
Ethernet:
BIOS> tftp 08000000 fpgafirmware.bit
fpgafirmware.bit is of course the name of your bitfile stored in your TFTP shared directory (/tftpboot/)

or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send path_to_your_tftp/fpgafirmware.bit
then you can type the c command to reconnect to the terminal

* Flash your firmware image with:
BIOS> run flash_firmware

* Test your new FPGA firmware:
BIOS> fpga load 0 ${firmware_addr} ${firmware_len}

* When your are satisfied with your firmware you can make it "autoloaded" at power up:
BIOS> setenv firmware_autoload 1
BIOS> saveenv

==Update U-Boot==

There are two steps to update U-Boot:
*1] Load the new U-Boot code in RAM
You can use the following commands to download U-boot:<br>
With Ethernet and a TFTP server:
BIOS> tftp 08000000 /tftpboot_path_to_buildroot/u-boot.bin
With Ethernet and a NFS server:
BIOS> nfs 08000000 host_ip_addr:/nfs_path_to_buildroot/u-boot.bin
With the kermit and a serial line
BIOS> loadb 08000000
<CTRL><ALT GR>\
c
send path_to_buildroot/u_boot.bin
c

*2] Transfer code from RAM to Flash memory
There is a simple U-Boot command/script to do that:
BIOS> run flash_uboot

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

User:NicolasL

2008-06-17T15:18:28Z

NicolasL: New page: Bonjour, Je m'appelle Nicolas Lantz, j'ai 26 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 3 ans. Sinon,...

Bonjour,

Je m'appelle Nicolas Lantz, j'ai 26 ans, je suis Ingénieur en Génie électrique (INSA Lyon), et je fait de l'informatique embarqué avec du logiciel libre depuis 3 ans.

Sinon, j'habite à coté de grenoble au milieu des montagnes. (-;

== '''Différentes réalisations professionnel:''' ==

-Outils de génération et d'installation de Debian embarqué ( < 16Mo) ou de système réduits (<4Mo avec buildroot). Avec utilisation de "kexec", boot sur usb, interface d'adminisatration web...

-Démonstrateur de réseaux de capteurs cognitifs (Atmega 2561 et chip RF CC1000) utilisant un noyau à composant du Framework THINK et permettant la reconfiguration dynamique (rechargement d'une partie du code en flash dynamiquement et sans reboot).

-Passerelle Zigbee Ethernet (carte de dev Atmel AT91SAM7-XC-EK, avec FreeRTOS, Framework THINK, et pile TCP/IP Lwip).

== '''Mes compétences :''' ==

Du copier coller de mon CV (-;

Environnements : GNU/Linux: Debian / Ubuntu
Noyaux en Embarqué : Construction de tout système, Linux (à partir de 2Mo) et Open-sources (à partir de quelques kilo-octets pour le multi-taches): Framework THINK (noyau à composant logiciel), FreeRTOS...
Microprocesseurs : ARM7, ARM9, i386, ATMEGA 8bit, NIOS 2...
Protocoles : TCP/ IP /UDP, DHCP, ftp, tftp, http, cgi, série, spi, zigbee...
Langages info. emb. : C, ShellScripts, Assembleur...
Outils sous Linux : Eclipse, SVN, gcc, gdb, make, ant, Buildroot, OpenOCD, Avarice...

== '''Objectifs :''' ==

Members

2008-06-11T09:46:18Z

NicolasL:

==Google Map==

<googlemap lat="47" lon="6" width=640 height=480 zoom=4>
47.270377, 6.025314, [[User:JulienB]] Besancon
47.752598,7.301788, ARMadeus Systems
47.760791, 7.339897, [[User:Salocin68]] Mulhouse
47.734392,7.316975, [[User:FabienM]] Mulhouse
46.550833, 6.632309, [[User:Jorasse]] Lausanne
47.681108, 7.390366, [[User:Carbure]] Helfranzkirch
47.436448, 8.429947, [[User:SonZerro]] Baden
44.653992, 6.176672, [[User:JulienN]] Chabottes
48.573342, 7.911476, [[User:KroMignon]] Legelshurst
42.734405, 2.894211, ELIAUS Perpignan
47.653363, 6.862335, UTBM Belfort
48.879619, 2.351074, Paris - 20 membres
-21.115141, 55.536384, La Réunion - 1 member
14.551684, -60.912323, La Martinique - 1 member

47.399744, 8.53775, Zurich - 1 member
46.810282, 7.151241, Fribourg
47.574904, 7.580566, Basel

53.371859, -6.2677, Dublin - 1 member
50.637704, 5.608521, Liège - 1 member
50.67, 3.48, Velaines - 1 member
48.199964, 11.57959, Munich - 1 member
48.109588,-1.678752, Rennes - 1 member
47.750109,-3.366339, [[User:MatthieuT]] Lorient
48.70,2.03, [[User:JulienPeeters]] Chevreuse
45.2023, 5.84063, [[User:NicolasL]] Domène
</googlemap>
<br>
<br>
<br>

==!!! Everything above this line is obsolete and will be removed soon !!!==

<div style="position: relative">[[Image:France.jpg]]

<div style="position: absolute; left: 350px; top: 250px">
{| style="background:transparent"
|-
| Besançon(3)
|}
</div>
<div style="position: absolute; left: 350px; top: 320px">
{| style="background:transparent"
|-
| Lyon(1)
|}
</div>
<div style="position: absolute; left: 390px; top: 340px">
{| style="background:transparent"
|-
| Grenoble(1)
|}
</div>
<div style="position: absolute; left: 350px; top: 360px">
{| style="background:transparent"
|-
| Valence(1)
|}
</div>
<div style="position: absolute; left: 310px; top: 220px">
{| style="background:transparent"
|-
| Dijon(1)
|}
</div>
<div style="position: absolute; left: 420px; top: 180px">
{| style="background:transparent"
|-
| Mulhouse(3)
|}
</div>
<div style="position: absolute; left: 400px; top: 210px">
{| style="background:transparent"
|-
| Montbéliard/Belfort(2)
|}
</div>
<div style="position: absolute; left: 460px; top: 120px">
{| style="background:transparent"
|-
| Strasbourg(3)
|}
</div>
<div style="position: absolute; left: 400px; top: 100px">
{| style="background:transparent"
|-
| Metz(1)
|}
</div>
<div style="position: absolute; left: 400px; top: 145px">
{| style="background:transparent"
|-
| Charmes(1)
|}
</div>
<div style="position: absolute; left: 255px; top: 5px">
{| style="background:transparent"
|-
| Lille(1)
|}
</div>
<div style="position: absolute; left: 250px; top: 70px">
{| style="background:transparent"
|-
| Amiens(1)
|}
</div>
<div style="position: absolute; left: 250px; top: 150px">
{| style="background:transparent"
|-
| Paris(20)
|}
</div>
<div style="position: absolute; left: 300px; top: 120px">
{| style="background:transparent"
|-
| Soisson(1)
|}
</div>
<div style="position: absolute; left: 335px; top: 132px">
{| style="background:transparent"
|-
| Reims(1)
|}
</div>
<div style="position: absolute; left: 150px; top: 190px">
{| style="background:transparent"
|-
| Angers(1)
|}
</div>
<div style="position: absolute; left: 100px; top: 210px">
{| style="background:transparent"
|-
| Nantes(1)
|}
</div>
<div style="position: absolute; left: 180px; top: 170px">
{| style="background:transparent"
|-
| Le Mans(1)
|}
</div>
<div style="position: absolute; left: 80px; top: 150px">
{| style="background:transparent"
|-
| Rennes(2)
|}
</div>
<div style="position: absolute; left: 250px; top: 480px">
{| style="background:transparent"
|-
| Perpignan(1)
|}
</div>
<div style="position: absolute; left: 350px; top: 450px">
{| style="background:transparent"
|-
| Aix/Marseille(1)
|}
</div>
<div style="position: absolute; left: 200px; top: 400px">
{| style="background:transparent"
|-
| Toulouse(2)
|}
</div>
<div style="position: absolute; left: 200px; top: 350px">
{| style="background:transparent"
|-
| Périgueux(1)
|}
</div>
</div>

[[Category:Association]]

MemberList

2008-06-11T09:30:30Z

NicolasL: /* 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
<br>

{| 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 || 1 || 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 ||
|}

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

[[Category:Association]]