hpost(1M)

NAME | SYNOPSIS | CAUTION | DESCRIPTION | OPTIONS | USAGE | FILES | ENVIRONMENT VARIABLES | DIAGNOSTICS | SEE ALSO

NAME

hpost- control and sequence POST through JTAG

SYNOPSIS

hpost [-?| -h] [ -?postrc| -?blacklist| -?level| -?verbose]
hpost [-aCcfnqs] [-D [boardmask,][path]] [-D "comment"] [-excode] [-g[path| none]] [-Hboardmask,refproc] [-i[proc]] [-Jbus_mask] [-JJbus_mask] [-llevel] [-pproc] [-Qproc[,skipmask]] [-R{redlist_file| none} ] [-vlevel] [-X{blacklist_file| none} ] [-W[c]] [-Zproc]

CAUTION

This command is for use by your service provider only. Improper use can cause catastrophic operating system failure.

DESCRIPTION

The POST (power-on-self-test) program probes and tests the components of uninitialized Sun Enterprise 10000 hardware, configures what it deems worthwhile into a coherent initialized system, and hands it off to OBP (OpenBoot PROM). hpost is the SSP-resident executable program that controls and sequences the operations of POST through the IEEE 1149.1 JTAG scan interface between the Sun Enterprise 10000 domain and the SSP.

Unless -n is the first argument on the hpost command line, hpost reads an optional file, .postrc, and executes the directives in that file before it begins operation with the host (see postrc(4)). hpost first looks for .postrc in the current directory (.). If it does not find it there, hpost looks in $SSPVAR/etc/platform_name/$SUNW_HOSTNAME. If it does not find .postrc there, it looks in the user's home directory, $HOME. Exception: If the current directory is $HOME, the first element of the search path (.) is skipped. If hpost does not find .postrc it proceeds without it.

The following command provides a terse listing of .postrc file syntax and directives:

hpost ?postrc

OPTIONS

The following information pertains to the hpost options:

• Numerical option arguments are generally assumed to be decimal, but may be given as hex if preceded by x or 0x. Exception: arguments identified as a mask are assumed hex.

• board is a system board number in the range 0 to 15, inclusive.

