Guidelines for sett ing up the Tribbox

Transcription

1 Guidelines for sett ing up the Tribbox What is needed: Linux distribution ( recommended is Fedora Core 6 for x86 ) Serial adaptercable ( Kabel.pdf ) Tribbox Network SATA Harddisk ( for Tribbox, if needed ) For setting up access to the Tribbox over the host computer, the manual on t he following url can be used. Important subjects that are definitely needed are described below. - Installation Guide - Get ting Start ed Guide ( Setting up the NFS server ) - How To Guide You should aim to, apart from the system supplied with your Tribbox, also use the system from ST-linux. Please set up your host system st ep-by-st ep according to t he manual mentioned above. This is why it is also recommended to use the Linux distribution Fedora Core 6for x86 as a host system. It is however also possible to use other distributions, if the Linux system for the Tribbox should just be started from this distribution over NFS. Cross-compiling of software is not directly possible without further prior actions (by configuring the dist ribution accordingly, cross-compiling can of cours e be done.) The manual for setting up a cross-compiler can be found on the website mentioned above: Important software packages that must be installed in your distribution are Minicom, the TFTP-server and the NFS-server. Please consult the documentation of the distribution that you are using, on how to install these servers and applications. For M inicom the following parameters should be set: Device /dev/ttys0 Hardware flowcontrol no Software flowcontrol no Speed

2 When Minicom is properly set up and started, you will get the following output when you switch on the Tribbox. Press a key on the keyboard right after switching on the Tribbox, to interrupt the autoboot and to enter the u-boot shell.

3 Once in the u-boot shell, you can use "help" for the helpfunct ion. With "print" all the variables are shown that are currently set in u-boot. To change the u-boot variables to your own needs, please consult the documentations that are supplied with the precompiled kernels of the Tribbox, or read the u-boot chapter in the beforementioned manual. In most cases there should be a kernel as well as a ramdisk installed in the flash-rom of the Tribbox. Optionally, a userfs can be installed additionally. To use the possibility to update the flash-rom yourself with a new kernel, ramdisk or a new userfs, the TFTP-server or the NFSserver is needed. Installing the NFS-server is recommended in any case, b ecause it enables using the target system over NFS on the Tribbox. The advantage is that you have direct access to the files over the host computer. All the configurations shown here in the pictures are taken from the Linux distribution Fedora Core 6, and can vary with other distributions. Please consult the forums of these distributions for information on the configuration of these programs. The configuration of the NFS-server is done through the file /etc/export s. The first part of the line should contain the path to the directory where the NFS-server points to. The second part of the line holds the options for the server. Below is a screenshot of how the file could look like.

4 As can be seen in the first picture, the NF S-s erver is mount ed on the direct ory /mnt /dis k1/sh4- target - or rather points to it. In the second picture we check if the server is running correctly. If it is, then in KDE a direct ory with a plug will be shown (not e the red arrow). For the installation of the TFTP-server, only t he following needs t o be done after installing the software package. In the root directory the directory /tftpboot should be created. In this directory, the kernel and/or the ramdisk can be put, in order to have these loaded into the right

5 place in the file system, by the TFTP-server. If both servers are running correctly, then t his can be checked in the U-Boot shell. For the TFTP-server this can be checked in the following way: Enter the following line in the U-Boot shell (uimage_bw is the filename of the used kernel, in this example) : tftpboot uimage_bw If at this stage problems arise with the network, causing the server not to be loaded then in most cases either the firewall settings are the problem, or the way Selinux has been configured. With a ping to the IP address of the Tribbox or from the Tribbox to the IP address of the host computer, you can check if the hardware network functionality is working. This way faulty network settings of your configuration can be ruled out. In this second screenshot it is shown how the U-Boot shell should look with the NFS-server. The command for loading the kernel from NFS should be entered as follows: nfs :/mnt/disk1/sh4-t arget/uimage_bw

6 Now the host system is configured in the way, that the T ribbox can be st artet. Let 's now show how to configure/install a target system (s h4) to work on the Tribbox over NFS. Even when you only want to use the supplied SH4 target syst em from t he DVD, we recommend the installation of STLinux in version 2.2. This is very helpful to learn about the whole system and the relations. From that point, other varieties can be tried. The ISO of the STLinux 2.2 inst allation CD can be downloaded at the following url: ft p://ft p. stlinux.com/pub/stlinux/2.2/iso For the installation in your host system. please use the script ins tall on this CD. If all files are installed without problems, then the ST -Linux SH4 t arget system will be installed in the following path: /opt/stm/stlinux-2.2/devkit/sh4/target There are now two ways to configure the host system, to be able to load the SH4 target system through NFS. The first way would be to change the file /etc/exports. This would then show like this: "/opt/stm/stlinux-2.2/devkit/sh4/target *(rw,no_root _squash,async)" The second way would be to copy the files to the place where the directory of the NFS-server point to, in the example above. In our example this would be /mnt/disk1/sh4-target. Please decide for yourself which way to choose. Pleas e note however that the variables in U- Boot should also be changed. In the current case the files were copied to /mnt/disk1/sh4-target kopiert. This offers us the opportunity of using different target systems for the SH4, just by renaming the directories. Following this example, t he installation of the SH4 target system is now described, that is supplied on the DVD.

7 First we rename the current directory in /mnt/disk1 from sh4-target in sh4-target -stl. Then we create a new directory sh4-target in /mnt/disk1. Now we copy the right archives from the target-system directory on the DVD to the newly created directory sh4-target. Now we unpack the files in this irectory with the following command. Please do not create further subdirectories in which you want to unpack the files. "tar zxvf...name tar.gz Archiv..." oder "t ar jxvf...name tar.bz2 Archiv..." Now it is possible to switch between the two target systems, when the directory is correctly renamed and the files are in the path of the NFS-server.