02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4<br />

Hardware <strong>Guide</strong>lines<br />

4.1 Introduction<br />

VxWorks runs on many architectures and targets from a wide variety of vendors,<br />

including custom and embedded hardware, VMEbus, Multibus, and PCIbus<br />

single-board computers, and workstation and PC mother boards. VxWorks can<br />

also boot from many different UNIX and Windows hosts using a variety of<br />

communication media.<br />

With the number of combinations that have been configured, Wind River has<br />

gathered sufficient experience to make recommendations in board design to best<br />

suit the VxWorks run-time environment. However, this document should not be<br />

used to determine the desirability of potential or existing ports. Many<br />

considerations essential to such determinations, such as cost analysis, time to<br />

market, and power and cooling requirements, are beyond the scope of this<br />

document.<br />

This chapter enumerates run-time functional requirements, distills features of<br />

important run-time components, and warns against potential pitfalls. The primary<br />

objective of this chapter is to assist developers in selecting appropriate boards and<br />

components for VxWorks operation. The following issues are discussed in this<br />

chapter:<br />

■<br />

■<br />

■<br />

■<br />

architectural considerations<br />

memory<br />

bus<br />

devices<br />

The particulars of how an individual architecture implements these considerations<br />

are discussed in the VxWorks Architecture Supplement document for each<br />

63

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!