📄 c-config2.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Configuration and Build </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-config.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-config1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-config3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="87032">8.2 The Board Support Package (BSP)</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84404"> </a>The directory <i class="textVariable">installDir</i><b class="file">/target/config/</b><i class="textVariable">bspname</i> contains the <i class="term">Board Support Package (BSP)</i>, which consists of files for the particular hardware used to run VxWorks, such as a VME board with serial lines, timers, and other devices. The files include: <b class="file">Makefile</b>,<b class="file"> sysLib.c</b>, <b class="file">sysSerial.c</b>,<b class="file"> sysALib.s</b>, <b class="file">romInit.s</b>, <i class="textVariable">bspname</i><b class="file">.h</b>, and <b class="file">config.h</b>. </p><dd><p class="Body"><a name="84405"> </a>Wind River Systems BSPs conform to a standard, introduced with BSP Version 1.1. The standard is fully described in the <i class="title">Tornado BSP Developer's Kit for VxWorks</i>.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84407">The System Library</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84410"> </a>The file <b class="file">sysLib.c</b> provides the board-level interface on which VxWorks and application code can be built in a hardware-independent manner. The functions addressed in this file include:</p></dl><dl class="margin"><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84411"> </a>Initialization functions</li></ul></p><dl class="margin"><ul class="DashSingle2" type="circle"><li><a name="84412"> </a>initialize the hardware to a known state</li></ul><ul class="DashSingle2" type="circle"><li><a name="84413"> </a>identify the system</li></ul><ul class="DashSingle2" type="circle"><li><a name="84414"> </a>initialize drivers, such as SCSI or custom drivers</li></ul></dl><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84415"> </a>Memory/address space functions</li></ul></p><dl class="margin"><ul class="DashSingle2" type="circle"><li><a name="84416"> </a>get the on-board memory size</li></ul><ul class="DashSingle2" type="circle"><li><a name="84417"> </a>make on-board memory accessible to external bus (optional)</li></ul><ul class="DashSingle2" type="circle"><li><a name="84418"> </a>map local and bus address spaces</li></ul><ul class="DashSingle2" type="circle"><li><a name="84419"> </a>enable/disable cache memory</li></ul><ul class="DashSingle2" type="circle"><li><a name="84420"> </a>set/get nonvolatile RAM (NVRAM)</li></ul><ul class="DashSingle2" type="circle"><li><a name="84421"> </a>define the board's memory map (optional)</li></ul><ul class="DashSingle2" type="circle"><li><a name="84422"> </a>virtual-to-physical memory map declarations for processors with MMUs</li></ul></dl><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84423"> </a>Bus interrupt functions</li></ul></p><dl class="margin"><ul class="DashSingle2" type="circle"><li><a name="84424"> </a>enable/disable bus interrupt levels</li></ul><ul class="DashSingle2" type="circle"><li><a name="84425"> </a>generate bus interrupts</li></ul></dl><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84426"> </a>Clock/timer functions</li></ul></p><dl class="margin"><ul class="DashSingle2" type="circle"><li><a name="84427"> </a>enable/disable timer interrupts</li></ul><ul class="DashSingle2" type="circle"><li><a name="84428"> </a>set the periodic rate of the timer</li></ul></dl><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84429"> </a>Mailbox/location monitor functions (optional)</li></ul></p><dl class="margin"><ul class="DashSingle2" type="circle"><li><a name="84430"> </a>enable mailbox/location monitor interrupts</li></ul></dl></dl><dl class="margin"><dd><p class="Body"><a name="84431"> </a>The <b class="library">sysLib</b> library does not support every feature of every board: some boards may have additional features, others may have fewer, others still may have the same features with a different interface. For example, some boards provide some <b class="library">sysLib</b> functions by means of hardware switches, jumpers, or PALs, instead of by software-controllable registers.</p><dd><p class="Body"><a name="84432"> </a>The configuration modules <b class="file">usrConfig.c</b> and <b class="file">bootConfig.c</b> in <b class="file">config/all</b> are responsible for invoking this library's routines at the appropriate time. Device drivers can use some of the memory mapping routines and bus functions.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84435">Virtual Memory Mapping</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84437"> </a>For boards with MMU support, the data structure <b class="symbol_lc">sysPhysMemDesc</b> defines the virtual-to-physical memory map. This table is typically defined in <b class="file">sysLib.c</b>, although some BSPs place it in a separate file, <b class="file">memDesc.c</b>. It is declared as an array of the data structure <b class="symbol_UC">PHYS_MEM_DESC</b>. No two entries in this descriptor can overlap; each entry must be a unique memory space. </p><dd><p class="Body"><a name="84439"> </a>The <b class="symbol_lc">sysPhysMemDesc</b> array should reflect your system configuration, and you may encounter a number of reasons for changing the MMU memory map, for example: the need to change the size of local memory or the size of the VME master access space, or because the address of the VME master access space has been moved. For information on virtual memory mapping, as well as an example of how to modify <b class="symbol_lc">sysPhysMemDesc</b>, see <a href="c-vm3.html#84391"><i class="title">7.3 Virtual Memory Configuration</i></a>.</p></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/caution.gif"></td><td><hr><div class="CalloutCell"><a name="87042"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">CAUTION: </font></b></a>A bus error can occur if you try to access memory that is not mapped.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84453">The Serial Driver </a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84455"> </a>The file <b class="file">sysSerial.c</b> provides board-specific initialization for the on-board serial ports. The actual serial I/O driver is in the <i class="textVariable">installDir</i><b class="file">/target/src/drv/sio</b> directory. The library <b class="library">ttyDrv</b> uses the serial I/O driver to provide terminal operations for VxWorks.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84458">BSP Initialization Modules</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84459"> </a>The following files initialize the BSP:</p></dl><dl class="margin"><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84461"> </a>The file <b class="file">romInit.s</b> contains assembly-level initialization routines. </li></ul></p><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84463"> </a>The file <b class="file">sysALib.s</b> contains initialization and system-specific assembly-level routines. </li></ul></p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="84466">BSP Documentation</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84468"> </a>The file <b class="file">target.nr</b> in the <i class="textVariable">installDir</i><b class="file">/target/config/</b><i class="textVariable">bspname</i> directory is the source of the online reference entry for target-specific information. (For information on how to view these reference entries, see <i class="title">Tornado Getting Started</i>.) The <b class="file">target.nr</b> file describes the supported board variations, the relevant jumpering, and supported devices. It also includes an ASCII representation of the board layout with an indication of board jumpers (if applicable) and the location of the ROM sockets.</p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-config.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-config1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-config3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -