ArmadeusWiki - User contributions [en]

POD Tutorial 2

2009-09-16T09:37:06Z

PaoloB: updated pod syntax: addcomponent became addinstance

{{Under_Construction}}

Here is a simple use case example for POD. We will create a project to include a full modem UART coming from OpenCores.org. This IP is compatible with the [[OpenCore_16550_IP_Linux_driver|16550 Linux serial driver]]. The platform used is the APF9328.

[[image:projectuart.png|center|thumb|500px|'''figure 1''' - ''Simple example with one uart'']]

In this example, a complete POD project is built including the synthesis, the simulation and the generation of the Linux drivers. The operating system used to run POD is Ubuntu 7.10.

== Project creation ==

In a terminal, run POD as follow:

<source lang="bash">
$ python pod.py
POD>
</source>

The runtime file ''pod.py'' is in directory ''pod/bin/''.

A console prompt is displayed. To create a project, enter in the project environment
then write ''create'':

<source lang="bash">
POD> project
POD.project> create uartproject
Project uartproject created
POD.project:uartproject>
</source>

The project created is named ''uartproject''. Now, the targeted platform can be selected with the ''selectplatform'' command:

<source lang="bash">
POD.project:uartproject> selectplatform apf9328
Component platform added as apf9328
Component imx9328_wb16_wrapper added as imx9328_wb16_wrapper00
Component rstgen_syscon added as rstgen_syscon00
Component irq_mngr added as irq_mngr00
setting base address 0x0 for irq_mngr00.swb16
Platform apf9328 selected
POD.project:uartproject>
</source>

When the platform APF9328 is selected, POD automatically loads some components : the wrapper, the syscon and the interrupts manager corresponding to this platform. These components are used for a Wishbone bus. If they are not required they can be deleted with the ''delcomponent'' command.

To complete the project, the uart16550 component must be loaded. The component library proposes severals components categories that can be displayed with the ''listcomponent'' command:

<source lang="bash">
POD.project:uartproject> listcomponents
syscons wrappers test components
</source>

UART components can be found in "components" category :

<source lang="bash">
POD.project:uartproject> listcomponents components
i2cocore button irq_mngr led uart16550 ledsensor simplegpio
</source>

A component can then be load with the ''addcomponent'' command:
<source lang="bash">
POD.project:uartproject> addinstance components.uart16550 uart
Component uart16550 added as uart
</source>

Now that all the components of the project are loaded, we can connect them.

== Component connection ==

=== Interrupt connection ===

The UART component has one connection pin named ''interrupt.int_o'', it will be connected to the irqport pin 0 of the interrupt manager (irq_mngr00):

<source lang="bash">
uartproject> connectpin uart.interrupt.int_o irq_mngr00.irq.irqport.0
pin connected
</source>

=== FPGA connections ===

The UART signals must be connected outside the fpga. The platform name is used like another component of the project. The UART pins will be connected to the platform pins ''via'' the apf9328 instance.

<source lang="bash">
POD.project:uartproject> connectpin uart.uart.srx_pad_i apf9328.fpga.IO_L21N_2
POD.project:uartproject> connectpin uart.uart.stx_pad_o apf9328.fpga.IO_L21P_2
POD.project:uartproject> connectpin uart.uart.rts_pad_o apf9328.fpga.IO_L22N_2
POD.project:uartproject> connectpin uart.uart.cts_pad_i apf9328.fpga.IO_L22P_2
POD.project:uartproject> connectpin uart.uart.dtr_pad_o apf9328.fpga.IO_L23N_2
POD.project:uartproject> connectpin uart.uart.dsr_pad_i apf9328.fpga.IO_L23P_2
POD.project:uartproject> connectpin uart.uart.dcd_pad_i apf9328.fpga.IO_L24N_2
POD.project:uartproject> connectpin uart.uart.ri_pad_i apf9328.fpga.IO_L40N_2
</source>

=== Bus connection ===

The irq manager was automaticaly connected to the wrapper/syscon when the platform was selected (part of the plateform), thus only the UART must be connected to the wrapper with the ''connectbus'' command:

<source lang="bash">
POD.project:uartproject> connectbus imx9328_wb16_wrapper00.mwb16 uart.swb16
Bus connected
</source>

=== Clock connection ===

The Wishbone bus requires a clock and a reset connection to be assigned, this can be done by means of the ''addbusclock'' command.

<source lang="bash">
> addbusclock rstgen_syscon00.candr imx9328_wb16_wrapper00.mwb16
Connected
</source>

This connection is done automatically when command ''autoconnectbus'' is called.

== Code generation ==

The component connections are now done. The Intercon and the Top components
can then be automatically generated.

=== Intercon ===

The intercon is a component creating the connections for the Wishbone bus. It is generated with the ''intercon'' command and with the master bus interface as parameter :

<source lang="bash">
POD.project:uartproject> intercon imx9328_wb16_wrapper00.mwb16
setting base address 0x10 for uart.swb16
Component imx9328_wb16_wrapper00_mwb16_intercon added as
imx9328_wb16_wrapper00_mwb16_intercon
Intercon with name : imx9328_wb16_wrapper00_mwb16_intercon Done
</source>

A new component named ''imx9328_wb16_wrapper00_mwb16_intercon'' is created and added to the project.

=== Top ===

The Top component is a VHDL component creating the non Wishbone connections. To generate it just type ''top'' :

<source lang="bash">
POD.project:uartproject> top
Top generated with name : top_uartproject.vhd
</source>

== Toolchain project generation ==

The project is now fully specified, we can generate the project files for the synthesis, for the simulation and for the driver.

=== Synthesis ===

