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.

VxWorks 5.5<br />

<strong>BSP</strong> Developer’s <strong>Guide</strong><br />

SEE ALSO Section<br />

INCORRECT:<br />

* RETURNS: OK, or ERROR<br />

* if the tick rate is invalid or<br />

* the timer cannot be set.<br />

The SEE ALSO section should be the last section of a reference-page entry.<br />

■<br />

■<br />

If the entry is a subroutine, refgen automatically includes the parent library in<br />

the SEE ALSO section.<br />

Do not cross-reference manual section numbers using the UNIX<br />

parentheses-plus-number scheme:<br />

CORRECT:<br />

SEE ALSO: sysLib, vxTas()<br />

INCORRECT:<br />

SEE ALSO: sysLib(1), vxTas(2)<br />

■<br />

In the SEE ALSO section, include cross-references to chapters of the VxWorks<br />

Programmer’s <strong>Guide</strong> or the Tornado User’s <strong>Guide</strong> by using the .pG macro or the<br />

.tG macro, respectively. The dot must be the first character on the effective line<br />

(for a subroutine section, refgen strips the star plus space); for example:<br />

* SEE ALSO: someLib, anotherLib,<br />

* .pG "Basic OS, Cross-Development,"<br />

* .tG "Setup and Startup"<br />

*/<br />

As this example illustrates, the cross-reference to another volume should come<br />

after cross-references to other libraries or subroutines. The .pG and .tG macros<br />

should only be used in SEE ALSO sections.<br />

Target Information Reference Page: target.nr<br />

A template for the target-information reference page is provided in<br />

target/config/templateCPU/target.nr. This reference entry always contains the<br />

subsections described below, and others as needed. Summary:<br />

NAME<br />

the name of the board<br />

186

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

Saved successfully!

Ooh no, something went wrong!