LynxOS Installation Guide

Installing LynxOS PowerPC Native Development Systems

Starting Installation

To install LynxOS onto a hard disk, it must first be booted from the ODE
CD-ROM.

Note: Some Force CPCi boards do not support bootable CD-ROMs. Users installing LynxOS natively onto these types of boards must boot either through the system's network or use the x-dev command.

After LynxOS is booted, the installit script must be executed by entering installit at the command prompt.

During the installation process, the installit script gathers information about the installation system hardware and software by presenting several menus for the user to respond to. The user may quit the installation at any time by selecting Q in any of the menus, or by typing Ctrl-C on the keyboard. However, if the installation is interrupted before successful completion, the user must re-enter the installit command and begin the installation again.

Installing a LynxOS PowerPC Native Development System

Caution! Any existing data on the installation partition is overwritten during installation. On PowerPC systems, LynxOS always uses partition a as the installation partition. Please back up important information before installation; see the LynxOS User's Guide for additional information on using tar to back up important data.

LynxOS supports more than one type of PowerPC processor. Each CPU / board has its own firmware prompt. The differences in the installation procedure for LynxOS are described in the board-specific sections of this chapter.

For locating information that details installation for a specific board, use the following table:

Installing on Specific Manufacturer Boards  

Manufacturer	Reference
Motorola PrPMC800 boards	See "Installing onto Motorola PrPMC800 Boards".
Motorola PrPMC600 boards	See "Installing onto Motorola PrPMC600".
Motorola MVME products	See "Installing onto Motorola MVME Boards".
Thales VMPCxx boards	See "Installing onto Thales VMPCxx Boards".
Motorola 8260 ADS boards	See the LynxOS Board Support Guide for MPC8260 ADS.
Motorola MPMC860 boards	See the LynxOS Board Support Guide for MPMC860
Force PowerCore boards	See the LynxOS Board Support Guide for Force PowerCore
Embedded Planet RPXLite823E boards	See the LynxOS Board Support Guide for RPXLite823E

Additional Boards may be supported. See the respective Board Support Guide for installation and configuration information.

Default Console

A PowerPC system needs either a VGA terminal connected to a video port or a terminal connected to the serial (COM1) port to serve as the console. By default, LynxOS performs an auto-detection test for the VGA terminal at boot time. If a VGA terminal is not found, the COM1 port becomes the console.

Note: The auto-detection test is valid only if the VGA chip is present and the keyboard is connected.

By default, the console type is "dumb" when it comes up. However, it can be set to the appropriate type using an export command or by modifying the /etc/ttys file.

For example, type the following to use the export command:

export TERM=vt100at

This assumes the user has a vt100 terminal. The user can also enter this command in the startup file.

To modify /etc/ttys for the same terminal type as the console, use a text editor to make the following changes:

# default for console

# /dev/con:0:default96:dumb:/bin/login

# change console to have no logins and set correct type

/dev/con:0:default96:vt100at:/bin/login

/dev/com1:0:default96:wyse50:/bin/login

/dev/com2:0:default96:wyse50:/bin/login

# enable logins on the VGA port

/dev/atc0:1:default:vt100at:/bin/login

Installing onto Motorola PrPMC800 Boards

The PrPMC800 processor board is a PMC card that connects to a PPMCBASE board, deriving its clock from the PPMCBASE board. The PrPMC800 board operates in Monarch or non-Monarch mode, depending on the PMC slot of the PPMCBASE board it is connected to.

When connected to the Monarch slot, the board can access the PCI bus and can be booted from the network, disk, flash or cPCI backplane. When connected to the non-Monarch slot, the board can only be booted from flash or a KDI download from the Monarch board.

This section contains the steps for installing and booting the PrPMC800 BSP. Before proceeding with the installation, the user must have a LynxOS cross development host system with which to create a bootable image.

Once the PrPMC800 card is booted with this image, a LynxOS image can be copied to disk, if there is one connected to the second PMC slot. The board can then boot directly from the disk.

Alternatively, a bootable disk can be created by copying the LynxOS image and BSP to any PReP partitioned disk, and connecting that disk to the base board.

Cross Development Kit Installation

Users do not need to build separate kernels or KDIs for Monarch and non-Monarch operations of the board. The BSP is source and binary compatible for either mode.

Installing the PrPMC800 BSP

Insert the PrPM800 BSP CD in the cross development system. Untar the LynxOS and PrPMC800 BSP images in the same directory where the cross development system is installed.

The example in the LynxOS Installation guide uses the directory /usr/lynx/<release_num>/<target>, where <release_num> is the release number of LynxOS, and <target> is the target processor of the host.

The following example provides command line installation instructions for a a Linux Cross development System:

