ArmadeusWiki - User contributions [en]

LinuxInstall

2009-12-01T16:15:04Z

SebastienVC: /* Debian/Ubuntu based systems */

<noinclude>
<big>How-To install Armadeus Software Development Kit (SDK) on Linux systems. This SDK is currently based on the (excellent) [http://buildroot.net/ Buildroot].</big>
</noinclude>

The installation was successfully tested on the following distributions:
* Debian Sarge (3.1), Etch (4.0) & Lenny (5.0)
* Fedora Core 3 & 4
* Fedora 10
* KUbuntu Edgy Eft (6.10), Gutsy Gibbon (7.10), Hardy Heron (8.04) & Jaunty Jackalope (9.04)
* Mandriva 2006
* SuSE 10.1
* Ubuntu Dapper Drake (6.04), Hardy Heron (8.04) & Intrepid Ibex (8.10)
* Xubuntu Edgy Eft (6.10)
* Red Hat Enterprise 5.2

'''The installation may fail on:'''
* Ubuntu Karmic Koala (9.10): tslib fails to build

==Prerequisites for Linux installation==
{{Note|From here we assume that your Linux system has a ''make'' version '''greater or equal to''' 3.81. To check it:
<pre class="host">
$ make -v
GNU Make 3.81
...
</pre>
}}

Depending on your distribution, some additional packages are required.

===Debian/Ubuntu based systems===
* you can use the following command to get them (assuming your userid is allowed to use sudo (execution of commands as root)):
<pre class="host">
sudo apt-get install build-essential gcc g++ autoconf automake libtool bison flex gettext
sudo apt-get install patch subversion texinfo wget git-core
sudo apt-get install libncurses5 libncurses5-dev
sudo apt-get install zlib1g-dev liblzo2-2 liblzo2-dev
sudo apt-get install libacl1 libacl1-dev
sudo apt-get install uuid-dev
</pre>

Not mandatory but useful to add for compiling some Buildroot packages:
<pre class="host">
sudo apt-get install libglib2.0-dev
sudo apt-get install libnetpbm10-dev (for fbtest)
</pre>

{{Warning|For Ubuntu based systems, the following is now required if your ''/bin/sh'' is '''not''' pointing to ''/bin/bash'':
<pre class="host">
$ ls -al /bin/sh
lrwxrwxrwx 1 root root 4 2007-12-08 18:33 /bin/sh -> dash
$ sudo dpkg-reconfigure dash
and select no
</pre>
Indeed dash do not support all the capabilities needed by Buildroot (our build system).
}}

{{Warning|For Ubuntu 9.10, it is required to patch the target Linux Kernel and use GCC 4.1.x supplied in the distribution:

Go to the Linux Kernel source tree, in the source directory, replace any occurence of the word ''getline'' in the file ''scripts/unifdef.c'' by
anything else like ''fetchline''. In newer versions of the GNU Libc, getline is a standard function. It makes collisions with the function
included in the build scripts

<pre class="host">
$ sudo rm /usr/bin/gcc
$ sudo ln -s /usr/bin/gcc-4.1 /usr/bin/gcc
</pre>
If you let GCC 4.4.x compile GCC 4.2.x it WILL fail.
}}

===Mandriva based systems===
* name of packages are different therefore use the lines hereafter instead (assuming sudo is configured to support root commands):
<pre class="host">
sudo urpmi gcc gcc-c++ make autoconf automake libtool bison flex gettext
sudo urpmi patch subversion texinfo wget git
sudo urpmi libncurses5 libncurses-devel
sudo urpmi zlib1-devel liblzo2_2 liblzo-devel
sudo urpmi libacl1 libacl-devel
sudo urpmi uuid-dev
</pre>

Not mandatory but useful to add some Buildroot packages:
<pre class="host">
sudo urpmi libglib2.0-devel
</pre>

===RPM-based systems===
*like RedHat, Fedora, CentOS, the following commands should install all the needed prerequisites (assuming root shell):
<pre class="host">
yum install gcc gcc-c++ make autoconf automake libtool bison flex gettext
yum install patch subversion texinfo git wget
yum install zlib-devel gettext-devel ncurses-devel lzo-devel libacl-devel
</pre>

Not mandatory but useful to add some extra packages:
<pre class="host">
yum install glib2-devel lzo2-devel
</pre>
* On RedHat Enterprise 5.2 not all packages are available by default. You can get extra packages here: http://download.fedora.redhat.com/pub/epel/5/i386/ (for example missing ''lzo'' and ''lzo-devel'' can be found here).

==Get Armadeus software==
* '''If you are a "careful" user''', then download [http://sourceforge.net/project/showfiles.php?group_id=122057&package_id=133240 the latest stable installation tarball from SourceForge] and detar it wherever you want:
<pre class="host">
$ tar xjvf armadeus-3.1.tar.bz2
</pre>
* '''If you want the latest snapshot''', the whole development tree can now be checked out from the new [[GIT]] repository. (SVN repository is no more maintained !!!)
<pre class="host">
$ git clone git://armadeus.git.sourceforge.net/gitroot/armadeus/armadeus armadeus
</pre>

A directory named ''armadeus/'' or ''armadeus-3.1/'' will be created on your hard-disk and will contain all the files you need.

'''Remarks''':
* '''Do not use spaces''' in the directory name !
* GIT write/push accesses are limited to the integrators ([[User:JulienB|JulienB]], [[User:Salocin68|Salocin68]], [[User:Jorasse|Jorasse]], [[User:FabienM|FabienM]])

==Configure SDK options==
The first time you compile an Armadeus distribution you have to specify the target to work with.
<pre class="host">
$ cd armadeus/ (or armadeus-3.1/)
$ make apf9328_defconfig
</pre>
This command reloads the default configuration to support an [[APF9328|APF9328 board]] and automatically start a Buildroot's configuration menu. For the [[APF27]] it would be:
<pre class="host">
$ make apf27_defconfig
</pre>

{{Note|If you ever made changes in the following steps, at any time you can reload the default configuration with '''make apf9328_defconfig''' or '''make apf27_defconfig'''.}}

[[Image:Menuconfig3.png]] 
*If you are not familiar with Buildroot here are some tips:
*# you can move the highlighted item with the "up"/"down" arrow keys
*# with the "left"/"right" arrow keys you can choose between "Select", "Exit" or "Help" buttons
*# "space"/"enter":
*#* selects the currently highlighted item if you are on the "Select" button
*#* go back in previous menu if you are on "Exit" button
*#* show you some Help for current item if you are on "Help" button
*# for more Help about Buildroot commands, select "Help" in the main configuration screen

*In menu:
:<pre class="config">Target options --->
:[*] Armadeus Device Support ---></pre>
:you can check and change the quantity of RAM available on your Armadeus board. Default value 16MB is just fine with all [[APF9328]] boards, for [[APF27]] it could be either 64MB or 128MB (2 x 64MB) (in that case be sure to select 2 chips of 64MB instead of 1 chip of 128MB).

*In menu:
:<pre class="config">Target filesystem options --> </pre>
:for each type of filesystems to build, you have the option (''also copy the image to...'') to copy the binary file to secondary location like your tftp server folder (for example ''/tftpboot''). 
:Even U-Boot can be copied to a second location (like ''/tftpboot''). You will find the U-Boot options at the end of the list.

*In menu:
:<pre class="config">Kernel -->
:Destination for linux kernel binaries --> </pre>
:you will find options to copy Linux to a secondary location (like ''/tftpboot'')

* You may decrease the compilation time by increasing the number of parallel jobs running simultaneously on your system (the result is not guaranteed). This option is located in
:<pre class="config">Build Options --->
:(1) Number of jobs to run simultaneously</pre>

* During the toolchain/distribution automatic build, a lot of software archives are downloaded from Internet. The downloaded files are put by default in the ''armadeus/downloads/'' directory. '''If you have several views or plan to build the toolchain several times''', we advise you to put all the downloaded files in ''/local/downloads'' (for example). This is done by configuring Buildroot to use this directory for all your views. Nevertheless, buildroot will be downloaded separately for each build environment you set up.
:<pre class="config">Build options --->
:(...) Download dir</pre>
:[[Image:Build_config_menu_download.png]] 
:[[Image:Build_config_download.png]]

* After the build, we advise you too to copy all the files in ''downloads/'' on a removable medium, in case you want to install the development tools on several systems.

* Now, Exit the configuration tool and save your configuration

==Launch build==
$ make
The toolchain and the full distribution are automatically built. During this procedure, several files are downloaded from Internet. 
'''Please wait for a while.... it takes at least one hour for the first run!''' 
By default, the downloaded files/tarball are put in the ''armadeus/downloads/'' directory. Please see the previous chapter to know how to optimize that if you plan to build several views.

==Enjoy the result==
The generated binary files can be found in the subdirectory ''buildroot/binaries/apfXX/'' (where XX is the name of your board):

*''apf9328-u-boot.brec'' (only on [[APF9328]]): BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working (see [[BootLoader]] page)
*''apfXX-u-boot.bin'': U-Boot image file to be used with U-Boot itself, (see [[BootLoader#Update_U-Boot | updating U-Boot]])
*''apfXX-linux.bin'': Linux image to use with U-Boot, (see [[Target_Software_Installation#Linux_kernel_installation | updating Linux]])
*''apfXX-rootfs.arm.jffs2'': JFFS2 filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''apf27-rootfs.arm.ubifs'' (only on [[APF27]]): [[UBIFS]] filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''apfXX-rootfs.arm.tar'': for an NFS/MMC based rootfs, (see [[Network_Configuration#Boot_from_NFS | Booting from NFS]] & [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])

'''Please note the new naming convention of binary files and directories'''

The toolchain and project files share a new naming convention too (YY is 4t for APF9328 and 5te for APF27):
*''buildroot/build_armvYY'': contains all non configurable user-space tools
*''buildroot/project_build_armvYY/apfXX'': contains all configurable user-space tools: target filesystem, linux, busybox and u-boot...
*''buildroot/toolchain_build_armvYY'': cross compilation toolchain

More information is available in the [http://buildroot.uclibc.org/buildroot.html buildroot documentation]

* Note: Previous versions of Armadeus SDK stored the generated binary files at different place ''buildroot/binaries/armadeus/'' and file names did not contained any prefix of board name:
**u-boot.brec (BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working)
**u-boot.bin (U-Boot image file for use with U-Boot itself)
**linux-kernel-2.6.xx-arm.bin (Linux image to use with U-Boot)
**rootfs.arm.jffs2 (FileSystem/RootFS image to use with U-Boot)
**rootfs.arm.tar (for an NFS/MMC RootFS)

<noinclude>

==To keep your local copy/repository up-to-date with the armadeus GIT repository==
<pre class="host">
$ git pull
</pre>
This will update your working directory to the latest release.

Note: if "git pull" fails because a directory or a file already exists, then do:
$ rm -rf <this-directory/file>
$ git pull

You can do a:
$ make apf9328_defconfig
to have the latest features automatically activated.

You have to do a '''make''' to rebuild binary files and then upload the binary files to your target.

Note: if definitively everything goes wrong while it worked before the last update.
You can apply the following procedure (all your modifications in buildroot will be lost):
$ rm -rf buildroot/
$ rm Makefile
$ git pull
$ make apf9328_defconfig
$ make

Enjoy!

{{LanguageBar|LinuxInstall|Compilateur croisé|LinuxInstall}}
</noinclude>

LinuxInstall

2009-12-01T16:12:50Z

SebastienVC: Little workaround for Ubuntu 9.10

<noinclude>
<big>How-To install Armadeus Software Development Kit (SDK) on Linux systems. This SDK is currently based on the (excellent) [http://buildroot.net/ Buildroot].</big>
</noinclude>

The installation was successfully tested on the following distributions:
* Debian Sarge (3.1), Etch (4.0) & Lenny (5.0)
* Fedora Core 3 & 4
* Fedora 10
* KUbuntu Edgy Eft (6.10), Gutsy Gibbon (7.10), Hardy Heron (8.04) & Jaunty Jackalope (9.04)
* Mandriva 2006
* SuSE 10.1
* Ubuntu Dapper Drake (6.04), Hardy Heron (8.04) & Intrepid Ibex (8.10)
* Xubuntu Edgy Eft (6.10)
* Red Hat Enterprise 5.2

'''The installation may fail on:'''
* Ubuntu Karmic Koala (9.10): tslib fails to build

==Prerequisites for Linux installation==
{{Note|From here we assume that your Linux system has a ''make'' version '''greater or equal to''' 3.81. To check it:
<pre class="host">
$ make -v
GNU Make 3.81
...
</pre>
}}

Depending on your distribution, some additional packages are required.

===Debian/Ubuntu based systems===
* you can use the following command to get them (assuming your userid is allowed to use sudo (execution of commands as root)):
<pre class="host">
sudo apt-get install build-essential gcc g++ autoconf automake libtool bison flex gettext
sudo apt-get install patch subversion texinfo wget git-core
sudo apt-get install libncurses5 libncurses5-dev
sudo apt-get install zlib1g-dev liblzo2-2 liblzo2-dev
sudo apt-get install libacl1 libacl1-dev
sudo apt-get install uuid-dev
</pre>

Not mandatory but useful to add for compiling some Buildroot packages:
<pre class="host">
sudo apt-get install libglib2.0-dev
sudo apt-get install libnetpbm10-dev (for fbtest)
</pre>

{{Warning|For Ubuntu based systems, the following is now required if your ''/bin/sh'' is '''not''' pointing to ''/bin/bash'':
<pre class="host">
$ ls -al /bin/sh
lrwxrwxrwx 1 root root 4 2007-12-08 18:33 /bin/sh -> dash
$ sudo dpkg-reconfigure dash
and select no
</pre>
Indeed dash do not support all the capabilities needed by Buildroot (our build system).
}}

{{Warning|For Ubuntu 9.10, it is required to patch the target Linux Kernel and use GCC 4.1.x supplied in the distribution:

Go to the Linux Kernel source tree, in the source directory, replace any occurence of the word ''getline'' in the file ''unifdef.c'' by
anything else like ''fetchline''. In newer versions of the GNU Libc, getline is a standard function. It makes collisions with the function
included in the build scripts

<pre class="host">
$ sudo rm /usr/bin/gcc
$ sudo ln -s /usr/bin/gcc-4.1 /usr/bin/gcc
</pre>
If you let GCC 4.4.x compile GCC 4.2.x it WILL fail.
}}

===Mandriva based systems===
* name of packages are different therefore use the lines hereafter instead (assuming sudo is configured to support root commands):
<pre class="host">
sudo urpmi gcc gcc-c++ make autoconf automake libtool bison flex gettext
sudo urpmi patch subversion texinfo wget git
sudo urpmi libncurses5 libncurses-devel
sudo urpmi zlib1-devel liblzo2_2 liblzo-devel
sudo urpmi libacl1 libacl-devel
sudo urpmi uuid-dev
</pre>

Not mandatory but useful to add some Buildroot packages:
<pre class="host">
sudo urpmi libglib2.0-devel
</pre>

===RPM-based systems===
*like RedHat, Fedora, CentOS, the following commands should install all the needed prerequisites (assuming root shell):
<pre class="host">
yum install gcc gcc-c++ make autoconf automake libtool bison flex gettext
yum install patch subversion texinfo git wget
yum install zlib-devel gettext-devel ncurses-devel lzo-devel libacl-devel
</pre>

Not mandatory but useful to add some extra packages:
<pre class="host">
yum install glib2-devel lzo2-devel
</pre>
* On RedHat Enterprise 5.2 not all packages are available by default. You can get extra packages here: http://download.fedora.redhat.com/pub/epel/5/i386/ (for example missing ''lzo'' and ''lzo-devel'' can be found here).

==Get Armadeus software==
* '''If you are a "careful" user''', then download [http://sourceforge.net/project/showfiles.php?group_id=122057&package_id=133240 the latest stable installation tarball from SourceForge] and detar it wherever you want:
<pre class="host">
$ tar xjvf armadeus-3.1.tar.bz2
</pre>
* '''If you want the latest snapshot''', the whole development tree can now be checked out from the new [[GIT]] repository. (SVN repository is no more maintained !!!)
<pre class="host">
$ git clone git://armadeus.git.sourceforge.net/gitroot/armadeus/armadeus armadeus
</pre>

A directory named ''armadeus/'' or ''armadeus-3.1/'' will be created on your hard-disk and will contain all the files you need.

'''Remarks''':
* '''Do not use spaces''' in the directory name !
* GIT write/push accesses are limited to the integrators ([[User:JulienB|JulienB]], [[User:Salocin68|Salocin68]], [[User:Jorasse|Jorasse]], [[User:FabienM|FabienM]])

==Configure SDK options==
The first time you compile an Armadeus distribution you have to specify the target to work with.
<pre class="host">
$ cd armadeus/ (or armadeus-3.1/)
$ make apf9328_defconfig
</pre>
This command reloads the default configuration to support an [[APF9328|APF9328 board]] and automatically start a Buildroot's configuration menu. For the [[APF27]] it would be:
<pre class="host">
$ make apf27_defconfig
</pre>

{{Note|If you ever made changes in the following steps, at any time you can reload the default configuration with '''make apf9328_defconfig''' or '''make apf27_defconfig'''.}}

[[Image:Menuconfig3.png]] 
*If you are not familiar with Buildroot here are some tips:
*# you can move the highlighted item with the "up"/"down" arrow keys
*# with the "left"/"right" arrow keys you can choose between "Select", "Exit" or "Help" buttons
*# "space"/"enter":
*#* selects the currently highlighted item if you are on the "Select" button
*#* go back in previous menu if you are on "Exit" button
*#* show you some Help for current item if you are on "Help" button
*# for more Help about Buildroot commands, select "Help" in the main configuration screen

*In menu:
:<pre class="config">Target options --->
:[*] Armadeus Device Support ---></pre>
:you can check and change the quantity of RAM available on your Armadeus board. Default value 16MB is just fine with all [[APF9328]] boards, for [[APF27]] it could be either 64MB or 128MB (2 x 64MB) (in that case be sure to select 2 chips of 64MB instead of 1 chip of 128MB).

*In menu:
:<pre class="config">Target filesystem options --> </pre>
:for each type of filesystems to build, you have the option (''also copy the image to...'') to copy the binary file to secondary location like your tftp server folder (for example ''/tftpboot''). 
:Even U-Boot can be copied to a second location (like ''/tftpboot''). You will find the U-Boot options at the end of the list.

*In menu:
:<pre class="config">Kernel -->
:Destination for linux kernel binaries --> </pre>
:you will find options to copy Linux to a secondary location (like ''/tftpboot'')

* You may decrease the compilation time by increasing the number of parallel jobs running simultaneously on your system (the result is not guaranteed). This option is located in
:<pre class="config">Build Options --->
:(1) Number of jobs to run simultaneously</pre>

* During the toolchain/distribution automatic build, a lot of software archives are downloaded from Internet. The downloaded files are put by default in the ''armadeus/downloads/'' directory. '''If you have several views or plan to build the toolchain several times''', we advise you to put all the downloaded files in ''/local/downloads'' (for example). This is done by configuring Buildroot to use this directory for all your views. Nevertheless, buildroot will be downloaded separately for each build environment you set up.
:<pre class="config">Build options --->
:(...) Download dir</pre>
:[[Image:Build_config_menu_download.png]] 
:[[Image:Build_config_download.png]]

* After the build, we advise you too to copy all the files in ''downloads/'' on a removable medium, in case you want to install the development tools on several systems.

* Now, Exit the configuration tool and save your configuration

==Launch build==
$ make
The toolchain and the full distribution are automatically built. During this procedure, several files are downloaded from Internet. 
'''Please wait for a while.... it takes at least one hour for the first run!''' 
By default, the downloaded files/tarball are put in the ''armadeus/downloads/'' directory. Please see the previous chapter to know how to optimize that if you plan to build several views.

==Enjoy the result==
The generated binary files can be found in the subdirectory ''buildroot/binaries/apfXX/'' (where XX is the name of your board):

*''apf9328-u-boot.brec'' (only on [[APF9328]]): BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working (see [[BootLoader]] page)
*''apfXX-u-boot.bin'': U-Boot image file to be used with U-Boot itself, (see [[BootLoader#Update_U-Boot | updating U-Boot]])
*''apfXX-linux.bin'': Linux image to use with U-Boot, (see [[Target_Software_Installation#Linux_kernel_installation | updating Linux]])
*''apfXX-rootfs.arm.jffs2'': JFFS2 filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''apf27-rootfs.arm.ubifs'' (only on [[APF27]]): [[UBIFS]] filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''apfXX-rootfs.arm.tar'': for an NFS/MMC based rootfs, (see [[Network_Configuration#Boot_from_NFS | Booting from NFS]] & [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])

'''Please note the new naming convention of binary files and directories'''

The toolchain and project files share a new naming convention too (YY is 4t for APF9328 and 5te for APF27):
*''buildroot/build_armvYY'': contains all non configurable user-space tools
*''buildroot/project_build_armvYY/apfXX'': contains all configurable user-space tools: target filesystem, linux, busybox and u-boot...
*''buildroot/toolchain_build_armvYY'': cross compilation toolchain

More information is available in the [http://buildroot.uclibc.org/buildroot.html buildroot documentation]

* Note: Previous versions of Armadeus SDK stored the generated binary files at different place ''buildroot/binaries/armadeus/'' and file names did not contained any prefix of board name:
**u-boot.brec (BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working)
**u-boot.bin (U-Boot image file for use with U-Boot itself)
**linux-kernel-2.6.xx-arm.bin (Linux image to use with U-Boot)
**rootfs.arm.jffs2 (FileSystem/RootFS image to use with U-Boot)
**rootfs.arm.tar (for an NFS/MMC RootFS)

<noinclude>

==To keep your local copy/repository up-to-date with the armadeus GIT repository==
<pre class="host">
$ git pull
</pre>
This will update your working directory to the latest release.

Note: if "git pull" fails because a directory or a file already exists, then do:
$ rm -rf <this-directory/file>
$ git pull

You can do a:
$ make apf9328_defconfig
to have the latest features automatically activated.

You have to do a '''make''' to rebuild binary files and then upload the binary files to your target.

Note: if definitively everything goes wrong while it worked before the last update.
You can apply the following procedure (all your modifications in buildroot will be lost):
$ rm -rf buildroot/
$ rm Makefile
$ git pull
$ make apf9328_defconfig
$ make

Enjoy!

{{LanguageBar|LinuxInstall|Compilateur croisé|LinuxInstall}}
</noinclude>

Toolchain

2009-12-01T15:57:50Z

SebastienVC:

How-To install Armadeus Software Development Kit for Linux/Window$

=Forewords=
Before writing your first program or changing some of your system's utilities, you will need to build the tools required to compile them on your Host system (cross compilation).
The GNU toolchain will be used.

=Lexical=
* Binutils: several GNU utilities to generate executable files
* [http://buildroot.uclibc.org/ Buildroot]: set of Makefiles that allow to entirely build embedded Linux systems
* [http://www.busybox.net/ Busybox]: "swiss knife" of the embedded Linux (regroup many common programs in one executable)
* [http://gcc.gnu.org/ GCC]: GNU C compiler
* GDB: GNU debugger
* rootfs (root filesystem): filesystem image which will be installed on your target and used by Linux as root ("/") mountpoint.
* [http://www.denx.de/wiki/U-Boot U-Boot]: Bios / Bootloader

=Recommended System Requirements=
* HD free space: at least 3GB
* 1GB RAM is preferable
* 2GHz processor with a 533MHz FSB
* High speed Internet connection (1Mbits)
With these settings, you will get a complete toolchain, Linux and the RootFS in about 1h30.

=[[LinuxInstall | Linux installation]]=
{{:LinuxInstall}}

=Window$ installation=
There are 3 ways of having Armadeus SDK (Linux based) running on Window$ Hosts:
* Cygwin (not supported anymore)
* VMWare
* VirtualBox / QEmu x86

{{Note|After a performance test with VMWare, it is clear that '''Cygwin won't be supported anymore.''' We have observed quite a factor 2 in terms of compilation improvements with VMWare}}

So, on Window$ Hosts, installing the SDK will summary in:
* install VMWare or VirtualBox,
* install a Linux distribution on it (Ubuntu, Mandriva, Fedora, Gentoo,... as you like)
* and then follow [[LinuxInstall | Linux installation steps]].

==What are [http://www.vmware.com/ VMWare] & [http://www.virtualbox.org/ Virtual Box] ?==
* They are virtualization tools able to run a standard Linux distribution on a native Window$ system or Window$ on a Linux native system.
* VMWare player is free. VMWare desktop (used to create the first virtual system) is available for evaluation. You need it only one time.
* VirtualBox is a Open Source software.

Be aware that VMWare/VirtualBox will require more disk space than cygwin, because a complete Linux distribution will be installed. 
 
[[WindowsInstall | Windows installation with Cygwin (no more used)]]

[[Category:Toolchain]]

Members

2009-12-01T15:51:07Z

SebastienVC:

==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.946161,7.517052, [[User:Jorasse]] Gümligen
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
45.689589, 5.026395, [[User:OlivierT]] St Bonnet de Mure
48.879619, 2.351074, Paris - 20 members
43.622159, 1.442642, Toulouse - 2 members
-21.115141, 55.536384, La Réunion - 1 member
14.551684, -60.912323, La Martinique - 1 member
48.682805, 2.169186, [[User:BrunoL]] Les Ulis
47.399744, 8.53775, Zurich - 1 member
46.810282, 7.151241, Fribourg
47.574904, 7.580566, Basel
48.839250, 2.392584, [[User:jmn12]] Paris

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.190325, 5.700316, [[User:NicolasL]] Fontaine
49.279296, 2.472973 [[User:DavidC]] Nogent sur Oise
46.208644, 6.130027, [[User:EugeneR]] Genève
48.667158, 2.706585, [[User:BernardR]] Soignolles en Brie, France
45.188963, 5.709822, [[User:OlivierS]], [[User:HugoP|Hugo Petit]] - Grenoble, France
47.214613,-0.737329, [[User:BrunoS]] Chemillé, France
47.225164,-1.556625, [[User:KevinP]] Nantes, France
43.609234, 1.442642, [[User:PierreBa]] Toulouse, France
41.668809,-0.87616, [[User:AntonioMB]] Zaragoza, España
49.200145, 0.407136, [[User:JeanFrancoisR]] - Asnières
48.109588,-1.678752, [[User:MichelTe]] - Rennes
49.163073, 2.550201, [[User:JulienBa]] - Pontarmé
43.488299, 5.494709, [[User:FrankA]] - Meyreuil
43.622159, 1.442642, [[User:PierreAlexandreS]] - Toulouse, France
51.46513, -0.9692, [[User:AlexG]] - Reading, UK
43.312439, 10.517693, [[User:PaoloB]] - Cecina, Italy
52.63, 4.75, Alkmaar - 1 member
47.201843, -0.991516, [[User:SamuelM]] - Beaupreau, France
50.776093, 14.632759, [[User:PetrD]] - Cvikov, ČR
48.42097, -4.471693, [[User:OlivierR]] - Brest, France
48.575244,-4.563446, [[User:JeanChristopheL]] - Brest, France
49.417767, 2.826945, [[User:PhilippeL]] - Compiègne, France
48.806044, 2.347512, [[User:PierreDe]] - Arcueil, France
50.803050, 4.358533, [[User:SebastienVC]] - Bruxelles, Belgique

</googlemap>
 
===How to add your position===
* go to http://maps.google.com/
* type in the name of your town and launch "Search Google Maps", for example:
[[Image:Google_maps_search.png]]
* right click on "Get URL of this page" and copy the URL
[[Image:Google_maps_url.png]]
* you should get something like that:
<pre>
http://maps.google.com/maps?f=q&hl=fr&geocode=&q=besan%C3%A7on&ie=UTF8&ll=47.257796,6.025314&spn=0.216236,0.601501&z=11&iwloc=addr
</pre>
* the data between ''&ll='' and ''&spn'' are the needed one (latitude/longitude)
* extract them and copy them in the "Edit" of this wiki page. Add it you wiki name and your town. For example:
<pre>
<googlemap lat="47" lon="6" width=640 height=480 zoom=4>
...
Others coordinates
...
47.257796, 6.025314, [[User:YourID]|YourName] - Your Town
</googlemap>
</pre>

[[Category:Association]]

MemberList

2009-12-01T15:41:04Z

SebastienVC: /* 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
|}

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

[[Category:Association]]

MemberList

2009-12-01T15:39:40Z

SebastienVC: /* 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 || embedded software, robotics

|}

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

[[Category:Association]]

User:SebastienVC

2009-12-01T15:36:14Z

SebastienVC: ArmadeusWiki:Users moved to User:SebastienVC

[[MemberList | << liste des membres]]

= Présentation =

Sébastien Van Cauwenberghe, Ingénieur Industriel en Electronique.

J'ai toujours été passionné par l'informatique et l'électronique. Lors de mes études et surtout lors de la dernière année, j'ai eu l'occasion de découvrir cette carte embarquée que j'ai utilisé dans le cadre de mon travail de fin d'études pour le pilotage et la régulation numérique de convertisseurs DC-DC.

== Compétences ==

* Programmation en C, C++, PHP, Bash
* Developpement avec des RTOS et de drivers Linux
* Conception et simulation VHDL
* Microcontrolleurs PIC, Z80, 8051, ARM

== Participation au projet ==
* Documentation
* Quelques patchs sans prétention

== Projets ==

* Pilotage et régulation numérique d'un convertisseur DC-DC avec commande par Ethernet
* Gestionnaire d'IO

ArmadeusWiki:Users

2009-12-01T15:36:14Z

SebastienVC: ArmadeusWiki:Users moved to User:SebastienVC

#REDIRECT [[User:SebastienVC]]

User:SebastienVC

2009-12-01T15:34:54Z

SebastienVC: Undo revision 7705 by SebastienVC (Talk)

User:SebastienVC

2009-12-01T15:33:24Z

SebastienVC: Removing all content from page

User:SebastienVC

2009-12-01T15:29:22Z

SebastienVC: New page: << liste des membres = Présentation = Sébastien Van Cauwenberghe, Ingénieur Industriel en Electronique. J'ai toujours été passionné par l'informatique et l'élect...

FPGA registers access from Linux userspace

2008-11-22T20:11:49Z

SebastienVC: /* the mmap problem */

[[Category:FPGA]]

= fpgaregs =

== compile ==
To access FPGA registers a tool named ''fpgaregs'' is available under ''target/linux/module/fpga/dev_tools/'' directory. To compile it for apf9328, use the command above :

<source lang="bash">
arm-linux-gcc -mcpu=arm920t fpgaregs.c -o fpgaregs
</source>

== use ==

fpgaregs can be used to read and write 16 or 32 bits registers.

'''read 16 bits'''
<source lang="bash">
fpgaregs w <address>
</source>

Where <address> is an address relative to fpga mapping in hexadecimal value.

'''write 16 bits'''
<source lang="bash">
fpgaregs w <address> <value>
</source>

Where <value> is hexadecimal value to write.

'''read 32 bits'''
<source lang="bash">
fpgaregs l <address>
</source>

'''write 32 bits'''
<source lang="bash">
fpgaregs l <address> <value>
</source>

= the mmap problem =

First of all, you need to get a file descriptor for ''/dev/mem'' using the ''open()'' function
<source lang="c">
ffpga=open("/dev/mem",O_RDWR|O_SYNC);
</source>
Now you have a valid file descriptor to access your FPGA.

The O_SYNC option is recommanded to avoid Linux to cache the content of /dev/mem and delay any modification done in this file.

To access fpga register, fpgaregs use the ''mmap()'' system call :

<source lang="c">
ptr_fpga = mmap (0, 8192, PROT_READ|PROT_WRITE, MAP_SHARED, ffpga, FPGA_ADDRESS);
</source>

Thanks to this function, fpga registers are accessible directly on memory with pointer ptr_fpga. To read and write in 16bits or in 32 bits we will cast the pointer value in ''unsigned short'' or ''unsigned int'' :

'''16bits'''
''write''
<source lang="c">
*(unsigned short*)(ptr_fpga+(address)) = (unsigned short)value;
</source>
''read''
<source lang="c">
value = *(unsigned short*)(ptr_fpga+(address));
</source>

'''32 bits'''
''write''
<source lang="c">
*(unsigned int*)(ptr_fpga+(address)) = (unsigned short)value;
</source>

''read''
<source lang="c">
value = *(unsigned int*)(ptr_fpga+(address));
</source>

== The problem ==

By default, if the specific ''arm920t'' target is not specified, ''arm-linux-gcc'' will try to generate compatible read/write for all ARM9 model when it access register in 16bits. Indeed it seems that not all ARM9 have 16bits read/write capabilities (''ldrh'' asm instruction).

As the interface between i.MXL and FPGA on APF9328 has no 8bits read/write capabilities, each 8 bits access is recognized by the FPGA as a 16bits access. So on each 16bits access of the i.MXL, FPGA will process two 16bits access instead of 1. That is a problem when accessing a FIFO for example.

To avoid this painful problem don't forget the ''-mcpu=arm920t'' option when compiling ''fpgaregs'' for APF9328.

==Links==
* http://sources.redhat.com/ml/crossgcc/2005-08/msg00120.html : Explanation of the problem.

FPGA registers access from Linux userspace

2008-11-19T10:42:59Z

SebastienVC: /* the mmap problem */

[[Category:FPGA]]

= fpgaregs =

== compile ==
To access FPGA registers a tool named ''fpgaregs'' is available under ''target/linux/module/fpga/dev_tools/'' directory. To compile it for apf9328, use the command above :

<source lang="bash">
arm-linux-gcc -mcpu=arm920t fpgaregs.c -o fpgaregs
</source>

== use ==

fpgaregs can be used to read and write 16 or 32 bits registers.

'''read 16 bits'''
<source lang="bash">
fpgaregs w <address>
</source>

Where <address> is an address relative to fpga mapping in hexadecimal value.

'''write 16 bits'''
<source lang="bash">
fpgaregs w <address> <value>
</source>

Where <value> is hexadecimal value to write.

'''read 32 bits'''
<source lang="bash">
fpgaregs l <address>
</source>

'''write 32 bits'''
<source lang="bash">
fpgaregs l <address> <value>
</source>

= the mmap problem =

To access fpga register, fpgaregs use the ''mmap()'' system call :

<source lang="c">
ptr_fpga = mmap (0, 8192, PROT_READ|PROT_WRITE, MAP_SHARED, ffpga, FPGA_ADDRESS);
</source>

Thanks to this function, fpga registers are accessible directly on memory with pointer ptr_fpga. To read and write in 16bits or in 32 bits we will cast the pointer value in ''unsigned short'' or ''unsigned int'' :

'''16bits'''
''write''
<source lang="c">
*(unsigned short*)(ptr_fpga+(address)) = (unsigned short)value;
</source>
''read''
<source lang="c">
value = *(unsigned short*)(ptr_fpga+(address));
</source>

'''32 bits'''
''write''
<source lang="c">
*(unsigned int*)(ptr_fpga+(address)) = (unsigned short)value;
</source>

''read''
<source lang="c">
value = *(unsigned int*)(ptr_fpga+(address));
</source>

== The problem ==

By default, if the specific ''arm920t'' target is not specified, ''arm-linux-gcc'' will try to generate compatible read/write for all ARM9 model when it access register in 16bits. Indeed it seems that not all ARM9 have 16bits read/write capabilities (''ldrh'' asm instruction).

As the interface between i.MXL and FPGA on APF9328 has no 8bits read/write capabilities, each 8 bits access is recognized by the FPGA as a 16bits access. So on each 16bits access of the i.MXL, FPGA will process two 16bits access instead of 1. That is a problem when accessing a FIFO for example.

To avoid this painful problem don't forget the ''-mcpu=arm920t'' option when compiling ''fpgaregs'' for APF9328.

==Links==
* http://sources.redhat.com/ml/crossgcc/2005-08/msg00120.html : Explanation of the problem.

A simple design with Wishbone bus

2008-09-26T20:05:40Z

SebastienVC: /* Wb_led */

[[Category: FPGA]]
This article intended to explain how to design Wishbone compatible
components with simple example.
The VHDL design can be found in sourceforge
[http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/firmware/Wisbone_example/ tree].

Description of wishbone structure for armadeus can be found [[FpgaArchitecture#Le_bus_Wishbone | here]] in french.

== General structure ==

The main functionality of this component is to do the same things
that [[FPGA_and_led | benoît]] project : switch on a led when a button is
pressed.

But to learn about designing Wishbone component and linux driver, the design
is little bit more complicated (!).

When button is pressed, the component ''Wb_button'' send interrupt signal to ''irq_mngr''. ''irq_mngr'' will toggle a flag and send interruption to
'''i.mx''' processor. A Linux driver on '''i.mx''' will read ''irq_mngr'' and
acknowledge irq by writing '1' on a register. And finally, Linux driver will
toggle led value by writing on led register.

[[Image:Wb_buttonled_top.png|center|800px]]

''imx_wrapper'', ''syscon'' and ''irq_mngr'' are standards
ARMadeus-Wishbone IPs that just been instantiated in our design.

''Wb_button'' and ''Wb_led'' are simple slave component we want to
integrate in the FPGA.

All these components are connected together with the 'glue logic' component ''intercon''.

== Wishbone slave application components ==

=== Wb_led ===

This component is a simple 16-bit Wishbone slave output port, from [http://www.opencores.org/projects.cgi/web/wishbone/wbspec_b3.pdf wishbone specification example] (p110).

[[Image:wbs_led.png|center|600px]]

It is a simple register, that can be read and write. The led is controled with register pin 0.

[[Wb_led.vhd | The VHDL source code]]

=== Wb_button ===

Wb_button component, is like Wb_led but in read only and with an edge detector to rise irq.

[[Image:wbs_button.png|center|500px]]

[[Wb_button.vhd | The VHDL source c]]ode

== Drivers ==

=== Wb_led ===
The Wb_led driver implements a character device with read(), write() system calls. It implements sys/led/status entry. Driver sources can be found in [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/target/linux/modules/fpga/others/Wb_led/ sourceforge].

=== Wb_button ===
The Wb_button driver implements a character device with only read() system calls. If used as blocking read, it will return value only when button is push/release. Drivers sources are on [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/target/linux/modules/fpga/others/Wb_button/ sourceforge].

== XML ==

A simple design with Wishbone bus

2008-09-26T20:03:55Z

SebastienVC:

[[Category: FPGA]]
This article intended to explain how to design Wishbone compatible
components with simple example.
The VHDL design can be found in sourceforge
[http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/firmware/Wisbone_example/ tree].

Description of wishbone structure for armadeus can be found [[FpgaArchitecture#Le_bus_Wishbone | here]] in french.

== General structure ==

The main functionality of this component is to do the same things
that [[FPGA_and_led | benoît]] project : switch on a led when a button is
pressed.

But to learn about designing Wishbone component and linux driver, the design
is little bit more complicated (!).

When button is pressed, the component ''Wb_button'' send interrupt signal to ''irq_mngr''. ''irq_mngr'' will toggle a flag and send interruption to
'''i.mx''' processor. A Linux driver on '''i.mx''' will read ''irq_mngr'' and
acknowledge irq by writing '1' on a register. And finally, Linux driver will
toggle led value by writing on led register.

[[Image:Wb_buttonled_top.png|center|800px]]

''imx_wrapper'', ''syscon'' and ''irq_mngr'' are standards
ARMadeus-Wishbone IPs that just been instantiated in our design.

''Wb_button'' and ''Wb_led'' are simple slave component we want to
integrate in the FPGA.

All these components are connected together with the 'glue logic' component ''intercon''.

== Wishbone slave application components ==

=== Wb_led ===

This component is a simple 16-bit Wishbone slave output port, from [http://www.opencores.org/projects.cgi/web/wishbone/wbspec_b3.pdf wishbone specification example] (p110).

[[Image:wbs_led.png|center|600px]]

It is a simple register, that can be read and write. The led is controled with register pin 0.

[[Wb_led.vhd | The VHDL source code]]

=== Wb_button ===

Wb_button component, is like Wb_led but in read only and with an edge detector to rise irq.

[[Image:wbs_button.png|center|500px]]

[[Wb_button.vhd | The VHDL source c]]ode

== Drivers ==

=== Wb_led ===
The Wb_led driver implements a character device with read(), write() system calls. It implements sys/led/status entry. Driver sources can be found in [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/target/linux/modules/fpga/Wb_led/ sourceforge].

=== Wb_button ===
The Wb_button driver implements a character device with only read() system calls. If used as blocking read, it will return value only when button is push/release. Drivers sources are on [http://armadeus.svn.sourceforge.net/viewvc/armadeus/trunk/target/linux/modules/fpga/others/Wb_button/ sourceforge].

== XML ==