ArmadeusWiki - User contributions [en]

User:JulienPeeters

2010-09-15T10:56:49Z

JulienPeeters: /* Compétences & travaux de recherche (personnels) */

== Qui suis-je ? ==
[[Image:Tete_julien_bg.jpg]]
* Nom, Prénom: Peeters Julien
* Age: 23 ans
* Profession: Etudiant en dernière année d'école d'ingénieur, spécialité systèmes embarqués (+M2R architectures embarquées)

== Qu'est-ce qui m'intéresse ? ==
* '''L'électronique''' m'intéresse depuis pas mal d'années. Plus particulièrement les systèmes embarqués et les systèmes de contrôle-commande. Si on peut rajouter des contraintes, type temps réel ou autre, j'en suis d'autant plus ravi! Bien que je vienne au départ du monde de l'informatique théorique, j'espère pouvoir augmenter mes compétences en électronique pour pouvoir allier les deux. J'ai aussi un petit faible pour la domotique.

* '''L'informatique'''. Que dire, je suis tombé dedans tout petit comme pas mal de gens de ma génération. Ca a commencé comme une histoire de famille, c'est devenu ensuite une passion à plein temps. Je m'intéresse à la vérification de code, à la preuve des systèmes. Plutôt le côté formel donc.

* '''Les logiciels libres''' ne sont pas seulement pour moi une part de l'informatique mais une véritable vision de la conception et de la réalisation des systèmes. C'est pour moi une véritable façon d'intégrer l'humain dans les productions industrielles (pour le moment majoritairement informatique, bien qu'on voit arriver des productions électroniques libres).

* '''Nouvelles technologies'''. J'essaye autant que se peut, d'être au coeur de la veille technologique. Mais c'est pas forcément simple de part la nature même des informations recherchées.

== Compétences & travaux de recherche (personnels) ==

Je sais pas trop quoi mettre, je mets donc une copie (un peu baclée...) de mon CV et de ce sur quoi je me documente en ce moment. J'espère que ce sera pas trop pompeux...

* '''Programmation''' (tous niveaux confondus): ASM (8086, PIC), C/C++, OCaml, JoCaml, Python, Erlang.
* '''Electronique''': ABEL, VHDL, SystemC, architectures multiprocesseurs.
* '''OS''': Linux(Debian, Ubuntu), Windows, MacOS X
* '''Technologie/Sciences''': compléxité, langages fonctionnels et impératif, noyau Linux, programmation concurrente et distribuée, design pattern, tolérances aux pannes, reseaux, détection de mouvements, implantation d'architectures, communication sur bus avec contraintes, ...

== My board ==

[[Image:little-board-jp.jpg|center|frame|APF9328 + DevLight v2 + custom casing]]

User:JulienPeeters

2010-09-15T10:55:19Z

JulienPeeters: /* Qui suis-je ? */

== Qui suis-je ? ==
[[Image:Tete_julien_bg.jpg]]
* Nom, Prénom: Peeters Julien
* Age: 23 ans
* Profession: Etudiant en dernière année d'école d'ingénieur, spécialité systèmes embarqués (+M2R architectures embarquées)

== Qu'est-ce qui m'intéresse ? ==
* '''L'électronique''' m'intéresse depuis pas mal d'années. Plus particulièrement les systèmes embarqués et les systèmes de contrôle-commande. Si on peut rajouter des contraintes, type temps réel ou autre, j'en suis d'autant plus ravi! Bien que je vienne au départ du monde de l'informatique théorique, j'espère pouvoir augmenter mes compétences en électronique pour pouvoir allier les deux. J'ai aussi un petit faible pour la domotique.

* '''L'informatique'''. Que dire, je suis tombé dedans tout petit comme pas mal de gens de ma génération. Ca a commencé comme une histoire de famille, c'est devenu ensuite une passion à plein temps. Je m'intéresse à la vérification de code, à la preuve des systèmes. Plutôt le côté formel donc.

* '''Les logiciels libres''' ne sont pas seulement pour moi une part de l'informatique mais une véritable vision de la conception et de la réalisation des systèmes. C'est pour moi une véritable façon d'intégrer l'humain dans les productions industrielles (pour le moment majoritairement informatique, bien qu'on voit arriver des productions électroniques libres).

* '''Nouvelles technologies'''. J'essaye autant que se peut, d'être au coeur de la veille technologique. Mais c'est pas forcément simple de part la nature même des informations recherchées.

== Compétences & travaux de recherche (personnels) ==

Je sais pas trop quoi mettre, je mets donc une copie (un peu baclée...) de mon CV et de ce sur quoi je me documente en ce moment. J'espère que ce sera pas trop pompeux...

* '''Programmation''' (tous niveaux confondus): ASM (8086, PIC), C/C++, Java, OCaml, JoCaml (OCaml concurrent et distribué basé sur le Join-Calculus), Python, PHP, Erlang.
* '''Electronique''': ABEL, VHDL (je débute), Architecture des processeurs (pipeline, ...), bus (I2C, CAN et MODBUS peut-être bientôt).
* '''OS''': Linux(Debian, Ubuntu), Windows, MacOS X
* '''Technologie/Sciences''': compléxité, langages fonctionnels et impératif, noyau Linux, programmation concurrente et distribuée, design pattern, tolérances aux pannes, reseaux, détection de mouvements, implantation d'architectures, communication sur bus avec contraintes, ...

== My board ==

[[Image:little-board-jp.jpg|center|frame|APF9328 + DevLight v2 + custom casing]]

NEON HelloWorld

2009-11-02T12:49:50Z

JulienPeeters: /* And in the add3 function ? */

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

=== Source code ===

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };

/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

=== What is done ? ===
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

=== And in the '''add3''' function ? ===
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== Result ===

<pre class="host">
$ ./a.out
data = 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
data (new) = 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19
</pre>

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

[[Category:Software]]
[[Category:Architecture dependent]]

NEON HelloWorld

2009-11-02T12:49:22Z

JulienPeeters: Add the pretty print result

NEON HelloWorld

2009-11-02T12:31:20Z

JulienPeeters: /* Links */

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

=== Source code ===

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };

/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

=== What is done ? ===
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

=== And in the '''add3''' function ? ===
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

[[Category:Software]]
[[Category:Architecture dependent]]

Category:Architecture dependent

2009-11-02T12:30:45Z

JulienPeeters: New page: Architecture dependent software articles ...

Architecture dependent software articles ...

NEON HelloWorld

2009-11-02T12:29:03Z

JulienPeeters: Add categories

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

=== Source code ===

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };

/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

=== What is done ? ===
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

=== And in the '''add3''' function ? ===
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

[[Category:Software]]
[[Category:Architecture dependent]]
[[Category:SIMD]]

NEON HelloWorld

2009-11-02T12:23:39Z

JulienPeeters: /* Let's go programming */

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

=== Source code ===

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };

/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

=== What is done ? ===
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

=== And in the '''add3''' function ? ===
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

NEON HelloWorld

2009-11-02T12:21:40Z

JulienPeeters: /* Let's go programming */

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };

/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

What is done ?
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

And in the '''add3''' function ?
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

NEON HelloWorld

2009-11-02T12:20:54Z

JulienPeeters: /* Links */

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
int i;

/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };
/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

What is done ?
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

And in the '''add3''' function ?
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

== Links ==

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

NEON HelloWorld

2009-11-02T12:20:33Z

JulienPeeters: Add links

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
int i;

/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };
/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

What is done ?
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

And in the '''add3''' function ?
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

=== Links ===

