Intel® is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Java™ and all other Java-based marks are trademarks or registered trademarks of Oracle America, Inc. in the U.S. and other countries.
Microsoft®, Windows® and Windows Me® are registered trademarks of Microsoft Corporation; and Windows XP™ is a trademark of
Microsoft Corporation.
PICMG®, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logos are registered trademarks of the PCI
Industrial Computer Manufacturers Group.
UNIX® is a registered trademark of The Open Group in the United States and other countries.
Notice
While reasonable efforts have been made to assure the accuracy of this document, Artesyn assumes no liability resulting from any
omissions in this document, or from the use of the information obtained therein. Artesyn reserves the right to revise this document
and to make changes from time to time in the content hereof without obligation of Artesyn to notify any person of such revision or
changes.
Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to
an Artesyn website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise
altered without the permission of Artesyn.
It is possible that this publication may contain reference to or information about Artesyn products (machines and programs),
programming, or services that are not available in your country. Such references or information must not be construed to mean that
Artesyn intends to announce such Artesyn products, programming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply
unless otherwise agreed to in writing by Artesyn.
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in
Technical Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and
Documentation clause at DFARS 252.227-7014 (Jun. 1995).
This manual is divided into the following chapters and appendix:
Chapter 1, Introduction, on page 9, provides an overview of this manual.
Chapter 2, Booting VxWorks, on page 11, describes the procedure to boot VxWorks on the
MVME2500.
Chapter 3, Building Board Support Package, on page 19, describes the procedure to build
Board Support Package (BSP).
Appendix A, Sample Output, on page 27, provides the sample output of VxWorks booting
through network, disk and USB.
Appendix B, Related Documentation, on page 41, lists the related documents of VxWorks on
the MVME2500.
Abbreviations
This document uses the following abbreviations:
AbbreviationDefinition
BSPBoard Support Package
FTPFile Transfer Protocol
IPInternet Protocol
SATASerial Advanced Technology Attachment
SBCSingle Board Computer
TFTPTrivial File Transfer Protocol
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
5
Page 6
Conventions
The following table describes the conventions used throughout this manual.
NotationDescription
0x00000000Typical notation for hexadecimal numbers (digits are
0b0000Same for binary numbers (digits are 0 and 1)
boldUsed to emphasize a word
ScreenUsed for on-screen output and code related elements
Courier + BoldUsed to characterize user input and to separate it
ReferenceUsed for references and for table and figure
About this Manual
About this Manual
0 through F), for example used for addresses and
offsets
or commands in body text
from system output
descriptions
File > ExitNotation for selecting a submenu
<text>Notation for variables and keys
[text]Notation for software buttons to click on the screen
and parameter description
...Repeated item for example node 1, node 2, ..., node
12
.
.
.
..Ranges, for example: 0..4 means one of the integers
|Logical OR
6
Omission of information from example/command
that is not necessary at the time being
0,1,2,3, and 4 (used in registers)
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 7
NotationDescription
Indicates a hazardous situation which, if not avoided,
could result in death or serious injury
Indicates a hazardous situation which, if not avoided,
may result in minor or moderate injury
Indicates a property damage message
No danger encountered. Pay attention to important
information
About this Manual
Summary of Changes
This manual has been revised and replaces all prior editions.
Part NumberPublication DateDescription
6806800L66ANovember 2010Preliminary Version
6806800L66BFebruary 2011Final Version
6806800L66CApril 2014Re-branded to Artesyn template.
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Added SPI Flash Boot on page 16, Appendix A, SPI Flash Boot, on page 31.
7
Page 8
About this Manual
About this Manual
8
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 9
Introduction
1.1Overview
The MVME2500 Single Board Computer (SBC) is a VMEbus board, which features a single-core
P2010 or the dual-core P2020 Freescale QorIQ processors. For more information on
MVME2500series, visit our website www.artesyn.com/computing.
This document describes the procedure to boot VxWorks 6.8 on MVME2500 board.
1.2Deliverables
The following table lists the MVME2500 deliverables.
Table 1-1 List of Deliverables
Name Description
Chapter 1
vxWorks-2020.stVxWorks boot image file for P2020 blades
vxWorks-2010.stVxWorks boot image file for P2010 blades
mvme2500_sp1.tar.gzVxWorks 6.8 Board Support Package (BSP)
for MVME2500
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
9
Page 10
Introduction
10
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 11
Booting VxWorks
2.1Introduction
You can boot VxWorks on the MVME2500 board using any of the following methods:
Network Boot
Disk Boot
USB Boot
SPI Flash Boot
2.2Network Boot
2.2.1Prerequisites
Chapter 2
You should have:
Connectivity to the TFTP server
2.2.2Booting Procedure
The TFTP server should be configured and started in the connected PC. The VxWorks boot
Image file, vxWorks-2020.st or vxWorks-2010.st, should be made available at the
standard TFTP boot image path /tftpboot.
To boot VxWorks through network, perform the following steps:
1. Power up the MVME2500 board.
By default, it provides the U-Boot prompt.
2. Set the environmental variables at the U-Boot prompt.
setenv ipaddr <Board ip address>
setenv serverip <TFTP server ip address>
setenv gatewayip <Gateway ip address>
setenv netmask <Netmask>
10.130.101.206 : Board IP
ffffff00 : Netmask
u=vxworks : Username on host machine
p=vxworks : Password for the above user in host machine
f=0x80 : File Transfer Protocol (FTP)
10.130.101.206 : Board IP
ffffff00 : Netmask
u=vxworks : Username on host machine
p=vxworks : Password for the above user in host machine
f=0x80 : File Transfer Protocol (FTP)
10.130.101.206 : Board IP
ffffff00 : Netmask
u=vxworks : Username on host machine
p=vxworks : Password for the above user in host machine
f=0x80 : File Transfer Protocol (FTP)
7. To boot VxWorks through USB, execute the following command:
run vxusbboot
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
15
Page 16
For sample output, refer Appendix A, USB Boot, on page 30.
2.5SPI Flash Boot
2.5.1Prerequisites
You should have:
TFTP server connectivity is required only when you want to copy new VxWorks image to
SPI Flash.
2.5.2Booting Procedure
The TFTP server should be configured and started in the connected PC. The VxWorks boot
Image file, vxWorks-2020.st or vxWorks-2010.st, should be made available at the
standard TFTP boot image path /tftpboot.
Booting VxWorks
16
Follow 1to 8 steps to copy VxWorks image from network to SPI Flash:
1.Power up the MVME2500 board.
By default, it provides the U-Boot prompt.
2.Set the environmental variables at the U-Boot prompt.
setenv ipaddr <Board ip address>
setenv serverip <TFTP server ip address>
setenv gatewayip <Gateway ip address>
setenv netmask <Netmask>
10.130.101.206 : Board IP
ffffff00 : Netmask
u=vxworks : Username on host machine
p=vxworks : Password for the above user in host machine
f=0x80 : File Transfer Protocol (FTP)
5.Initialize SPI Flash0 device:
sf probe 0
Note: To initialize SPI Flash 1, set the command as below:
sf probe 1
6.To erase SPI Flash memory region:
sf erase 0x200000 0x300000
Note: Maximum space available in SPI Flash for VxWorks image is 5MB (0x500000). Here it
is assumed that the VxWorks image size is less than 3MB(0x300000). If the VxWorks image
size is more than 3MB, then you can change the image size here accordingly.
7.Load the VxWorks image from network to the memory location (0x1000000):
tftpboot VxWorks.st
8.Write to SPI Flash 0 device at location (0x200000) from memory location(0x1000000):
sf write 0x1000000 0x200000 0x300000
Note: VxWorks image is loaded permanently to SPI flash 0. To load Vxworks image use SPI
Flash device from next time.
9.To boot directly from SPI Flash follow below steps:
a.Initialize SPI Flash0 device
sf probe 0
Note: To initialize SPI Flash 1, set the command as below:
sf probe 1
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
17
Page 18
Booting VxWorks
b.Copy VxWorks image from SPI Flash 0 location (0x200000) to memory location
e.To boot VxWorks through SPI Flash, execute the following command:
run vxboot
Before executing SPI erase/write commands, ensure that the SPI Flash offset location and
length are correct. Incorrect address can corrupt the U-Boot image.
18
For sample output, refer Appendix A, SPI Flash Boot, on page 31.
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 19
Building Board Support Package
3.1Building Procedure
The mvme2500_sp1.tar.gz contains VxWorks 6.8 BSP source files for the MVME2500
board.
Perform the following steps to build the BSP:
1. Extract the mvme2500_sp1.tar.gz to any working directory.
2. Start the Wind River VxWorks Workbench by executing the following command:
3. Open the Wind River VxWorks Workbench. Select File -> New -> VxWorks Image
Project.
Chapter 3
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
19
Page 20
4. Give a project name and then click Next.
Building Board Support Package
20
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 21
Building Board Support Package
5. Go to BSP and select mvme2500 from the dropdown list. Click Browse and point to
the location where you have extracted the BSP. Click Next.
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
21
Page 22
6. Select any configuration profile.
Building Board Support Package
22
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 23
7. Click Finish.
Building Board Support Package
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
23
Page 24
Building Board Support Package
8. Double-click mvme2500.h file. Enable MVME2500_P2020 or MVME2500_P2010
based on the MVME2500 board version.
24
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 25
Building Board Support Package
9. Right-click the project name which you have created, and select Build Project.
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
25
Page 26
Building Board Support Package
26
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 27
A Sample Output
A.1Network Boot
=> run vxboot
Speed: 100, full duplex
Using eTSEC1 device
TFTP from server 10.130.101.216; our IP address is 10.130.101.217
Filename 'vxWorks-2020.st'.
Load address: 0x1000000
Loading:
#################################################################
#################################################################
#################################################################
#########################################
done
Bytes transferred = 3460440 (34cd58 hex)
## Ethernet MAC address not copied to NV RAM
## Using bootline (@ 0x4200): motetsec(0,0)10.130.101.216:vxWorks
h=10.130.101.216 e=10.130.101.154:ffffff00 u=vxworks pw=vxworks
f=0x80
## Starting vxWorks at 0x00100000 ...
Target Name: vxTarget
Bulk Class Driver Successfully Initialized
usbCbiUfiDevInit() returned OK
CBI Class Driver Successfully Initialized
0x46c5850 (devConnect): ahciDrv called 0x46c3c40 0xa4100000
Instantiating /ahci00:2 as rawFs, device = 0x30001
->
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 29
A.2Disk Boot
=> run vxdiskboot
Loading file "vxWorks-2010.st" from scsi device 0:1 (sda1)
2346368 bytes read
## Ethernet MAC address not copied to NV RAM
## Using bootline (@ 0x4200): motetsec(0,0)10.130.101.216:vxWorks
h=10.130.101.216 e=10.130.101.250:ffffff00 u=vxworks pw=vxworks
f=0x80
## Starting vxWorks at 0x00100000 ...
Bulk Class Driver Successfully Initialized
usbCbiUfiDevInit() returned OK
CBI Class Driver Successfully Initialized
0xc92b50 (devConnect): ahciDrv called 0xc8fa20 0xa4100000
Found Bulk Device with 1 Logical Units at node 2
Instantiating /ahci00:1 as rawFs, device = 0x50001
->
A.3USB Boot
=> run vxusbboot
Sample Output
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
reading vxWorks-2010.st
3160632 bytes read
## Ethernet MAC address not copied to NV RAM
## Using bootline (@ 0x4200): motetsec(0,0)10.130.101.216:vxWorks
h=10.130.101.216 e=10.130.101.250:ffffff00 u=vxworks pw=vxworks
f=0x80
## Starting vxWorks at 0x00100000 ...
Target Name: vxTarget
Bulk Class Driver Successfully Initialized
usbCbiUfiDevInit() returned OK
CBI Class Driver Successfully Initialized
0x46a9250 (devConnect): vxbIntelAhciInstConnect pDev 0x36ae50
30
MVME2500 VxWorks 6.8 User Guide (6806800L66C)
Page 31
Sample Output
0x46a9250 (devConnect): ahciDrv called 0x46a7010 0xa4100000
Found Bulk Device with 1 Logical Units at node 2
Instantiating /ahci00:1 as rawFs, device = 0x50001
Loading symbol table from 10.130.101.216:vxWorks.sym ...done
The publications listed below are referenced in this manual. You can obtain electronic copies of
Artesyn Embedded Technologies - Embedded Computing publications by contacting your
local Artesyn sales office. For released products, you can also visit our Web site for the latest
copies of our product documentation.
1.Go to www.artesyn.com/computing.
2.Under SUPPORT, click TECHNICAL DOCUMENTATION.
3.Under FILTER OPTIONS, click the Document types drop-down list box to select the type of
document you are looking for.
4.In the Search text box, type the product name and click GO.
Artesyn Embedded Technologies, Artesyn and the Artesyn Embedded Technologies logo are trademarks and service marks of Artesyn Embedded Technologies, Inc.
All other product or service names are the property of their respective owners.