CERN TMS - Alpha Data System Setup

Introduction
============
This document gives information on setting up the CERN TMS System Controller
and Module Controller for development use. The System Controller boots
a cut down Linux Fedora 6 system. The System Controller provides a simple
Network Boot Linux system, based on fedora Core 6, for the Module Controllers.
The Module Controller will network boot from the System Controller.

System Controller
=================
The system controller has all of the software installed and should
be ready to use except for local network configuration.
Connect a monitor, keyboard and mouse to the system as well as network
and power leads and boot.

To connect the system to your local network plug in an Ethernet lead to the
first Ethernet port (the one closest to the keyboard connector). The system
is by default set to use DHCP to configure its network and has the MAC
address: 00:30:48:8C:6F:D2. If your DHCP server is setup to provide it with
an IP address and your local network info the system should, during boot,
configure itself correctly. If your DHCP server is not configured, you can
manually set the IP address using the menu item: Fedora/Administration/Network.
Configure the Address,SubnetMask and Gateway address for the "eth0" network
interface only.

There are two user logins configured on the system, the "root" user for admin
and the "tms" user for normal work:

User:		root
Password:	beam00

User:		tms
Password	beam00

Module Controller
=================
Install the Concurrent Technologies PP 41x/03x cPCI Controller into the
cPCI rack at the far left hand side.
Install the Concurrent Technologies AD PP5/002 cPCI Bus Transition Module
behind the Controller. The switches SW1,SW2,SW3 and SW4 should all be set
to on to enable	the back panel Ethernet ports.

Some BIOS settings need to be configured on the Controller board. To do this
use the Concurrent Technologies breakout lead connected to the front panel
of the PP 41x/03x cPCI Controller and connect a monitor and keyboard.
use the <F2> key to enter the BIOS Setup screen during boot.

Setup the following BIOS settings:
	1. Enable the "PXE Boot Firmware" to use the Read Eth0 A Ethernet
		port for boot in the "Advanced/PCI Configuration" screen.
	3. Setup BIOS to retry boot indefinitely. This is done using the
		"Auto-retry On Boot Fail" option in the "Boot Features" menu.
	4. Save the BIOS settings as user defaults.
	5. Save and exit the BIOS
	
Plug an Ethernet lead between the Bus Transition Module's Eth2 port and the
second Ethernet port on the System Controller (The one furthest away from the
keyboard connector). A network switch is not required.

Now the System controller has to be configured with the Ethernet MAC address
of the Module Controller. First find out the MAC address of the
Module Controller. Todo this, as root, run the command "tail /var/log/messages".
If the Module Controller is connected and attempting to boot you will see
messages such as: "DHCPDISCOVER from 00:30:48:8c:6f:d4 via eth0".
Alternatively read the MAC address from the Controller boards labels.

Now on the System Controller run the following commands as root,
substituting the Module Controller's MAC address as appropriate:

1. "cd /usr/tms/config"
2. "./tmsSetupModuleController 1 00:30:48:8c:6f:d4"

The Module Controller should now boot.

Using The Module Controller for Test/Development
================================================
You can now log into the System Controller as the user "tms".
From here you can log into the Module Controller using the command:
"telnet tmsmod1.tmsnet". Use the userid "root" to login, no password
is required.

The "/data" directory on the System Controller is exported using NFS and SAMBA
with read and write permissions.
You can access the /data directory from the Module Controller. I have installed
the ADMXRC SDK in here to assist you in checking out any ADMXRC2 boards.
The "/data" directory is exported under the Microsft Windows Workgroup "TMS"
and should be accessable from Microsft Windows systems on your network.
Use the userid "tms" and password "beam00" to access the /data directory.

Only the System Controller has a 'C' development system on it, so any code
needs to be compiled using this system. It has the ADMXRC libraries already
installed into the system places and so ADMXRC code should readily compile.
If all the code devlopment is done in the /data directory then it is
directly available to the Module Controller.

The Module Controller has the ADMXRC Linux driver installed, and we have
tested the environment here using an ADMXRC PMC module plugged directly into
the Module Controller card.