# mount /dev/cdrom /cdrom

# cd /usr/lynx/4.0.0/ppc/

# gnutar -xvzpf  /cdrom/tar_images/<media_num>.devos.tar.gz

# gnutar -xvzpf  /cdrom/tar_images/<media_num>.bsp.pmc800_drm.tar.gz

This extracts the complete LynxOS environment and the BSP-specific files to the cross development directory.

Creating a Kernel downloadable Image (KDI)

Refer to the LynxOS User's Guide for instructions on how to create a Kernel Downloadable Image (KDI). No special steps are required for making KDIs for the PrPMC800 board.

The PrPMC800 board can boot the same KDI in both Monarch and
non-Monarch modes.

Booting the KDI using TFTP Boot

The following steps are for booting a LynxOS KDI using PrPMC800's
PPCBUG firmware:

Copy the KDI to default tftpboot location on the TFTP server machine. At the PPCBUG prompt of the PrPMC800 board, use the following command:

PPCBUG> nbo 0 0 172.17.3.15 172.17.3.14 pmc800.kdi

The CLUN and DLUN ( 0 0 ) above refer to the DEC ethernet controller on the PPMCBASE board. 172.17.3.15 is the IP address used for the PrPMC800 board. 172.17.3.14 is the IP address for the TFTP server.

Booting PrPMC800 in non-Monarch Mode from Flash

The following steps can be used to burn a KDI image on to the flash on PrPMC800 board and then use this image to boot the card in non-Monarch mode.

1. Put the PrPMC800 board in Monarch slot of the PPMCBASE board.

2. Type the following command:

PPCBUG > nbh 0 0 172.17.3.15 172.17.3.14 pmc800.kdi

PPCBUG> pflash 1F0000:<KDI_size> F0200000

(Do not to use the address range 0xF0000000 to 0xF0200000, because this is where the PPCBUG resides on PrPMC800. Also, this command line assumes that tftpboot dumps the KDI at address 0x1F0000. If this address is different, then supply the same in the above command line).

3. Remove the card from the Monarch slot and insert it in the non-Monarch slot.

4. Type the following command:

PPCBUG> g F0200020

(This boots the KDI in non-Monarch mode).

Uninstallation

To uninstall the build environment, delete the BSP directory.

Installing onto Motorola PrPMC600

Use the following instructions to install the PrPMC600 BSP.

Installing the PrPMC600 BSP

Insert the PrPM600 BSP CD in the cross development system. Untar the LynxOS and PrPMC600 BSP images in the same directory where the cross development system is installed.

The example in the LynxOS Installation guide uses the directory /usr/lynx/<release_num>/<target>, where <release_num> is the release number of LynxOS, and <target> is the target processor of the host.

The following example provides command line installation instructions for a Linux cross development system:

# mount /dev/cdrom /cdrom

# cd /usr/lynx/4.0.0/ppc/

# gnutar -xvzpf  /cdrom/tar_images/<media_num>.devos.tar.gz

# gnutar -xvzpf  /cdrom/tar_images/<media_num>.bsp.pmc600_drm.tar.gz

This extracts the complete LynxOS environment and the BSP-specific files to the cross development directory.

Creating a Kernel downloadable Image (KDI)

Refer to the LynxOS User's Guide for instructions on how to create a Kernel Downloadable Image. No special steps are required for making KDIs for the PrPMC600 board.

Booting the KDI using TFTP Boot

The following steps are for booting a LynxOS KDI using PrPMC600's
PPCBUG firmware:

Copy the KDI to default tftpboot location on the TFTP server machine. At the PPCBUG prompt of the PrPMC600 board, use the following command:

PPCBUG> nbo 0 0 172.17.3.15 172.17.3.14 pmc600.kdi

The CLUN and DLUN ( 0 0 ) above refer to the Pro100 ethernet controller on the PPMCBASE board. 172.17.3.15 is the IP address used for the PrPMC600 board. 172.17.3.14 is the IP address for the TFTP server.

Uninstallation

To uninstall the build environment, delete the BSP directory.

Installing onto Motorola MVME Boards

The real-time clock is disabled on new Motorola MVME boards. If the user has a new board, the real-time clock must be enabled before installing LynxOS.

To enable the Motorola real-time clock, use the following instructions:

1. Use the set command at the PPC1-Bug (firmware) prompt to set the time, enabling the clock (Note that the PPC1-Bug prompt reflects the MVME platform.):

PPC1-Bug> SET <MMDDYYhhmm>

2. Clear the BBRAM area by using the BF command at the PPC1-Bug prompt:

PPC1-Bug> BF FFFC0000 FFFC0040 0

