Locate the Ethernet network connected to your target system. It is usually
called ethernet_switch0, but check that using
list-objects command:
simics> list-objects type = ethernet_switch -all
Component Class Object
-----------------------------------
<ethernet_switch ethernet_switch0
In a start-up script that uses the common Simics Ethernet setup scripts, you
can also use the script variable $eth_link to locate the Ethernet
network.
On the Simics command-line, issue one command to set up outbound port
forwarding:
simics> connect-real-network-port-out service-node-port=<port-in-target>
ethernet-link=<ethlink> target-ip=<debug-host-ip>
target-port=<port-on-host> -udp
where:
- <ethlink> is the name of the Ethernet link as discussed
above.
- <port-on-host> is the port to use to connect on the host
side. It can be the same as the target-side port specified above, such as
50010.
- <simics-target-ip> is the IP address of the Simics target,
such as 10.10.0.100 for the QSP-x86 example.
- <port-in-target> is the port configured on the target
above, such as 50010.
- <debug-host-ip> is the IP address of the real-world machine
running WinDbg. To run WinDbg on the host running Simics, use 127.0.0.1.
For another machine on the local network, use its network address. You
would use the IP of another machine for the case where you are simulating
a Windows target on a Linux host, and need to call into a Windows host
that actually runs WinDbg.
For example in the QSP-x86 example, with WinDbg on the host running Simics:
simics> $eth_link
'ethernet_switch0'
simics> connect-real-network-port-out ethernet-link = $eth_link
service-node-port = 50010 target-port = 50010 target-ip = '127.0.0.1'
10.10.0.1 UDP port 50010 on link ethernet_switch0.link -> host 127.0.0.1:50010
10.10.0.1 TCP port 50010 on link ethernet_switch0.link -> host 127.0.0.1:50010
ff02::1:2 UDP port 50010 on link ethernet_switch0.link -> host 127.0.0.1:50010
ff02::1:2 TCP port 50010 on link ethernet_switch0.link -> host 127.0.0.1:50010