BSP Developer's Guide

6
Components
(2) comps/vxWorks/arch/arch
Contains all architecture-specific VxWorks components (or component
overrides).
(3) config/bsp
Contains all BSP-specific components.
(4) the project directory
Contains all other components.
Within a directory, to control alphanumeric order, a two digit number is prepended
to each .cdf file. Wind River reserves the first 50 numbers, that is 00xxxx.cdf
through 49xxxx.cdf. The remaining numbers, 50 through 99, are reserved for third
parties. The xx in the .cdf files above are placeholders for these numbers. (That is,
0n+1 overrides 0n.)
This method of setting precedence allows project, BSP, and CPU
architecture-specific overrides of generic components or parameters. If a BSP
provider wanted to change the maximum number of files that can be open
(NUM_FILES) to 75 from the default value of 50, it could be done in a BSP-specific
CDF, as follows:
6
Parameter NUM_FILES {
DEFAULT 75
}
If you are creating a new CDF, you must place it in the appropriate path, based on
the nature of the contents and the desired level of precedence. Your choices of
paths are listed above in the discussion about precedence:
– comps/vxWorks for generic VxWorks component descriptions only
– comps/vxWorks/arch/arch for architecture-specific VxWorks component
descriptions
– config/bsp for board-specific component descriptions
– the project directory for all other files
6.3.3 Defining a Component
This section describes the process of defining your own component. To allow for
the greatest flexibility, there is no convention governing the order in which
properties describe a component or the sequence in which CDL objects are entered
127