Set Environment to Bug/Operating System
A-3
A
Modification is possible through use of the commandÕs M option.
At the end of the modification session, you are prompted for the
update to Non-Volatile RAM (NVRAM). A Y response must be
made for the update to occur; any other response terminates the
update (disregards all changes). The update also recalculates the
checksum.
Be cautious when modifying parameters. Some of these parameters
are set up by the factory, and correct board operation relies upon
these parameters.
Once modification/update is complete, you can display the current
contents as described earlier.
Set Environment to Bug/Operating System
ENV [;[D]]
The ENV command allows you to interactively view/configure all
Bug operational parameters that are kept in battery-backed-up
RAM (BBRAM), also known as non-volatile RAM (NVRAM). The
operational parameters are saved in NVRAM and used whenever
power is lost.
Whenever the Bug uses a parameter from NVRAM, the NVRAM
contents are first tested by checksum to insure the integrity of the
NVRAM contents. In the instance of BBRAM checksum failure,
certain default values are assumed as stated below.
The bug operational parameters (which are kept in NVRAM) are
not initialized automatically on power up/warm reset. It is up to
the Bug user to invoke the ENV command. Once the ENV command
is invoked and executed without error, Bug default and/or user
parameters are loaded into NVRAM along with checksum data. If
any of the operational parameters have been modified, the new
parameters do not go into effect until a reset/powerup condition
occurs. Should you determine that the NVRAM contents have been
corrupted, use a double-button reset (described under Restarting the
System in Chapter 3) to reinitialize the system.