Visible to Intel only — GUID: hoh1678629053804
Ixiasoft
1. About This Document
2. Intel® Simics® Simulator and Virtual Platforms
3. Intel® Simics® Simulator for Intel® FPGAs Device Portfolio
4. Installing the Intel® Simics® Simulator for Intel® FPGAs
5. Getting Started with Intel® Simics® Simulator
6. Debugging Target Software
7. Networking with the Simulated Target System
8. Intel® Simics® Scripting
9. Software Debug Examples with Intel® Simics® Simulator
10. Document Revision History for Intel® Simics® Simulator for Intel FPGAs User Guide
A. Intel® Simics® Simulator Command Reference
5.3.1. Version of the Intel® Simics® Simulator for Intel FPGAs Software
5.3.2. Simulation Run Control from CLI
5.3.3. Intel® Simics® Simulator Command Scope
5.3.4. Intel® Simics® Simulator CLI Variables and Operations
5.3.5. Intel® Simics® Simulator CLI Command Completion and Command History
5.3.6. Intel® Simics® Command-Line Interface Help
5.3.7. Capture of CLI Session to a File
5.3.8. Intel® Simics® Simulator File Location and Intel® Simics® Search Path
Visible to Intel only — GUID: hoh1678629053804
Ixiasoft
5.3.3. Intel® Simics® Simulator Command Scope
The commands that can be executed from the Intel® Simics® simulator CLI may have a global or local scope. As the name indicates, global commands affect the overall simulation, or all the objects related to the command called. Local scope commands only apply to the object for which the command was called. These are also referred to as namespaced commands. As an example, the log-level command on its own is a global command. It sets the verbosity level for all objects in the model.
log-level <verbosity_level>For example:
# Intel Simics simulator CLI simics> log-level 4 New global log level: 4
The version command shown earlier in this document is another example of a global command.
Scoping a command with a hierarchical name makes it a local command. As an example, to change the verbosity level for the system.board.fpga.hps.core[0] component, prefix the component name to the command. For example, change the log level for the system.board.fpga.hps.core[0] component from the earlier level of 4 to 2 as follows:
# Intel Simics simulator CLI simics> system.board.fpga.soc_inst.hps_subsys.agilex_hps.core[0].log-level 2 [system.board.fpga.soc_inst.hps_subsys.agilex_hps.core[0]] Changing log level: 4 -> 2