The targeted FPGA is a Xilinx Spartan3 and thus ISE is needed for the synthesis. Under the ''synthesis'' environment ISE can be selected with the ''selecttoolchain'' command :

<source lang="bash">
POD.project:uartproject> synthesis
POD.project.synthesis> selecttoolchain ise
</source>

Then the synthesis project can be generated :

<source lang="bash">
POD.project.synthesis> generateproject
Make directory for imx9328_wb16_wrapper
Make directory for rstgen_syscon
Make directory for irq_mngr
Make directory for uart16550
Make directory for imx9328_wb16_wrapper00_mwb16_intercon
POD.project.synthesis> generatepinout
Constraint file generated with name :
uartproject/synthesis/uartproject.ucf
POD.project.synthesis> generatetcl
Script generated with name uartproject.tcl
</source>

The ''generateproject'' command creates a subdirectory for each component and fill in it with the corresponding VHDL code.
''generatepinout'' command creates the constraint file for the fpga-pin configuration and ''generatetcl'' creates the tcl script to automatise ISE.

In ISE, to synthesize the project we just have to launch :
<source lang="bash">
% source uartproject.tcl
</source>

===Simulation project===
TBD

=== Driver generation ===

To generate the driver, the operating system must be selected :
<source lang="bash">
POD.project:uartproject> driver
POD.project.driver> selectoperatingsystem linux
</source>

Then command ''generateproject'' can be used to create the driver project:
<source lang="bash">
POD.project.driver> generateproject
No driver for imx9328_wb16_wrapper
No driver for rstgen_syscon
Copy drivers template for irq_mngr
Copy drivers template for uart16550
No driver for imx9328_wb16_wrapper00_mwb16_intercon
</source>

For each component in the project, POD looks for a template driver according to the OS selected (here Linux). If a template is found, the files are copied in the ''project/drivers/'' directory.
In this example, only the ''irq_mngr'' and the ''uart16550'' have a linux driver.

Once the template sources copied, they can be filled in with the ''filltemplates'' command :

<source lang="bash">
POD.project.driver> filltemplates
Fill template for irq_mngr
Fill template for uart16550
</source>

The drivers will be copied in the Armadeus project tree with the command ''copydrivers''. But before, the driver directory must be selected with the ''selectprojecttree'' command:

<source lang="bash">
...> selectprojecttree ~/armadeus/target/linux/modules/fpga/POD
POD.project:uartproject.driver> copydrivers
</source>

== Script ==

Scripts can be used to automatize the conception of a project.
A script is a simple text file with one command per line. The # symbol can be used for delimiting comments.

Scripts can be launched directly from the command line when calling POD:

<source lang="bash">
$ python pod.py scriptname
</source>

Or can be loaded from POD :
<source lang="bash">
POD> source scriptname
</source>

Finally a command history can be saved as a script with the ''savehistory'' command :

<source lang="bash">
POD> savehistory uartscript
</source>

The whole script for the uart project example can be found below :
<source lang="bash">
project.create uartproject
project.selectplatform apf9328
project.listcomponents
project.listcomponents components
project.addcomponent components.uart16550 uart
project.connectpin uart.interrupt.int_o irq_mngr00.irq.irqport.0
project.connectpin uart.uart.srx_pad_i apf9328.fpga.IO_L21N_2
project.connectpin uart.uart.stx_pad_o apf9328.fpga.IO_L21P_2
project.connectpin uart.uart.rts_pad_o apf9328.fpga.IO_L22N_2
project.connectpin uart.uart.cts_pad_i apf9328.fpga.IO_L22P_2
project.connectpin uart.uart.dtr_pad_o apf9328.fpga.IO_L23N_2
project.connectpin uart.uart.dsr_pad_i apf9328.fpga.IO_L23P_2
project.connectpin uart.uart.dcd_pad_i apf9328.fpga.IO_L24N_2
project.connectpin uart.uart.ri_pad_i apf9328.fpga.IO_L40N_2
project.connectbus imx9328_wb16_wrapper00.mwb16 uart.swb16
project.addbusclock rstgen_syscon00.candr imx9328_wb16_wrapper00.mwb16
project.intercon imx9328_wb16_wrapper00.mwb16
project.codegen.intercon imx9328_wb16_wrapper00.mwb16
project.codegen.top
project.synthesis.selecttoolchain ise
project.synthesis.generateproject
project.synthesis.generatepinout
project.synthesis.generatetcl
project.simulation.selecttoolchain ghdl
project.simulation.generatetestbench
project.simulation.generatemakefile
project.driver.selectoperatingsystem linux
project.driver.generateproject
project.driver.filltemplates
project.driver.selectprojecttree ~/armadeus/target/linux/modules/fpga/POD
project.driver.copydrivers
</source>
[[Category:POD]]

QEMU

2009-06-17T16:05:12Z

PaoloB: /* Launch it */

{{Under_Construction}}

Well, you don't have enough money to buy an Armadeus board and just want to be part of the "Software" side of the project ? Then QEMU can be a good choice for you !! 
{{Warning|
Just be aware that currently Armadeus hardware is not emulated under QEMU, we are just using an other board hardware emulation (ARM Versatile) and Linux kernel to launch our rootfs and test our software which is not hardware related (ie User interface, Network, etc...)
}}

In order to build a hardware matching machine for Armadeus boards under Qemu, follow this link and add devices you are interested to see emulated in Qemu:
[[QemuMachineDevelopment | Qemu machine development]]

==Installation==
* on Debian, *Ubuntu just do a:
[armadeus]$ sudo apt-get install qemu bridge-utils ?vde?

==Configuration==

