Intel® Simics® Simulator for Intel® FPGAs: User Guide

Download PDF
ID 784383
Date 11/16/2024
Public
Document Table of Contents
Document Table of Contents x
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
1. About This Document x
1.1. Documentation Conventions for Examples 1.2. Terminology 1.3. List of Acronyms
2. Intel® Simics® Simulator and Virtual Platforms x
2.1. Device Model and Virtual Platforms 2.2. Intel® Simics® Simulator 2.3. Intel® Simics® Simulator Architecture
2.2. Intel® Simics® Simulator x
2.2.1. Intel® Simics® Simulator for Intel FPGAs Capabilities
4. Installing the Intel® Simics® Simulator for Intel® FPGAs x
4.1. Installing the Intel® Simics® Simulator for Intel® FPGAs on Linux* Systems 4.2. Installing the Intel® Simics® Simulator for Intel® FPGAs on Microsoft Windows* Systems 4.3. Installing Ashling* RiscFree* IDE for Intel® FPGAs 4.4. Intel® Simics® Simulator for Intel® FPGAs Support
5. Getting Started with Intel® Simics® Simulator x
5.1. Simulation Set Up 5.2. Starting the Simulation 5.3. Intel® Simics® Simulator Command-Line Interface (CLI) 5.4. Hardware Inspection 5.5. Intel® Simics® Simulator Timing
5.1. Simulation Set Up x
5.1.1. Initializing an Intel® Simics® Project and Deploying a Virtual Platform 5.1.2. Understanding Target Scripts
5.2. Starting the Simulation x
5.2.1. Starting a Simulation from a Command Prompt 5.2.2. Starting a Simulation with Ashling* RiscFree* IDE
5.3. Intel® Simics® Simulator Command-Line Interface (CLI) x
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
5.4. Hardware Inspection x
5.4.1. Listing Objects in the Target System 5.4.2. Processor (CPU) Inspection 5.4.3. Device Inspection 5.4.4. Memory Mapping and Memory Inspection 5.4.5. Logging
5.4.2. Processor (CPU) Inspection x
5.4.2.1. Listing Processors 5.4.2.2. Inspect Processor Registers
5.4.3. Device Inspection x
5.4.3.1. Retrieve List of Devices 5.4.3.2. Inspecting Device Registers
5.4.4. Memory Mapping and Memory Inspection x
5.4.4.1. Memory Mapping Inspection 5.4.4.2. Memory Inspection
5.4.5. Logging x
5.4.5.1. Breakpoints on CLI Log Messages
5.5. Intel® Simics® Simulator Timing x
5.5.1. CPU Frequency 5.5.2. CPU Cycles and Steps 5.5.3. Events 5.5.4. Enable Real Time
6. Debugging Target Software x
6.1. Intel® Simics® Debugger and Debug Context 6.2. Capturing Serial Console Output 6.3. Breakpoints 6.4. Debugging Target Software with Symbol Files 6.5. Debugging Target Software with Ashling* RiscFree* Debugger 6.6. Capturing CPU Instruction Execution Trace
6.3. Breakpoints x
6.3.1. Memory Breakpoints 6.3.2. Temporal Breakpoints 6.3.3. CPU Control Register Breakpoints 6.3.4. Hardware Access Breakpoints 6.3.5. CPU Register Breakpoints 6.3.6. Tracing Breakpoints 6.3.7. Text Console Activity Breakpoints
6.4. Debugging Target Software with Symbol Files x
6.4.1. Loading Symbol Files in a Simulation
6.5. Debugging Target Software with Ashling* RiscFree* Debugger x
6.5.1. Remote Debugging with RiscFree* IDE
6.5.1. Remote Debugging with RiscFree* IDE x
6.5.1.1. Remote Debugging With Intel® Simics® Simulation and RiscFree* IDE on the Same System 6.5.1.2. Remote Debugging With Intel® Simics® Simulation and RiscFree* IDE on Different Systems 6.5.1.3. Remote Access to the Target System Serial Console
7. Networking with the Simulated Target System x
7.1. Network Simulation and Service Node 7.2. Connectivity Between Host PC and Target System
7.2. Connectivity Between Host PC and Target System x
7.2.1. Port Forwarding 7.2.2. Transferring Files Between Host PC and Target System 7.2.3. Accessing Target System from Host PC Through HTTP 7.2.4. Networking Commands Reference Table
7.2.1. Port Forwarding x
7.2.1.1. Incoming Port Forwarding 7.2.1.2. Outgoing Port Forwarding
7.2.1.1. Incoming Port Forwarding x
7.2.1.1.1. Example of an SSH Connection with Incoming Port Forwarding
7.2.1.2. Outgoing Port Forwarding x
7.2.1.2.1. Example of SSH Connection With Outgoing Port Forwarding 7.2.1.2.2. Example of SSH Connection via NAPT
7.2.2. Transferring Files Between Host PC and Target System x
7.2.2.1. Transferring Files with SCP service 7.2.2.2. Transferring Files with TFTP service
7.2.2.1. Transferring Files with SCP service x
7.2.2.1.1. Transferring Files With SCP Service via Forwarding Ports 7.2.2.1.2. Transferring Files with SCP from Target System to Host PC via NAPT
7.2.2.2. Transferring Files with TFTP service x
7.2.2.2.1. TFTP Using Forwarding Port 7.2.2.2.2. TFTP via NAPT 7.2.2.2.3. TFTP Using TFTP Server in Intel® Simics® Service Node
8. Intel® Simics® Scripting x
8.1. Scripts in CLI
8.1. Scripts in CLI x
8.1.1. Variables 8.1.2. Command Return Values 8.1.3. Control Flow Commands 8.1.4. Local Variables 8.1.5. Integer Conversion 8.1.6. Accessing Configuration Parameters 8.1.7. Error Handling in Scripts 8.1.8. Script Branches
8.1.8. Script Branches x
8.1.8.1. Script Branches Commands 8.1.8.2. Variables in Script Branches 8.1.8.3. Branch Synchronization 8.1.8.4. Canceling Script Branches 8.1.8.5. Script Branches Restrictions
9. Software Debug Examples with Intel® Simics® Simulator x
9.1. Debugging Linux* User-Mode Application
9.1. Debugging Linux* User-Mode Application x
9.1.1. Debugging a Linux Application with GDB 9.1.2. Debugging a Linux Application with RiscFree* IDE
9.1.1. Debugging a Linux Application with GDB x
9.1.1.1. Debugging with GDB Debug from Host PC Using Forwarding Ports 9.1.1.2. Debugging with GDB from Host PC with Intel® Simics® Simulator GDB Server
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

