Tornado

Tornado 2.0
User’s Guide
■
■
■
■
WDB banner (INCLUDE_WDB_BANNER)
VIO driver (INCLUDE_WDB_VIO)
WDB task creation (INCLUDE_WDB_START_NOTIFY)
WDB user event (INCLUDE_WDB_USER_EVENT)
These components are in the development tool components>WDB agent
components>WDB agent services folder path.
You can also reduce the maximum number of WDB breakpoints with the
WDB_BP_MAX parameter of the WDB breakpoints component. And if you are using
a serial connection, you can set the INCLUDE_WDB_TTY_TEST parameter to
FALSE.
If you are using a communication path which supports both system and task mode
agents, then by default both agents are started. Since each agent consumes target
memory (for example, each agent has a separate execution stack), you may wish to
exclude one of the agents from the target system. You can configure the target to
use only a task-mode agent or only a system-mode with the WDP task debugging or
WDB system debugging options (which are in the folder path development tool
components>WDB agent components>select WDB mode).
Configuring the Target Agent for Exception Hooks
If your application (or BSP) uses excHookAdd( ) to handle exceptions, host tools
will still be notified of all exceptions (including the ones handled by your exception
hook). If you want to suppress host tool notifications, you must exclude the
component WDB exception notification. When this component is excluded, the target
server is not notified of target exceptions, but the target will still report them in its
console. In addition, if an exception occurs in the WDB task, the task will be
suspended and the connection between the target server and the target agent will
be broken.
Starting the Agent Before the Kernel
By default, the target agent is initialized near the end of the VxWorks initialization
sequence. This is because the default configuration calls for the agent to run in task
mode and to use the network for communication; thus, wdbConfig( ) must be
called after kernelInit( ) and usrNetInit( ). (See VxWorks Programmer’s Guide:
Configuration and Build for an outline of the overall VxWorks initialization
sequence.)
142