* [http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html GCC NEON intrinsics]
* [http://code.google.com/p/math-neon/source/browse/#svn/trunk Example of a mathematic library using NEON]

NEON HelloWorld

2009-11-02T12:18:15Z

JulienPeeters: Add a "Hello World" example with SIMD intrinsics

Developing with SIMD instructions or intrinsics need a bit of experience. That is a complete different way of thinking and programming.

== Prerequisites ==

* Install a emulation environment
* Build a GCC toolchain which support NEON intrinsics

== Let's go programming ==

Here is a brief example of what is possible with SIMD programming. This piece of code only add the value "3" to each value of the SIMD vector.

On the Cortex-A platform there is both 64 bits and 128 bits vector registers. Here we use 128 bits ones then we can code sixteen 8 bits values (unsigned integers).

{{Warning | Not all ARM Cortex processors have a NEON unit and old ARM processors may have a SIMD unit not compliant with NEON (cf. ARM reference manuals).}}

<source lang="c">
#include <stdio.h>

#include "arm_neon.h"

void add3 (uint8x16_t *data) {
/* Set each sixteen values of the vector to 3.
*
* Remark: a 'q' suffix to intrinsics indicates
* the instruction run for 128 bits registers.
*/
uint8x16_t three = vmovq_n_u8 (3);

/* Add 3 to the value given in argument. */
*data = vaddq_u8 (*data, three);
}

void print_uint8 (uint8x16_t data, char* name) {
int i;
static uint8_t p[16];

vst1q_u8 (p, data);

printf ("%s = ", name);
for (i = 0; i < 16; i++) {
printf ("%02d ", p[i]);
}
printf ("\n");
}

int main () {
int i;

/* Create custom arbitrary data. */
const uint8_t uint8_data[] = { 1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14, 15, 16 };
/* Create the vector with our data. */
uint8x16_t data;

/* Load our custom data into the vector register. */
data = vld1q_u8 (uint8_data);

print_uint8 (data, "data");

/* Call of the add3 function. */
add3(&data);

print_uint8 (data, "data (new)");

return 0;
}
</source>

What is done ?
* We first create custom data: an array of 16 uint8_t values.
* We load the custom values in a vector register through the '''vld1q_u8''' intrinsic (note the 'q' suffix which means we use 128 registers)
* We call our '''add3''' function

And in the '''add3''' function ?
* Because we use SIMD vectors and want to add 3 to each value we need to set the same value (3) with the '''vmovq_n_u8''' intrinsic
* We call the '''vaddq_u8''' intrinsic to do the addition

{{Note | all sixteen values of each vector are compute in real parallelism}}

=== How to compile ? ===

The gcc options to give in order to compile NEON intrinsics in case of an ARM Cortex-A8 is :
<pre class="host">
$ gcc -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon <sources>
</pre>

{{Note | Do not forget to include the "arm_neon.h" header file.}}

Development

2009-11-02T11:52:23Z

JulienPeeters: Add a SIMD section

On this page you will find useful information to develop software for your Armadeus board
<br>
==Project==
* [[Sources organisation | Armadeus project sources organisation]]
* [[SVN#Providing_modifications | How to submit patches with your modifications]]

==Tools==
* [[Toolchain|C/C++ Cross Compiler (Toolchain) installation]]
* [[SVN|SVN usage on Armadeus]] and the way to inform us about your changes
* [[GDB|Debugging with GDB and GDBserver]]
* [[QEMU | Simulate an Armadeus system under QEMU]]
* [[Eclipse| Eclipse IDE with GDB debugger]]
* [[ JTAG | Support JTAGKey and BDI2000 JTAG probes]]

==Linux==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|
===Userland applications===
* [[HelloWorld | How to create your first Linux C application for your board]]
* [[HelloWorldCpp |How to create your first Linux C++ application for your board]]
* [[Automatically launch your application]]
* [[AsDevices | ARMadeus specific library]]
||
===Linux kernel development===
* [[kernel drivers status list|Kernel driver status list for the APF boards]]
* [[Linux Debug |Tips to debug under Linux]]
* [[Linux drivers development|Instructions to develop Linux drivers for Armadeus]]
* [[Linux on i.MXL|Resources available on i.MXL Linux kernel development]]
* [[Oops, Linux crashes | Interpreting Linux kernel Oops (crashes)]]
|----------------
|

===Graphical User Interface / Games===
* [[Qt/Embedded]] (Qtopia core 4.2)
* [[EFL|Enlightenment Foundation Libraries]]
* [[SDL Development|SDL]]
* [[Allegro|Allegro]]
* [[Mesa| Mesa 3D graphics library (OpenGL compatible)]]
* [[pygame]]
||

===Scripts===
* [[Perl development | Perl]]
* [[Python development | Python]]
* [[Lua development | Lua]]
|----------------
|
===Realtime applications===
* [[Xenomai]]

|----------------
|}

== Architecture dependent ==
{| border="0" cellpadding="5" cellspacing="5" summary="Hardware Add-Ons by functionnalities"
|----------------
|
=== SIMD ===
* [[SIMD | What is SIMD?]]
* [[NEON HelloWorld | Hello World example in NEON]]
||
|}

==Miscellaneous software packages==
* [[Buildroot Packages | Adding packages to Buildroot]]
* [[Samba]]

==Links==
* Things to know when porting x86 software to ARM: http://www.handhelds.org/minihowto/porting-software.html

File:Little-board-jp.jpg

2009-08-23T09:07:54Z

JulienPeeters:

User:JulienPeeters

2009-08-23T09:02:33Z

JulienPeeters: /* Compétences & travaux de recherche (personnels) */

== Qui suis-je ? ==
[[Image:Tete_julien_bg.jpg]]
* Nom, Prénom: Peeters Julien
* Age: 22 ans
* Profession: Etudiant en 2e année d'école d'ingénieur, spécialité systèmes embarqués

== Qu'est-ce qui m'intéresse ? ==
* '''L'électronique''' m'intéresse depuis pas mal d'années. Plus particulièrement les systèmes embarqués et les systèmes de contrôle-commande. Si on peut rajouter des contraintes, type temps réel ou autre, j'en suis d'autant plus ravi! Bien que je vienne au départ du monde de l'informatique théorique, j'espère pouvoir augmenter mes compétences en électronique pour pouvoir allier les deux. J'ai aussi un petit faible pour la domotique.

* '''L'informatique'''. Que dire, je suis tombé dedans tout petit comme pas mal de gens de ma génération. Ca a commencé comme une histoire de famille, c'est devenu ensuite une passion à plein temps. Je m'intéresse à la vérification de code, à la preuve des systèmes. Plutôt le côté formel donc.

* '''Les logiciels libres''' ne sont pas seulement pour moi une part de l'informatique mais une véritable vision de la conception et de la réalisation des systèmes. C'est pour moi une véritable façon d'intégrer l'humain dans les productions industrielles (pour le moment majoritairement informatique, bien qu'on voit arriver des productions électroniques libres).

* '''Nouvelles technologies'''. J'essaye autant que se peut, d'être au coeur de la veille technologique. Mais c'est pas forcément simple de part la nature même des informations recherchées.

== Compétences & travaux de recherche (personnels) ==

Je sais pas trop quoi mettre, je mets donc une copie (un peu baclée...) de mon CV et de ce sur quoi je me documente en ce moment. J'espère que ce sera pas trop pompeux...

* '''Programmation''' (tous niveaux confondus): ASM (8086, PIC), C/C++, Java, OCaml, JoCaml (OCaml concurrent et distribué basé sur le Join-Calculus), Python, PHP, Erlang.
* '''Electronique''': ABEL, VHDL (je débute), Architecture des processeurs (pipeline, ...), bus (I2C, CAN et MODBUS peut-être bientôt).
* '''OS''': Linux(Debian, Ubuntu), Windows, MacOS X
* '''Technologie/Sciences''': compléxité, langages fonctionnels et impératif, noyau Linux, programmation concurrente et distribuée, design pattern, tolérances aux pannes, reseaux, détection de mouvements, implantation d'architectures, communication sur bus avec contraintes, ...

== My board ==

[[Image:little-board-jp.jpg|center|frame|APF9328 + DevLight v2 + custom casing]]

GIT

2009-08-12T13:47:03Z

JulienPeeters: /* How to use GIT (Armadeus integrators) */

We have migrated our Source Code Management tool to GIT scm.
Therefore the Armadeus software release 3.1 is the last one available under SVN management tool.
This page aims to help you to use our new GIT tool.

==Install GIT==

Install the following packages:
git-core gitk git-gui

==How to use GIT (for everyone)==

# [http://git-scm.com/course/svn.html GIT-SVN Crash course ]
# [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
# [http://git-scm.com GIT website]

*Get the Armadeus GIT/SF repository:
{{Note| This is Read Only method
<pre class="host">
$ git clone git://armadeus.git.sourceforge.net/gitroot/armadeus armadeus
</pre>
}}

*Get the GIT/SF repository in Read/Write mode (for integrators only):
<pre class="host">
$ git clone ssh://USER@armadeus.git.sourceforge.net/gitroot/armadeus armadeus
</pre>

==How to use GIT (Armadeus integrators)==
* Before first commit define your global personnal data:
<pre class="host>
$ git config --global user.name "James Bond"
$ git config --global user.email "james.bond@007.com"
</pre>

*Do your changes and commit to your '''local''' repository (here add ''fileorpath''):
<pre class="host>
$ git add fileorpath
$ git commit -m 'Explain what I changed'
or
$ git commit -a -m 'Explain what I changed' (if you have local modifications (=not versioned files) and wants GIT to ignore them)
</pre>

*Update your repository to the latest version on SF:
<pre class="host>
$ git pull
</pre>

*If git pull fails with an error: "Untracked working tree file '{SOMEFILE}'"
<pre class="host">
$ rm -rf {SOMEFILE}
$ git pull
</pre>

*If you have modified some armadeus files and want to revert your changes"
<pre class="host">
$ rm -rf buildroot/package
$ rm -rf buildroot/target
$ rm -rf buildroot/toolchain
$ git checkout -f
$ make apf9328_defconfig or make apf27_defconfig
</pre>

{{Note | The command
<pre>
git clean -dfx
</pre>
cleans the working repository as like it was after the clone or the last rebase.}}

*Push your changes to SF:
<pre class="host>
$ git push
</pre>

*Tag a revision:
<pre class="host>
$ git tag -m "Creates TAG for Armadeus 3.1 release" release-3.1
$ git push --tags origin master
</pre>

==GIT to do list==
*To update to support git:
# release/change.sh
# buildroot/target/device/armadeus/linux/kernel-patches/move-patches.sh

GIT

2009-08-12T13:45:49Z

JulienPeeters: /* How to use GIT (Armadeus integrators) - How to clean a GIT repository */

We have migrated our Source Code Management tool to GIT scm.
Therefore the Armadeus software release 3.1 is the last one available under SVN management tool.
This page aims to help you to use our new GIT tool.

==Install GIT==

Install the following packages:
git-core gitk git-gui

==How to use GIT (for everyone)==

# [http://git-scm.com/course/svn.html GIT-SVN Crash course ]
# [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
# [http://git-scm.com GIT website]

*Get the Armadeus GIT/SF repository:
{{Note| This is Read Only method
<pre class="host">
$ git clone git://armadeus.git.sourceforge.net/gitroot/armadeus armadeus
</pre>
}}

*Get the GIT/SF repository in Read/Write mode (for integrators only):
<pre class="host">
$ git clone ssh://USER@armadeus.git.sourceforge.net/gitroot/armadeus armadeus
</pre>

==How to use GIT (Armadeus integrators)==
* Before first commit define your global personnal data:
<pre class="host>
$ git config --global user.name "James Bond"
$ git config --global user.email "james.bond@007.com"
</pre>

*Do your changes and commit to your '''local''' repository (here add ''fileorpath''):
<pre class="host>
$ git add fileorpath
$ git commit -m 'Explain what I changed'
or
$ git commit -a -m 'Explain what I changed' (if you have local modifications (=not versioned files) and wants GIT to ignore them)
</pre>

*Update your repository to the latest version on SF:
<pre class="host>
$ git pull
</pre>

*If git pull fails with an error: "Untracked working tree file '{SOMEFILE}'"
<pre class="host">
$ rm -rf {SOMEFILE}
$ git pull
</pre>

*If you have modified some armadeus files and want to revert your changes"
<pre class="host">
$ rm -rf buildroot/package
$ rm -rf buildroot/target
$ rm -rf buildroot/toolchain
$ git checkout -f
$ make apf9328_defconfig or make apf27_defconfig
</pre>

{{Note | The command "git clean -dfx" cleans the working repository as like it was after the clone or the last rebase.}}

*Push your changes to SF:
<pre class="host>
$ git push
</pre>

*Tag a revision:
<pre class="host>
$ git tag -m "Creates TAG for Armadeus 3.1 release" release-3.1
$ git push --tags origin master
</pre>

==GIT to do list==
*To update to support git:
# release/change.sh
# buildroot/target/device/armadeus/linux/kernel-patches/move-patches.sh

ArmadeusWiki:Current events

2009-07-11T21:43:03Z

JulienPeeters: /* Assembly General / LSN 2009 */

==Assembly General / LSN 2009==
* On Wednesday July 8 2009 occurred the General Assembly in Nantes (France)
{|border=0 summary="Photos"
|----------------
|[[Image:GA2009-01.jpg|thumb|center|JulienB ]] || [[Image:GA2009-02.jpg|thumb|center| ]] || [[Image:GA2009-03.jpg|thumb|center| ]] || [[Image:GA2009-04.jpg|thumb|center|JulienP (very serious)]] || [[Image:GA2009-05.jpg|thumb|center| ]]
|----------------
| [[Image:GA2009-07.jpg|thumb|center| ]] || [[Image:GA2009-08.jpg|thumb|center|L2R: GillesD, JeanFrancoisR ]] || [[Image:GA2009-09.jpg|thumb|center| ]] || [[Image:GA2009-10.jpg|thumb|center| ]] || [[Image:GA2009-11.jpg|thumb|center|L2R: ]]
|----------------
| [[Image:GA2009-12.jpg|thumb|center|L2R:YoannC, GillesD, JeanFrancoisR ]] || [[Image:GA2009-15.jpg|thumb|center| L2R:JulienB, YvanR (explaining its project)]] || [[Image:GA2009-17.jpg|thumb|center|L2R:JulienB, YvanR (explaining its project) ]] || [[Image:GA2009-21.jpg|thumb|center|L2R:JulienB, YvanR: 2008 contest price award ]] || [[Image:GA2009-22.jpg|thumb|center|L2R:JulienB, YvanR: 2008 contest price award ]]
|----------------
| [[Image:GA2009-23.jpg|thumb|center|L2R:JulienB, FabienM, NicolasC: at the hotel ]]
|----------------
|}

==LSN 2008==
* On 1st to 3rd July 2008 we attended the [http://2008.rmll.info/ RMLL at Mont de Marsan]:
** [http://free-electrons.com/pub/video/2008/rmll/rmll2008-julien-boibessot-nicolas-colombain-fabien-marteau-armadeus.ogg Video of Embedded systems conference]
** [http://2008.rmll.info/IMG/pdf/armadeus.pdf sides of the conference is available here]

==General Assembly 2008==
* On Saturday Mar. 9th 2008 occurred the General Assembly in Mulhouse (France).

{|border=0 summary="Photos"
|----------------
|[[Image:AG2008_01.jpg|thumb|center|L2R: Nicolas, Frédéric and Fabien]] || [[Image:AG2008_02.jpg|thumb|center|Nicolas and Frédéric]] || [[Image:AG2008_03.jpg|thumb|center|Julien, Michael and Fabrice]]
|----------------
|[[Image:AG2008_04.jpg|thumb|center|L2R: Nicolas and Frédéric ]] || [[Image:AG2008_05.jpg|thumb|center| L2R: Fabrice and Eric]] || [[Image:AG2008_06.jpg|thumb|center| everyone ;-)]] ||
|----------------
|}

==General Assembly 2007==
* On Saturday Feb. 17th 2007 occured the annual meeting in Mulhouse (France).

{|border=0 summary="Photos"
|----------------
|[[Image:ArmadeusAM07-1.JPG|thumb|center| L2R: Paola, Nicolas, Julien, Sébastien, Michael]] || [[Image:ArmadeusAM07-2.JPG|thumb|center|Paola, Michael]] || [[Image:ArmadeusAM07-3.JPG|thumb|center|Michael, Eric, Fabrice, Frédéric, Julien]]
|----------------
|[[Image:ArmadeusAM07-4.JPG|thumb|center|L2R: Eric, Fabrice, Frédéric,Nicolas, Julien, Michael]] || [[Image:ArmadeusAM07-5.JPG|thumb|center|again ;-)]] ||
|----------------
|}

Communicate

2009-06-13T18:11:44Z

JulienPeeters: /* Server configuration: errata on tftp configuration with xinetd */

<noinclude>
How-To connect your Armadeus board to your development Host.

==Forewords==
The default connection uses a simple RS232 Null-Modem cable (with or without USB<->serial adapter). <br>
As you will have to transfer some mega bytes of data, the Ethernet link is mandatory.<br>
In order to use these two media with the APF target a terminal emulator (for RS232 link) and a TFTP server (for Ethernet link) have to be configured.
</noinclude>
At this stage, you should have something looking like that (IP addresses may change):<br><br>
[[Image:BoardConnection.png]]

{{:RS232 Terminal configuration}}

==TFTP server==
In order to send your image files (U-Boot, Linux, rootfs or FPGA's firmware) at higher speed (than serial port) to your Armadeus board, you can use the Ethernet link and [http://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol a TFTP server].
Once the server configured, the files located in the server shared directory (''/tftpboot'' by default) will be accessible from the U-Boot/Linux TFTP clients.

===TFTP server installation===
* On *Ubuntu / Debian:
<pre class="host">
[ ] $ sudo apt-get install tftpd xinetd
</pre>
or use your preferred graphical package manager
* On Fedora:
<pre class="host">
[ ] $ rpm -q tftpd xinetd
</pre>

* Then create the directory (''/tftpboot/'') that will contain all the files that the server will export:
<pre class="host">
[ ] $ sudo mkdir /tftpboot
[ ] $ sudo chmod 777 /tftpboot
</pre>

===Server configuration===
* Edit (as root user) or create the configuration file ''/etc/xinetd.d/tftp'' and modify/add it the following lines:
# default: off
# description: The tftp server serves files using the trivial file transfer
# protocol. The tftp protocol is often used to boot diskless
# workstations, download configuration files to network-aware printers,
# and to start the installation process for some operating systems.
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot
# disable = yes
}

* Restart xinetd service:
<pre class="host">
[ ] $ sudo killall -HUP xinetd
</pre>
<noinclude>
For more information regarding how-to setup a tftp server please check one of many web how-to:
* [http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch16_:_Telnet,_TFTP,_and_xinetd#TFTP TFTP server quick how-to]
* [https://linuxlink.timesys.com/docs/linux_tftp Another how-to configure a TFTP Server for Linux]
* [http://www.webune.com/forums/how-to-install-tftp-server-in-linux.html till another how-to...]
* [http://doc.ubuntu-fr.org/tftpd ubuntu TFTP server documentation in French]

==== Errata ====

It looks like xinetd configuration is not sufficient in new versions. IPv6 is enabled by default and seems to be not compatible with the TFTP protocol. A simple inetd configuration should work for people who have this problem (''connection refused'' in logs with addresses like ::ffff:192.168.0.100).

* Edit (as root user) - if necessary - the ''/etc/inetd.conf'' file and add this line:
<pre>
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd -s /tftpboot
</pre>

* Install inetd tools

On Ubuntu/Debian
<pre>
armadeus# sudo apt-get install inetutils-tools
</pre>

* Setup the hosts rules: edit (ass root user) ''/etc/hosts.allow'' and add the following lines:
<pre>
in.tftpd: ALL
tftpd: ALL
</pre>

* Restart inetd
<pre>
armadeus# sudo /etc/init.d/openbsd-inet restart
</pre>

It's done... and should work for most people.

==Links==
* [http://www.columbia.edu/kermit/ Kermit Homepage]
* [http://www.jls-info.com/julien/linux/ GTKTerm Homepage]
* [http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch16_:_Telnet,_TFTP,_and_xinetd#TFTP TFTP server quick how-to]
* [https://linuxlink.timesys.com/docs/linux_tftp Another how-to configure a TFTP Server for Linux]
* [http://www.webune.com/forums/how-to-install-tftp-server-in-linux.html till another how-to...]
* [http://doc.ubuntu-fr.org/tftpd ubuntu TFTP server documentation in French]
* [[Windows uBoot Connection | configuring RS-232 and TFTP on Windows to communicate with your board]]
</noinclude>

User:JulienPeeters

2009-03-23T20:25:39Z

JulienPeeters: /* Compétences & travaux de recherche (personnels) */

User:JulienPeeters

2009-03-23T20:23:03Z

JulienPeeters: /* Qu'est-ce qui m'intéresse ? */

== Qui suis-je ? ==
[[Image:Tete_julien_bg.jpg]]
* Nom, Prénom: Peeters Julien
* Age: 22 ans
* Profession: Etudiant en 2e année d'école d'ingénieur, spécialité systèmes embarqués

== Qu'est-ce qui m'intéresse ? ==
* '''L'électronique''' m'intéresse depuis pas mal d'années. Plus particulièrement les systèmes embarqués et les systèmes de contrôle-commande. Si on peut rajouter des contraintes, type temps réel ou autre, j'en suis d'autant plus ravi! Bien que je vienne au départ du monde de l'informatique théorique, j'espère pouvoir augmenter mes compétences en électronique pour pouvoir allier les deux. J'ai aussi un petit faible pour la domotique.

* '''L'informatique'''. Que dire, je suis tombé dedans tout petit comme pas mal de gens de ma génération. Ca a commencé comme une histoire de famille, c'est devenu ensuite une passion à plein temps. Je m'intéresse à la vérification de code, à la preuve des systèmes. Plutôt le côté formel donc.

* '''Les logiciels libres''' ne sont pas seulement pour moi une part de l'informatique mais une véritable vision de la conception et de la réalisation des systèmes. C'est pour moi une véritable façon d'intégrer l'humain dans les productions industrielles (pour le moment majoritairement informatique, bien qu'on voit arriver des productions électroniques libres).

* '''Nouvelles technologies'''. J'essaye autant que se peut, d'être au coeur de la veille technologique. Mais c'est pas forcément simple de part la nature même des informations recherchées.

== Compétences & travaux de recherche (personnels) ==

Je sais pas trop quoi mettre, je mets donc une copie (un peu baclée...) de mon CV et de ce sur quoi je me documente en ce moment. J'espère que ce sera pas trop pompeux...

* '''Programmation''' (tous niveaux confondus): ASM (8086, PIC), C/C++, Java, OCaml, JoCaml (OCaml concurrent et distribué basé sur le Join-Calculus), Python, PHP, Erlang.
* '''Electronique''': pas encore grand chose. Surtout l'électronique numérique du fait que je vienne de l'informatique.
* '''OS''': Linux(Debian, Ubuntu), Windows(mais je dois l'allumer 2 fois par an), MacOS X
* '''Informatique-Mathématiques''': compléxité, langages fonctionnels et impératif, noyau Linux (un peu), programmation concurrente et distribuée, design pattern, tolérances aux pannes, reseaux, détection de mouvements, ...

User:JulienPeeters

2009-03-23T20:21:30Z

JulienPeeters: /* Qui suis-je ? */

== Qui suis-je ? ==
[[Image:Tete_julien_bg.jpg]]
* Nom, Prénom: Peeters Julien
* Age: 22 ans
* Profession: Etudiant en 2e année d'école d'ingénieur, spécialité systèmes embarqués

== Qu'est-ce qui m'intéresse ? ==
* '''L'électronique''' m'intéresse depuis pas mal d'années. Plus particulièrement les systèmes embarqués et les systèmes de contrôle-commande. Si on peut rajouter des contraintes, type temps réel ou autre, j'en suis d'autant plus ravi! Bien que je vienne au départ du monde de l'informatique théorique, j'espère pouvoir augmenter mes compétences en électronique pour pouvoir allier les deux. J'ai aussi un petit faible pour la domotique.

* '''L'informatique'''. Que dire, je suis tombé dedans tout petit comme pas mal de gens de ma génération. Ca a commencé comme une histoire de famille, c'est devenu ensuite une passion à plein temps. Je m'intéresse à la vérification de code, à la preuve des systèmes. Beaucoup de maths quoi. Je fais pas mal d'OCaml en ce moment pour ceux qui connaissent.

* '''Les logiciels libres''' ne sont pas seulement pour moi une part de l'informatique mais une véritable vision de la conception et de la réalisation de produits. C'est pour moi une véritable façon d'intégrer l'humain dans les productions industrielles (pour le moment majoritairement informatique, bien qu'on voit arriver des productions électroniques libres).

* '''Nouvelles technologies'''. J'essaye autant que se peut, d'être au coeur de la veille technologique. Mais c'est pas forcément simple de part la nature même des informations recherchées.

== Compétences & travaux de recherche (personnels) ==

Je sais pas trop quoi mettre, je mets donc une copie (un peu baclée...) de mon CV et de ce sur quoi je me documente en ce moment. J'espère que ce sera pas trop pompeux...

* '''Programmation''' (tous niveaux confondus): ASM (8086, PIC), C/C++, Java, OCaml, JoCaml (OCaml concurrent et distribué basé sur le Join-Calculus), Python, PHP, Erlang.
* '''Electronique''': pas encore grand chose. Surtout l'électronique numérique du fait que je vienne de l'informatique.
* '''OS''': Linux(Debian, Ubuntu), Windows(mais je dois l'allumer 2 fois par an), MacOS X
* '''Informatique-Mathématiques''': compléxité, langages fonctionnels et impératif, noyau Linux (un peu), programmation concurrente et distribuée, design pattern, tolérances aux pannes, reseaux, détection de mouvements, ...

Contest

2008-11-17T06:29:29Z

JulienPeeters: /* Projects List */

'''Association Contest'''

On this page, you will find all the usefull informations to participate to the Armadeus Project Association Contest

==What is it and why ?==
After one year of existence, the association has generated enough cash to promote or speed up internal developments.
Several proposals have been sent to the members and during the last annual meeting, it has been decided to use a part of these funds to organize a contest.
The goal of this contest is to increase the number of applications developped by the members.

==Who can participate ?==
The members of the association (ie the people who already have an APF9328 board).
This is a restrictive point, but we consider that a common development system is mandatory to share the work.

== The rules ==
* The projects have to be registered before: December 31 2008
* The participant(s) is a (are) member(s) of the Armadeus Project association
* The whole sources and the schematics have to be publicly available and usable (GPL/LGPL)
* Hardware or/and software applications can be proposed
* A wiki page is mandatory and must contain ([[Contest_Template_Page|here is a template]]):
** a description of the project (a few words)
** the name(s) of the member(s)
** the documentation to use the application, to compile the sources and to build the hardware
* No special components have to be used (for electronics projects): all must be easily purchased
* Registration is done by adding the link of the wiki page to the list below
* The jury is composed of all the interested Armadeus Project members (min 5 members) and will have one month to deliberate after the contest closure. The vote will be done by email and have to be sent to contest(at)armadeus(dot)org

== The awards==
* First award: an [[APF27]] kit (APF27 + corresponding dev board + TFT LQ043 and adapter board)
* Second award: an APF9328 kit ([[APF9328]] + [[APF9328DevFull]] + TFT LQ043 and adapter board)
* Third award: an [[APF9328]] + [[APF9328DevFull]]

==Projects List==
* [[FireBoard | FireBoard, development cards emulation project]] (in pause)
* [[MotionSystem | MotionSystem, R/C Servos Controller and Motion Measurement]]

File:Tete julien bg.jpg

2008-09-27T20:33:44Z

JulienPeeters: uploaded a new version of "Image:Tete julien bg.jpg"

File:Tete julien bg.jpg

2008-09-27T20:30:46Z

JulienPeeters: uploaded a new version of "Image:Tete julien bg.jpg"

QemuMachineDevelopment

2008-09-27T20:28:28Z

JulienPeeters: /* Introduction */

== Introduction ==
The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

'''See FireBoard project in the [[Contest | Contest 2008]] page.'''

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-09-27T20:27:45Z

JulienPeeters: /* Introduction */

== Introduction ==
The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

'''See FireBoard project in the Contest 2008 page [[Contest]].'''

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-09-27T20:27:30Z

JulienPeeters: /* Introduction */

== Introduction ==
The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

See FireBoard project in the Contest 2008 page [[Contest]].

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-09-27T20:25:48Z

JulienPeeters: /* Source trees */

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

FireBoard

2008-06-29T20:27:51Z

JulienPeeters: /* Project Description */

==Project Description==

The aim of our project is to make a modular emulator for Armadeus development boards.

The software will be based on the [http://softgun.sourceforge.net SoftGun emulator]. It'll be able to emulate the apf9328 with dev light kit.

A XML file will describe the system architecture and connection between devices. An engine will parse the XML file and make the emulator for the requested architecture (connect virtual devices together).

==Participating Armadeus members==
* [[User:JulienPeeters]]
* [[User:MatthieuT]]

==Project data==
===Link to software sources and the way to build it===
(comming soon)

===Link to hardware schematics (if any)===
(comming soon)

==How to use the project==
(comming soon)

==Links==
* [http://www.armadeus.com/wiki/index.php?title=QemuMachineDevelopment QemuMachineDevelopment ]
* [http://softgun.sourceforge.net/ SoftGun]

Contest

2008-06-29T18:14:33Z

JulienPeeters: /* Projects List */

'''Association Contest (PRELIMINARY)'''
[[Image:Construction.png]]<br>

On this page, you will find all the usefull informations to participate to the Armadeus Project Association Contest

==What is it and why ?==
After one year of existence, the association has generated enough cash to promote or speed up internal developments.
Several proposals have been sent to the members and during the last annual meeting, it has been decided to use a part of these funds to organize a contest.
The goal of this contest is to increase the number of applications developped by the members.

==Who can participate ?==
The members of the association (ie the people who already have an APF9328 board).
This is a restrictive point, but we consider that a common development system is mandatory to share the work.

== The rules ==
* The projects have to be registered before: December 31 2008
* The participant(s) is a (are) member(s) of the Armadeus Project association
* The whole sources and the schematics have to be publicly available and usable (GPL/LGPL)
* Hardware or/and software applications can be proposed
* A wiki page is mandatory and must contain ([[Contest_Template_Page|here is a template]]):
** a description of the project (a few words)
** the name(s) of the member(s)
** the documentation to use the application, to compile the sources and to build the hardware
* No special components have to be used (for electronics projects): all must be easily purchased
* Registration is done by adding the link of the wiki page to the list below
* The jury is composed of all the interested Armadeus Project members (min 5 members) and will have one month to deliberate after the contest closure. The vote will be done by email and have to be sent to contest(at)armadeus(dot)org

== The awards==
* First award: an [[APF27]] kit (APF27 + corresponding dev board + TFT LQ043 and adapter board)
* Second award: an APF9328 kit ([[APF9328]] + [[APF9328DevFull]] + TFT LQ043 and adapter board)
* Third award: an [[APF9328]] + [[APF9328DevFull]]

==Projects List==
* [[FireBoard | FireBoard, development cards emulation project]]

QemuMachineDevelopment

2008-06-22T15:52:54Z

JulienPeeters:

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T15:51:59Z

JulienPeeters: /* Improve Qemu understanding */

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.

The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.

=== The Target specific code ===

It's not alredy clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T13:30:24Z

JulienPeeters:

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation system core ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.

Qemu is also composed of a common emulation system mainly contained in the vl.c file (in the root of the source tree). Every function which manage the emulation system are placed in this file.

=== The Target specific code ===

It's not alredy clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T13:29:32Z

JulienPeeters:

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation core system ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.

Qemu is also composed of a common emulation system mainly contained in the vl.c file (in the root of the source tree). Every function which manage the emulation system are placed in this file.

=== The Target specific code ===

It's not alredy clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T13:24:55Z

JulienPeeters:

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Qemu mechanisms : Qemu separated in three parts ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== The code translation and the emulation core system ===

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.

Qemu is also composed of a common emulation system mainly contained in the vl.c file (in the root of the source tree). Every function which manage the emulation system are placed in this file.

=== The Target specific code ==

It's not alredy clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").

=== The hardware emulation layer ===

Despite of the hardware emulation layer is implemented both in the common emulation system and in an independent directory (named "hw"). It interacts with the emulation core through Qemu common functions each time. (see vl.c file)

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T13:16:11Z

JulienPeeters: /* Adding Qemu mechanisms explanations */

== Introduction ==
{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

== Understanding of the Qemu functions ==

Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.

=== Qemu separated in two parts ===

==== The code translation and the emulation core system ====

Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.

Qemu is also composed of a common emulation system mainly contained in the vl.c file (in the root of the source tree). Every function which manage the emulation system are placed in this file.

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-22T13:02:12Z

JulienPeeters:

QemuMachineDevelopment

2008-06-22T11:47:49Z

JulienPeeters:

{{Under_Construction}}

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

QemuMachineDevelopment

2008-06-08T13:43:47Z

JulienPeeters:

== UNDER CONSTRUCTION ==
[[Image:Construction.png]]

The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.

In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).

== Armadeus boards devices ==

{| border="1" cellspacing="0" cellpadding="5"
|- style="background:#efefef;"
! Device || Implemented ?
|-
| Network interface || style="background:#ff0000;" |not implemented
|-
| SD/MMC card reader || style="background:#ff0000;" |not implemented
|-
| GPIO || style="background:#ff0000;" |not implemented
|-
| Led's || style="background:#ff0000;" |not implemented
|-
| CAN bus || style="background:#ff0000;" | not implemented
|-
| I2C bus || style="background:#ff0000;" | not implemented
|-
| ADC/DAC || style="background:#ff0000;" | not implemented
|-
| SPI || style="background:#ff0000;" | not implemented
|-
| SSI || style="background:#ff0000;" | not implemented
|-
| UART || style="background:#ff0000;" | not implemented
|-
| USB (slave/host) || style="background:#ff0000;" | not implemented
|-
| LCD || style="background:#ff0000;" | not implemented
|-
| FPGA || style="background:#ff0000;" | not implemented
|-
| SRAM || style="background:#ff0000;" | not implemented
|-
| CSI || style="background:#ff0000;" | not implemented
|-
| Touchscreen || style="background:#ff0000;" | not implemented
|}

== Source trees ==

Firstly, you have to install Subversion and Git packages

On Debian/Ubuntu (any version) :
<pre>
[myhome] # apt-get install subversion git-core
</pre>

On Gentoo
<pre>
[myhome] # emerge dev-util/subversion dev-util/git
</pre>

You can download the official QEMU svn tree here :

<pre>
[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk
</pre>

And [[User:JulienPeeters | my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :

<pre>
[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters
</pre>

==Links==
* [http://softgun.sourceforge.net/ Softgun ARM emulator (already has many i.MX21/i.MX1 devices)]
* [http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html Low level ARM booting]
* [http://www.arm.linux.org.uk/ Linux on all arm machines]

[[Category:Emulation]]

Talk:QemuMachineDevelopment

2008-06-08T13:40:57Z

JulienPeeters:

Talk:QemuMachineDevelopment

2008-06-07T20:09:02Z

JulienPeeters:

* '''JulienB:''' It could be interesting to look at softgun source code because they already have many i.MX21/i.MX1 devices emulated:
http://softgun.sourceforge.net/
* '''JulienP''' Yes I agree. I took a look at this project yestudray. Despite they have a few different way to manage devices than in Qemu many things could reused. For the moment I think Qemu would be better to build the base system. It could be also interesting to implement a board specification language in XML and be able to parse it in order to make the boards descriptions easier. But I don't know what's the best way to do that for now.
* '''JulienP''' I've read several lines from different files of QEMU and at this time I think we have to take only a part of it. To be more precise QEMU is a big program from which we will only use a very little part. The aim is to reduce to its maximum the application we want to build in terms of memory space and easiness of the code maintenance. I'm seeing if we could extract just what we need from QEMU (cpu emulation + dynamic code translation) and then build a software into which we could connect other functionalities (devices emulation + board generator based on XML, ...). I would like to know now what people from Armadeus Project who are interested in this project think of that...

Members

2008-06-03T08:49:09Z

JulienPeeters:

==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.568077, 7.912888, [[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
</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]]

Talk:QemuMachineDevelopment

2008-06-01T11:49:19Z

JulienPeeters:

QemuMachineDevelopment

2008-05-31T14:13:26Z

JulienPeeters:

QemuMachineDevelopment

2008-05-27T19:03:44Z

JulienPeeters: /* Armadeus boards devices */

QemuMachineDevelopment

2008-05-27T18:55:23Z

JulienPeeters: /* Git development tree */

QemuMachineDevelopment

2008-05-27T18:54:29Z

JulienPeeters:

QemuMachineDevelopment

2008-05-24T11:00:02Z

JulienPeeters: /* Git development tree */

== UNDER CONSTRUCTION ==
[[Image:Construction.png]]

== Armadeus boards devices ==

* Network device
* SD/MMC card reader
* ...

== Git development tree ==

Coming soon and depends on the interest people have in this project.

QemuMachineDevelopment

2008-05-23T22:23:35Z

JulienPeeters: