Tornado

4
Projects
In some cases (for example, if you are doing a BSP port for the first time), you may
want to start the agent before the kernel starts, and initialize the kernel under the
control of the Tornado host tools. To make that change, perform the following steps
when you configure VxWorks:
1. Choose a communication path that can support a system-mode agent
(NetROM or raw serial). The END communication path cannot be used as it
requires the system be started before it is initialized.
2. Change your configuration so that only WDB system debugging is selected (in
folder path development tool components>WDB agent components>select WDB
mode). By default, the task mode starts two agents: a system-mode agent and
a task-mode agent. Both agents begin executing at the same time, but the taskmode
agent requires the kernel to be running.
3. Create a configuration descriptor file called fileName.cdf (for example,
wdb.cdf) in your project directory that contains the following lines:
4
InitGroup usrWdbInit {
INIT_RTN usrWdbInit (); wdbSystemSuspend ();
_INIT_ORDER usrInit
INIT_BEFORE INCLUDE_KERNEL
}
This causes the project code generator to make the usrWdbInit( )call earlier in
the initialization sequence. It will be called from usrInit( ), just before the
component kernel is started. 8
After the target server connects to the system-mode target agent, you can resume
the system to start the kernel under the agent’s control. (See 5.2.6 Using the Shell for
System Mode Debugging, p.170 for information on using system mode from the
shell, and 7.5 System-Mode Debugging, p.261 for information on using it from the
debugger.
After connecting to the target agent, set a breakpoint in usrRoot( ), then continue
the system. The routine kernelInit( )starts the multi-tasking kernel with usrRoot( )
as the entry point for the first task. Before kernelInit( )is called, interrupts are still
locked. By the time usrRoot( ) is called, interrupts are unlocked.
Errors before reaching the breakpoint in usrRoot( ) are most often caused by a
stray interrupt: check that you have initialized the hardware properly in the BSP’s
8. The code generator for prjConfig.c is based on a component descriptor language that specifies
when components are initialized. The component descriptors are searched in a specific
order, with the project directory last in the search path. This allows the .cdf files in the
project directory to override default definitions in the generic .cdf files.
143