Difference between revisions of "Target Software Installation"

Revision as of 00:07, 7 December 2008

Flash memory partitions (APF9328)

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=
autoload=no
...

Use the command setenv to change these variables. For example, to set the IP address:

BIOS> setenv ipaddr 192.168.0.10

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.10 
BIOS> setenv serverip 192.168.0.2 (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.10
BIOS> setenv serverip 192.168.0.2
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:

On your host:
[armadeus]$ make linux26-menuconfig (previously linux-menuconfig)

• save your configuration and then rebuild your kernel image:

[armadeus]$ make linux26 (previously make linux)

• check that your Armadeus kernel image size is smaller than the U-Boot partition (2MB with Armadeus 3):

[armadeus]$ ls -al buildroot/binaries/apf9328/
...
[armadeus]$ cp buildroot/binaries/armadeus/apf9328-linux.bin /tftpboot/

• Load kernel image with U-Boot through network:

   BIOS> tftpboot 08000000 apf9328-linux.bin

or with the serial line:

   BIOS> loadb 08000000
   Ctrl+Altgr+\+c to access kermit command line then...
   send pathtoyourhostedbuildrootdir/apf9328-linux.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 2097152 (0x200000 hex) with armadeus 3

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, you can use automatic scripts. So next time you will only launch:

BIOS> run update_kernel

• If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM:

BIOS> setenv bootargs ${console} ${mtdparts}; run addjffsargs addipargs; bootm

(the kernel image you want to try must have been loaded at 0x08000000)

Linux RootFS installation

• check that your Armadeus RootFS image size is smaller than the RootFS partition :

[armadeus]$ ls -al buildroot/binaries/apf9328/
...
[armadeus]$ cp buildroot/binaries/paf9328/apf9328-rootfs.arm.jffs2 /tftpboot/

• Load RootFS image with U-Boot through network:

   BIOS> tftpboot 08000000 apf9328-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, you can use automatic scripts. So next time you will only launch:

BIOS> run update_rootfs

FPGA firmware installation

The FPGA firmwares are all located in the firmware/ directory of your Armadeus view:

[armadeus]$ ls firmware/
apf_pkg  BRAMTest  bus_led  led  PS2  PS2_Opencore  servo  sram_test  wishbone_example  Xtools

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 apf9328-u-boot.bin

With Ethernet and a NFS server:

BIOS> nfs 08000000 host_ip_addr:/nfs_path_to_buildroot/apf9328-u-boot.bin

With the kermit and a serial line

BIOS> loadb 08000000
   <CTRL><ALT GR>\
   c
   send path_to_buildroot/apf9328-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.