BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
To set appropriate values for these constants, consider the following:
END_LOAD_FUNC
Specify the name of your driver’s endLoad( ) entry point. For example, if your
driver’s endLoad( ) entry point is ln7990EndLoad( ), you would edit config.h
to include the line:
#define END_LOAD_FUNC ln7990EndLoad
END_LOAD_STRING
Specify the initialization string passed into muxDevLoad( ) as the initString
parameter.
You must also edit the definition of endTbl (a table in configNet.h that specifies
the ENDs included in the image) to include the following:
END_TBL_ENTRY endTbl
{
{ 0, LOAD_FUNC_0, LOAD_STRING_0, BSP_0, FALSE},
{ 1, LOAD_FUNC_1, LOAD_STRING_1, BSP_1, FALSE},
{ 0, END_TBL_END, 0, NULL},
};
The first number in each table entry specifies the unit number for the device. The
first entry in the example above specifies a unit number of 0. Thus, the device it
loads is deviceName0. The FALSE at the end of each entry indicates that the entry
has not been processed. After the system successfully loads a driver, it changes this
value to TRUE in the run-time version of this table. To prevent the system from
automatically loading your driver, set this value to TRUE.
Finally, you must edit your BSP’s config.h file to define INCLUDE_END. This tells
the build process to include the END/MUX interface. A this point, you are ready
to rebuild VxWorks to include your new drivers. When you boot this rebuilt image,
it calls muxDevLoad( ) for each device specified in the table in the order listed. 1
1. For a description of the parameters to muxDevLoad( ), see the appropriate reference entry.
222