Abatron bdiWind PowerPC MPC8xx User Manual
                                                         | |
Contents
| 
bdi Windfor Tornado™, BDI2000 (MPC8xx/MPC5xx)User Manual 41© Copyright 1997-2007 by ABATRON AG Switzerland V 1.383.4 AGENT modeBecause 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 applicationmust be fully linked because no dynamic loading is supported.3.4.1 Target setupTarget initialization may be done at two places. First with the BDI configuration file, second within theVxWorks routine "sysHwInit". The setup in the configuration file must at least enable access to thetarget memory where the VxWorks core will be loaded. Disable the watchdog and setting the CPUclock rate should also be done with the BDI configuration file. Application specific initializations likesetting the timer rate are best located in the routine "sysHwInit".3.4.2 Configure VxWorksTornado 1.01:Use the VxWorks file "config.h" to scale your VxWorks core. Undefine INCLUDE_WDB and staticallylink all your modules with the VxWorks core. Don’t forget to create your tasks because they can’t becreated dynamically.Add the following lines to the VxWorks Makefile:ADDED_CFLAGS = -gMACH_EXTRA = myModule.oFor more information about building a bootable VxWorks application, see Tornado User’s Guidechapter 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 ofsysHwInit()./* 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. |
This manual is suitable for:
manualsdatabase
Your AI-powered manual search engine