Target Software Installation

2007-02-04T17:54:31Z

GregoireV:

===Flash memory partitions===
{| cellspacing=5 cellpadding=5 border=0 width=100%
|- style="background:black; color:white; font-size:16px"
! width="66%" | Address range !! type
|- align="center"
|0x10000000 - 0x10040000 ( 256KB )
| U-Boot
|- align="center"
|0x10040000 - 0x10060000 ( 128KB )
| U-Boot environment variables
|- align="center"
|0x10060000 - 0x100A0000 ( 256KB )
| FPGA bitfile
|- align="center"
|0x100A0000 - 0x10220000 ( 1.5MB )
| Linux kernel image
|- align="center"
|0x10220000 - 0x10800000 ( ~6 MB )
| Root filesystem
|}

==Configure U-Boot==

There is a set of variables you can customize to your needs.
The commande '''printenv''' show you most of them and their current state.
Use the command '''setenv''' to change one of these variable.
For instance:
setenv ipaddr 192.168.0.3
Use the command '''saveenv''' to save the state of your environment variables in flash memory.

In order to use network features with u-boot you have to set the network environment variables:
setenv netmask=255.255.255.0 (default value should be fine in most situations)
setenv ipaddr 192.168.0.3
setenv serverip=192.168.0.5 (the IP adresse of your tftp host server to download update files )
setenv rootpath "/tftpboot/root" (to boot linux over nfs)

You can use the '''dhcp''' command to configure these variable from your dhcp server. Probably you 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 with '''saveenv''' to have them available at power up. In case of troubleshoots you can use the script '''run flash_reset_env''' to reset the variables to the factory settings.

===Linux kernel installation===

First check your kernel size is smaller than the armadeus kernel partiiton (ex 1MB) How ??????????????????????????
Load kernel image with u-boot through network:
BIOS> tftpboot 08000000 pathtoyourhostedbuildrootdir/linux-kernel-2.6.12-arm.bin
or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/linux-kernel-2.6.12-arm.bin
the you can type the c command to reconnect to the terminal

Flash kernel image with:
BIOS> run flash_kernel
<span style="color:red">
!!! WARNING!! If the new kernel is too large, this operation can destroy data that is stored behind the kernel (e.g. rootfs) !!!
</span>
Check that Bytes transferred = 1040676 (fe124 hex) value is less than 0xfffff ????????????????????????,

===Linux rootfs installation===
Load rootfs image with u-boot through network:
BIOS> tftpboot 08000000 pathtoyourhostedbuildrootdir/rootfs.arm_nofpu.jffs2
or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
send pathtoyourhostedbuildrootdir/rootfs.arm_nofpu.jffs2
the 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

===FPGA firmware installation===

The FPGA firmwares are in the armadeus/software/firmware tree
You can make some trials with the armadeus/software/firmware/ps2/ps2_top.bin file
!!! check your file size is smaller than the firmware partition size (AKA 256KB)

Load FPGA firmware image file with u-boot through network:
BIOS> tftpboot 08000000 pathtoyourhostedfirmwaredir/fpgafirmware.bin
or serial line:
BIOS> loadb 08000000
Ctrl+Altgr+\+c to access kermit command line then...
C-Kermit> send pathtoyourhostedfirmwaredir/fpgafirmware.bin
then you can type the c command to reconnect to the terminal

Flash 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 tftpboot server:
tftpboot 08000000 /tftpboot_path_to_buildroot/u-boot.bin
With ethernet and a nfs server:
nfs 08000000 host_ip_addr:/nfs_path_to_buildroot/u-boot.bin
With the kermit and a serial line
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:
run flash_uboot

advanced information can be found at the [[BootLoader]] wiki page.

Communicate with your board from a Linux Host (Basics)

2007-02-04T16:57:50Z

GregoireV:

==RS232 configuration==
We suggest you to use Kermit as Terminal emulator for RS232 connection. Minicom was sadly reported to have problems when communicating with U-Boot.

===Kermit installation===
* On Ubuntu:
apt-get install ckermit
or use Synaptic graphical package manager.

* On Fedora:
rpm -q ckermit

===Kermit configuration===
* Edit/Create .kermrc file in your $HOME directory and put it in:
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
* In this example, we assume that your serial port is ttyS0 (first serial port). Change this to correct value if necessary.
* If you use an USB<->Serial converter then serial port would surely be named like that: ttyUSB0
* If you get an error message such
$ kermit -c
/dev/ttyS0
?SET SPEED has no effect without prior SET LINE
check that you have read/write rights on /dev/ttyS0 (btw. your serial port)

===Kermit usage===
* To launch it:
$ kermit -c
* To switch from terminal mode to command mode:
CTRL + \ + c
* To switch from command mode to terminal mode:
C-Kermit>c

==TFTP server==
In order to send your image files (U-Boot, Linux zImage, rootfs ...) with higher speed to the armadeus board, you can use a tftp server.
Once the server started, the files located in the server shared directory (/tftpboot by default) will be accessible from the U-Boot TFTP client.

===TFTP server installation===
* On Ubuntu:
# apt-get install tftpd
or use Synaptic<br>
* On Fedora:
# rpm -q tftpd

Then create the directory that will contain all the files that the server will export (you have to be root to do that):
# mkdir /tftpboot
# chmod 777 /tftpboot

===Server configuration===
Edit 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:
# killall -HUP xinetd

==Links==
* [http://www.columbia.edu/kermit/ Kermit Homepage]
*

ArmadeusWiki - User contributions [en]

Target Software Installation

Communicate with your board from a Linux Host (Basics)