Summary of running VxWorks on a virtual machine

My virtual machine environment: VMware Workstation, 7.1.4 build-385536

Tornado2.2.1, vxworks5.5.1

Where the file downloaded in the article: http://download.csdn.net/detail/dijkstar/4377523

The completed virtual VxWorks System can be placed at: http://download.csdn.net/detail/javasstar/5173934, which can be directly stored in VMware workstation6.5 ~ If it is used in Step 7, you need to change bootrom. SYS. for how to create and put it in, see the following article! )

The generated VxWorks project configuration file can be found at: http://download.csdn.net/detail/javasstar/5174246; (edit)

The first is to create a DOS-based operating environment on the virtual machine with a disk size of 250 MB. The tools used are the images of ramdisknt15 and dos622. For details about how to create this virtual machine, refer to the "VMware + VxWorks advanced tutorial". In addition, once the Virtual Machine disk is partitioned and formatted, in addition to copying data to drive a according to the article, and then copying data to drive C of the virtual machine after entering the virtual machine, in Windows, you can use a ing disk to interact with virtual machines. For example, the C disk of a virtual machine is directly mapped to the Z disk of windows, which facilitates data interaction.

In addition, it is prompted that the tool ramdisknt15 is used to create a virtual soft drive after Windows starts to enter the desktop. The tool vfloppy is used when Windows is started, create a menu similar to "one-click Recovery System". Click this menu to go directly to the created vro. Therefore, ramdisknt15 is suitable for Virtual Machine environments and experiments. vfloppy can be used directly for actual projects and projects.

(Ramdisknt15 will no longer be used once the above Virtual DOS system has been created !)

Directly use the BSP [VMware] folder and copy it to "C: \ tornado2.2 \ target \ config; (BSP [amd] is used for learning with "VMware + VxWorks advanced tutorial ,);

The next step is to modify the NIC file, config. H, and so on. Follow the article "VMware + VxWorks advanced tutorial" step by step. Do not add the following windml section first. Ln97xend. C and ln97xend. h have been set up, and you can override them by following the methods in the article. When modifying the config. h configuration, note that this sentence is in the article:

"H = 192.168.237.1 E = 192.168.237.88" indicates the host (the operating host in Windows XP) and end (the virtual machine to run VxWorks) respectively ), for their definition, You need to query [network connection]-> [VMWare virtual Ethernet Adapter forvmnet1] ([vmnet1] corresponds to host-only, and [vmnet8] corresponds to Nat) IP Address Settings, set them to the same:

After the VM is actually running, the configuration is as follows:

After [VMware] is compiled,

Also run:

@echo offrem Command line build environmentsset WIND_HOST_TYPE=x86-win32set WIND_BASE=C:\Tornado2.2.1_x86set PATH=%WIND_BASE%\host\%WIND_HOST_TYPE%\bin;%PATH%objcopypentium -O binary --gap-fill=0 bootrom bootrom.sys

After obtaining bootrom. sys, the file is finally loaded in the final Virtual Machine file \ config. SYS:

On the Internet, you can see that ln97xend. C and ln97xend. H is directly placed in [c: \ tornado2.2 \ target \ config \ amd]. For example, the content in [VMware] Is ln97xend. O is directly compiled in makefile, eliminating the need to modify libdrv in VMware + VxWorks advanced tutorial. in Part A, you can compare the differences between makefile files in VMware and AMD:

There is nothing to say about creating bootrom. SYS. Just follow the article. Make. BAT file, be sure to note that the actual tornado2 of "set wind_base = c: \ tornado2.2" follows the path.

You can go to usrappinit. c file. Add printf ("helloworld \ n") at the prompt. Once the VxWorks file is created, copy it to the virtual machine using the ing method for the first time; after the Virtual Machine VxWorks runs, it can be pinged to the Virtual Machine by using VxWorks on Windows XP. Later, you can use the FTP software to transmit the modified VxWorks file for trial and use;

Notes for using two FTP servers:

One is bootrom guided by a virtual machine. sys, to get VxWorks from the host machine, use the tornado WFTPD tool (C: \ tornado2.2 \ host \ x86-win32 \ bin), the user name/password used is: target/target, that is, the virtual machine is the client, and the tornado side is the server:

The other is that after running VxWorks on a virtual machine, it is also an FTP server. On Windows, you can use an FTP client tool to log on to the virtual machine. The user name/password used is: lnpci/Target

After the virtual machine becomes an FTP server, you can easily download various. out files for verification!

The above VxWorks is a network boot method. If the hard disk boot mode is used, change the config. h of [VMware:

#define DEFAULT_BOOT_LINE \"ata=0,0(0,0)host:/ata0a/vxWorks h=192.168.237.1 e=192.168.237.88 u=target pw=target"/*"lnPci(0,0)host:vxworks h=192.168.237.1 e=192.168.237.88 u=target pw=target"*/#elif(CPU == PENTIUM2)

After the BSP is compiled, use make1.bat in [VMware] to generate bootrom. sys and copy it to the DOS disk using the disk ing method!