Load_Ixc; Log; Logical - Intel IXP2400 User Manual

®
Intel IXP2400/IXP2800 Network Processors
Transactor
8.3.22

load_ixc

Format:
load_ixc [useq_spec | ustore_stats_name] ucode_file_name
Definition:
"load_ixc" loads and validates all microcode in the control store. The control store can either
be specified directly by name, or by using the chip/useq format used in other commands such
as "set_default_goto_filter". If this format is used, IXP code will be loaded into all control
stores that map to the specification.
8.3.23

log

Format:
log file_name |commands| |responses|
Definition:
Opens a log file of the specified name to log various simulation information. A log file may be
closed using the "close" command All log files are automatically closed when the simulator
exits.
file_name
commands
responses
8.3.24

logical

Format:
logical [logical_name] [= logical_definition]
Definition:
If both optional parameters are specified, the specified logical name is defined to be the
specified logical definition string
If no definition string follows the "=", then the logical_name is deleted from the list of
logicals. This logical definition is saved in the Win32 registry.
If only the logical_name field is specified, the current definition for this field is displayed.
If neither field is specified, all logical definitions are listed.
Examples:
(1) The following Simulator call illustrates how to list existing logicals:
242
If the file_name is not specified, the log command displays all currently
open log files.
Logs all simulator commands typed by the user.
Logs all general simulator output. If no optional switch is specified the
default assumes both "commands" and "responses".
>>> logical
Logical: $model_dir = "c:\vmod_models"
Logical: testdir = "c:\test"
Logical: newworkingdir = "c:\test\subtest"
Logical: newworkdir = "c:\test\subtest"
Development Tools User's Guide