02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9<br />

Documentation <strong>Guide</strong>lines<br />

The following example demonstrates our general style:<br />

.TS<br />

expand;<br />

l l l .<br />

Column Head 1 | Column Head 2 | Column Head 3<br />

_<br />

Row 1 Col 1 | Row 1 Col 2 | Row 1 Col 3<br />

Row 2 Col 1 | Row 2 Col 2 | Row 2 Col 3<br />

.TE<br />

Alternatively, in the target.nr file only you can instead use tab characters as the<br />

column separator in place of “|”.<br />

9.5.4 Processing<br />

9<br />

The steps below describe how to generate <strong>BSP</strong> documentation using the makefiles<br />

based on the templates delivered with the <strong>BSP</strong> Developer’s Kit.<br />

1. In target/config/bspname, check for the existence of the three required constants<br />

in Makefile:<br />

TARGET_DIR<br />

target directory name (bspname); for example, “mv147”<br />

VENDOR<br />

vendor name; for example, “Motorola”<br />

BOARD<br />

board model name; for example, “MVME147, MVME147S-1”<br />

2. Generate the reference pages by running:<br />

make man<br />

This does the following:<br />

– Builds an appropriate depend.bspname.<br />

– Runs sysLib.c through the C preprocessor to collect any drivers included<br />

by #include directives.<br />

– Runs refgen -mg.<br />

– Distributes HTML reference pages to the appropriate WIND_BASE/docs<br />

directories.<br />

193

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

Saved successfully!

Ooh no, something went wrong!