This section of the release notes contains information that will be placed in other documents at the next revision of those documents. The following information is provided here:
The bs save and bs restore commands (see Section 3.1)
Setting the bh skipMemClear flag from the opmode command (see Section 3.1)
This section contains all the information about the bs command that currently exists in the SSM/CSM Power-UP Monitor Guide, plus descriptions of the save and restore arguments.
The bs command loads the Level-B power-up monitor software or the Diagnostic Executive. The bs command also allows you to set boot flags and boot paths to boot automatically each time the system is powered up or reset.
Syntax:
bs [diagAuto [= {1,0}]] [diagPath [= bootstring]] [doDiags] [lvlBPath [= bootstring]] [lvlBTests [= bootstring]] [monAuto [= {1,0}]] [restore] [save]
Description:
ATTENTION The save and restore options in CSM software versions prior to V1.6.1 cannot write to filesystems created under DYNIX/ptx V4.2 or later.
Entering the bs command without any options at Level-A boots the Level-B software from the path designated in lvlBPath.
Entering the bs command and an option name without specifying a value displays the current setting of that option.
Defaults
These paths will differ from one system type to another:
---> print bs
bsbootSSM or CSM firmware or the Diagnostic Executive
lvlBPath=qd(0,1)ssw/fw/csm/lvlB
monAuto=0
diagPath=qd(0,1)ssw/diag/csm/exec
diagAuto=0
lvlBTests=qd(0,1)ssw/fw/csm
Examples
For SSM systems:
---> bs diagPath = wd(0,2)ssw/diag/exec
For S5000 systems:
---> bs diagPath = qd(0,2)ssw/diag/csm/exec
---> bs lvlBTests = qd(0,2)ssw/fw/csm
---> bs save
Save boot strings to fileqd(0,10)boot_str.....
For WS5000 systems:
---> bs diagPath= qd(0,1)ssw/diag/csm/exec
---> bs lvlBTests= qd(0,1)ssw/fw/csm
For any system:
---> bs monAuto= 1
Boot string data is saved in the file /usr/options/< product_name>/BOOTSTRING-INFO, where <product_name> can be ssm, csm, or qcic. You can look at the current values of the bs and bh boot strings by using the print command from the Level-B prompt.
---> print bh
ATTENTION On DYNIX/ptx systems, you can display and change bootstrings from the OS using the DYNIX/ptx bootflags command. For information, type man bootflags at the OS prompt.
During system software installation, the system displays the name of each product as it is installed and lists the path for the boot strings. If any of the boot strings do not match what is listed by the installation script, you must change them to match the output from the installation script. For example:
---> bh loaderPath=qd(0,2)ssw/boot
This section contains all the information about the opmode command that currently exists in the SSM/CSM Power-UP Monitor Guide plus a description of how to set the bh skipMemClear flag from the opmode command.
The opmode command applies to CSM-based systems only (S5000 and WS5000). The opmode command allows you to set various flags that control the flow of debugging information.
Syntax:
opmode[p | s | custom=< dd>]
Description:
ATTENTION You can set the opmode flags from DYNIX/ptx V4.2 or later using the bootflags command as shown in this example (from the OS, production is the same as p, service is the same as s). The CSM opmode command does not inform the OS. Therefore, using the OS bootflags command is recommended over the CSM command.
Flag Settings
Using the opmode p or opmode s command selects a default set of flag values, as shown in the following two tables. If you want to set the flags in some other configurations, you must use the opmode custom command.
The following flag values are set when you select the opmode p setting:
Flag |
Bits |
Description |
OPMODE_TEST_PUP |
0x01 |
Run hardware tests after a power cycle |
OPMODE_AUTODUMP_ SOMETIMES |
0x10 |
Dump memory only for non-hardware errors. Some panic types (such as DIRPE errors, AC or DC failures, lack of resources, multi-bit errors and fatal I/O board errors) do not produce useful dump information. The bootflag autoDump is set to 1, which means the OS decides whether or not to dump memory based on the type of panic. |
OPMODE_NO_ SHUTDOWN_INT |
0x40 |
What to debug on Model-F or Model-5 shutdown: 0 = debug hardware (INT, do scan dump) , 1 = debug software (NMI, do core dump) |
OPMODE_ SKIPMEMCLEAR |
0x80 |
Set the bh skipMemClear flag to 1 |
The following flag values are set when you select the opmode s setting:
Flag |
Bits |
Description |
OPMODE_TEST_ ALWAYS |
0x02 |
Run hardware tests whenever booting Level-B |
OPMODE_SBE_ REPORTING_HDM |
0x04 |
Always report HDM single-bit errors to the console |
OPMODE_SBE_ REPORTING_PROC |
0x08 |
Always report PROC single-bit errors to the console |
OPMODE_AUTODUMP_ ALWAYS |
0x20 |
Dump memory if any error occurs. The bootflag autoDump is set to 2, which means the OS forces a dump on any MMU fault, NMI error, or forced reset. |
OPMODE_NO_ SHUTDOWN_INT |
0x40 |
What to debug on Model-F or Model-5 shutdown: 0 = debug hardware (INT, do scan dump) 1 = debug software (NMI, do core dump) |
OPMODE_ SKIPMEMCLEAR |
0x80 |
Set the bh skipMemClear flag to 1 |
ATTENTION Flag settings are saved across reboots. In some cases, the software will turn off SBE (for example, certain HDM and Model-20 board failures). The software displays a warning message before changing the SBE reporting mode.
Setting Custom Flag Values
Each flag value is assigned a specific bit position in a 16-bit byte. Note that bits 9 through 16 are unused at this time.
Bit 8 (0x80) |
SKIPMEMCLEAR |
Bit 7 (0x40) |
NO_SHUTDOWN_INT |
Bit 6 (0x20) |
AUTO_DUMP_ALWAYS |
Bit 5 (0x10) |
AUTO_DUMP_SOMETIMES |
Bit 4 (0x08) |
SBE_REPORTING_PROC |
Bit 3 (0x04) |
SBE_REPORTING_HDM |
Bit 2 (0x02) |
TEST_ALWAYS |
Bit 1 (0x01) |
TEST_PUP |
To create a value for the opmode custom command, add the hex values for the bits you want to set and convert the result to decimal.
For example, if you want to select OPMODE_AUTODUMP_ALWAYS (0x20) and OPMODE_TEST_PUP (0x01), add the hex values (01 + 20 = 21 hex) and convert the result to decimal (21 hex = (2 x 16) + 1 = 33. So the decimal number to enter for the opmode custom command is 33 in this example.
Examples
---> opmode s# select servicemode
---> opmode custom=24# select flag bits 0x08
# (OPMODE_SBE_REPORTING_PROC) and
# 0x10 (OPMODE_AUTODUMP_SOMETIMES)
# 08 + 10 = 18 =
# (1 x 16) + 8 = 24
---> opmode custom=128# select flag bit 0x80
# (OPMODE_SKIPMEMCLEAR)
# 8 x 16 = 128
Defaults
opmode p default flag values are:
OPMODE_TEST_PUP= yes OPMODE_AUTODUMP_SOMETIMES= yes OPMODE_NO_SHUTDOWN_INT = yes OPMODE_SKIPMEMCLEAR = 1
opmode s default flag values are:
OPMODE_TEST_ALWAYS = yes OPMODE_SBE_REPORTING_HDM = yes OPMODE_SBE_REPORTING_PROC = yes OPMODE_AUTODUMP_ALWAYS = yes OPMODE_NO_SHUTDOWN_INT = yes OPMODE_SKIPMEMCLEAR = 1