• proc is a processor number in the range 0 to 63, inclusive, that corresponds to the physical location as (board * 4 + processor_module #).

• Hyphenated flags and their arguments are not separated by a space.

• The question mark that precedes the first group of options can be replaced by the letter h. For example, -?postrc = -hpostrc.

-?

Display a terse description of arguments.

-h

An alias for the -? option.

-?postrc

Display a terse description of the .postrc file.

-?blacklist

Display a terse description of blacklist(4) / redlist(4) file syntax.

-?level

Display a terse description of level number meanings.

-?verbose

Display a terse description of verbose number meanings.

-a

Run POST at the alternate diagnostic level. -a is intended as a convenience to be used during certain error reboot scenarios where you want to run POST at a higher-than-normal diagnostic level. If you provide a value for alt_level in the .postrc file, -a attempts to use it as the alternate diagnostic level. If you do not provide a value for alt_level in .postrc, -a attempts to use its default value, which is higher than the diagnostic level used by default when -a is not specified. However, -a never causes the diagnostic level to be lower than it would be if -a is not specified.

You cannot use -a and -l at the same time. See also -l and postrc(4).

-C

Do the initial configuration of the centerplane. If -C is not invoked, hpost assumes that one or more other domains in the same physical platform have already been configured and are running. hpost probes the centerplane to determine the bus configuration, the only configuration it considers. If hpost cannot determine a valid configuration from this probe, it immediately fails.

If -C is invoked, hpost assumes nothing else is running on this platform, and tests and configures the system, including the centerplane, in the bus configuration with the highest figure of merit in the domain in which it is run.

-c

Parse (as hpost normally does) the .postrc, blacklist(4) and redlist(4) files, reporting any syntax errors, then immediately exit. See postrc(4), blacklist(4) and redlist(4).

-D[boardmask,] [path]

Invoke a special mode of POST that scans out state from the host, dumps it to a binary file, then immediately exits. If path is not specified, a default path is used. (The comma after boardmask is always required.) hpost cannot examine the dump files, but your service provider and Sun Microsystems can.

If specified, boardmask is a 20-bit mask of the parts of the machine to be included in the dump. Bits 0 through 15 correspond to the system boards, bits 16 and 17 to the two half-centerplanes, and bits 18 and 19 to the two control boards. If boardmask is not specified, hpost assumes its value is FFFFF and includes all parts of the system in the dump. However, hpost then applies a heuristic decision algorithm to recognize system boards that are not present or powered off, and it does not include these boards in the dump file. No such editing is done if a boardmask is specified.

If -D is specified and the standard input of hpost is a terminal, hpost prompts for a one-line comment to be embedded in the file. If you simply press Return, the comment line is empty. If you also specify -d, the prompt for a comment is suppressed. See -d.

-d "comment"

Insert the specified comment into the dump file. A space must separate this option from its argument. Quotes are not necessary for a single-word comment. The comment is inserted regardless of the standard input means (terminal, script, and so forth). See -D.

-excode

Print a one-line description of a POST exit code to standard output.

-g [path | none]

Create a screen log file. See the FILES section for the default name of this file. The path is either a directory in which the default log file is to be generated or an explicit path and file name. The none option suppresses the creation of the screen log file, if the log file is invoked in the .postrc file.

-Hboardmask,refproc

Run a special mode of POST that prepares one or more boards to be DR Attached to a running domain. boardmask is a 16-bit mask of the boards on which POST is to run. refproc is the current master CPU of the target domain, which must be on a different board.

Caution: Do not specify -H on the command line; it should be invoked only by another program as one step in the DR process. See dr(1M).

-i[proc]

Execute in interactive mode. This option is used for debugging. If proc (a single processor number) is specified, only that processor is used and hpost begins an interactive session. If proc is not specified, all processors are used and hpost begins a simpler interactive session, just stopping before each phase of debug to ask whether it should execute that phase or continue to the next.

-Jbus_mask

Use the specified bus configuration rather than selecting the configuration based on testing. This support mode of POST, for use only by Sun Microsystems, interprets bus_mask as a 6-bit binary mask for the desired bus configuration. The 2 most-significant bits are the data buses, the 4 least-significant bits are the address buses. 3F tells hpost to use all buses.

-JJbus_mask

This option is similar to -J, but does only the JTAG initialization.

-llevel

Set the diagnostic level for this run of POST. Acceptable values are in the range 7 to 127, inclusive; the default level is 16. -?level displays a brief summary.

-n

Inhibit reading of the .postrc file. If present, this argument must appear first.

-pproc

Use the specified processor as the preferred boot processor. This request is ignored if the specified processor is not in the final configuration.

-Qproc [,skipmask]

(Quick POST) Make POST read configuration information from bootbus SRAM in the indicated processor, then reconfigure, with minimum testing, the system described. This option is intended for quick recovery from software crashes. It is considered to have failed if the specified configuration cannot be effected.

The skipmask option enables the caller (usually another program) to skip certain steps in the initialization process that it determines are unnecessary. The goal is an even faster recovery. The bits in skipmask have the following meaning:

0 - Perform all phases of the reconfiguration (the default)

0x0001 - Do not clear processor IMU tags and do not disable the IMU

0x0002 - Do not clear processor DMU tags and do not disable the DMU

0x0004 - Do not clear processor instruction caches

0x0008 - Do not clear processor data caches

0x0010 - Do not clear processor external caches

0x0020 - Do not clear CIC duplicate tags (DTAGs)

0x0040 - Do not initialize I/O controllers

0x0080 - Do not clear memory

-q

Quiet mode. All screen output is discarded.

-R {redlist_file | none}

Use the specified redlist file, or no redlist file (none), rather than the default redlist file. See the Caution at the end of this section..

-s

Divert all screen output to syslog with appropriate priorities.

-vlevel

Set the message verbosity level. Acceptable values are in the range 0 to 255, inclusive; the default is 20. -?verbose displays a brief summary.

-X {blacklist_file | none}

Do not use the default path. none suppresses use of any blacklist(4) file. See the Caution at the end of this section.

-W [c]

Clear any Recordstop state that may be present in the current domain, and attempt to re-enable centerplane ASIC recording. If an Arbstop or other fatal error condition is detected in this domain, it is reported and the Recordstop clear attempt is abandoned. The result of this operation is reported in the hpost exit code.

If a Recordstop condition exists in a different domain the attempt to re-enable centerplane recording will fail. The failure will be reported, but will not cause this -W operation to be considered failed.

Use the optional c flag with -W for a domain that is part of an InterDomain Network (IDN). Invoke -Wc for one and only one domain of the IDN; hpost clears Recordstop in that domain and all other domains in the IDN.

This mode of hpost is normally invoked by an SSP event detection daemon after it creates a state dumpfile. See the -D option.

-Zproc

(Zip POST) Make POST read configuration information from bootbus SRAM in the indicated processor, and perform only the JTAG initialization of the system to effect the configuration described. This option is intended to allow dumps of the software state after a crash; this state would be destroyed by the normal POST configuration process. hpost -Z is considered to have failed if the specified configuration cannot be effected.

Caution: Be careful when using -R or -X in a production system; other SSP software will not know that a nonstandard blacklist(4) or redlist(4) file is in use by POST.

USAGE

POST is normally executed by supervisory scripts or programs on the SSP, but can be invoked from the command line in engineering development, manufacturing, or field service applications.

FILES

The following files are supported:

./.postrc

Local POST configuration file

$HOME/.postrc

User's default POST configuration file

$SSPVAR/etc/platform_name/$SUNW_HOSTNAME/.postrc

Hostname-specific default POST configuration file

$SSPVAR/etc/platform_name/blacklist

Default blacklist file (see -X)

$SSPVAR/etc/platform_name/redlist

Default redlist file (see -R)

$SSPVAR/adm/$SUNW_HOSTNAME/post/postmmdd.hhmm.log

Default log file (see -g)

$SSPVAR/adm/$SUNW_HOSTNAME/xfstatemmdd.hhmm.ss

Default dump file (see -D)

$SSPVAR/adm/$SUNW_HOSTNAME/hpost.lock

POST lock file

$SSPOPT/release/Ultra-Enterprise-10000/*/*/*/hostobjs/*.elf

Path to download (host-resident) POST executable files

ENVIRONMENT VARIABLES

The environment variable SUNW_HOSTNAME must be set to the name of the domain.

DIAGNOSTICS

An exit status in the range 0 to 63, inclusive, indicates successful configuration. The exact value is the number of the processor whose bootbus SRAM contains the POST-to-OBP handoff structures that describe the configuration. Values outside the range 0 to 63 indicate that the system was not configured. (Those values outside the range have been codified for use by Sun Microsystems, and the information is described in a restricted-use header file. However, the -e option will provide a description of any value.)

SEE ALSO

obp_helper(1M), redx(1M), blacklist(4), postrc(4), redlist(4)

SSP 3.5  Last Revised 11 July 2000

NAME | SYNOPSIS | CAUTION | DESCRIPTION | OPTIONS | USAGE | FILES | ENVIRONMENT VARIABLES | DIAGNOSTICS | SEE ALSO