📄 pc.html
字号:
<html><head><!-- /vobs/wpwr/docs/vxworks/bsp/pc386/pc.html - generated by refgen from target.nr --> <title> pc386/486 </title></head><body bgcolor="#FFFFFF"> <hr><a name="top"></a><p align=right><a href="libIndex.html"><i>BSP Reference : pc386</i></a></p></blockquote><h1>pc386/486</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote> <p><strong>pc386/486</strong> - PC 386/486</p></blockquote><h4>INTRODUCTION</h4><blockquote><p>This manual entry provides board-specific information necessary to run VxWorks for the pc386, pc486, pcPentium andpcPentiumpro BSPs. Before using a board with VxWorks, verify that the board runs in the factory configuration by using vendor-supplied ROMs and jumper settings and checking the RS-232 connection.<p>Please note that the pc386, pc486, pcPentium and pcPentiumpro BSPsare generic BSPs for generic PC-AT style motherboards. For best results, the board vendor's documentation should be usedin conjunction with this document.<p></blockQuote><h4>TrueFFS support</h4><blockQuote>This BSP supports the optional product TrueFFS for Tornado. To use TrueFFSinstall the product, add <b>sysTffs.o</b> to <b>MACH_EXTRA</b> in the Makefile and define<b>INCLUDE_TFFS</b> or <b>INCLUDE_PCMCIA</b> in <b>config.h</b>.<p>Defining <b>INCLUDE_PCMCIA</b> assumes that TrueFFS support is needed.<p>TrueFFS is set up to use the M-Systems DiskOnChip 2000 and two PCMCIAslots as a drive for use with dosFs.<p>If you wish to reboot from the DiskOnChip device change the finition for<b>SYS_WARM_TYPE</b> in <b>config.h</b> from <b>SYS_WARM_FD</b> to <b>SYS_WARM_TFFS</b>.<p></blockQuote><h4>BOOT ROMS</h4><blockQuote>The PC-AT generic boards use a boot diskette instead of boot ROMs. The boot diskette includes the boot sector (sector 0) and a DOS file systemcontaining a boot ROM image named <b>bootrom.sys</b>.The boot ROM image could be one of following:<p><table><tr valign=top><th align=left> </th><th align=left> </th><th align=left> Image is </th><th align=left> Image Loads</tr><tr valign=top><th align=left>Image Name </th><th align=left> Description </th><th align=left> Compressed </th><th align=left> Into</tr><tr><td colspan="4"><hr></tr><tr valign=top><td align=left>vxWorks_rom </td><td align=left> bootable vxWorks </td><td align=left> No </td><td align=left> High Memory</tr><tr valign=top><td align=left>vxWorks_rom_low </td><td align=left> bootable vxWorks </td><td align=left> No </td><td align=left> Low Memory</tr><tr valign=top><td align=left>vxWorks.st_rom </td><td align=left> bootable vxWorks.st </td><td align=left> Yes </td><td align=left> High Memory</tr><tr valign=top><td align=left>bootrom </td><td align=left> bootrom </td><td align=left> Yes </td><td align=left> Low Memory</tr><tr valign=top><td align=left>bootrom_uncmp </td><td align=left> bootrom </td><td align=left> No </td><td align=left> Low Memory</tr><tr valign=top><td align=left>bootrom_high </td><td align=left> bootrom </td><td align=left> Yes </td><td align=left> High Memory</tr><tr valign=top><td align=left></tr><tr><td colspan="4"><hr></tr></tr></table>VxWorks.st is a fully linked stand alone image which includes a target based shell, symbol table, and network interface. Note that the network interface is not initialized.<p>The boot ROM image must be copied into the floppy disk (a:) or the IDE disk (c:) using the DOS boot utility "mkboot.bat" or the VxWorks boot utilities "mkbootFd" for floppy disks or "mkbootAta" for hard disks. <p>For TrueFFS disks that appear as a hard disk using BIOS extentions the boot utility is "mkbootTffs".<p>The usage of the three VxWorks boot utilities is as follows:<p><pre>STATUS mkbootFd ( int drive, /* destination drive number: (0 - 3) */ int fdType, /* type of floppy disk: (0 - 1) */ char *in /* source file name */ )STATUS mkbootAta ( int ctrl, /* dest. controller number: (0 - 1) */ int drive, /* dest. drive number: (0 - 1) */ char *in /* source file name */ )STATUS mkbootTffs ( int drive, /* drive number: (0 - TFFS_MAX_DRIVES - 1) */ int removable, /* removable or not: (TRUE - FALSE) */ char *in /* name of file to read: "bootrom_uncmp" */ )</pre>All routines return OK on success and ERROR if there is an error whilecopying the image from the source onto the disk.<p></blockquote><h4>EXAMPLES</h4><blockquote><p><p>Example 1: Creating a boot floppy disk using mkbootFd:<p>The floppy disk is in drive 0 (or a:), the diskette is of type 0,and the image file name is <b>bootrom_uncmp</b>:<pre> -> mkbootFd 0, 0, "bootrom_uncmp"</pre>Example 2: Creating a bootable hard disk using mkbootFd:<p>The hard disk is on ATA controller 0 and is drive number 0(or c:). The image file name is <b>bootrom_uncmp</b>:<pre> -> mkbootAta 0, 0, "bootrom_uncmp"</pre>Example 3: Creating a bootable TrueFFS disk using mkbootTffs:<p>The TrueFFS disk is drive 0 (or c:), that is a non removable drive.The image file name is <b>bootrom_uncmp</b>:<pre> -> mkbootTffs 0, 0, "bootrom_uncmp"</pre>These boards do not have non-volatile RAM; thus, boot parameters are notpreserved whenever the system is powered off. However, static bootparameters can be set in the boot disk by setting the boot parameter line<b>DEFAULT_BOOT_LINE</b> in <b>config.h</b>.<p>For information on the use of the DOS utility "mkboot.bat" and how to boot VxWorks,please refer to the<i>VxWorks Programmer's Guide, Appendix D: Intel i386/i486. </i><p>To load VxWorks, and for more information, follow the instructions in the<i>Tornado User's Guide: Getting Started. </i><p>The <b>config.h</b> macro <b>INCLUDE_ADD_BOOTMEM</b> is used to memAddToPool some upper memory to a x86 low memory rom image. VxWorks low memory rom images run within a memory range from 0x8000 to 0xa0000. This restricts the size of the bootrom kernels memory pool available to drivers. This macro is used to make upper memory (above 1MB) available to driversfor the bootrom image only. It is defined in <b>config.h</b> and used in <b>sysLib.c</b>, <b><i><a href="./sysLib.html#sysHwInit2">sysHwInit2</a></i>( )</b>. It should be un-defined for x86 systems with memory less than 4MB. The default value is 0x00200000 (2MB). This value may be increased, but beware that the added pool does not overlap with the downloaded vxWorks image. If there is an overlap, then loading the vxWorks runtime image will corrupt the added memory pool.<p>To calculate the safe amount:<p><pre> (RAM_LOW_ADRS + vxWorks image size) < (memTopPhys + ADDED_BOOTMEM_SIZE)</pre> Where: <b>RAM_LOW_ADRS</b> == 0x00108000 and memTopPhys is from <b>sysLib.c</b>.<p></blockQuote><h4>Jumpers</h4><blockQuote>Refer to the board vendor's documentation.<p></blockquote><h4>FEATURES</h4><blockquote><p>Since this is a generic BSP for generic PC-AT style motherboards,your board may or may not have all of these features, and yourboard may have some features not discussed here.Your board vendor's documentation should be used in conjunction with this section.<p></blockQuote><h4>Supported Features</h4><blockQuote>Supported features are discussed below in the "Devices" sectionunder the "HARDWARE DETAILS" heading.<p></blockQuote><h4>Unsupported Features</h4><blockQuote><p>This BSP does not support ISA PnP. Such devices can be supported ifPnP is disabled and the device parameters (IO address, Memory address,IRQ, DMA channel etc) are set to match those in theBSP driver configuration. Ifthe device uses soft-configuration instead of jumpers, an appropriateutility program, usually available from the device manufacturer,should be used to set the device parameters.<p></blockQuote><h4>Feature Interactions</h4><blockQuote>Refer to the board vendor's documentation.<p></blockquote><h4>HARDWARE DETAILS</h4><blockquote><p>This section documents the details of the device drivers and boardhardware elements.<p></blockQuote><h4>Devices</h4><blockQuote>Drivers included with this BSP are for both on-board chipsand for separate adaptor cards that can be used with themotherboard.Refer to the vendor's documentation for both the motherboard andany adaptor cards used. Vendor documentation for on-boardchips may be necessary also.<p>Note that for all ISA drivers, the I/O base address,memory address, and interrupt level must match those in <b>config.h</b>or <b>pc.h</b>.<p>In the table below, drivers ending in the .c extension aredelivered in source form; the other drivers are deliveredin object form only.<p><table><tr valign=top><td align=left><b>i8250Sio.c</b> </td><td align=left> Intel UART tty driver</tr><tr valign=top><td align=left><b>i8237Dma.c</b> </td><td align=left> 8237 DMA driver</tr><tr valign=top><td align=left><b>pcConsole.c</b> </td><td align=left> console driver</tr><tr valign=top><td align=left><b>i8042Kbd.c</b> </td><td align=left> Intel keyboard controller</tr><tr valign=top><td align=left><b>i8048Kbd.c</b> </td><td align=left> Intel keyboard controller</tr><tr valign=top><td align=left><b>m6845Vga.c</b> </td><td align=left> Motorola M6845 VGA controller</tr><tr valign=top><td align=left><b>nec765Fd.o</b> </td><td align=left> nec765 floppy disk controller</tr><tr valign=top><td align=left><b>ataDrv.o</b> </td><td align=left> IDE/ATA hard disk controller</tr><tr valign=top><td align=left><b>ataShow.o</b> </td><td align=left> IDE/ATA hard disk controller show routines</tr><tr valign=top><td align=left><b>aic7880Lib.o</b> </td><td align=left> AHA-2940 PCI SCSI Adapter card</tr><tr valign=top><td align=left><b>i8253Timer.c</b> </td><td align=left> Intel 8253 timer driver</tr><tr valign=top><td align=left><b>loApicTimer.c</b> </td><td align=left> Intel PentiumPro's Local APIC Timer driver</tr><tr valign=top><td align=left><b>i8259Intr.c</b> </td><td align=left> Intel 8259 PIC</tr><tr valign=top><td align=left><b>loApicIntr.c</b> </td><td align=left> Intel PentiumPro's Local APIC</tr><tr valign=top><td align=left><b>ioApicIntr.c</b> </td><td align=left> Intel PentiumPro's IO APIC</tr><tr valign=top><td align=left><b>nullNvRam.c</b> </td><td align=left> null NVRAM library</tr><tr valign=top><td align=left><b>nullVme.c</b> </td><td align=left> null VMEbus library</tr><tr valign=top><td align=left><b>pcmciaLib.o</b> </td><td align=left> PCMCIA driver</tr><tr valign=top><td align=left><b>pcmciaShow.o</b> </td><td align=left> PCMCIA driver show routine</tr><tr valign=top><td align=left><b>if_ultra.o</b> </td><td align=left> SMC Elite16 network interface driver</tr><tr valign=top><td align=left><b>if_eex.o</b> </td><td align=left> Intel EtherExpress16 network interface driver</tr><tr valign=top><td align=left><b>if_elt.o</b> </td><td align=left> 3Com EtherLinkIII network interface driver</tr><tr valign=top><td align=left><b>if_ene.o</b> </td><td align=left> Novell/Eagle 2000 network interface driver</tr><tr valign=top><td align=left><b>if_esmc.o</b> </td><td align=left> Ampro Ethernet2(SMC 91c9x chip) network interface driver</tr><tr valign=top><td align=left><b>if_fei.o</b> </td><td align=left> EtherExpress PRO100B network interface driver</tr><tr valign=top><td align=left><b>fei82557End.o</b> EtherExpress PRO100B END/SENS driver</tr><tr valign=top><td align=left><b>ln97xEnd.o</b> AMD Am79C97X PCnet-FAST PCI END/SENS driver</tr><tr valign=top><td align=left><b>elt3c509End.o</b> 3COM 3C509 END/SENS driver</tr><tr valign=top><td align=left><b>el3c90xEnd.o</b> 3COM 3C90x END/SENS driver</tr><tr valign=top><td align=left><b>ultraEnd.o</b> SMC Elite Ultra END driver</tr><tr valign=top><td align=left><b>if_ene.o</b> </td><td align=left> Novell/Eagle 2000 END driver</tr><tr valign=top><td align=left></tr></tr></table>Below are some brief notes on each driver.For more details refer to theentry for each driver in the Libraries section of the <i>VxWorks Reference Manual </i><p>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -