|Boards Supported||Newt (VL-EPIC-17)|
|Expansion Modules Supported||EPM-NET-100|
|OS Version||VxWorks 6.8|
|OS Kernel Version||WIND version 2.13|
|IDE/Platform||Wind River Workbench|
|Workbench Version||3.2 (Build id: 20091119-1228)|
VersaLogic is making no claims of usability, efficacy or warranty. Information in this document is provided in connection with VersaLogic products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. VersaLogic assumes no liability whatsoever, and VersaLogic disclaims any express or implied warranty relating to the sale and/or use of VersaLogic products, including liability or warranties relating to fitness for a particular purpose, merchantability or infringement of any patent, copyright or other intellectual property right. VersaLogic products are not intended for use in life-saving or life-sustaining applications.
VersaLogic disclaims all warranties and liabilities for the use of this document and the information contained herein, and assumes no responsibility for any errors which may appear in this document, nor does VersaLogic make a commitment to update the information contained herein. VersaLogic reserves the right to make changes to this document at any time without notice.
This BSP is based on the pcPentium BSP (version 2.0/12) that ships with VxWorks 6.8 + Workbench 3.2 installation media. This BSP has been ported to include driver support for the RDC6040 Ethernet controller and to support VersaLogic's Tomcat (VL-EPM-16) and Newt (VL-EPIC-17) single board computers (SBCs).
-- or --
-- or --
-- or --
We are assuming that you have installed the VxWorks development tools at their default location as specified by the setup program:
If this is not the case, you will need to substitute the proper path as per your customized setup.
The BSP-VXW-VRTX zip file contains the following items:
We are assuming that your VxWorks workspace directory is located at:
C:\directory and NOT to
C:\BSP-VXW-VRTX-R1.00. Using the application WinRar is recommended. Before you start building your image, it is highly recommended that you first install the RDC6040 Ethernet driver in your VxWorks development environment. Please see the section Installing the Network Driver for details.
Copy the above bootrom.bin file as bootrom.sys in the root directory (
C:\) of a FAT-formatted, bootable VxWorks media. See  for detailed steps on how to create a VxWorks bootable media.
To check whether the VxWorks boot sector got installed properly or not, boot your media and check for the following text:
You can create a VxWorks OS image either by importing the supplied project file Vortex.wpj or by creating a new VxWorks Image Project (VIP) from Wind River Workbench.
Upon successful build, you will find the VxWorks OS image vxWorks, in the project directory located at:
Follow the instructions in the ReadMe file located at:
The following features have been tested on this BSP:
The supplied BSP's config.h file at:
is configured to boot the VxWorks OS image over a network. To do that, you need to have an FTP/TFTP server running on your development host with the path to the directory containing the vxWorks file accessible to it. You will have to adjust the following line in the config.h based on your setup:
rdc(0,0)organiza-bac0jk:vxWorks h=192.168.4.117 e=192.168.4.37:ffffff00 g=192.168.4.1 f=0x80 tn=target
If you would like to boot the image locally on the target (from the storage media), you need to comment the above line and then uncomment and adjust the following line based on your setup:
ata(0,0)host:/ata0a/vxWorks h=192.168.4.117 e=192.168.4.37:ffffff00 g=192.168.4.1
The Wind River VxWorks installation comes with an FTP server called WFTPD. Optionally, you can use TFTPD , which is simpler to set up.
The driver AMD Am79C97x PCnet/PCI VxBus Enhanced Network Driver for the EPM-NET-100 card is included in the supplied project file by enabling the INCLUDE_AM79C97X_VXB_END option. Once your VxWorks image boots on the target, you need to initialize and configure the driver with the following commands:
Check if the interface is up:
You should see an interface named lnPci0 listed in the output.
→ifconfig("lnPci0 192.168.4.38 netmask 255.255.255.0 up")
→routec "add default 192.168.4.1"
tgtsvr -V -R C:/WindRiver/workspace -RW -Bt 3 -c C:\WindRiver\workspace\Vortex\default\vxWorks -A 192.168.4.37
Copyright © 2011 VersaLogic Corp. All rights reserved.