» Support » Software » Search » BSP-VXW-VRTX-R1.00 » ReadMe

ReadMe: BSP-VXW-VRTX-R1.00

VxWorks 6.8 Board Support Package (BSP) for the DMP Vortex86DX platform

Boards Supported Newt (VL-EPIC-17)
Tomcat (VL-EPM-16)
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)
Eclipse Version 3.5.1


  1. Legal Disclaimer
  2. Purpose
  3. Prerequisites
  4. Package Contents
  5. Build Instructions
  6. Installing the Network Driver
  7. Hardware Tested
  8. Boot Instructions
  9. Expansion Modules
  10. Known Issues
  11. References


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).


Host (Development Machine)

  1. Windows XP
  2. 256 MB RAM (min.)
  3. Wind River Workbench 3.2
  4. 1 GB of free space (min.)

Target (Vortex-based Board)

  1. Keyboard and Mouse
    1. PS/2 (recommended)
    2. -- or --

    3. USB
  2. Boot Media (at least 25 MB)
    1. PATA/IDE device - Hard drive/CompactFlash
    2. -- or --

    3. USB device - Hard drive or jump drive
  3. Display Device
    1. VGA monitor
    2. -- or --

    3. Flat Panel Display


Warning!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:

  1. C:\WindRiver\vxworks-6.8\target\config
    This folder contains the actual BSP for the Vortex86DX SoC platform.
  2. C:\WindRiver\workspace
    This folder contains the project files required to build the VxWorks image.
  3. C:\WindRiver\vxworks-6.8\target\3rdparty
    This folder contains driver for the RDC6040 Ethernet controller.
  4. C:\WindRiver\vxworks-6.8\target\config\vortex\README_BSP-VXW-VRTX-R1.00.txt
    This page/file.
  5. C:\WindRiver\vxworks-6.8\target\config\vortex\CHANGELOG_BSP-VXW-VRTX.txt
    A brief history and summary of the version releases for this package.


Warning!We are assuming that your VxWorks workspace directory is located at:


  1. Unzip the supplied zip package directly to the root of your C:\ directory and NOT to C:\BSP-VXW-VRTX-R1.00. Using the application WinRar[2] 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.
  2. Creating a bootloader (bootrom.bin):
    1. From Wind River Workbench, go to File→New→VxWorks Boot Loader / BSP Project.
    2. Enter any project name (such as Vortex-BootLoader) in the Project Name field.
    3. Select vortex under the Board Support Package field. Leave all other settings to their defaults and click Finish.
    4. Go to Project→Build Project.
    Upon successful build, you will find a bootrom.bin file in the BSP directory:
    Copy the above bootrom.bin file as bootrom.sys in the root directory (C:\) of a FAT-formatted, bootable VxWorks media. See [1] for detailed steps on how to create a VxWorks bootable media.

    TipTo check whether the VxWorks boot sector got installed properly or not, boot your media and check for the following text:

  3. Building a VxWorks OS image (vxWorks)

    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.

    Using the Supplied Project File

    1. From Wind River Workbench, go to File→Import→VxWorks 6.x→Existing VxWorks 6.x Image Project into Workspace. Click Next.
    2. Browse to the Vortex.wpj file in the VxWorks 6.x Image Project File field. Leave all other settings to their defaults and click Finish.
    3. Optionally, you can add and/or remove components from your image by right-clicking the Kernel Configuration component in your Project Explorer window and selecting Edit Kernel Configuration.
    4. Go to Project→Build Project.

    Creating a VIP

    1. From Wind River Workbench, go to File→New→VxWorks Image Project.
    2. Enter any project name (such as Vortex) in the Project Name field. Click Next.
    3. Select vortex under the BSP field. Leave all other settings to their defaults and click Finish.
    4. Go to Project→Build Project.

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:

  1. PS/2 and USB keyboard
  2. COM1 and COM2 serial ports (8,N,1@115200 bps)
  3. PATA/IDE hard drive and/or CompactFlash
  4. RDC6040 Ethernet


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= e= g= 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= e= g=

The Wind River VxWorks installation comes with an FTP server called WFTPD. Optionally, you can use TFTPD [3], 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 netmask up")

→routec "add default"


  1. You will need to change the following parameters in your project as per your own network configuration:
  2. Make sure the bootrom file bootrom.sys is contiguous and not fragmented after copying it to the boot media.
    chkdsk C:\bootrom.sys
  3. To communicate with your target device over a network, you can use the Target Server Connection (TSC) method from Wind River Workbench by going to Target→New Connection→Wind River VxWorks 6.x Target Server Connection. The supplied project file Vortex.wpj contains the necessary support to enable TSC. The following is a sample command line after setting up all the parameters in the Target Server Options GUI window:
    tgtsvr -V -R C:/WindRiver/workspace -RW -Bt 3 -c C:\WindRiver\workspace\Vortex\default\vxWorks -A
  4. Upon connecting the USB keyboard, you will not be able to use the PS/2 keyboard (even if the driver is included). To disable USB keyboard support, disable the following component in your project:


  1. The BSP does not have driver support for the second on-board Ethernet controller (Micrel KSZ8841) on the VL-EPIC-17EB model of the Newt SBC.
  2. The device on Primary Slave will not be accessible after the VxWorks image boots on the target.



Copyright © 2011 VersaLogic Corp. All rights reserved.