bdi
Wind
for Tornado™, BDI2000 (MPC8xx/MPC5xx)
User Manual
41
© Copyright 1997-2007 by ABATRON AG Switzerland
V 1.38
3.4 AGENT mode
Because the target agent runs within BDI, no debug support has to be linked to your VxWorks appli-
cation. There is also no need for any BDI specific changes in the VxWorks sources. Your application
must be fully linked because no dynamic loading is supported.
3.4.1 Target setup
Target initialization may be done at two places. First with the BDI configuration file, second within the
VxWorks routine "sysHwInit". The setup in the configuration file must at least enable access to the
target memory where the VxWorks core will be loaded. Disable the watchdog and setting the CPU
clock rate should also be done with the BDI configuration file. Application specific initializations like
setting the timer rate are best located in the routine "sysHwInit".
3.4.2 Configure VxWorks
Tornado 1.01:
Use the VxWorks file "config.h" to scale your VxWorks core. Undefine INCLUDE_WDB and statically
link all your modules with the VxWorks core. Don’t forget to create your tasks because they can’t be
created dynamically.
Add the following lines to the VxWorks Makefile:
ADDED_CFLAGS
= -g
MACH_EXTRA
= myModule.o
For more information about building a bootable VxWorks application, see Tornado User’s Guide
chapter 11.6 "Creating Bootable Applications".
Tornado II:
Use the VxWorks configuration utility and exclude all "development tool components".
Note:
If your vxWorks application needs information from the boot line (e.g. if you are using networking),
enter the following statement at the end of
sysHwInit().
/* init boot line for BDM debugging */
strcpy(sysBootLine, DEFAULT_BOOT_LINE);
This is necessary because there is no Boot-ROM which initializes the boot line variable in RAM.
