Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Please note:
- Each instance of Charon-PAR must be started in a separate directory because certain files (SSTORAGE.DAT, NVOLATILE.DAT, UA_SSTORAGE.DAT, and console.dat) will always be created in the current working directory of the emulator instance. Starting multiple emulator instances in the same directory will lead to errors due to file locking problems.
- If Charon-PAR is to be started by a non-root user (introduced in version 3.0.5 build 21906), certain capabilities must be set for the Charon-PAR image, for example via the following command:
sudo setcap 'cap_sys_nice+eip cap_ipc_lock+eip cap_net_admin+eip' /opt/charon/bin/charon-par
When starting Charon-HPA-PAR (the command /opt/charon/bin/charon-par), there are several command-line options that can be used. The following table provides an overview:
Options (1) | Description |
---|---|
-D , --dump | Do not use in a production environment unless instructed to do so by Stromasys support! |
-F , --fast-fpu | Fast FPU mode provides better floating-point performance at the expense of minor deviation in floating-point status reporting. When this option is enabled, all floating-point operations produce exactly the same values as the real hardware. The differences cause FPU tests (ODE WDIAG and llmc_em) to report errors. However, it is highly unlikely that any real system or application software is impacted by this deviation. Configuration show in emulator log as (FPU DIT Mode: Fast - vs Precise). |
| Do not use in a production environment unless instructed to do so by Stromasys technicalsupport! Possible values:
|
-S <mode> --ditsync <mode> | Do not use in a production environment unless instructed to do so by Stromasys technical support!-support! Possible values:
|
| Do not use in a production environment unless instructed to do so by Stromasys support! Each Charon-PAR model has a built-in maximal DIT optimization level. This parameter allows to reduce this level. As result, the emulation will run with reduced performance. |
-X <mode> --collect-statistics <mode> | Collect the available statistics. The output-descriptor can be one of the following:
|
-a <name>--instance-name <name> | Assigns a logical name to the emulated system instance at start (reserved for future use). |
| Redirects the Charon-PAR console to a TCP/IP port that can be accessed via telnet (from local system only). This makes the console accessible also when the emulator runs in daemon mode. The port number can be in the range of 0-65535. However, port numbers 0-1023 are generally reserved for specific applications and should not be used. |
| Specifies the path to the emulator configuration file. |
| Displays a short help information. |
-l <logpath>--logfile-path <logpath> | Specifies the path to the logfile. |
| Name of file File to store the process ID of the emulator process. Used mostly when running emulator as a daemon. |
-x --daemon | The emulator is started as a daemon. The output of the emulator console (at the hp3k or hp9k prompt) will be sent to journalctl. This mode can be used when the emulator is to be started at system boot. It can also be used to start the emulator while connected to the system via the network to avoid license problems. This option can be used together with the following options:
|
...
. | |
--mmu-assist <setting> | Do not use unless advised to do so by Stromasys support! MMU assist type. Possible values: none, simple, advanced. Used in debugging situations to modify Charon optimization modes. |
--no-libc-assist | Do not use unless advised to do so by Stromasys support! Disable libc assist mode. Used in debugging situations. |
Added in 3.0.5 build 21904 (do not use unless advised to do so by Stromasys support): | |
--dit_page_headers <number> | DIT code headers number (default 0 - automatic) |
--dit_page_size <number> | DIT code page size KB (default 48). The parameter defines the size of a single translated page chunk size. |
--dit_pool_size <number> | DIT pool size GB (default 2; maximum value 128). Any increase will increase the emulator's memory requirements accordingly. |
Include Page | ||||
---|---|---|---|---|
|