VxWorks 5.5/5.5.1 Tornado 2.2/2.2.

1
BSP Rel. 2.0 for PrPMC6001 Installation Guide
P/N 6806800B52 Revision A September 2006

 Copyright 2006 Motorola Inc. All rights reserved. Printed in the United States of America.

Trademarks
Motorola and the stylized M logo are trademarks of Motorola, Inc., registered in the U.S. Patent and Trademark Office. IEEE is a registered trademark of the Institute for Electrical and Electronics Engineers, Inc. PICMG, CompactPCI, and the CompactPCI logo are registered trademarks and the PICMG logo is a trademark of the PCI Industrial Computer Manufacturers Group. MS-DOS, Windows95, Windows98, Windows2000 and Windows NT are registered trademarks and the logos are a trademark of the Microsoft Corporation. SolarisTM is a registered trademark and the logo is a trademark of Sun Microsystems, Inc. Intel and Pentium are registered trademarks and the Intel logo is a trademark of the Intel Corporation. PowerPC is a registered trademark and the PowerPC logo is a trademark of International Business Machines Corporation. VxWorks, Wind River Systems, CrossWind, Tornado, VxMP, VxSim, VxVMI, wind, WindC++, WindConfig, Wind Foundation Classes, WindNet, WindPower, WindSh, WindView and the Wind River Systems logo are registered trademarks of Wind River Systems, Inc. All other product or service names mentioned in this document are the property of their respective owners.

Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc., assumes no liability resulting from any omissions in this document, or from the use of the information obtained therein. Motorola reserves the right to revise this document and to make changes from time to time in the content hereof without obligation of Motorola 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 a Motorola website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise altered without the permission of Motorola, Inc. It is possible that this publication may contain reference to or information about Motorola 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 Motorola intends to announce such Motorola 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 Motorola, Inc. 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). Motorola, Inc. Embedded Communications Computing 2900 South Diablo Way Tempe, Arizona 85282

Contents
Using This Guide Related Documents ......................................................................................................... v Conventions ..................................................................................................................... v Abbreviations ................................................................................................................. vi Revision History ............................................................................................................ vii Documentation CHAPTER 1 Introduction

Overview ....................................................................................................................... 1-1 Supported Features........................................................................................................ 1-1 Delivered BSP Configuration........................................................................................ 1-2 CHAPTER 2 Installation

Installing the BSP.......................................................................................................... 2-1 Installation in the Solaris Environment:................................................................. 2-1 Installation in the Windows NT Environment: ...................................................... 2-1 Setup.log file .......................................................................................................... 2-2 Building the Binary ....................................................................................................... 2-3 Procedure for Single CPU Build from the IDE: .................................................... 2-3 Procedure for Single CPU Build from the Command Line Interface (CLI):....... 2-10 Procedure to Build bootrom image from the IDE:............................................... 2-10 Building the Testtool ............................................................................................ 2-11

ii

Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Creating a new project............................................................. Custom Configure VxWorks image ......................................... Step 1: Specify the location of the project ............................... Step 2: Specify the location of the BSP ................................... Building a bootable VxWorks image ........................................ Options for Developmental tools components ......................... Options for Boot Modes........................................................... Building the vxWorks_romCompress.bin image ...................... Building the vxWorks image .................................................... Build Menu............................................................................... Building bootrom image options .............................................. 3 3 4 4 5 6 7 8 9 10 11

iii

iv

Using This Guide

This Installation Guide is intended for users qualified in software engineering. Users must also have a working understanding of electronics, VxWorks/Tornado, and of the board supported by the BSP. This guide is to be referenced for VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001.

Related Documents
For more information, refer VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 Programmers Guide.

Conventions
Notation 57 0000000016 Description All numbers are decimal numbers except when used with the notations described below Typical notation for hexadecimal numbers (digits are 0 through F), e.g. used for addresses and offsets Same for binary numbers (digits are 0 and 1) Generic use of a letter Generic use of numbers Decimal point indicator is signaled Character format used to emphasize a word Character format used for on-screen output Character format used to characterize user input Character format for references, table, and figure descriptions Notation for selecting a submenu

00002 x n n.nn
Bold

Courier
Courier+Bold

Italics
File> Exit

Notation <text> [text] ... . . . .. : |

Note:

Description Typical notation used for variables and keys Typical notation for buttons Repeated item Omission of information from example/command that is not necessary at the time being Ranges Extents Logical OR No danger encountered. Pay attention to important information marked using this layout Possibly dangerous situation: slight injuries to people or damage to objects possible

!
Caution

Abbreviations
Abbreviation Description

BIB BSP CLI GUI IDE PCI PMC PPMC RTC

Board Information Block Board Support Package Command Line Interface Graphical User Interface Integrated Development Environment Peripheral Component Interconnect PCI Mezzanine Card Processor PCI Mezzanine Card Real Time Clock

vi

Revision History
Order Number Revision Date Description

224839410000

AA

June 2005

This is the first revision of the PrPMC-6001 VxWorks Installation and Use guide. Release 2.0 Release for Tornado 2.2.1

6806800B52

September 2006

Documentation
Information on booting VxWorks, on BSP configuration, features supported by the BSP is provided by the VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 Programmers Guide delivered with the BSP.

vii

viii

1Introduction

Overview
This document describes the installation of Tornado 2.2/2.2.1 (VxWorks) Board Support Package (BSP) Rel. 2.0 for PrPMC6001. The steps for setting up a project are also detailed in this chapter. Note: This VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 must be used only with Tornado 2.2. Motorola does not guarantee the compatibility of this BSP with any other Tornado versions. This VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 is not supported by Wind River Systems. Any problem should be directly reported to Motorola technical support.

Supported Features
VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 supports the following features of PrPMC6001: Motorola PowerPC 7448 processor Marvell MV64460 System Controller Support of up to 1 GB of total SDRAM. ATMEL and AT24C64A Serial EEPROM on I2C MAX6900 RTC support on the I2C bus PCI boot PCI Bus access One serial port Two Ethernet ports BIB RTC Disk On Chip

1-1

Delivered BSP Configuration

The default BSP configuration is given below. It is possible to adapt most of the configuration items by changing the defines in the file config.h and pmc280.h in the BSP directory. Support for 512 MB and 1 GB of memory. The upper 16 MB range of the total available memory is reserved as User Reserved Memory. Cache is configured in copy-back mode. Window to access PCI Bus Number 0 is opened. The sysclk is defined in pmc280.h (set by default to 133 Mhz) For information on how to adapt the configuration, refer to the VxWorks 5.5/5.5.1 / Tornado2.2/2.2.1 BSP Rel. 1.x for PrPMC6001 Programmers Guide.

1-2

2Installation

Installing the BSP

The default packaging of the BSP is a compressed tar file or zip file. You can download the .zip file or .tar file from the Motorola SMART page at: http://splus.forcecomputers.com/cgi-bin/user/account/services. The BSP Rel. 2.0 has been built under Tornado on Sun Solaris host machine. The tar file has the following directory:
PrPMC6001: which is the main target BSP directory

Installation in the Solaris Environment:

To install the BSP in the Solaris environment, use the compressed tar file. The following procedure explains the Solaris installation of a BSP contained in a file named, for example, bspFile.tar: 1. Uncompress the tar file to a temporary directory. For example, to uncompress the tar file to a temporary directory in a Solaris environment, use the following command.
tar -xvf <bspFile>.tar

2. Browse the untarred folders to locate and copy the PrPMC6001 directory to the $(WIND_BASE)/target/config directory path.
Note:

WIND_BASE is the directory where Tornado is installed.

Installation in the Windows NT Environment:

To install the BSP in the Windows environment, use the compressed tar file. The following procedure explains the Windows NT installation of a BSP contained in a file named, for example, bspFile.tar: 1. Uncompress the tar file to a temporary directory. 2. Browse the unzipped folders to locate and copy the PrPMC6001 directory to the $(WIND_BASE)/target/config folder path.
Note:

WIND_BASE is the directory where Tornado is installed.

2-1

Setup.log file
The Tornado configuration setup.log file which is automatically generated while installing the tools is shown below for reference.
07-Mar-03.13:53SETUP detected the following warning, and installation was continued: "WARNING: SETUP has detected that this machine is running on Solaris 2.5.x. Tornado does not officially support Solaris 2.5.x and Solaris 2.6." 07-Mar-03.14:00CD manufacturing time: Thu Oct 03 16:55:33 PDT 2002 07-Mar-03.14:00TDK-14620-ZC-01SETUP-2.2/home3/champ/tor2_2Ppc 07-Mar-03.14:00Tornado 2.2/VxWorks 5.5 for PowerPC 07-Mar-03.14:00SunOS surya 5.5.1 Generic_103640-20 sun4m sparc SUNW,SPARCstation-5 07-Mar-03.14:00100-22651-30Back End Developer's Toolkit 07-Mar-03.14:00100-22700-30Compiler - GNU: solaris x ppc 07-Mar-03.14:01100-22566-30Tornado Setup SDK 07-Mar-03.14:02100-22531-30Tornado Tools: solaris x ppc 07-Mar-03.14:35100-23549-30VxWorks: ppc40x 07-Mar-03.14:37100-23550-30VxWorks: ppc44x 07-Mar-03.14:37100-22535-30VxWorks: ppc6xx 07-Mar-03.14:38100-22537-30VxWorks: ppc74xx 07-Mar-03.14:39100-22536-30VxWorks: ppc7xx 07-Mar-03.14:40100-22539-30VxWorks: ppc82xx 07-Mar-03.14:40100-22538-30VxWorks: ppc8xx 07-Mar-03.14:41100-22533-30WindView: solaris x ppc 07-Mar-03.14:42 07-Mar-03.14:42licensed product: tornado 310 07-Mar-03.14:42licensed product: windview 320 07-Mar-03.14:42

2-2

Building the Binary

Procedure for Single CPU Build from the IDE:
Follow these procedures to create a project and build the image using the IDE: 1. Adopt the installation procedure for the relevant host OS (please refer see the Installing the BSP section on page 1) 2. Go to the IDE window and select File > New Project to create a new project as shown in Figure 1 Creating a new project on page -3.

Figure 1:

Creating a new project

3. Create a bootable VxWorks image that is custom configured as shown in Figure 2 Custom Configure VxWorks image on page -3.

Figure 2:

Custom Configure VxWorks image

2-3

4. Follow these steps to create a bootable VxWorks image: Step 1: Specify the location of the project (see Figure 3 Step 1: Specify the location of the project on page -4)

Figure 3:

Step 1: Specify the location of the project

Step 2: Specify the location of the BSP (see Figure 4 Step 2: Specify the location of the BSP on page -4). Check A BSP option and select the gnu Tool.

Figure 4:

Step 2: Specify the location of the BSP

2-4

Step 3: Click finish to create a bootable VxWorks image (see Figure 5 Building a bootable VxWorks image on page -5).

Figure 5:

Building a bootable VxWorks image

5. Click the [VxWorks] tab in the Workspace window, as shown in Figure 6, to view the components contained in the created project. The Workspace window displays the various components available under VxWorks and also the BSP configuration variants. Enable the following configuration options from the VxWorks Workspace window: Select development tool components > symbol table components > symbol table initialization components > select symbol table initialization. Right click select symbol table initialization option as shown in Figure 6, and select Configure select symbol table initialization. From the following options available on Properties pop-up screen [Component] tab: uncheck the downloaded symbol table option

2-5

 check the built-in symbol table option

Figure 6:

Options for Developmental tools components

Select Hardware > Bsp configuration variants > select boot mode. Right click select boot mode option, as shown in Figure 7, and select the Configure select symbol table initialization option. Check the

2-6

required boot mode, (bootrom boot or pci boot) from the Properties pop-up screen [Components] tab.

Figure 7:

Options for Boot Modes

6. Click the [Builds] tab in the Workspace window, as shown in Figure 8. To build the vxWorks_romCompress.bin image: Right click the default_romCompress option, as shown in Figure 8, and select the following: set default_romCompress as Active Build properties: Selecting this options brings up the Properties pop-up screen. Go to the [Rules] tab and select vxWorks_romCompress.bin from the drop-down menu.

2-7

 Build VxWorks_romCompress.bin: Selecting this options builds the vxWorks_romCompress.bin image.

Figure 8:

Building the vxWorks_romCompress.bin image

2-8

To build the vxWorks image: Right click the default option, as shown in Figure 9, and select the following: set default as Active Build Build vxWorks: Selecting this options builds the vxWorks image.

Figure 9:

Building the vxWorks image

7. The built images are now available in the project folder (see step 5) under folders default_romCompress (vxWorks_romCompress.bin image) and default (vxWorks image) respectively.

2-9

Procedure for Single CPU Build from the Command Line Interface (CLI):
Follow these procedures to create a project and build the image from the CLI: 1. Adopt the installation procedure for the relevant host OS (please referInstalling the BSP section on page -1). 2. Do a make clean operation. 3. Undefine the macro INCLUDE_DUAL_CPU_SUPPORT in the file config.h. 4. Based on your Tornado build requirements, select one of these options: To build BSP in Tornado 2.2.1 installation, enable macro defined in Makefile T2_2_1. To build BSP in Tornado 2.2 installation, disable macro defined in Makefile T2_2_1. 5. Define WINDVIEW_SUPPORT variable if Ethernet initialization is to be done while booting. Undefine this variable for booting from Disk on chip(DOC). 6. Select any one of the 2 boot modes available: Bootrom Boot: Define the macro INCLUDE_BOOTROM_BOOT in config.h. Pci Boot: Define the macro INCLUDE_PCI_BOOT in config.h. 7. Build all the images supported (for example, to build the vxWorks image use command 'make vxWorks').

Procedure to Build bootrom image from the IDE:

Note: The bootrom.bin image built from the IDE is equivalent to a CLI build. Ensure that the macro INCLUDE_DUAL_CPU_SUPPORT is defined for a Dual CPU build and undefined for a Single CPU build in config.h

1. Select Build > Build Boot ROM to build the bootrom.bin image.

Figure 10: Build Menu

2. Make the following selections (see Figure 11) from the Build Boot ROM pop-up screen: bootrom.bin: as the image to build

2-10

 gnu : as the tool

Figure 11: Building bootrom image options

Building the Testtool

Note:The testtool cannot be built from the IDE. It can only be built from the command line as shown below.

Procedure to Build the Testtool for Single CPU: 1. Define the macro PMC280_DUAL_CPU as FALSE in the tests\Makefile file. 2. Go to tests directory using the cd command. 3. Type make to create the library testtoolSingle.a

2-11

2-12