This guide describes how to run the ChorusOSTM 4.0 product for the PowerPC 60x/750 processor family.
ChorusOS 4.0 PowerPC 60x/750 specific information is provided in the following major sections:
"Development Environment", includes supported hosts, host operating systems and development systems.
"ChorusOS 4.0 Supported Features", includes kernel components and POSIX components.
"Utilities", includes host and target utilities.
"Reference Hardware", includes supported reference platforms, supported devices, and validated reference platforms.
Appendix A, ChorusOS 4.0 for PowerPC 60x/750 Product Packages and Part Numbers, details the list of Solaris packages in the product components, and the associated part numbers.
See the ChorusOS 4.0 Installation Guide for Solaris Hosts for a description of the installation process of the ChorusOS 4.0 product on a host workstation running the SolarisTM operating environment. This document also describes how to set up a boot server running the Solaris operating environment.
See the ChorusOS 4.0 Installation Guide for Windows NT Hosts for a description of the installation process of the ChorusOS 4.0 product on a host workstation running Windows NT 4.0.
See the ChorusOS 4.0 Introduction for a complete description of the ChorusOS 4.0 features.
The following table describes the typographic changes used in this book.
Table 1-1 Typographical Conventions
Typeface or Symbol |
Meaning |
Example |
---|---|---|
AaBbCc123 | The names of commands, files, and directories; on-screen computer output |
Edit your .login file. Use ls -a to list all files. machine_name% you have mail. |
AaBbCc123 | What you type, contrasted with on-screen computer output | machine_name% su Password: |
AaBbCc123 | Command-line placeholder: replace with a real name or value |
To delete a file, type rm filename. |
AaBbCc123 |
Book titles, new words or terms, or words to be emphasized. |
Read Chapter 6 in User's Guide. These are called class options. You must be root to do this. |
The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.
Table 1-2 Shell Prompts
Shell |
Prompt |
---|---|
C shell prompt | machine_name% |
C shell superuser prompt | machine_name# |
Bourne shell and Korn shell prompt | $ |
Bourne shell and Korn shell superuser prompt | # |
Fatbrain.com, an Internet professional bookstore, stocks selected product documentation from Sun Microsystems, Inc.
For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at http://www1.fatbrain.com/documentation/sun.
The docs.sun.comSM Web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. The URL is http://www.oracle.com/technetwork/indexes/documentation/index.html.
Sun Support Access offerings are available exclusively to members of the Sun Developer Connection Program. To get free membership in the Sun Developer Connection Program, go to http://www.sun.com/developers. For more information or to purchase Sun Support Access offerings, visit: http://www.sun.com/developers/support or contact the Sun Developer Connection Program office near you.
The ChorusOS 4.0 product provides a host-target development environment. Applications are developed on a workstation (the host), and then downloaded and executed on a specific board (the target).
A cross development system is needed to build the applications that execute on the target board (see Section "Utilities").
Prerequisites for the Solaris host reference configuration are the following:
Sun SPARCstationTM
Solaris 2.6, or Solaris 7
JDKTM 1.1.3 to 1.1.8, for the installation tool
JDK 1.2, for the graphical configuration tool
The Windows NT host reference configuration is as follows:
PC Windows NT 4.0 workstation or server, with Service Pack 5.
Solstice Network ClientTM SNC 3.1 is required as an NFS server for ChorusOS 4.0. Only NT FAT file system partitions are validated.
A Solaris system providing TFTP and RARP daemons in order to allow booting of the ChorusOS 4.0 product.
JDK 1.2, for the graphical configuration tool.
The serial line used for debugging with XRAY can only be used at 9600 bauds.
This development environment component is bundled with the ChorusOS 4.0 for PowerPC 60x/750 product:
Chorus Cross Development System 5.0, target PowerPC ELF
The Chorus Cross Development System is based on the Experimental GNU Compiler System egcs 1.1.2 and binutils 2.9.1 and additional patches.
This development environment component is bundled with the ChorusOS 4.0 for PowerPC 60x/750 product:
XRAY Debugger from Mentor Graphics, target PowerPC ELF version 4.4crb and additional patches.
The following table shows the ChorusOS kernel and operating system optional features that are available for the PowerPC 60x/750 processor family. The availability status of a feature, can be one of:
The feature is supported, and is configurable with the configurator(1CC) command, or with the ews GUI configuration tool.
Please refer to the note at the end of the table for information about specific conditions, or restrictions, for a given supported feature.
Some of the features (such as MSDOSFS, FLASH, FS_MAPPER, for example) require specific low-level drivers. These features operate only on platforms which provide these drivers.
The feature is not supported.
The ChorusOS operating system provides the elementary libraries indicated in the following list:
The following utilities may be run on the target ChorusOS operating system:
The following utilities may be run on the host machine:
ChorusOS 4.0 targets are described in this section from three different points of view:
This subsection describes the processors on which the ChorusOS 4.0 product can run as well as the details of the BSPs included in the delivery
This section describes all the target platforms which can be used as references in the context of Sun support contracts
This section describes the precise platforms used to run the Sun QA tests; this may be useful, in case of bugs, as a hint or guide to help in identifying issues which are closely hardware related.
The ChorusOS 4.0 system for PowerPC 60x/750 supports the following processors:
Motorola PowerPC 603[e/v]
Motorola PowerPC 604[e/v]
Motorola PowerPC 750
The ChorusOS 4.0 system for PowerPC 60x/750 supports the following reference BSPs:
The genesis2 reference BSP supports the following VME CPU boards (with additional MVME712 or MVME761 transition module - Motorola MCG), and ATX mother boards:
The genesis2 reference BSP supports the following on board devices:
The mcp750 reference BSP supports the following CompactPCI CPU board:
The mcp750 reference BSP supports the following on board devices:
Device Id |
ChorusOS Driver |
---|---|
/cpu (time base and decrementer) |
sun:powerpc-(tb,dec)-timer |
/flash (FLASH memory) |
not supported |
/raven (PCI bridge) |
sun:powerpc-raven-pci |
/raven/dec21140 (on board ethernet) |
sun:pci-dec21x4x-ether |
/raven/dec21154 (PCI-PCI bridge) |
sun:pci-dec2115x-pci |
/raven/vt82c586b (ISA bridge) |
sun:pci-vt82c586-(bus,isa) |
/raven/vt82c586b/m48t559 (RTC) |
sun:bus-m48txx-(nvram,rtc) |
/raven/vt82c586b/m48t559 (NVRAM) |
sun:bus-m48txx-(nvram,rtc) |
/raven/vt82c586b/fdd (floppy) |
not supported |
/raven/vt82c586b/kbd (keyboard) |
not supported |
/raven/vt82c586b/lpt (parallel) |
not supported |
/raven/vt82c586b/mouse (mouse) |
not supported |
/raven/vt82c586b/ns16550-1 (UART) |
sun:bus-ns16550-uart |
/raven/vt82c586b/ns16550-2 (UART) |
sun:bus-ns16550-uart |
/raven/vt82c586b/z85230-1 (UART) |
not supported |
/raven/vt82c586b/z85230-1 (HDLC) |
not supported |
/raven/vt82c586b/z85230-2 (UART) |
not supported |
/raven/vt82c586b/z85230-2 (HDLC) |
not supported |
/raven/vt82c586b-usb |
not supported |
/raven/vt82c586b-ide (IDE disk) |
not supported |
/raven/vt82c586b-ide (IDE other) |
not supported |
Reference target platforms are configurations to be used by customers covered by a Sun support contract.
VME Board
MPC603/604 (200-333 MHz)
16-64 MB
0-512 KB
Processor to PCI, PCI to VME, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, SCSI-2, Real-time clock, Timers
PPC1-Bug version 3.2/3.3
ATX Motherboard
MPC603e/604e (100-300 MHz)
16-32 MB
0-256 KB
Processor to PCI, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, SCSI-3, Real-time clock, Timers
PPC1-Bug version 3.3
VME Board
MPC750 (233-366 Mhz)
16-64 MB
1 MB
Processor to PCI, PCI to VME, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, SCSI-2, Real-time clock, Timers
PPC1-Bug version 3.3
CompactPCI System Board
MPC750 (233-366 Mhz)
32-64 MB
1 MB
Processor to PCI, PCI to cPCI, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, Real-time clock, Timers
PPC1-Bug version 3.7
This section describes the precise platforms used to run the Sun QA tests.
MVME2300/2600/3600: MVME2301, MVME2604-4331, MVME3604-5342A
MTX603/604: MTX 603-003A, MTX 604-003A
MVME2700: MVME2700-4351, MVME2700-4441
MCP750: MCP750-1232A-F
The procedures below concern PowerPC target systems such as genesis2 or mcp750 reference platforms.
The following procedure assumes that the ChorusOS 4.0 product has already been correctly installed on the host workstation. See the ChorusOS 4.0 Installation Guide for Solaris Hosts or the ChorusOS 4.0 Installation Guide for Windows NT Hosts for instructions.
Create and change to a build directory where you will build system images:
$ mkdir build_dir $ cd build_dir |
Set an environment variable to use with the configure(1CC) command as a shortcut to the base directory:
Set the environment variable... |
To the family-specific product directory. The default value is... |
---|---|
DIR |
/opt/SUNWconn/SEW/4.0/chorus-powerpc on a Solaris host |
DIR |
/c/cygnus/cygwin-b20/Chorus/opt/SUNWconn/SEW/4.0/chorus-powerpc on a Windows NT host |
Make sure your PATH has been set correctly to include the directory install_dir/4.0/chorus-powerpc/tools/host/bin where the default install_dir is /opt/SUNWconn/SEW.
If your host is running the Solaris operating environment, also make sure that your PATH includes /usr/openwin/bin, which contains the imake utility.
If your host is running Windows NT, also make sure that your PATH includes /usr/bin, which contains the imake utility.
Configure the build directory, using the configure(1CC) command:
If you are building from a binary distribution:
$ configure -b $DIR/kernel \ $DIR/os \ $DIR/tools \ -s $DIR/src/nucleus/bsp/drv \ $DIR/src/nucleus/bsp/powerpc \ $DIR/src/nucleus/bsp/powerpc/genesis2 \ $DIR/src/iom |
Depending on the target system architecture, you may need to enter $DIR/src/nucleus/bsp/powerpc/mcp750 instead of $DIR/src/nucleus/bsp/powerpc/genesis2 as the next to last argument.
The above command configures the build directory to include components installed during a "Default Install". It does not include optional components, such as the X library or code examples, that you may choose to install separately on Solaris host workstations. For example, in order to include everything in your build environment:
$ configure -b $DIR/kernel \ $DIR/os \ $DIR/opt/X11 \ $DIR/opt/jvm \ $DIR/tools \ -s $DIR/src/nucleus/bsp/drv \ $DIR/src/nucleus/bsp/powerpc \ $DIR/src/nucleus/bsp/powerpc/genesis2 \ $DIR/src/iom \ $DIR/src/opt/examples |
If you are building from the source distribution, see the ChorusOS 4.0 Production Guide.
As a result of configuration, build_dir now contains a Makefile, which is used to generate the build environment, and a Paths file, which specifies paths to files required by and created in the build environment.
Generate the build environment:
$ make |
Build a system image:
$ make chorus |
The resulting system image file is located in the build directory, build_dir and is called chorus.RAM.
You can also make a smaller system image that includes only the operating system kernel:
$ make kernonly |
The standard way to boot a system image built on a Windows NT host workstation is to copy the system image to a Solaris boot server and boot from the Solaris system. See the ChorusOS 4.0 Installation Guide for Solaris Hosts for instructions on how to configure the boot server.
Copy the system image to the boot server.
For example, on a Solaris host workstation:
$ rcp chorus.RAM boot_server:/tftpboot |
Or, on a Windows NT host workstation, using the Cygwin tools:
$ rcp -b chorus.RAM boot_server.user:/tftpboot |
The -b option causes rcp to transfer the system image as a binary file rather than an ASCII file, which is the default.
It is assumed that the user has access to perform this copy on the Solaris boot_server system and therefore that the user is the same on the Windows NT host and on the Solaris boot server .
Verify that everyone has at least read access to the system image on the boot server.
For example, on a Solaris host workstation:
$ rlogin boot_server Password: password_for_user $ ls -l /tftpboot/chorus.RAM -rwxr-xr-x 1 user group 1613824 Dec 15 17:33 chorus.RAM* |
As rlogin(1) is not available as part of the Cygwin tools, you should use the Windows NT Telnet
application to log in from the Windows NT host to the boot server. You can run Telnet
by selecting Start | Programs | Accessories | Telnet from the Start menu.
PPC1-Bug
FirmwareRestart the target system.
Change the network configuration of the target system through the target system console:
PPC1-Bug> niot Controller LUN =00? Device LUN =00? Node Control Memory Address =01F9E000? Client IP Address =129.157.196.64? <- target IP Server IP Address =129.157.196.1? <- boot server IP Subnet IP Address Mask =255.255.255.0? Broadcast IP Address =129.157.196.255? Gateway IP Address =0.0.0.0? Boot File Name ("NULL" for None) =chorus.RAM? <- file to load Argument File Name ("NULL" for None) =? Boot File Load Address =00400000? <- configured start Boot File Execution Address =00400000? <- addr of the system Bank Boot File Execution Delay =00000000? Boot File Length =00000000? Boot File Byte Offset =00000000? |
Disable PReP-Boot mode and then update NVRAM through the target system console:
PPC1-Bug> env ... Network PReP-Boot Mode Enable [Y/N] =N? <- must be turned off |
Load and boot the ChorusOS system image:
PPC1-Bug> nbo Network Booting from: DEC21140, Controller 0, Device 0 Device Name: /pci@80000000/pci1011,9@e,0:0,0 Loading: chorus.RAM Client IP Address = 129.157.173.193 Server IP Address = 129.157.196.1 Gateway IP Address = 0.0.0.0 Subnet IP Address Mask = 255.255.255.0 Boot File Name = chorus.RAM Argument File Name = Network Boot File load in progress... To abort hit <BREAK> Bytes Received =&1875968, Bytes Loaded =&1875968 Bytes/Second =&208440, Elapsed Time =9 Second(s) > ..... Booting Chorus ..... ChorusOS r4.0.0 for PowerPC - Motorola Genesis 2 family Copyright (c) 1999 Sun Microsystems, Inc. All rights reserved. Kernel modules : CORE SCHED_FIFO SEM MIPC IPC_L MEM_VM KDB TICK MON ENV ETIMER LOG LAPSAFE MUTEX EVENT MEM_DFPXM UI DATE PERF TIMEOUT LAPBIND DKI MEM: memory device 'sys_bank' vaddr 0xfaaf3000 size 0x1c9000 /cpu: sun:powerpc-(timebase,dec)-timer driver started /raven: sun:powerpc-raven-(bus,pci) driver started /raven/w83c553: sun:pci-w83c553-(bus,isa) driver started /raven/w83c553/i8254: sun:bus-i8254-timer driver started /raven/w83c553/m48t559: sun:bus-m48txx-(nvram,rtc) driver started /raven/w83c553/ns16550-2: sun:bus-ns16550-uart driver started /raven/w83c553-ide: sun:pci-w83c553-ide driver started /raven/dec-21140: 10BaseT (Twisted Pair) link auto-detected /raven/dec-21140: Ethernet address 08:00:3e:28:38:97 /raven/dec-21140: sun:pci-dec21x4x-ether driver started MEM: VM resource manager daemon starts MEM: PXM mapper daemon starts (site 0x1) MEM: PXM fs flush daemon starts IOM: SOFTINTR DISABLED (-31). Using an Interrupt thread IOM Init cluster space from: 0xfaacf000 to: 0xfaaef800 [65 items of size: 2048] IOM Init io-buf pool from: 0xfaaef850 to: 0xfaaefd70 [8 items of size: 164] IOM Init raw io-buffer pool from: 0xfaaefd70 to: 0xfaaf11f0 [32 items of size: 164] Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. max disk buffer space = 0x10000 /rd: sun:ram--disk driver started C_INIT: started C_INIT: /image/sys_bank mounted on /dev/bd01 C_INIT: found /image/sys_bank/sysadm.ini C_INIT: executing start-up file /image/sys_bank/sysadm.ini bpf: ifeth0 attached IOM: ifnet ifeth0 bound to device /raven/dec-21140 bpf: lo0 attached C_INIT: Internet Address: 129.157.173.193 C_INIT: RARP Network Initialization OK ifeth0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 129.157.173.193 netmask 0xffff0000 broadcast 129.157.255.255 ether 08:00:3e:28:38:97 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 C_INIT: rshd started |