ArmadeusWiki - User contributions [en]

Members

2008-11-15T13:07:17Z

JeanFrancoisR:

==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.199337,5.693665, [[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
</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]]

User:JeanFrancoisR

2008-08-16T14:31:23Z

JeanFrancoisR:

Je pense que je suis le doyen de l'association : 55 ans.

Dans les années 1973 à 1978, je me suis occupé de conception éléctronique : ampli op, portes, bascules, registres et compteurs en DIL
(pensait t'on déjà aux FPGA ?)

Dans les années 1979 à 1981, je me suis occupé de développement de cartes à base de microprocesseur 6800 et de programmation en assembleur 6800
(les compilations sur disquettes 8" duraient plusieurs heures et on faisait attention au code que l'on écrivait).

Dans les années 1982 à 1989, je me suis occupé de développement divers en informatique industrielle.

Dans les années 1990 à 1995, je me suis occupé de développement matériel et logiciel dans l'environnement 68000, OS-9, VME
(avec beaucoup d'assembleur 68000).

Dans les années 1993 à 2006, j'étais informaticien indépendant, en informatique industrielle bien sur.
Vers la fin de cette période j'ai réalisé quelques développements avec Linux donc une application embarquée en µClinux sur proccesseur XScale.

Je m'occupe actuellement de développement sous Linux pour une startup parisienne (1 jour à Paris et 4 jours en télétravail)
mais pas dans le domaine embarqué :(

J'habite en Normandie où je suis membre de 2 LUG : EURIX et RotomaLUG.

Target Software Installation

2008-06-16T12:03:01Z

JeanFrancoisR:

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

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=00:0E:32:00:00:01
autoload=no
...

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

Use the command '''saveenv''' to save the state of your environment variables in FLASH memory:
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors

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

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

BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.3
BIOS> setenv serverip 192.168.0.5
BIOS> saveenv

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

===Linux kernel building and installation===

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

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

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

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

'''!!! WARNING !! If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS) !!!'''
 
Check that transfered size value is less than 1572864 (0x180000 hex)
Bytes transferred = 1313216 (1409c0 hex)
----

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

----

* Flash kernel image with:
BIOS> run flash_kernel

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

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

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

* Flash RootFS image with:
BIOS> run flash_rootfs

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

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

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

===FPGA firmware installation===

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
BRAMTest led PS2 PS2_Opencore sram_test
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file. 
 
----
'''!!! Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!'''
----
 

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

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

* Flash your firmware image with:
BIOS> run flash_firmware

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

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

==Update U-Boot==

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

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

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

USB Host

2008-06-16T09:21:01Z

JeanFrancoisR:

How-To use the ISP176x USB Host controller of the APF9328DevFull

The DevFull is equipped with a USB 2.0 Host controller featuring three USB high speed ports. 

= USB HOST Controller =
== Driver installation ==
make linux-menuconfig

select Device Driver->USB support->support for Host-side USB (kernel) 
select Device Driver->Armadeus Specific Drivers->ISP1761 USB 2.0 Host controller (module)

== Starting the drivers ==
Three drivers have to be started in order to get the ISP working.
They have to be started in the following order:
modprobe apf9328-isp1761
modprobe hal_imx
modprobe pehci

= USB devices =

== USB keyboard ==
=== driver installation ===
Adding USB keyboard support
make linux-menuconfig
select Device Driver->HID Devices-> Generic HID support (kernel) 
select Device Driver->HID Devices-> USB Human Interface Device (module)
=== Starting the driver ===
modprobe usbhid

== USB Flash memory ==
=== driver installation ===
Adding USB Flash support
make linux-menuconfig
select Device Driver-> SCSI device support->SCSI device support (kernel) 
select Device Driver-> SCSI device support->legacy /proc/scsi/ support (kernel) 
select Device Driver-> SCSI device support->SCSI disk support (kernel) 

select Device Driver-> USB support ->USB device filesystem (kernel) 
select Device Driver-> USB support ->USB Mass Storage support (kernel) 

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

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

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

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

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

Target Software Installation

2008-06-13T13:08:04Z

JeanFrancoisR:

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

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=00:0E:32:00:00:01
autoload=no
...

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

Use the command '''saveenv''' to save the state of your environment variables in FLASH memory:
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors

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

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

BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.3
BIOS> setenv serverip 192.168.0.5
BIOS> saveenv

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

===Linux kernel building and installation===

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

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

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

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

'''!!! WARNING !! If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS) !!!'''
 
Check that transfered size value is less than 1572864 (0x180000 hex)
Bytes transferred = 1313216 (1409c0 hex)
----

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

----

* Flash kernel image with:
BIOS> run flash_kernel

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

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

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

* Flash RootFS image with:
BIOS> run flash_rootfs

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

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

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

===FPGA firmware installation===

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
BRAMTest led PS2 PS2_Opencore sram_test
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file. 
 
----
'''!!! Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!'''
----
 

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

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

* Flash your firmware image with:
BIOS> run flash_firmware

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

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

==Update U-Boot==

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

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

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

Target Software Installation

2008-06-01T19:04:16Z

JeanFrancoisR:

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

==Configure U-Boot==

===Environment variables===
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
The command '''printenv''' shows you most of them and their current value:
BIOS> printenv
bootcmd=run jffsboot
bootdelay=20
baudrate=115200
ethaddr=00:0E:32:00:00:01
autoload=no
...

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

Use the command '''saveenv''' to save the state of your environment variables in FLASH memory:
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors

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

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

BIOS> dhcp
dm9000 i/o: 0x15c00000, id: 0x90000a46
MAC: 00:0e:32:00:00:01
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.3
BIOS> setenv serverip 192.168.0.5
BIOS> saveenv

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

===Linux kernel installation===

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

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

'''!!! WARNING !! If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS) !!!'''
 
Check that transfered size value is less than 1572864 (0x180000 hex)
Bytes transferred = 1313216 (1409c0 hex)
----

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

----

* Flash kernel image with:
BIOS> run flash_kernel

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

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

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

* Flash RootFS image with:
BIOS> run flash_rootfs

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

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

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

===FPGA firmware installation===

The FPGA firmwares are all located in the ''firmware/'' directory of your Armadeus view:
[armadeus]$ ls firmware/
BRAMTest led PS2 PS2_Opencore sram_test
You can make some trials with the ''firmware/PS2/ps2_top.bit'' file. 
 
----
'''!!! Check that your bitfile size is smaller than the firmware partition size (256KB) before trying the following commands or you may corrupt your Linux kernel FLASH partition !!!'''
----
 

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

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

* Flash your firmware image with:
BIOS> run flash_firmware

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

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

==Update U-Boot==

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

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

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

User:JeanFrancoisR

2008-04-21T11:47:22Z

JeanFrancoisR:

Je pense que je suis le doyen de l'association : 55 ans.

Dans les années 1973 à 1978, je me suis occupé de conception éléctronique : ampli op, portes, bascules, registres et compteurs en DIL
(pensait t'on déjà aux FPGA ?)

Dans les années 1979 à 1981, je me suis occupé de développement de cartes à base de microprocesseur 6800 et de programmation en assembleur 6800
(les compilations sur disquettes 8" duraient plusieurs heures et on faisait attention au code que l'on écrivait).

Dans les années 1982 à 1989, je me suis occupé de développement divers en informatique industrielle.

Dans les années 1990 à 1995, je me suis occupé de développement matériel et logiciel dans l'environnement 68000, OS-9, VME
(avec beaucoup d'assembleur 68000).

Dans les années 1993 à 2006, j'étais informaticien indépendant, en informatique industrielle bien sur.
Vers la fin de cette période j'ai réalisé quelques développements avec Linux donc une application embarquée en µClinux sur proccesseur XScale.

Je m'occupe actuellement de développement Linux pour une startup parisienne (1 joour à Paris et 4 jours en télétravail)
mais pas dans le domaine embarqué :(

J'habite en Normandie où je suis membre de 2 LUG : EURIX et RotomaLUG.

User:JeanFrancoisR

2008-04-21T11:45:50Z

JeanFrancoisR: New page: Dans les années 1973 à 1978, je me suis occupé de conception éléctronique : ampli op, portes, bascules, registres et compteurs en DIL (pensait t'on déjà aux FPGA ?) Dans les année...

Dans les années 1973 à 1978, je me suis occupé de conception éléctronique : ampli op, portes, bascules, registres et compteurs en DIL
(pensait t'on déjà aux FPGA ?)

Dans les années 1979 à 1981, je me suis occupé de développement de cartes à base de microprocesseur 6800 et de programmation en assembleur 6800
(les compilations sur disquettes 8" duraient plusieurs heures et on faisait attention au code que l'on écrivait).

Dans les années 1982 à 1989, je me suis occupé de développement divers en informatique industrielle.

Dans les années 1990 à 1995, je me suis occupé de développement matériel et logiciel dans l'environnement 68000, OS-9, VME
(avec beaucoup d'assembleur 68000).

Dans les années 1993 à 2006, j'étais informaticien indépendant, en informatique industrielle bien sur.
Vers la fin de cette période j'ai réalisé quelques développements avec Linux donc une application embarquée en µClinux sur proccesseur XScale.

Je m'occupe actuellement de développement Linux pour une startup parisienne (1 joour à Paris et 4 jours en télétravail)
mais pas dans le domaine embarqué :(

J'habite en Normandie où je suis membre de 2 LUG : EURIX et RotomaLUG.

MemberList

2008-04-21T11:43:36Z

JeanFrancoisR:

==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 || 1 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|[[User:JeanBaptisteMa| Jean-Baptiste Maillet]] || 2 || 1 || 0 || 0 || system
|----------------
|[[User:JeanFrancoisR| Jean-François Rousval]] || 2 || 1 || 0 || 1 ||
|----------------
|}

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

[[Category:Association]]