QEMU has several ways of emulating the network:
* user mode (by default): you can access Internet from your emulated target or an internal Samba/TFTP server but your are not directly accessible
* bridge mode: you can communicate directly with the Host

 
{{Note|For a first try you can skip following part and go directly [[QEMU#Get.2Fgenerate_simulation_images|here.]]}}
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
This mode require some configuration on your Host:
* Install ''bridge_utils'' package
* Activate IPv4 forwarding, for example on Ubuntu, uncomment the following line in ''/etc/sysctl.conf'':
<pre class=host>
$ sudo vim /etc/sysctl.conf

# Uncomment the next line to enable packet forwarding for IPv4
#net/ipv4/ip_forward=1
</pre>
* In ''/etc/network/interface'' comment the line referring to your current Ethernet card and replace them with:

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

#auto eth0
#iface eth0 inet dhcp
{{Note|If you are using a modern linux distribution like Ubuntu, also be sure NetworkManager is disabled/not configured. Otherwise conflict occur and network does not work at all.}}

* Create a script ''/etc/qemu-ifup'' that will be executed upon the start of QEMU:
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2

* Now you can append the following options to the qemu command line:
-net nic,vlan=0,macaddr=00:16:3e:00:00:01 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup
You don't need to give a MAC address if you are emulating only one machine, as QEMU will use a default one. However if you have more than one emulated machine (don't forget QEMU can also emulate other architectures than ARM), you will have to specify a unique MAC address for each machine.

* Once booted, on your guest you can configure the network simply as follows:
<pre class="apf">
# udhcpc -i eth0
</pre>

==Get/generate simulation images (Linux & rootfs)==
* As QEMU doesn't support (yet) the APF, we will use the Versatile PB emulated hardware. To get a compatible Linux kernel for this board do:
<pre class="host">
$ cd your_armadeus_view/
$ wget http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.26-2-versatile
</pre>
* get some useful environment variables:
<pre class="host">
$ make shell_env
$ source armadeus_env.sh
</pre>
* in ''$ARMADEUS_ROOTFS_DIR/etc/inittab'', comment following line:
<pre class="host">
ttySMX0::respawn:/sbin/getty -L ttySMX0 115200,57600,38400 vt100
</pre>
* Re-generate your Armadeus rootfs:
<pre class="host">
$ make
</pre>
* check the size of your rootfs image
<pre class="host">
$ ls -al $ARMADEUS_ROOTFS_TAR
</pre>
* generate a dummy image larger than your rootfs; here 60 MBytes for a 45 MBytes tared rootfs:
<pre class="host">
$ dd if=/dev/zero of=armadeus-qemu.img bs=1MB count=60
$ sudo mke2fs -F -m 0 -b 1024 armadeus-qemu.img
</pre>
* mount it and copy it your rootfs:
<pre class="host">
$ mkdir qemu_mnt
$ sudo mount -t ext2 -o loop armadeus-qemu.img qemu_mnt/
$ sudo tar xf $ARMADEUS_ROOTFS_TAR -C qemu_mnt/
$ sudo umount qemu_mnt/
</pre>
* now you have all you need to launch Qemu

==Launch it==
* Example with 64 MBytes of RAM:
<pre class="host">
$ qemu-system-arm -M versatilepb -kernel ./vmlinuz-2.6.26-2-versatile -hda armadeus-qemu.img -m 64 \
-append "root=/dev/sda mem=64M ro"
</pre>

[[Image:qemu_apf_ramdisk.png]]

* When system has booted, if you are French, load a usable keymap:
<pre class="apf">
# loadkmap < /etc/i18n/fr.kmap
</pre>
<pre class="host">
=> loqdk,qp < !etc!i&_n!fr:k,qp on your PC keyboard
</pre>

==To Be Continued... ;-) ==

==Links==
* [http://fabrice.bellard.free.fr/qemu/ QEMU WebPage]
* [http://www.aurel32.net/info/debian_arm_qemu.php Debian on an emulated ARM machine tutorial by Aurel32] + [http://qemu-forum.ipi.fi/viewtopic.php?t=3919 comments about it]
* [http://909ers.apl.washington.edu/~dushaw/ARM/ Debian ARM Linux on Qemu]
* http://www.gnome.org/~markmc/qemu-networking.html
* [http://compsoc.dur.ac.uk/~djw/qemu.html QEMU - Debian - Linux - TUN/TAP - network bridge]
* [http://gumstix.net/wiki/index.php?title=Running_qemu Gumstix's way of using QEmu]
* [http://gumstix.net/wiki/index.php?title=Making_qemu_images Gumstix's way of generating QEmu's images]
* [https://wiki.ubuntu.com/ARM/RootfsFromScratch Generating Ubuntu for ARM with QEMU]

[[Category:Emulation]]

QEMU

2009-05-29T10:06:01Z

PaoloB:

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

Well, you don't have enough money to buy an Armadeus board and just want to be part of the "Software" side of the project ? Then QEMU can be a good choice for you !! 
'''Just be aware that currently Armadeus hardware is not emulated under QEMU, we are just using an other board hard and linux kernel to launch our Rootfs an test our software which is not custom hardware related (ie User interface, Network, etc...)'''

In order to build a hardware matching machine under Qemu for Armadeus boards, follow this link and add devices you are intrested to see emulated in Qemu:
[[QemuMachineDevelopment | Qemu machine development]]

==Installation==
* on Debian, *Ubuntu just do a:
[armadeus]$ sudo apt-get install qemu bridge-utils ?vde?

==Configuration==

QEMU has several ways of emulating the network:
* user mode (by default): you can access Internet from your emulated target or an internal Samba/TFTP server but your are not directly accessible
* bridge mode: you can communicate directly with the Host

 
{{Note|For a first try you can skip following part.}}
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
This mode require some configuration on your Host:
* Install ''bridge_utils'' package
* Activate IPv4 forwarding, for example on Ubuntu, uncomment the following line in ''/etc/sysctl.conf'':
<pre class=host>
$ sudo vim /etc/sysctl.conf

# Uncomment the next line to enable packet forwarding for IPv4
#net/ipv4/ip_forward=1
</pre>
* In ''/etc/network/interface'' comment the line referring to your current Ethernet card and replace them with:

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

#auto eth0
#iface eth0 inet dhcp
{{Note|If you are using a modern linux distribution like Ubuntu, also be sure NetworkManager is disabled/not configured. Otherwise conflict occur and network does not work at all.}}

* Create a script ''/etc/qemu-ifup'' that will be executed upon the start of QEMU:
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2

* Now you can append the following options to the qemu command line:
-net nic,vlan=0,macaddr=00:16:3e:00:00:01 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup
You don't need to give a MAC address if you are emulating only one machine, as QEMU will use a default one. However if you have more than one emulated machine (don't forget QEMU can also emulate other architectures than ARM), you will have to specify a unique MAC address for each machine.

* Once booted, on your guest you can configure the network simply as follows:
<pre class="apf">
# udhcpc -i eth0
</pre>

==Get/generate simulation images==
* In our tests we used the QEMU Versatile PB emulated hardware. To get a compatible Linux kernel for this board then:
[armadeus]$ wget http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-6-versatile
* in ''buildroot/project_build_armv4t/apf9328/root/etc/inittab'', comment following line:
ttySMX0::respawn:/sbin/getty -L ttySMX0 115200,57600,38400 vt100
* Generate your Armadeus Rootfs as an EXT2 image:
<pre class="host">
[armadeus]$ make menuconfig
</pre>
<pre class="config">
Target filesystem options --->
[*] ext2 root filesystem
</pre>
<pre class="host">
[armadeus]$ make
</pre>
* be sure that your rootfs image is less than 16Mbytes (Ramdisk limit)
* and zip it (we will use it as Ramdisk first):
<pre class="host">
[armadeus]$ gzip -9 buildroot/binaries/apf9328/apf9328-rootfs.arm.ext2
</pre>
* Create a fake QEMU Hard disk image
<pre class="host">
[armadeus]$ qemu-img create -f qcow rootfs.arm_nofpu2.img 20M
</pre>

==Launch it==
* At first boot, you have to launch the system as a Ramdisk:
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
-initrd apf9328-rootfs.arm.ext2.gz -append "root=/dev/ram" -hda ./apf9328-rootfs.arm_nofpu2.img

[[Image:qemu_apf_ramdisk.png]]

* When system has booted, we will create the "hard disk" image. But first, if you are French, do:
<pre class="apf">
# loadkmap < /etc/i18n/fr.kmap
</pre>
* then:
<pre class="apf">
# mkdir /tmp/dev
# mknod /tmp/dev/sda b 8 0
# mknod /tmp/dev/sda1 b 8 1
# fdisk /tmp/dev/sda
n p 1 <enter> <enter> w
# mkfs.ext2 /tmp/dev/sda1
</pre>
* Now we can mount our brand new file system:
<pre class="apf">
# mkdir /mnt/root
# mount /tmp/dev/sda1 /mnt/root
</pre>
{{Note|Following steps need you already configured [[Communicate | tftp]] on your host and networking up and running}}

* And now we can populate it:
<pre class="apf">
# cd /mnt/root
# tftp -g -r apf27-rootfs.arm.tar -l rootfs.arm.tar [HOST IP]
# tar -xvf rootfs.arm.tar
</pre>

* Finally halt the emulated system and, next boot, we can omit the initrd image:
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
-append "root=/dev/sda1" -hda ./apf9328-rootfs.arm_nofpu2.img

==Links==
* [http://fabrice.bellard.free.fr/qemu/ QEMU WebPage]
* [http://www.aurel32.net/info/debian_arm_qemu.php Debian on an emulated ARM machine tutorial by Aurel32] + [http://qemu-forum.ipi.fi/viewtopic.php?t=3919 comments about it]
* [http://909ers.apl.washington.edu/~dushaw/ARM/ Debian ARM Linux on Qemu]
* http://www.gnome.org/~markmc/qemu-networking.html
* [http://compsoc.dur.ac.uk/~djw/qemu.html QEMU - Debian - Linux - TUN/TAP - network bridge]

[[Category:Emulation]]

Eclipse

2009-05-29T08:55:45Z

PaoloB: /* Eclipse starting and configuration for the target */

How-To install Eclipse IDE and GDB debugger

==Forewords==
Eclipse IDE has been choosen as standard IDE for the Armadeus software development process. 
Specific pluggins will be added to ease writing kernel drivers and user applications. 
Despite one or two drawbacks (Java slowliness and memory usage for example), Eclipse provides several advantages like the support of different languages, the good integration of GDB ...

==Eclipse installation==
* Go to the [http://www.eclipse.org/downloads/ Eclipse download page] and select '''Eclipse IDE for C/C++ Developers''' (Linux version)
* Install Eclipse to your Home directory:
$ cd $HOME
Assuming that the downloaded package is located on your desktop:
$ tar -xvzf Desktop/eclipse-cpp-europa-winter-linux-gtk.tar.gz

==Eclipse starting and configuration for the target==
$ eclipse/eclipse &

1. Select your workspace (where your projects will be saved) 
2. Go to the workbench by clicking on "Workbench" 
3. Create a new C Project with the name "helloworld" ->File ->New -> C project 
4. Enter the project name here "helloworld" and click '''finish''' 
5. Now the ARM compiler has to be choosen to build the code for the target. Right click on the project "helloworld" in the project explorer and select '''properties''' 
6. In the '''C/C++ Build''' entry, select '''Settings''' then '''GCC C Compiler''' then insert the path of the ARM compiler in the field '''Command'''; for example:
/home/nicolas/armadeus/buildroot/build_armv4t/staging_dir/usr/bin/arm-linux-gcc
7. GCC options can be modified in the '''All options''' field 
8. Now the ARM linker has to be chosen as well. '''GCC C Linker''' then insert the path of the ARM linker in the field '''Command'''; for example:
/home/nicolas/armadeus/buildroot/build_armv4t/staging_dir/usr/bin/arm-linux-gcc
9. And finally the ARM assembler. '''GCC Assembler''' then insert the path of the ARM assembler in the field '''Command'''; for example:
/home/nicolas/armadeus/buildroot/build_armv4t/staging_dir/usr/bin/arm-linux-as
10. The path for the include files has to be specified as well. Eclipse has, by default, the include path of the host. In the '''C/C++ General''', select '''Paths and Symbols''' then '''GNU C''' in languages and add (for example):
/home/nicolas/armadeus/buildroot/toolchain_build_armv4t/uClibc-0.9.29/include
This will add the standard include files for the small helloworld example below. Depending on the application additional paths can be specified.

==helloworld build==
Once the project is correctly configured, we will add a new C File to it.
# Add a source file to the project by right clicking on the "helloworld" project and selecting New -> Source File
# Enter the name '''main.c''' and click '''finish'''
# Write the code. See the [[HelloWorld | hello world example page]]
# Then build it by selecting "helloworld" in the Project Explorer and then Project-> Build Project
# Take a look at the '''problems''' tab on the bottom of the Eclipse window to verify that the build was successfully done.

==Debug helloworld on the target==
Once the project has successfully compiled and linked:
# In the Eclipse IDE, right click on "helloworld" in the Project Navigator, then Debug As -> Open Debug Dialog
# Select '''C/C++ Local Application''' and create a '''new launch configuration''' (first icon in the top menu)
# This new configuration will be automatically named "helloworld Debug". Select the '''Debugger''' tab
# Select '''gdbserver Debugger''' in the "debugger" drop down list
# Now indicates where GDB is located (debugger option and GDB Debugger input); for example: <pre>/home/nicolas/armadeus/buildroot/build_armv4t/staging_dir/bin/arm-linux-gdb</pre>
# Once done, the link between the GDB server (on the target) and the GDB client (on the host) has to be configured. In "Debugger Options", select the "Connection" tab then "TCP" for the type if you want to use the ethernet link
# Indicates the target IP address for the gdb host server and then the port number: here 2345 
# Close and save the Debug configuration
# Transfer the "helloworld binary" on the target by means of TFTP, SCP or whatever you want ( ''tftp -g -r [PATH]/helloworld HOST_IP_ADDRESS'' )
# On your APF, start the program with GDB: <pre># gdbserver HOST_IP_ADDRESS:2345 helloworld </pre>
# GDB will launch your program and starts listen on port 2345 for a GDB client.
# in Eclipse start the debug session Run-> Debug

==Links==
* [[GDB | GDB/GDBserver command line usage]]
* [[HelloWorld | "Manual" compilation of a C program]]

[[Category:Toolchain]]

QEMU

2009-05-29T08:36:53Z

PaoloB: Added some configuration tips in networking section and added instructions to populate the hd image

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

Well, you don't have enough money to buy an Armadeus board and just want to be part of the "Software" side of the project ? Then QEMU can be a good choice for you !! 
'''Just be aware that currently Armadeus hardware is not emulated under QEMU, we are just using an other board hard and linux kernel to launch our Rootfs an test our software which is not custom hardware related (ie User interface, Network, etc...)'''

In order to build a hardware matching machine under Qemu for Armadeus boards, follow this link and add devices you are intrested to see emulated in Qemu:
[[QemuMachineDevelopment | Qemu machine development]]

==Installation==
* on Debian, *Ubuntu just do a:
[armadeus]$ sudo apt-get install qemu bridge-utils ?vde?

==Configuration==

QEMU has several ways of emulating the network:
* user mode (by default): you can access Internet from your emulated target or an internal Samba/TFTP server but your are not directly accessible
* bridge mode: you can communicate directly with the Host

 
{{Note|For a first try you can skip following part.}}
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
This mode require some configuration on your Host:
* Install ''bridge_utils'' package
* Activate IPv4 forwarding, for example on Ubuntu, uncomment the following line in ''/etc/sysctl.conf'':
<pre class=host>
$ sudo vim /etc/sysctl.conf

# Uncomment the next line to enable packet forwarding for IPv4
#net/ipv4/ip_forward=1
</pre>
* In ''/etc/network/interface'' comment the line referring to your current Ethernet card and replace them with:

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

#auto eth0
#iface eth0 inet dhcp
{{Note|If you are using a modern linux distribution like Ubuntu, also be sure NetworkManager is disabled/not configured. Otherwise conflict occur and network does not work at all.}}

* Create a script ''/etc/qemu-ifup'' that will be executed upon the start of QEMU:
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2

* Now you can append the following options to the qemu command line:
-net nic,vlan=0,macaddr=00:16:3e:00:00:01 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup
You don't need to give a MAC address if you are emulating only one machine, as QEMU will use a default one. However if you have more than one emulated machine (don't forget QEMU can also emulate other architectures than ARM), you will have to specify a unique MAC address for each machine.

* Once booted, on your guest you can configure the network simply as follows:
# udhcpc -i eth0

==Get/generate simulation images==
* In our tests we used the QEMU Versatile PB emulated hardware. To get a compatible Linux kernel for this board then:
[armadeus]$ wget http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-6-versatile
* in ''buildroot/project_build_armv4t/apf9328/root/etc/inittab'', comment following line:
ttySMX0::respawn:/sbin/getty -L ttySMX0 115200,57600,38400 vt100
* Generate your Armadeus Rootfs as an EXT2 image:
<pre class="host">
[armadeus]$ make menuconfig
</pre>
<pre class="config">
Target filesystem options --->
[*] ext2 root filesystem
</pre>
<pre class="host">
[armadeus]$ make
</pre>
* be sure that your rootfs image is less than 16Mbytes (Ramdisk limit)
* and zip it (we will use it as Ramdisk first):
<pre class="host">
[armadeus]$ gzip -9 buildroot/binaries/apf9328/apf9328-rootfs.arm.ext2
</pre>
* Create a fake QEMU Hard disk image
<pre class="host">
[armadeus]$ qemu-img create -f qcow rootfs.arm_nofpu2.img 20M
</pre>

==Launch it==
* At first boot, you have to launch the system as a Ramdisk:
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
-initrd apf9328-rootfs.arm.ext2.gz -append "root=/dev/ram" -hda ./apf9328-rootfs.arm_nofpu2.img

[[Image:qemu_apf_ramdisk.png]]

* When system has booted, we will create the "hard disk" image. But first, if you are French, do:
# loadkmap < /etc/i18n/fr.kmap
* then:
# mkdir /tmp/dev
# mknod /tmp/dev/sda b 8 0
# mknod /tmp/dev/sda1 b 8 1
# fdisk /tmp/dev/sda
n p 1 <enter> <enter> w
# mkfs.ext2 /tmp/dev/sda1
* Now we can mount our brand new file system:
# mkdir /mnt/root
# mount /tmp/dev/sda1 /mnt/root

{{Note|Following steps need you already configured [[Communicate | tftp]] on your host and networking up and running}}

* And now we can populate it:
# cd /mnt/root
# tftp -g -r apf27-rootfs.arm.tar -l rootfs.arm.tar [HOST IP]
# tar -xvf rootfs.arm.tar

* Finally halt the emulated system and, next boot, we can omit the initrd image:
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
-append "root=/dev/sda1" -hda ./apf9328-rootfs.arm_nofpu2.img

==Links==
* [http://fabrice.bellard.free.fr/qemu/ QEMU WebPage]
* [http://www.aurel32.net/info/debian_arm_qemu.php Debian on an emulated ARM machine tutorial by Aurel32] + [http://qemu-forum.ipi.fi/viewtopic.php?t=3919 comments about it]
* [http://909ers.apl.washington.edu/~dushaw/ARM/ Debian ARM Linux on Qemu]
* http://www.gnome.org/~markmc/qemu-networking.html
* [http://compsoc.dur.ac.uk/~djw/qemu.html QEMU - Debian - Linux - TUN/TAP - network bridge]

[[Category:Emulation]]

QEMU

2009-05-28T15:16:26Z

PaoloB: /* Configuration */

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

Well, you don't have enough money to buy an Armadeus board and just want to be part of the "Software" side of the project ? Then QEMU can be a good choice for you !! 
'''Just be aware that currently Armadeus hardware is not emulated under QEMU, we are just using an other board hard and linux kernel to launch our Rootfs an test our software which is not custom hardware related (ie User interface, Network, etc...)'''

In order to build a hardware matching machine under Qemu for Armadeus boards, follow this link and add devices you are intrested to see emulated in Qemu:
[[QemuMachineDevelopment | Qemu machine development]]

==Installation==
* on Debian, *Ubuntu just do a:
[armadeus]$ sudo apt-get install qemu bridge-utils ?vde?

==Configuration==

QEMU has several ways of emulating the network:
* user mode (by default): you can access Internet from your emulated target or an internal Samba/TFTP server but your are not directly accessible
* bridge mode: you can communicate directly with the Host

 
{{Note|For a first try you can skip following part.}}
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
This mode require some configuration on your Host:
* Activate IPv4 forwarding, for example on Ubuntu, uncomment the following line in ''/etc/sysctl.conf'':
<pre class=host>
$ sudo vim /etc/sysctl.conf

# Uncomment the next line to enable packet forwarding for IPv4
#net/ipv4/ip_forward=1
</pre>
* In ''/etc/network/interface'' comment the line referring to your current Ethernet card and replace them with:

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

#auto eth0
#iface eth0 inet dhcp
* If you are using a modern linux distribution like Ubuntu, also be sure NetworkManager is disabled/not configured anyway. Otherwise conflict occur and network does not work at all.

==Get/generate simulation images==
* In our tests we used the QEMU Versatile PB emulated hardware. To get a compatible Linux kernel for this board then:
[armadeus]$ wget http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-6-versatile
* in ''buildroot/project_build_armv4t/apf9328/root/etc/inittab'', comment following line:
ttySMX0::respawn:/sbin/getty -L ttySMX0 115200,57600,38400 vt100
* Generate your Armadeus Rootfs as an EXT2 image:
<pre class="host">
[armadeus]$ make menuconfig
</pre>
<pre class="config">
Target filesystem options --->
[*] ext2 root filesystem
</pre>
<pre class="host">
[armadeus]$ make
</pre>
* be sure that your rootfs image is less than 16Mbytes (Ramdisk limit)
* and zip it (we will use it as Ramdisk first):
<pre class="host">
[armadeus]$ gzip -9 buildroot/binaries/apf9328/apf9328-rootfs.arm.ext2
</pre>
* Create a fake QEMU Hard disk image
<pre class="host">
[armadeus]$ qemu-img create -f qcow rootfs.arm_nofpu2.img 20M
</pre>

==Launch it==
* At first boot, you have to launch the system as a Ramdisk:
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
-initrd apf9328-rootfs.arm.ext2.gz -append "root=/dev/ram" -hda ./apf9328-rootfs.arm_nofpu2.img

[[Image:qemu_apf_ramdisk.png]]

* When system has booted, we will create the "hard disk" image. But first, if you are French, do:
# loadkmap < /etc/i18n/fr.kmap
* then:
# mkdir /tmp/dev
# mknod /tmp/dev/sda b 8 0
# mknod /tmp/dev/sda1 b 8 1
# fdisk /tmp/dev/sda
n p 1 <enter> <enter> w
# mkfs.ext2 /tmp/dev/sda1

==Links==
* [http://fabrice.bellard.free.fr/qemu/ QEMU WebPage]
* [http://www.aurel32.net/info/debian_arm_qemu.php Debian on an emulated ARM machine tutorial by Aurel32] + [http://qemu-forum.ipi.fi/viewtopic.php?t=3919 comments about it]
* [http://909ers.apl.washington.edu/~dushaw/ARM/ Debian ARM Linux on Qemu]
* http://www.gnome.org/~markmc/qemu-networking.html
* http://compsoc.dur.ac.uk/~djw/qemu.html

[[Category:Emulation]]

QEMU

2009-05-27T13:29:18Z

PaoloB: /* Launch it */

Members

2009-05-27T13:27:26Z

PaoloB: /* Google Map */

==Google Map==

<googlemap lat="47" lon="6" width=640 height=480 zoom=4>
47.270377, 6.025314, [[User:JulienB]] Besancon
47.752598,7.301788, ARMadeus Systems
47.760791, 7.339897, [[User:Salocin68]] Mulhouse
47.734392,7.316975, [[User:FabienM]] Mulhouse
46.946161,7.517052, [[User:Jorasse]] Gümligen
47.681108, 7.390366, [[User:Carbure]] Helfranzkirch
47.436448, 8.429947, [[User:SonZerro]] Baden
44.653992, 6.176672, [[User:JulienN]] Chabottes
48.573342, 7.911476, [[User:KroMignon]] Legelshurst
42.734405, 2.894211, ELIAUS Perpignan
47.653363, 6.862335, UTBM Belfort
45.689589, 5.026395, [[User:OlivierT]] St Bonnet de Mure
48.879619, 2.351074, Paris - 20 members
43.622159, 1.442642, Toulouse - 2 members
-21.115141, 55.536384, La Réunion - 1 member
14.551684, -60.912323, La Martinique - 1 member
48.682805, 2.169186, [[User:BrunoL]] Les Ulis
47.399744, 8.53775, Zurich - 1 member
46.810282, 7.151241, Fribourg
47.574904, 7.580566, Basel

53.371859, -6.2677, Dublin - 1 member
50.637704, 5.608521, Liège - 1 member
50.67, 3.48, Velaines - 1 member
48.199964, 11.57959, Munich - 1 member
48.109588,-1.678752, Rennes - 1 member
47.750109,-3.366339, [[User:MatthieuT]] Lorient
48.70,2.03, [[User:JulienPeeters]] Chevreuse
45.190325, 5.700316, [[User:NicolasL]] Fontaine
49.279296, 2.472973 [[User:DavidC]] Nogent sur Oise
46.208644, 6.130027, [[User:EugeneR]] Genève
48.667158, 2.706585, [[User:BernardR]] Soignolles en Brie, France
45.188963, 5.709822, [[User:OlivierS]] Grenoble, France
47.214613,-0.737329, [[User:BrunoS]] Chemillé, France
47.225164,-1.556625, [[User:KevinP]] Nantes, France
43.609234, 1.442642, [[User:PierreBa]] Toulouse, France
41.668809,-0.87616, [[User:AntonioMB]] Zaragoza, España
49.200145, 0.407136, [[User:JeanFrancoisR]] - Asnières
48.109588,-1.678752, [[User:MichelTe]] - Rennes
49.163073, 2.550201, [[User:JulienBa]] - Pontarmé
43.488299, 5.494709, [[User:FrankA]] - Meyreuil
43.622159, 1.442642, [[User:PierreAlexandreS]] - Toulouse, France
51.46513, -0.9692, [[User:AlexG]] - Reading, UK
43.312439, 10.517693, [[User:PaoloB]] - Cecina, Italy

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

[[Category:Association]]

MemberList

2009-05-27T13:21:45Z

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

==Here is the list of the (active) members and their skills==

This list is maintained by the users themself.

*0: Novice
*1: Notions. At least one successfull experiment
*2: Confirmed
 

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! '''Name / IRC Nickname''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain / Salocin]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot / Artemys]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer / JiBee]] || 2 || 1 || 1 || 1 || robotics
|----------------
|[[User:NicolasA|Nicolas Aguirre]] || 2 || 0 || 1 || 1 || multimedia
|----------------
|[[User:BenoitC|Benoît Canet]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:SonZerro|Sonzerro]] || 0 || 0 || 1 || 2 || domotics
|----------------
|[[User:HenriG|Henri Geist]] || 1 || 1 || 0 || 1 || robotics
|----------------
|[[User:BorredonB|Bernard Borredon]] || 2 || 1 || 0 || 1 || domotics
|----------------
|[[User:ThomasB|Thomas Bores]] || 2 || 0 || 0 || 1 || Entertainment
|----------------
|[[User:FabriceM|Fabrice Mousset / KroMignon]] || 1 || 1 || 2 || 1 || Domotics & multimedia
|----------------
|[[User:AmineH|Amine EL HEDADI]] || 2 || 2 || 0 || 0 || domotics & robotics
|----------------
|[[User:PhilippeM|Philippe Monteil]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:CedricZ|Cédric Zmyj]] || 0 || 0 || 0 || 0 || domotics & robotics
|----------------
|[[User:JeanMichelN|Jean Michel Naimo / jeanmi12 ]] || 2 || 1 || 1 || 1 || Domotics & entertainment
|----------------
|[[User:OlivierC|Olivier Coutanceau]] || 1 || 0 || 0 || 0 || multimedia
|----------------
|[[User:ArnaudC|Arnaud COFFINET]] || 0 || 0 || 1 || 2 || multimedia & domotics
|----------------
|[[User:SylvainP|Sylvain PARRINO]] || 2 || 1 || 0 || 0 || robotics
|----------------
|[[User:AurelienH|Aurélien HIRON]] || 2 || 0 || 0 || 1 || robotics
|----------------
|[[User:GuillaumeT|Guillaume TRANNOY]] || 0 || 0 || 0 || 2 || domotics & robotics
|----------------
|[[User:JulienN|Julien NICOLAS / jujun]] || 2 || 1 || 0 || 1 || multimedia & network
|----------------
|[[User:StephaneF|Stéphane Falck]] || 0 || 0 || 0 || 0 || multimedia & robotics & domotics
|----------------
|[[User:GillesD|Gilles DUSSIN/ Sellig]] || 1 || 0 || 1 || 1 || robotics
|----------------
|[[User:MaximeL|Maxime Liron]] || 0 || 0 || 0 || 0 || domotics, robotics & multimedia
|----------------
|[[User:NicolasC|Nicolas CHARLERY/ realniko]] || 2 || 0 || 0 || 0 || electronic
|----------------
|[[User:BenoitJ|Benoit JESTER]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:FabienM|Fabien MARTEAU/ FabM]] || 1 || 2 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|[[User:JeanBaptisteMa| Jean-Baptiste Maillet]] || 2 || 1 || 0 || 0 || system
|----------------
|[[User:JeanFrancoisR| Jean-François Rousval]] || 2 || 1 || 0 || 1 ||
|----------------
|[[User:JulienPeeters| Julien Peeters]] || 2 || 1 || 0 || 0 || domotics, real-time, entertainment, network
|----------------
|[[User:YoannC| Yoann Congal / Alpheb]] || 0 || 0 || 0 || 1 || robotics
|----------------
|[[User:MatthieuT| Matthieu Texier / weeber]] || 1 || 0 || 1 || 0 || robotics, real-time
|----------------
|[[User:MartialG| Martial Guex]] || 2 || 1 || 1 || 2 || transceiver RF, real-time, wireless
|----------------
|[[User:NicolasL| Nicolas Lantz]] || 2 || 2 || 1 || 1 ||
|----------------
|[[User:GuillaumeD| Guillaume DELVIT]] || 1 || 1 || 1 || 1 || system, asynchronous CPU
|----------------
|[[User:BernardR|Bernard REMOND ]] || x || x || x || x ||
|----------------
|[[User:SamirH| Samir HAMNACHE]] || 0 || 0 || 0 || 1 || électronique
|----------------
|[[User:OlivierT|Olivier TARDIEU]] || 0 || 0 || 0 || 1 || électronique,robotics,domotics
|----------------
|[[User:ThibautR|Thibault Rétornaz]] || 1 || 1 || 1 || 0 || bio-med, électronique
|----------------
|[[User:BrunoS|Bruno Suarez]] || 2 || 0 || 0 || 0 || bio-med, électronique
|----------------
|[[User:guillaumeDe|Guillaume Denis]] || 0 || 0 || 2 || 1 || Electronique numérique, FPGA
|----------------
|[[User:KevinP|Kévin PETIT]] || 1 || 0 || 1 || 1 || Multimedia
|----------------
|[[User:PierreBa|Pierre Baudemont / b4ud3]] || 2 || 0 || 1 || 0 || domotics, robotics
|----------------
|[[User:BrunoL|Bruno Landré]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:AntonioMB|Antonio Meléndez]] || 0 || 0 || 1 || 2 || domotics, robotics, eletcronics
|----------------
|[[User:MichelTe|Michel Le Mer]] || 0 || 0 || 2 || 2 || electronics, software
|----------------
|[[User:JulienBa|Julien Baley]] || 0 || 0 || 0 || 0 ||
|----------------
|[[User:FrankA|Frank ANJEAUX]] || 1 || 0 || 0 || 1 || software,robotics, domotics, electronics
|----------------
|[[User:JulienViaud|Julien viaud/polric]] || 2 || 0 || 1 || 1 ||
|----------------
|[[User:NicolasCa|Nicolas CARTIER]] || 1 || 1 || 0 || 2 || domotics & robotics
|----------------
|[[User:PierreAlexandreS|Pierre Alexandre SCHEMBRI]] || 2 || 1 || 2 || 2 || electronics, board design, embedded software, FPGA, robotics, low power
|----------------
|[[User:AlexG|Alex GONZALEZ]] || 2 || 2 || 0 || 1 || telecommunications, network & multimedia
|----------------
|[[User:JulienL|Julien Lefrique / apapi]] || 1 || 0 || 1 || 1 ||
|----------------
|[[User:PaoloB|Paolo Bernini / nihil84]] || 2 || 1 || 0 || 0 || robotics, real-time
|}

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

[[Category:Association]]