This guide describes how to run the ChorusOSTM 4.0.1 product for the UltraSPARCTM-IIi processor family.
ChorusOS UltraSPARC-IIi specific information is provided in the following major sections:
"Development Environment", includes supported hosts, host operating systems and development systems.
"ChorusOS 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 for UltraSPARC-IIi Additional Man Pages, presents additional man pages for the extended BSP and the MONITOR and JVM features (these man pages are not available for on-line search using the man command).
Appendix B, ChorusOS 4.0.1 for UltraSPARC-IIi Product Packages, 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 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 Introduction for a complete description of the ChorusOS 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 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 (32-bit).
Sun WorkShopTM 5.0 native compiler.
In order for the CC compiler to work properly, all patches related to the CC compiler must have been installed on the Solaris system.
JDKTM 1.1.8, for the installation tool.
JDK 1.2, for the graphical configuration tool and for JavaTM applications.
This development environment component is bundled with the ChorusOS for UltraSPARC-IIi product:
Chorus Cross Development System 5.0, target UltraSPARC-IIi 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 for UltraSPARC-IIi product:
XRAY Debugger from Mentor Graphics, ELF format, version 4.4crd.
The following table shows the ChorusOS kernel and operating system optional features that are available for the UltraSPARC-IIi processor family. The availability status of a feature can be one of:
The feature is supported, and is configurable using 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 targets are described in this section from three different points of view:
This subsection describes the processors on which the ChorusOS 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 system for UltraSPARC-IIi supports the following processor:
UltraSPARC-IIi.
The ChorusOS system for UltraSPARC-IIi supports the following reference BSP:
cp1500 Reference BSP.
The cp1500 reference BSP supports the following board and system:
CP1500 -- Sun Microsystems.
Netra t1 Model 105 -- Sun Microsystems.
The cp1500 reference BSP supports the following on board devices:
Device Id |
ChorusOS Driver |
---|---|
/cpu |
sun:usparc-tick-timer |
/ric |
sun:usparc-ric-ric |
/sabre |
sun:usparc-sabre-pci |
/sabre/simba |
sun:(pci,ric)-simba-pci |
/sabre/simba/cheerio-ethernet |
sun:pci-cheerio-ether |
/sabre/simba/ebus (ebus bridge) |
sun:pci-ebus-(bus,isa) |
/sabre/simba/ebus/ns16550-1 (UART) |
sun:bus-ns16550-uart |
/sabre/simba/ebus/ns16550-2 (UART) |
sun:bus-ns16550-uart |
/sabre/simba-2 |
sun:(pci,ric)-simba-pci |
/sabre/simba-2/dec21150 (cPCI bridge) |
sun:pci-dec2115x-(bus,pci) |
/sabre/simba/ebus/28f008 (system flash) |
not supported |
/sabre/simba/ebus/28f016 (user flash) |
intel28F016SA |
/sabre/simba/ebus/led (ready LED) |
not supported |
/sabre/simba/ebus/7seg (7-seg LED) |
not supported |
/sabre/simba/ebus/wdtimer (watchdog) |
not supported |
/sabre/simba/ebus/tempsensor |
not supported |
/sabre/simba/ebus/kbd (keyboard) |
not supported |
/sabre/simba/ebus/mouse |
not supported |
/sabre/simba/ebus/lpt (parallel) |
not supported |
/sabre/simba/ebus/fdd (floppy) |
not supported |
/sabre/simba/ebus/ide |
not supported |
/sabre/simba/ebus/tod (time of day) |
sun:bus-m48txx-(nvram,rtc) |
/sabre/simba/ebus/nvram |
sun:bus-m48txx-(nvram,rtc) |
/sabre/simba/sym53c875 (SCSI) |
sun:pci-ncr53c8xx-scsi |
Reference target platforms are configurations to be used by customers covered by a Sun support contract.
CompactPCI Board
UltraSPARC-IIi (270-333 Mhz)
64-512 MB
256-1024 MB
Processor to PCI, PCI to PCI, PCI to cPCI, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, SCSI-3, Real-time clock, Timers, Flash memory (Intel 28F016SA)
OpenBoot 3.10.x
Rack-mounted System
UltraSPARC-IIi (360-440 Mhz)
64-512 MB
1-2 MB
Processor to PCI, PCI to PCI, PCI to ISA
Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet, SCSI-3, Real-time clock, Timers, Flash memory (Intel 28F016SA)
OpenBoot 3.10.x
This section describes the precise platform used to run the Sun QA tests:
SPARCengine Ultra CP1500: 5093-01 REV-51 / 333 Mhz / 128 MB.
Netra 1 model 105 One pack 360Mhz, 1 MB eCache, 64 MB.
UltraSPARC-IIi target systems do not boot archives directly, but instead
require the inetboot
application
to boot.
As a result, the boot procedure that follows differs from the procedure described in the ChorusOS 4.0 Installation Guide for Solaris Hosts, and requires that you use a boot server that reads local files instead of the NISTM database.
The following procedure assumes that the ChorusOS product has already been correctly installed on the host workstation. See the ChorusOS 4.0 Installation Guide for Solaris Hosts.
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.
For example:
Set the environment variable... |
To the family-specific product directory. The default value is... |
---|---|
DIR |
/opt/SUNWconn/SEW/4.0.1/chorus-usparc |
Make sure your PATH has been set correctly to include the directory install_dir/4.0.1/chorus-usparc/tools/host/bin, where the default install_dir is /opt/SUNWconn/SEW.
Also make sure that your PATH includes /usr/openwin/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/usparc \ $DIR/src/nucleus/bsp/usparc/cp1500 \ $DIR/src/iom |
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/tools \ -s $DIR/src/nucleus/bsp/drv \ $DIR/src/nucleus/bsp/usparc \ $DIR/src/nucleus/bsp/usparc/cp1500 \ $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.obp.
You can also make a smaller system image that includes only the operating system kernel:
$ make kernonly |
The target system and boot server must be on the same subnet.
See the ChorusOS 4.0 Installation Guide for Solaris Hosts for instructions on how to enable TFTP and RARP services on the boot server.
Become root on the boot server:
$ su Password: root_password # |
Copy the inetboot.sun4u file, install_dir/4.0.1/chorus-usparc/opt/unsupported/inetboot.sun4u to the /tftpboot directory.
By default, install_dir is /opt/SUNWconn/SEW.
Create a soft link from the inetboot.sun4u file to a file called /tftpboot/target_IP_address_in_hex. For example, the file for the target system with IP address 129.157.197.88 is called 819DC558, and is constructed as follows:
129 in decimal translates to 81 in hexadecimal.
157 in decimal translates to 9D in hexadecimal.
197 in decimal translates to C5 in hexadecimal.
88 in decimal translates to 58 in hexadecimal.
To create the soft link for the above example:
# ln -s /tftpboot/inetboot.sun4u 819DC558 |
Create a /tftpboot/export/root/target/platform/sun4u directory on the boot server.
Copy the system image, chorus.obp, to the directory you just created.
Edit /etc/bootparams to include the following, creating the file if it does not yet exist:
target root=boot_server:/tftpboot/export/root/target
Where target is the target system hostname and boot_server is the boot server hostname.
Edit /etc/hosts to include the following:
target_IP_address target
Where target_IP_address is the target IP address, such as 129.157.197.88, and target is the target system hostname.
Edit /etc/ethers to include the following:
target_Ethernet_address target
Where target_Ethernet_address is the target IP address such as 8:0:20:a7:d6:f3 and target is the target system hostname.
Add the following line to /etc/dfs/dfstab:
share -F nfs -o rw -d "ChorusOS boot" /export/home
Edit /etc/nsswitch.conf so that the hosts, ethers, and bootparams entries read files rather than NIS databases. For example:
# # /etc/nsswitch.nis: # # An example file that could be copied over to /etc/nsswitch.conf; it # uses NIS (YP) in conjunction with files. # # "hosts:" and "services:" in this file are used only if the # /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports. # the following two lines obviate the "+" entry in /etc/passwd and /etc/group. passwd: files nis group: files nis # consult /etc "files" only if nis is down. hosts: files [NOTFOUND=return] nis networks: nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc: nis [NOTFOUND=return] files ethers: files [NOTFOUND=return] nis netmasks: nis [NOTFOUND=return] files bootparams: files [NOTFOUND=return] nis publickey: nis [NOTFOUND=return] files netgroup: nis automount: files nis aliases: files nis # for efficient getservbyname() avoid nis services: files nis sendmailvars: files
Reboot the boot server.
Boot the target by entering the following in the target system console:
# ok boot net /platform/sun4u/chorus.obp |