Env - Set Environment; Configuring The 162Bug Parameters; Table 3-3. Env Command Parameters - Motorola MVME162P-344 Series Installation And Use Manual

Vme embedded controller
Hide thumbs Also See for MVME162P-344 Series:
Table of Contents

Advertisement

ENV - Set Environment

Use the ENV command to view and/or configure interactively all 162Bug
operational parameters that are kept in Non-Volatile RAM (NVRAM).
Refer to the Debugging Package for Motorola 68K CISC CPUs User's
Manual for a description of the use of ENV. Additional information on
registers in the MVME162P4 that affect these parameters appears in your
MVME1X2P4 VME Embedded Controller Programmer's Reference
Guide.
Listed and described below are the parameters that you can configure
using ENV. The default values shown are those that were in effect when
this document was published.
Note

Configuring the 162Bug Parameters

The parameters that can be configured using ENV are:
ENV Parameter and Options
Bug or System environment [B/S]
Field Service Menu Enable [Y/N]
Remote Start Method Switch
[G/M/B/N]
Probe System for Supported I/O
Controllers [Y/N]
Negate VMEbus SYSFAIL∗
Always [Y/N]
http://www.motorola.com/computer/literature
In the event of difficulty with the MVME162P4, you may wish
to use env;d <CR> to restore the factory defaults as a
troubleshooting aid (see Appendix B).

Table 3-3. ENV Command Parameters

Default
B
N
B
Y
N
Modifying the Environment
Meaning of Default
Bug mode
Do not display field service menu.
Use both methods [Global Control and Status
Register (GCSR) in the VMEchip2, and
Multiprocessor Control Register (MPCR) in
shared RAM] to pass and execute cross-loaded
programs.
Accesses will be made to the appropriate
system buses (e.g., VMEbus, local MPU bus)
to determine presence of supported controllers.
Negate VMEbus SYSFAIL∗ after successful
completion or entrance into the bug command
monitor.
3
3-11

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents