PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM PRELIMINARY ISSUE 2: DECEMBER 2000 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM CONTENTS 1 INTRODUCTION.......................................................................................................................... 1 1.1 1.2 1.3 1.4 2 3 PURPOSE ........................................................................................................................ 1 SCOPE ............................................................................................................................. 1 APPLICATION ................................................................................................................ 1 DOCUMENTATION ....................................................................................................... 2 FEATURES .................................................................................................................................... 3 GENERAL DESCRIPTION........................................................................................................... 4 3.1 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM ARCHITECTURE ... 4 3.1.1 3.1.2 FULL DEVELOPMENT KIT PLATFORM CONFIGURATION..................... 4 STANDALONE DEVELOPMENT KIT PLATFORM ..................................... 5 4 5 6 TARGET MACHINE HARDWARE CONFIGURATION............................................................. 6 REMOTE COMMAND MACHINE HARDWARE CONFIGURATION...................................... 7 SOFTWARE................................................................................................................................... 8 6.1 6.2 PMC-SIERRA DEVELOPMENT KIT DISTRIBUTION CD-ROM............................... 8 TARGET MACHINE SOFTWARE CONFIGURATION...............................................11 6.2.1 6.2.2 6.3 HARD DISK FORMATTING ..........................................................................11 TARGET PLATFORM DIRECTORY STRUCTURE......................................11 SOFTWARE INSTALLATION ON THE TARGET PLATFORM ................................ 12 6.3.1 6.3.2 6.3.3 6.3.4 MAKING THE VXWORKS BOOT FLOPPY................................................ 13 SOFTWARE BINARIES INSTALLATION .................................................... 13 SOFTWARE SOURCE CODE INSTALLATION ........................................... 15 SOFTWARE UPDATES ON THE TARGET SYSTEM.................................. 16 6.4 SOFTWARE ON THE REMOTE COMMAND MACHINE ........................................ 16 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE i PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 6.4.1 6.4.2 7 8 REMOTE COMMAND MACHINE TERMINAL CONFIGURATION ......... 16 OTHER SOFTWARE ON THE REMOTE COMMAND MACHINE............ 21 TARGET SYSTEM STARTUP ................................................................................................... 22 SYSTEM COMMANDS EXECUTION OVERVIEW ................................................................ 23 8.1 8.2 8.3 8.4 ABOUT VXWORKS SHELL........................................................................................ 23 COMMANDS INVOKED AT THE HOST (REMOTE) SYSTEM............................... 24 COMMANDS INVOKED FROM THE TARGET SYSTEM ....................................... 25 SYNCHRONOUS MODE OF OPERATION ................................................................ 25 9 10 11 12 13 14 15 16 17 18 19 GLOSSARY ................................................................................................................................. 26 APPENDIX A: VXWORKS SHELL SCRIPTS........................................................................... 27 APPENDIX B: CONTENT OF THE STARTUP.VXS................................................................. 29 APPENDIX C: MS-DOS FILES NEEDED FOR THE AUTOMATIC INSTALLATION........... 30 APPENDIX D: DRIVER MAKEFILE......................................................................................... 31 APPENDIX E: HOW TO RECREATE TORNADO 2 BUILD ENVIRONMENT ..................... 32 APPENDIX F: TARGET SYSTEM SELF-TEST ........................................................................ 33 APPENDIX G: TARGET CONSOLE APPLICATION LEVEL DEBUG MESSAGES.............. 34 APPENDIX H: AUTOEXEC.BAT EXAMPLE ........................................................................... 35 APPENDIX I: CONFIG.SYS EXAMPLE.................................................................................... 36 APPENDIX J: DRIVER SOURCE CODE AND BINARIES FILES LIST ................................. 37 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE ii PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM LIST OF FIGURES FIGURE 1 - FULL AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM CONFIGURATION4 FIGURE 2 - STANDALONE DEVELOPMENT KIT PLATFORM............................................................ 5 FIGURE 3 - AAL1GATOR-32/TEMUX DISTRIBUTION CD-ROM DIRECTORY STRUCTURE ....... 10 FIGURE 4 - DIRECTORY STRUCTURE ON THE TARGET MACHINE HARD DRIVE..................... 12 FIGURE 5 - SETTING UP HYPERTERMINAL PROPERTIES............................................................... 17 FIGURE 6 - HYPERTERMINAL PROPERTIES BOX............................................................................. 17 FIGURE 7 - COM PORT SETTINGS........................................................................................................ 18 FIGURE 8 - HYPERTERMINAL SETTINGS DIALOG........................................................................... 19 FIGURE 9 - ASCII SETUP DIALOG ........................................................................................................ 20 FIGURE 10 - SAVE THE PROPERTIES................................................................................................... 21 FIGURE 11 - USER COMMAND INVOCATION ................................................................................... 24 FIGURE 12 - EXAMPLE OF THE VXWORKS SHELL `LKUP' COMMAND ...................................... 27 FIGURE 13 - EXAMPLE STARTUP.VXS SCRIPT ................................................................................. 29 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE iii PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM LIST OF TABLES TABLE 1 - CONTENTS OF THE DEVELOPMENT KIT DISTRIBUTION CD-ROM ............................ 9 TABLE 2 - TARGET MACHINE HARD DRIVE DIRECTORY STRUCTURE COMPONENTS ......... 12 TABLE 3 - AAL1GATOR-32 SOURCE FILES LIST................................................................................ 38 TABLE 4 - TEMUX SOURCE FILES LIST.............................................................................................. 39 TABLE 5 - DUPLEX SOURCE FILES LIST ............................................................................................ 39 TABLE 6 - DUPLEX SOURCE FILES LIST ............................................................................................ 40 TABLE 7 - SHARED SOURCE FILES LIST ............................................................................................ 40 TABLE 8 - TORNADO 2 BSP ADD-ON FILES ....................................................................................... 40 TABLE 9 - EXECUTABLES LIST ............................................................................................................ 41 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE iv PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 1 INTRODUCTION The AAL1GATOR-32/TEMUX Development Kit Platform is the hardware platform on which the PMCSierra AAL1GATOR-32/TEMUX Development Kit board and application software can be tested and verified. This development platform enables PMC-Sierra's customers to dramatically reduce their application software development cycle. The AAL1GATOR-32/TEMUX Development Kit consists of: * * AAL1GATOR-32/TEMUX Development Kit Board AAL1GATOR-32/TEMUX Development Kit software and documentation on the accompanying CD-ROM Please, note that: * The Pentium-based PC is not supplied by PMC-Sierra. The PC platform and its hardware and software configuration are the user's responsibility. The WindRiver Tornado 2 integrated development environment is not supplied by PMC-Sierra. If the user wants to continue development on the VxWorks OS it is the user's responsibility to purchase and configure the Tornado 2 development environment. The source code on the AAL1GATOR-32/TEMUX Development Kit Platform CD-ROM is distributed "as is". There is no backward compatibility with the latest software releases and the distributed source code shall be used for informational purposes only. * * 1.1 Purpose This document provides a system specification for the AAL1GATOR-32/TEMUX Development Kit Platform. 1.2 Scope This document describes the hardware and software requirements of the AAL1GATOR-32/TEMUX Development Kit Platform without going into the specifics of the PMC-Sierra AAL1GATOR-32/TEMUX Development Kit board. This document describes the AAL1GATOR-32/TEMUX Development Kit Platform in the level of detail required to configure and run the system. This document contains a detailed software installation procedure. 1.3 Application This document is designed for embedded systems development based on the functionality of the PMCSierra devices included in this design, namely the PM73122 AAL1gator-32, PM8315 TEMUX, PM7350 S/UNI-DUPLEX and the PM4354 COMET-QUAD. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 1 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 1.4 Documentation The AAL1gator-32/TEMUX Development Kit CD includes a documentation directory containing relevant PMC-Sierra documentation. This documentation is current as of the publication date of this document. For up-to-date PMC-Sierra documentation refer to the PMC-Sierra website at www.pmc-sierra.com. The documents included on the CD are: Document PMC-1981419 AAL1gator-32 Datasheet PMC-1991271 PM73122 (AAL1gator-32) 32-Link CES/DBCES AAL1 SAR Short Form Data Sheet PMC-2000421 AAL1gator-32 Revision A Device Errata PMC-1980581 S/UNI-DUPLEX Dual Serial Link PHY Multiplexer Data Sheet PMC-1990147 PM7350 S/UNI-DUPLEX Dual Serial Link PHY Multiplexer Short Form Data Sheet PMC-1971264 PM8315 TEMUX High Density T1/E1 Framer with Integrated VT/TU Mapper and M13 Mux Short Form Data Sheet PMC-1981141 Technical Overview of the High Density T1/E1 Framer with Integrated VT/TU Mapper and M13 Multiplexer Telecom Standard Product PMC-1981125 High Density T1/E1 Framer with Integrated VT/TU Mapper and M13 Multiplexer Telecom Standard Product Data Sheet PMC-1990495 High Density T1/E1 Framer with Integrated VT/TU Mapper and M13 Multiplexer Telecom Standard Product Register Descriptions PMC-1990677 PM8315 TEMUX Datasheet/Register Description Errata PMC-1991444 AAL1gator-32/-8/-4 Driver User's Manual PMC-1990799 Dual Serial Link, Phy Multiplexer (S/UNI-DUPLEX) Driver Manual PMC-1990865 S/UNI-DUPLEX Driver Release Notes PMC-1991611 PM8315 TEMUX (T1/E1 Multiplexer) Driver Manual PMC-2000200 TEMUX Device Driver Release Notes PMC-1991820 AAL1gator-32/8/4 Programmer's Guide PMC-1991268 Temux Programmer's guide PMC-1990887 AAL1gator-32 CES Reference Design PMC-2000024 AAL1gator Product Family Technical Overview PMC-2000088 Network Convergence of Voice, Data, and Video White Paper PMC-1981025 S/UNI-VORTEX and S/UNI-DUPLEX Technical Overview PMC-2000091 COMET-QUAD Short Form Data Sheet PMC-1990315 COMET-QUAD Long Form Data Sheet PMC-2000151 COMET-QUAD Programming Guide Issue 5 1 3 5 2 3 1 5 3 7 1 1 3 1 1 1 1 2 1 1 2 1 5 1 PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 2 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 2 FEATURES * Jump-start development. Right out of the box the user can test the features of the AAL1GATOR32/TEMUX Development Kit board and the application software supplied by PMC-Sierra. With the supplied software drivers and the evaluation board the customers can immediately start developing their own applications. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 3 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 3 3.1 GENERAL DESCRIPTION AAL1GATOR-32/TEMUX Development Kit Platform Architecture There are two types of configurations where the AAL1GATOR-32/TEMUX Development Kit Platform can be used: * * Standalone (reduced configuration) Full These two configurations are discussed below. 3.1.1 Full Development Kit Platform Configuration The full development platform consists of two basic components: * * Target Machine Remote Command Machine Startup Scripts Target Application Basic Test Scripts Logging TCL Test Scripts Terminal Programs Logging Development AAL1GATOR-32 Eval Board Keyboard Target Machine Serial (RS232) Link Remote Command Machine Keyboard Figure 1 - Full AAL1GATOR-32/TEMUX Development Kit Platform Configuration The target machine acts as the hardware support for the PMC-Sierra AAL1GATOR-32/TEMUX Development Kit Board. It is possible for the target machine alone to be used to test the basic functionality and features of the chipset on the board. To extend the testing and development capabilities of the basic system, the Remote Command Machine is required. The communication link is synchronous, serial RS232. The Remote Command Machine can then be used with more powerful tools (i.e. TCL scripting) for testing and development over and above what's available on the Target Machine. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 4 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM In this configuration it is not necessary to have a monitor and keyboard attached to the Target Machine since all the commands can be entered on the Remote Command Machine. In order to establish communication, the user must connect the remote and target machine via a null modem cable. Using the serial link a user can send the predefined set of commands (supported by the application software supplied by PMC-Sierra or by the user) and the commands will be executed on the target system. The application software will send the responses back to the Remote Command Machine. 3.1.2 Standalone Development Kit Platform The Standalone Development Kit Platform consists of one component: * Target Machine Startup Scripts Target Application Basic Test Scripts Logging AAL1GATOR-32 Eval Board Keyboard Target Machine Figure 2 - Standalone Development Kit Platform This is a minimal configuration of the Development Kit Platform. This standalone system has reduced capabilities compared to the full version. The full functionality of the AAL1GATOR-32/TEMUX Development Kit Board and the supplied software can still be tested with the minimal configuration. In this system configuration a monitor and keyboard are necessary. The commands can be entered on the target machine keyboard and the results are visible to the user on the target machine display. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 5 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 4 TARGET MACHINE HARDWARE CONFIGURATION The target machine must have the following minimal hardware configuration: * * Intel Pentium based motherboard (minimum 233MHz) with one free PCI slot (for the development kit board). One available serial communication port (required for communication with the Remote Command Machine) capable of sending and receiving data at a minimum of 9600 bps. The second serial communication port is optional. Standard 1.44 MB Floppy Disk Drive CD-ROM Drive IDE Hard Disk Drive. Recommended size is 2.1GB. Keyboard VGA Video Adapter VGA Compatible Monitor * * * * * * Network card is optional. There is no software network support on the target platform supplied by PMCSierra. If required, the user can install the network support software. Video Graphic Capabilities. There is no requirement for any graphical capabilities of the video card on the target machine since the system will run in text mode. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 6 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 5 REMOTE COMMAND MACHINE HARDWARE CONFIGURATION In order to establish the communication with the target system the Remote Command Machine must have: * One free standard serial communication port capable of sending and receiving data at minimum of 9600 bps. The second serial communication port is optional. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 7 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 6 SOFTWARE The current version of all PMC-Sierra software device drivers has been developed for only one operating system - VxWorks. Therefore, this document will restrict the examples and software installation procedures to cases that involves only the VxWorks operating system. The target platform software installation and configuration has to be done locally. In other words, the full target platform including keyboard and monitor is required during this process. 6.1 PMC-Sierra Development Kit Distribution CD-ROM The Development Kit distribution CD-ROM contains all the necessary documentation and software required for the target platform. Once installed the target system is fully functional and ready to run. Directory Item (D:) /DOC /SOFTWARE /SOFTWARE/ TARGET /SOFTWARE/ TARGET/BIN /SOFTWARE/ TARGET/BIN/OS /SOFTWARE/ TARGET/BIN/OS/ VxWorks /SOFTWARE/ TARGET/BIN/ DRV /SOFTWARE/ TARGET/BIN/ SCRIPTS /SOFTWARE/ TARGET/ SOURCE /SOFTWARE/ TARGET/ SOURCE/AL32 /SOFTWARE/ TARGET/ SOURCE/TEMUX /SOFTWARE/ TARGET/ SOURCE/ DUPLEX /SOFTWARE/ Comment Root directory of the distribution CD-ROM. Contains INSTALL.BAT. Running this file will start automatic installation of the required software binaries onto the target system hard drive. Location of all the required documentation. Root directory of the distributed software. Root directory of the software for the target system. Root directory of the software binaries required for the target system. Root directory of the target system operating system. Directory where the VxWorks operating system and its supporting binaries is located. Directory where the PMC-Sierra software chip drivers are located. Directory where all of the VxWorks shell scripts are located. Root directory of the source code. AAL1GATOR-32 chip driver source code root directory. It is in the form of a ZIP file. The ZIP file contains directory structure of the driver source code. TEMUX chip driver source code root directory. It is in the form of a ZIP file. The ZIP file contains directory structure of the driver source code. DUPLEX chip driver source code root directory. It is in the form of a ZIP file. The ZIP file contains directory structure of the driver source code. COMET-QUAD chip driver source code root directory. It is in the form of a ZIP file. The ZIP PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 8 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM Directory Item TARGET/ SOURCE/ COMETQ /SOFTWARE/ TARGET/ SOURCE/ SHARED /SOFTWARE/ TARGET/ SOURCE/OS /SOFTWARE/ TARGET/ SOURCE/OS/ VxWorks /SOFTWARE/ TARGET/ SOURCE/OS/ VxWorks/BSP /SOFTWARE/ TARGET/ UTIL/ MKVXBOOT Comment file contains directory structure of the driver source code. Shared components source code root directory. It is in the form of a ZIP file. The ZIP file contains directory structure of the driver source code. Root directory of the operating system source distribution. Currently, only VxWorks is supported. Root directory of the VxWorks operating system source distribution. Location of the add-on source code for the Tornado 2 development system Board Support Package (BSP). Location of the utility software for making VxWorks boot floppy disk. Table 1 - Contents of the Development Kit Distribution CD-ROM ZIP/UNZIP utilities are downloadable for free from a number of Internet sites. ZIP files on the distribution CD-ROM (like the driver source code) contains a directory structure. The user should unzip the files into the root directory and the necessary directory structure will be created. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 9 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM (D:) DOC SOFTWARE TARGET BIN OS VxWorks DRV SCRIPTS SOURCE DRV AL32 TEMUX DUPLEX COMETQ SHARED OS VxWorks UTIL MKVXBOOT BSP Figure 3 - AAL1GATOR-32/TEMUX Distribution CD-ROM Directory Structure PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 10 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 6.2 Target Machine Software Configuration The software that is required for the system startup and operation must be located on the target machine hard drive (with the exception of the boot disk). Since VxWorks is a real-time operating system there are not too many hard disk formats that this OS can support. One that users might find easy to install and use is FAT-16. This is also a format that operating systems like MS-DOS and MS Windows can recognize. It is assumed that the user is using a FAT-16 disk format. 6.2.1 Hard Disk Formatting In order to use the hard drive and install the new software the hard disk must be formatted. The fastest way to do this is to use MS-DOS version 6 or higher and follow the MS-DOS installation procedure from the Microsoft Corporation DOS User's Manual. The MS-DOS operating system has been chosen because of its fast boot time, fast installation time and small size. MS-DOS does not have to be installed, but the user may find some MS-DOS external commands useful during the development process (such as the DOSKEY command that repeats the commands on the command prompt). MS-DOS is required for automatic software installation on the target system. The file system on the hard drive must be FAT-16. VxWorks only recognizes the primary FAT-16 partition. The other partitions (if installed) may be used for other purposes. 6.2.2 Target Platform Directory Structure A minimal fixed directory structure has to be maintained on the target machine as shown in Figure 4. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 11 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM (C:) DOS TEMP VXWORKS KERNEL DRV SCRIPTS LOGS Figure 4 - Directory structure on the target machine hard drive Directory Item (C:) /DOS /TEMP /VXWORKS /VXWORKS/ KERNEL /VXWORKS/DRV /VXWORKS/ SCRIPTS /VXWORKS/LOGS Comment Root directory of the FAT-16 file system. Directory where the Disk Operating System (DOS) might be installed. Temporary directory. Root directory of the VxWorks operating system. Directory where VxWorks kernel and VxWorks supporting binaries should be installed. Directory where PMC-Sierra software chip drivers and supporting binaries should be installed. Directory where VxWorks shell script files should be installed. The most important script is startup.vxs which executes automatically during the system startup. This script must be located in this directory. Directory where application log dumps might be stored. Table 2 - Target machine hard drive directory structure components Normally the VxWorks directory structure will be created during automatic software installation. 6.3 Software Installation On the Target Platform Once the target platform has been prepared properly the binaries supplied by PMC-Sierra have to be installed onto the target platform hard drive and the source code supplied by PMC-Sierra has to be installed onto the software development platform. Note that a MS-DOS CD-ROM driver must be installed properly on the target machine prior to automatic software installation. PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS' INTERNAL USE 12 PRELIMINARY SYSTEM DESIGN SPECIFICATION PMC-2001068 ISSUE 2 AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM AAL1GATOR-32/TEMUX DEVELOPMENT KIT PLATFORM 6.3.1 Making the VxWorks Boot Floppy The target system boots up off the VxWorks boot floppy. All the necessary files and utilities necessary to make a VxWorks boot floppy are located on the AAL1GATOR-32/TEMUX distribution CD-ROM. The following steps should be taken in order to make a bootable VxWorks floppy: 1. 2. Put the AAL1GATOR-32/TEMUX distribution CD-ROM into your host machine CD-ROM drive. Open Windows Explorer and change the CD-ROM directory to /SOFTWARE/TARGET/UTIL/MKVXBOOT . Put the blank floppy disk into your floppy drive and label it as "VxWorks Hard Disk Boot". Make sure the floppy disk is not write protected. Doubleclick on mvxwbd.bat file. This action will open MS-DOS window and start making the bootable VxWorks floppy. Once the MS-DOS window has been closed, the VxWorks bootable floppy disk is ready and the user can remove it from the host machine floppy drive. The file bootrom.sys should exist on the bootable floppy. 3. 4. 5. Note: the MS-DOS window may not close automatically after the MS-DOS task has been finished. In that case the MS-DOS box will have "Finished..." at its top left corner. The user should close the window manually. 6.3.2 Software Binaries Installation 1. 2. 3. 4. Reboot the target platform in MS-DOS. Insert the distribution CD-ROM into the target machine CD-ROM drive. Set the current directory to D:\ (assuming that CD-ROM drive letter is D:). Run the install.bat
We use cookies to deliver the best possible
web experience and assist with our advertising efforts. By continuing to use
this site, you consent to the use of cookies. For more information on
cookies, please take a look at our Privacy Policy.