7.2.2.1.1. Transferring Files With SCP Service via Forwarding Ports

You can transfer files between the host PC and the simulated target system in both directions (it is assumed that the systems support the SCP service). To support this feature, create forwarding ports in both directions. The SCP service uses the standard port 22 and uses the TCP protocol (same as SSH service).

The following example shows how to transfer files in both directions. Set up the forwarding ports. In this case, the incoming forwarding port, the host port 4022 is forwarding the traffic to the port 22 with a target IP of 10.10.0.100 which corresponds to the IP in the target system. Similarly, in the outgoing forwarding port, the port 4022 in the service node is forwarding the traffic to the port 22 in the host PC, which has the 10.122.105.138 IP. The following capture shows this setup: 

HostPC | Target system
 Incoming    4022 ->  22
 Outgoing      22 <- 4022

#Intel Simics simulator CLI 

simics> connect-real-network-port-in ethernet-link = ethernet_switch0 
target-ip=10.10.0.100 target-port = 22 host-port = 4022 -tcp

Host TCP port 4022 -> 10.10.0.100:22
Warning: This can expose the target system on the host local network
simics> connect-real-network-port-out service-node-port = 4022 ethernet-link 
= ethernet_switch0 target-ip=10.122.105.138 target-port=22 -tcp
10.10.0.1 TCP port 4022 on link ethernet_switch0.link -> host 10.122.105.138:22
ff02::1:2 TCP port 4022 on link ethernet_switch0.link -> host 10.122.105.138:22
Warning: This can expose the target system on the host local network.
simics> list-port-forwarding-setup

Host TCP port 4022 -> 10.10.0.100:22
 
10.10.0.1 TCP port 4022 on link ethernet_switch0.link -> host 10.122.105.138:22
ff02::1:2 TCP port 4022 on link ethernet_switch0.link -> host 10.122.105.138:22
simics> run

Now, to verify that the SCP service works in both directions, the target2host.txt file was created in the simulated target system while the host2target.txt file was created in the host PC. Having created the files, you must move these files to the other end using the SCP command. This is shown in the following captures from the target system serial console and the host terminal.

In the host terminal, call the scp command to copy the host2target.txt file to the target system. In this command, indicate the port 4022 in the localhost (host PC). This port is the one that the host PC can see. You also indicate the user ( root ) that tries to copy the file and the file to be transferred. 

# Host Terminal 

/home/simicsUser/SimicsInstallDir/project-1$ scp -P 4022 host2target.txt \ 
root@localhost:/home/root/host2target.txt

The authenticity of host '[localhost]:4022 ([127.0.0.1]:4022)' can't be established.
ECDSA key fingerprint is SHA256:6+/zF935yx3AfluQh9yk4qwGB0a3G+qf+uYYH0eJkNU.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[localhost]:4022' (ECDSA) to the list of known hosts.
host2target.txt                               100%   20     1.9KB/s   00:00
:
# After the scp from the target console is issued, this is seen here.
/home/simicsUser/SimicsInstallDir/project-1$ ls
host2target.txt  target2host.txt

In the target serial console, call the scp command to copy the target2host.txt file to the host PC. In this command, indicate the port 4022 in the service node (address 10.10.0.1). This port is the one that the target system can see. Also indicate the user (simicsUser) that attempts to copy the file and the file to be transferred. 

# Target Serial Console

root@psgdevice:~# scp -P 4022 target2host.txt \ 
simicsUser@10.10.0.1:/home/simicsUser/SimicsInstallDir/project-1/

The authenticity of host '[10.10.0.1]:4022 ([10.10.0.1]:4022)' can't be established.
ED25519 key fingerprint is SHA256:XQzql2Lz5mbrPPsMX9Xc8a8Q4E3hmx3RrE7neHoO3Oc.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[10.10.0.1]:4022' (ED25519) to the list of known hosts.
simicsUser@10.10.0.1's password: 
target2host.txt                               100%   20    10.0KB/s   00:00
:
# After the scp from the host terminal is issued, this is seen here.
root@psgdevice:~# ls
host2target.txt    target2host.txt
root@psgdevice:~#

In both captures, ls command is used in each system to verify the files were copied. In these captures, you can confirm that after the calling the scp commands, both files exist in both places.

Level Two Title