Note: The user needs to enable the real-time clock only once on any given MVME board. However, the BBRAM area can get corrupted over time and should be cleared before installing LynxOS.

The following commands assume that the CDROM device is at SCSI ID 6:

3. Insert the CDROM and power up the computer.

4. Press the Break or Esc key to enable the PPC1-Bug monitor.

5. Enter the following command at the PPC1-Bug prompt:

pboot 0 60

where 0 is the CLUN and 60 is the DLUN.

If the CDROM device is at another SCSI ID, use the ioi command to determine the correct arguments for pboot. Consult the Motorola
PPC1-Bug documentation for more information.

Note: At this time, the preboot prompt is displayed on the console. For more information on the preboot command, see "Booting LynxOS" .

6. To boot LynxOS from a CD-ROM with SCSI ID 6, use the b command
   as follows:

Command? b s6

If the SCSI ID is not 6, change the root file system using the R command, and boot with the correct SCSI ID. For example:

Command? R 1 <SCSI_ID>

Command? b s<SCSI_ID>

In the example above, <SCSI_ID> is the SCSI ID of the CD-ROM.

7. After LynxOS boots, start the installation utility by entering the installit command at the root (#) prompt.

8. Navigate through the menus and change the settings to match the hardware configuration. Some screens have help topics that provide additional information about available options; refer to "Using installit" for more information.

9. The installed system must be rebooted. If the firmware is set to autoboot from the disk where LynxOS is installed, then the secondary installation starts. Otherwise, the user must use the appropriate boot command to boot from the disk.

For example, assuming that LynxOS is installed on the hard disk with SCSI ID 0 and partition b, the following commands should be used to reboot (note that the first command is a firmware command, and the second is a preboot command):

PPC1-Bug> pboot 0 0

Command? b s0b

Installing onto Thales VMPCxx Boards

The following commands assume that the CDROM device is at SCSI ID 6.

1. Insert the CDROM and power up the computer.

2. Press any key to stop autoboot and enter the firmware.

3. Boot VMPCxx from the CD-ROM as follows:

COMMAND> bop 60,c

If the CDROM device is at another SCSI ID, use this command:

COMMAND> bop <SCSI_ID>0, c

where <SCSI_ID> is the SCSI ID of the CD-ROM.

Note: At this time, the preboot prompt is displayed on the console. For more information on the preboot command, see "Booting LynxOS" .

4. To boot LynxOS from the CD-ROM, enter the following command:

COMMAND? b s6

If the SCSI ID is not 6, use the R command to set the root file system, and boot from the proper SCSI ID.

COMMAND? R 1 <SCSI_ID>

COMMAND? b s<SCSI_ID>

where <SCSI_ID> is the SCSI ID of the CD-ROM.

5. After LynxOS boots, start the installation utility by entering the command installit at the prompt.

6. Navigate through the menus and change the settings to match the hardware configuration. Some screens have help topics that provide additional information about the available options. See "Using installit" for further information.

7. The installed system must be rebooted. If the firmware is set to autoboot from the disk where LynxOS is installed, then the secondary installation starts. Otherwise, the user must use the appropriate boot command to boot from the disk.

For example, assuming that LynxOS is installed on a hard disk with SCSI ID 0 and partition b, the following commands are used. (Note that the first command is a firmware command, and the second is a preboot command.):

COMMAND> bop 0,c

Command? b s0b

Optional Software Installation

Additional components can be installed after the LynxOS ODE installation is complete. Some additional components include:

Additional Components  

CD-ROM	Application	Filename
Additional Components	Linux ABI Compatibility	<media_num>.linuxabi.tar.gz
	Additional Linux Libraries	<media_num>.linuxabi_advanced.tar.gz
	GNU Zebra Routing Package	<media_num>.zebra.tar.gz
	OpenSSL Encryption Components	<media_num>.openssl.tar.gz
ODE	Kernel Downloadable Images (KDI)s	<media_num>.kdi.tar.gz
	BSP demo Files	<media_num>.demo_<bsp_name>.tar.gz

To install any or all of these additional components on a UNIX-hosted system, use the following instructions:

1. Log into the system as root.

2. Mount the Additional Components CD-ROM.

# mount -o ro /dev/<cdrom> /mnt

where cdrom is the device node of the CD-ROM drive (ide.1, for example).

3. Change to the LynxOS root directory:

# cd /

4. From this directory, extract the tar file with the following command:

# gnutar -xvzpf /mnt/tar_images/<filename>

where <filename> is the name of the file.

Additional tools, such as LynxInsure++, TotalView, or SpyKer include separate documentation that describes their installation procedure.

LynuxWorks, Inc. 855 Branham Lane East San Jose, CA 95138 http://www.lynuxworks.com 1.800.255.5969