Versions Compared

Old Version 3

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version 4

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reviewed to match AXP&VAX

Anchor
TopConfigurationPage
TopConfigurationPage
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

By default, all the CHARON templates are located in the "/opt/charon/cfg" folder. Copy the appropriate template configuration file(s) to your home directory ( or to any directory intended for CHARON-VAX). Name , name them meaningfully and set proper privileges.

For exampleExample:

$ cp /opt/charon/cfg/mv3k6.cfg.template /my_charon_cfg/my_mv3k6.cfg
$ chmod 644 /my_charon_cfg/my_mv3k6.cfg

...

Once the file has been created you can open it in your favorite editing tool and proceed with modification modifications to reflect the exact features of the system you are going to emulate.

We will review all the parameters step by step issuing some recommendations and guidelines.

Note: the lines preceeded preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.

...

The first configuration statement is the specification of the exact VAX hardware model to emulate, for example.

Example:

set session hw_model = MicroVAX_3600

...

If you create the CHARON-VAX configuration file from scratch, it must be the very first uncommented line in the configuration file.

...

The next configuration statement is the "Configuration name" option.

Example:

#set session configuration_name = MicroVAX_3600

You can optionally uncomment this line to differentiate this CHARON-VAX instance from all others in a multi-instance instances environment. The configuration name can be any label that is meaningful. The example below shows the configuration name incorporated into  It is reported in the log file and is used to set the log file name for rotating log (see further: Rotating log (default) ).

Back to Table of Contents

...

Execution of CHARON-VAX creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation - start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of possible problems either with the running CHARON-VAX or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting.  If it becomes necessary to contact Stromasys for support, the cfg configuration and log files often , plus the license number, will be requested to begin problem resolution.

...

The next group of parameters defines the name of the CHARON-VAX log file and how CHARON-VAX will use it:

...

By default CHARON-VAX utilizes a so called "rotating log" mechanism. This means that a new default log file is always created each time CHARON starts and can switch to another log file if the size of the log file exceeds 64Kb (This this behavior can be changed with the "set session log_file_size" and "set session log_rotation_period" commandsparameters; see more details in the "General Settings" chapter of this guide). This  

This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is pointing to a an existing directory rather than to a file. If a directory is specified, the log files will be created in that directory.

Names The names of the rotating log files are composed as follows:

...

Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation. 

Note

Only an existing directory can be used as a value of the "log" parameter.

...

Alternatively it is possible to use just a single log file. Uncomment : uncomment the "set session log" line and specify the desired CHARON-VAX log file name. Optionally, a path can be added to the log file name. . If the path is not specified, the log file is created in the directory from where the guest (emulated machine) is started.

The log file can be extended ("log_method = append") or overwritten ("log_method = overwrite") by CHARON-VAX.

Below is a specification of a CHARON-VAX log file located in the "/my_logs" directory which will be overwritten appended each time CHARON-VAX starts:

set session log_method = overwriteappend
set session log = "/my_logs/my_vax.log"

...

TOY means "Time of Year"; its container records time, date and some console parameters while CHARON-VAX is not running. To enable the TOY, uncomment the following line:

...

The ROM container stores an intermediate state of the Flash ROM and some console parameters. So its container  It is also highly recommended to keep uncommenteddefine its location:

set rom container="vx4k106.rom"

EEPROM stores the NVRAM content, so its container is also recommended to keep uncommented. It is highly recommended to define its location:

set eeprom container="charon.rom"

...

The next parameter defines the amount of host memory the chosen CHARON-VAX model  reserves reserves for the emulation.

Example:

set ram size=64

The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each VAX model. It is very important to keep the listed predefined increment between possible memory values.

The following table shows lists all the parameters per model:

Hardware Model

RAM size (in MB)


Min

Max

Default

Increment

MicroVAX_II

1

16

16

1,8,16

MicroVAX_3600

16

64

16

16

MicroVAX_3900

16

64

16

16

VAXserver_3600

16

64

16

16

VAXserver_3900

16

64

16

16

VAXserver_3600_128

32

128

32

32

VAXserver_3900_128

32

128

32

32

MicroVAX_3100_Model_96

16

128

16

16

VAXstation_4000_Model_90

16

128

16

16

VAX_4000_Model_106

16

128

16

16

VAX_6000_Model_310

32

512

32

32

VAXserver_3600_512

32

512

32

32

VAXserver_3900_512

32

512

32

32

MicroVAX_3100_Model_98

16

512

16

16

VAX_4000_Model_108

16

512

16

16

VAX_4000_Model_700

64

512

64

64

VAX_4000_Model_705

64

512

64

64

VAX_6610

128

3584

128

128

VAX_6620

128

3584

128

128

VAX_6630

128

3584

128

128

VAX_6640

128

3584

128

128

VAX_6650

128

3584

128

128

VAX_6660

128

3584

128

128

...

The next step is the specification of the VAX console (OPA0) serial line.

Example:

#load physical_serial_line OPA0 line="/dev/ttyN"
#load virtual_serial_line OPA0 port=10003
load operator_console OPA0

...

OptionDescription
physical_serial_line

Mapping to host serial line, both physical and virtual. Use the following mapping for different types of host serial lines:

MappingDescription
/dev/tty<N>
- virtual
Virtual serial lines
/dev/ttyS<N>
- onboard
Onboard serial lines
/dev/ttyUSB<N>
- modem
Modem or usb serial lines adapters
Note

A The specific account for running CHARON ("charon") does not allow the usage of physical consoles, "/dev/tty<N>", as CHARON consoles. If you plan to map the CHARON console to "/dev/tty<N>" use only the "root" account for to run CHARON running.

virtual_serial_line

Mapping to an IP port of CHARON-VAX host.
Using this mapping it is possible to connect to the CHARON-VAX console and disconnect from it at any time.

operator_consoleMapping to the current TTY console

...

Note that the VAX 4000 and MicroVAX 3100 models have a 4-line QUART adapter onboard , so their configuration for the console line looks a bit different:

#load physical_serial_line/chserial TTA0 line="/dev/tty<N>"
#load virtual_serial_line/chserial TTA0 port=10000
#set quart line[0]=TTA0 
... 

#load physical_serial_line/chserial TTA2 line="/dev/tty<N>"
#load virtual_serial_line/chserial TTA2 port=10002
#set quart line[2]=TTA2

#load physical_serial_line OPA0 line="/dev/tty<N>"
#load virtual_serial_line OPA0 port=10003

load operator_console OPA0
set quart line[3]=OPA0

In case of VAX IF VAX 4000 and MicroVAX 3100 models are used, it is possible to configure up to 4 independent console lines: OPA0, TT0, TT1 and TT2. The main one is OPA0.

(warning) Note there are a number of additional parameters for CHARON-VAX serial line configuration. Follow this link for details.

Status
colourYellow
titleBM Marker

Exit on pressing F6 button

...

Follow this link for details of (T)MSCP controllers configuration.

Back to Table of Contents

SCSI controller NCR53C94

The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.

...