simpc - VxSim for Windows NT4.0/2000/XP
This reference entry provides target-specific information necessary to run the VxWorks simulator on Windows.
Not applicable.
To start the VxWorks simulator simply type "vxWorks" from a DOS shell, or use VxSim icon from The Tornado Graphical User Interface. For further information, follow the instructions in the VxSim chapter of the Tornado User's Guide and Getting Started chapter of the VxWorks Programmer's Guide.
Not applicable.
The simulator can access keyboard input and window output through a standard vxWorks sio driver. Because device drivers require direct hardware interaction, most VxWorks device drivers are not available with VxSim.
The VxSim full simulator provides full network capability for your simulator. This optional product also allows you to run more than one instance of VxSim on your host.
In order to simulate the network IP connectivity of a VxWorks target, the VxSim full simulator includes special drivers that operate using IP addresses. The ULIP network interface is available for Windows hosts.
All interfaces provide an I/O-based interface for IP networking that allows VxSim processes to be addressed at the IP level. When multiple programs are run, they can send packets to each other directly. This is because the host hands the packets back and forth; that is, the host OS effectively becomes a router with multiple interfaces.
Installing ULIP on a Windows NT Host
- From the Start menu select Settings>Control Panel>Network. - Click the Adapters tab in the Network window, click the Add button, and click Have Disk... in the Select Network Adaptor window and select the "host\x86-win32\bin" directory of your Tornado installation and click OK. - Click on Ulip Virtual Adapter and click OK. ULIP is added to the Network Adapters list. - Enter an IP address of the form nnn.nnn.nnn.254 (for example, 192.168.255.254). - Then from the Bindings tab select Show bindings for all adapters, select Ulip Virtual Adapter>WINS Client (TCP/IP)>NetBIOS Interface and click Disable and OK. - If you want to enable network communication between simulators and the outside world, select Settings>Control Panel>Network from the Start menu, then click the Protocols tab and double-click on TCP/IP Protocol. From the Routing tab of the TCP/IP Properties window, check Enable IP Forwarding. Click OK and Close. - Restart the computer so the new settings take effect. Installing ULIP on a Windows 2000 Host
- From the Start menu select Settings>Control Panel>Add/Remove hardware. This launches the driver installation wizard. - Click the Next button. Then click the subsequent Next button. This displays the Choose a Hardware Device dialog box. - From the dialog box, select the line Add a new device and click the Next button. - Select the option No, I want to select the hardware from a list, and click again on the Next button. - Select Network adapters, and click on Next. This stage can take several minutes. The Select Network Adapter dialog box appears. Click on the Have disk button, and select the "host\x86-win32\bin" directory of your Tornado installation and click OK. - Then select the line WindRiver Ulip, and click on Next. A new dialog box appears, click again on Next. - The Digital Signature Not Found dialog box appears, select Yes. - Then the last dialog box shows up, ensure it confirms that the installation went right, and finally, click on the Finish button. - Then starting from the Windows Desktop, right click on My Network Places, and select Properties. - Right click on the last Local Area Connection # icon and select Properties. (You can rename this Local Area Connection # title with WindRiver Ulip, select Rename instead of Properties). - Select the line Internet Protocol (TCP/IP) and click on Properties. (If TCP/IP protocol is not installed, please refer to the MS Windows help to install it). - Enter an IP address of the form nnn.nnn.nnn.254 (for example, 192.168.255.254) and 255.255.255.0 as Subnet mask, and click on Advanced. - In the WINS tab, select Disable NetBIOS over TCP/IP and click OK, to properly close all the remaining windows. - If you want to enable network communication between simulators and the outside world, select Setting>Control Panel>Administrative tools from the Start menu, double-click on Services, then search for the Routing and Remote access service. If it is disabled, right-click on it and change the startup type to Automatic so it will be started at Windows startup. Click OK to validate your change. The service can now be started using the play icon on the main service window. Installing ULIP on a Windows XP Host
For further information, follow the instructions in the Configuring the VxSim Full Simulator sub-chapter of the VxSim chapter of the Tornado User's Guide .
- From the Start menu select Settings>Control Panel>Add Hardware. This launches the driver installation wizard. Click Next. - The wizard will search for recently connected hardware, this stage can take several minutes. Then select Yes, I have already connected the hardware, and click Next. - From the Installed hardware list, select Add a new hardware device, and click Next. - Select Install the hardware that I manually select from a list [Advanced], click Next. - From the Common hardware types list, select Network adapters, click Next. - Click Have Disk..., and select the "host\x86-win32\bin" directory of your Tornado installation. - Select WindRiver ULIP, and click Next twice. - The Hardware Installation will report that "WindRiver ULIP" has not passed Windows Logo testing to verify its compatibility with Windows XP. You can safely ignore this warning and click Continue Anyway. - Then, from the Control Panel, launch Network Connections and right-click WindRiver ULIP connection (You can rename this connection). - From the WindRiver ULIP Properties panel, select Internet Protocol (TCP/IP), and click Properties. - Check use the Following IP address, and enter an IP address of the form nnn.nnn.nnn.254 (for example, 192.168.255.254), and 255.255.255.0 as Subnet mask, and click on Advanced. - In the WINS tab, select Disable NetBIOS over TCP/IP and click OK, to properly close all the remaining windows. - If you want to enable network communication between simulators and the outside world, select Setting>Control Panel>Administrative tools from the Start menu, double-click on Services, then search for the Routing and Remote access service. If it is disabled, right-click on it and change the startup type to Automatic so it will be started at Windows startup. Click OK to validate your change. The service can now be started using the play icon on the main service window.
VxSim supports up to eight Ulip END interfaces. To configure several ULIP END interfaces in VxSim (procedure is the same as for any other vxWorks BSP), edit the endDevTbl[] table defined in the configNet.h file. For example to add two interfaces (nt1 and nt2):
END_TBL_ENTRY endDevTbl [] = {
{ 0, WIN_LOAD_FUNC, "0", WIN_BUFF_LOAN, NULL, FALSE},
{ 1, WIN_LOAD_FUNC, "1", WIN_BUFF_LOAN, NULL, FALSE},
{ 2, WIN_LOAD_FUNC, "2", WIN_BUFF_LOAN, NULL, FALSE},
{ 0, END_TBL_END, NULL, 0, NULL, FALSE}, };Then use ipAttach( ) and ifAddrSet( ) to complete interfaces initialization:
ipAttach (1, "nt");
ifAddrSet ("nt1","192.168.255.2");ipAttach (2, "nt");
ifAddrSet ("nt2","192.168.255.3");For more information, follow the instructions in the Adding an END to VxWorks sub-chapter of the Integrating a New Network Interface Driver chapter of the VxWorks Network Programmer's Guide .
Interfaces have their IP last tupple and MAC address set according to the processor number of VxSim.
IP last tupple = MAC = processor number + interface number + 1
processor number : Simulator processor number set on vxWorks command line using /p option.
interface number : Network interface number, 0 for the first interface (nt0), 1 for the second (nt1), and so on ...For example, if VxSim is configured with four network interfaces, assuming the ULIP adapter address is 192.168.255.254, we will have:
VxSim0 (Processor number 0) :
nt0 192.168.255.1 MAC=1
nt1 192.168.255.2 MAC=2
nt2 192.168.255.3 MAC=3
nt3 192.168.255.4 MAC=4VxSim1 (Processor number 1) : Not available. (*)
VxSim2 (Processor number 2) : Not available. (*)
VxSim3 (Processor number 3) : Not available. (*)VxSim4 (Processor number 4) :
nt0 192.168.255.5 MAC=5
nt1 192.168.255.6 MAC=6
nt2 192.168.255.7 MAC=7
nt3 192.168.255.8 MAC=8VxSim5 (Processor number 5) : Not available. (*)
VxSim6 (Processor number 6) : Not available. (*)
VxSim7 (Processor number 7) : Not available. (*)... and so forth.
(*) As mentionned above, some VxSim instances become unavailable. VxSim1 expects to get the IP address 192.168.255.2, but since this address is already used by VxSim0, VxSim1 becomes unusable (as well as VxSim2 and VxSim3).
The IP address set using ifAddrSet( ) must be consistent with the VxSim configuration, it is not configurable. To avoid any confusion, the IP address for each interface is printed in VxSim's console at boot time.
The timestamp driver is used to extend the range of information available from VxWorks kernel instrumentation. For example, if the timestamp driver is available, a precise chronology can be displayed by WindView. VxSim contains a system-defined timestamp driver. This feature is selected by default by the macros INCLUDE_TIMESTAMP and INCLUDE_SYS_TIMESTAMP in the BSP configuration file "config.h".
To exit the simulator, type alt-F4, or click on the x (close) in the corner of the window.
VxSim can use any VxWorks file system. The default file system is the pass-through file system, passFs, which is unique to VxSim. The VxWorks syntax to access a host file system is : host:disk:/dir1/dir2/file For further information, please refer to File Systems sub-chapter of the Integrated Simulator chapter of the Tornado User's Guide.
Options may be passed to VxWorks from the command line:
/p proc num (set processor number) FULL SIMULATOR ONLY /r ram bytes (set memory size) Note that WindView graph can be impacted by the activity on your Windows machine if the VxSim process is preempted by another Windows process. In such a case, the current activity of each VxWorks thead is prolonged by an interval of time corresponding to the preempted time of vxWorks process. You should take this into account if you notice unreasonable data in a WindView graph.
VxWorks Programmer's Guide: Getting Started, Configuration and VxSim chapter of the Tornado User's Guide.