Getting Started Installing the target software Step-by-Step install

Which files you will need depends on exactly what you are intending to do. The following sections build up the system in a number of stages, to the point where you will have a fully working system.

Fundamentals

There are a number of packages which must be installed first. These create the basic directory heirarchy, and a few tools which will be used at later stages of the installation:

stm-host-filesystem
stm-cross-sh4-filesystem
stm-sh4-filesystem
stm-host-distributionutils
stm-cross-sh4-distributionutils
stm-sh4-initscripts

The next packages which need to be installed are shared libraries, which will be needed by applications installed later:

stm-sh4-glibc
stm-sh4-libstdc++
stm-sh4-termcap
stm-sh4-ncurses-base
stm-sh4-libncurses

Fundamental to the operating of Linux is the device special files in /dev. These are created by installing the package:

stm-sh4-makedev

There are also some fundamental files which are needed on the target system:

stm-sh4-basefiles
stm-sh4-base-passwd
stm-sh4-netbase
stm-sh4-release

You also need to install the st40load tool. This package provides a way of downloading a Linux kernel to the target board through an ST Micro Connect interface adaptor.

stm-st40load

Minimal Installation

At this point you have to make a choise. If you want the smallest possible system, then only one more package is needed. This uses the busybox application to provide all the system utilities. This is very useful in system where the size of the filesystem is limited (for example a ROM or RAM filesystems). For more details on BusyBox see the projects home page.

For this you will need:

stm-sh4-busybox

If you later find that you need the full version of some applications, this is fine. You can install them as required, however you do have to give rpm the --force flag to ensure that any links to the busybox program will be overwritten for just those new applications. For example, the shell which is provided as part of busybox is lash, the 'lame' shell. When you're tight on memory this is ideal, but when running from an NFS mounted disk, space is not at the same premium, and so most people would choose to also install bash.

Full version

This installation uses the 'full' versions of various applications, and so has many more features, but takes more disk space and memory. In fact which programs are included here, and which are not, is largely a matter of preference, and what you will be doing with the target system. A minimal set would include:

stm-sh4-bash
stm-sh4-diff
stm-sh4-distributionutils
stm-sh4-e2fsprogs
stm-sh4-fileutils
stm-sh4-findutils
stm-sh4-grep
stm-sh4-mount
stm-sh4-sed
stm-sh4-shellutils
stm-sh4-sysvinit
stm-sh4-textutils
stm-sh4-util-linux

Additional packages can then be added as required to create a more 'comfortable' environment:

stm-sh4-bzip2
stm-sh4-file
stm-sh4-gawk
stm-sh4-gzip
stm-sh4-ifupdown
stm-sh4-less
stm-sh4-modutils
stm-sh4-net-tools
stm-sh4-netkit-ftp
stm-sh4-netkit-ping
stm-sh4-netkit-rsh-client
stm-sh4-netkit-telnet-client
stm-sh4-nvi
stm-sh4-procps
stm-sh4-psmisc
stm-sh4-sysklogd
stm-sh4-tar

As well as being able to connect from the target to other machines, it can also be very useful to connect into the target from outside over the network. To do this a few extra packages are needed:

stm-sh4-libwrap
stm-sh4-netkit-inetd
stm-sh4-netkit-rsh-server
stm-sh4-netkit-telnet-server
stm-sh4-tcpd
st40load

If you are using networking, it can also be useful to use the Network Information Services (NIS), formerly called Yellow Pages (YP). This allows hostnames, password and other details to be stored on a central server.

stm-sh4-portmap
stm-sh4-yp-tools
stm-sh4-ypbind-mt

Remember to create the file /etc/defaultdomain which contains your domain name.

Development version

If you want to develop pgrams which will run on the target, other packages can be added which include the headerfiles, libraries and development tools needed to build and debug application programs:

stm-cross-sh4-binutils
stm-cross-sh4-cpp
stm-cross-sh4-gcc
stm-sh4-kernel-headers
stm-sh4-glibc-dev
stm-sh4-gdb

Many of the shared library packages also have development versions available, which typically provide the apropriate haeder files, the generic shared libraries, and static versions of the libraries. These packages all have the -dev suffix.

If you want to be able to look at man pages on the target, a number of extra packages are needed:

stm-sh4-groff
stm-sh4-libdb3
stm-sh4-man-db
stm-sh4-man-pages

Installing the RPMs

Once you have downloaded the RPMs, you need to install them. Install them in the order described above, otherwise you may get some errors resulting from dependency failures.

Remember that the target RPMS are for an SH4, but they are being installed onto an x86 host, so you will need to give the --ignorearch option to RPM.

For the kernel LSP, you will need to install one LSP for each board you will be using. We are supplying the following LSPs:

You will also need to set your path to make sure the tools are accessible. If you are using a shell which is compatible with the Bourne shell (sh, ash, bash, ksh, zsh etc.):

PATH=/opt/STM/ST40Linux-1.0/devkit/sh4/bin:/opt/STM/st40load/bin:$PATH

Or if you are using a C shell style shell (csh, tcsh etc.):

path=(/opt/STM/ST40Linux-1.0/devkit/sh4/bin /opt/STM/st40load/bin $path)

You may want to put these commands into the appropriate start up scripts to avoid having to re-type them.