BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
lib/*.a: kernelInit( )
The kernelInit( ) routine initiates the multitasking environment and never returns.
It takes the following parameters:
– The application to be spawned as the “root” task, typically usrRoot( ).
– The stack size.
– The start of usable memory; that is, the memory after the main text, data, and
bss of the VxWorks image. All memory after this area is added to the system
memory pool, which is managed by memPartLib. Allocation for dynamic
module loading, task control blocks, stacks, etc., all come out of this region.
– The top of memory as indicated by sysMemTop( ). If a contiguous block of
memory is to be preserved from normal memory allocation, set the macro
USER_RESERVED_MEM in config.h to the amount of reserved memory
desired.
– The interrupt stack size. The interrupt stack corresponds to the largest amount
of stack space that could be used by any interrupt-level routine that might be
called (plus a safe margin for the nesting of interrupts).
– The interrupt lock-out level. For architectures that have a level concept, it is the
maximum level. For architectures that do not have a level concept, it is the
mask to disable interrupts. See the appropriate VxWorks Architecture
Supplement.
The kernelInit( ) routine calls intLockLevelSet( ), disables round-robin mode, and
creates an interrupt stack if supported by the architecture. It then creates a root
stack and TCB from the top of the memory pool, spawns the root task, usrRoot( ),
and terminates the usrInit( ) thread of execution. At this time, interrupts are
enabled; it is critical that all interrupt sources are disabled and pending interrupts
cleared.
usrConfig.c and bootConfig.c: usrRoot( )
For the generic VxWorks development environment, usrRoot( ) initializes the I/O
system, installs drivers, creates devices, and then sets up the network as
configured in configAll.h and config.h.
The usrRoot( ) routine calls memInit( ). Optionally, it calls memShowInit( ) and
usrMmuInit( ).
The routine sysClkConnect( ) is the first routine called in the BSP after the system
is multitasking. It immediately calls sysHwInit2( ). This is an opportune time for
36