Tornado

Tornado 2.0
User’s Guide
! WARNING: Use of the project facility for configuring and building applications is
largely independent of the methods used prior to Tornado 2.0 (which included
manually editing the configuration files config.h or configAll.h). The project
facility provides the recommended and simpler means for configuration and
building, although the manual method may still be used (see VxWorks
Programmer’s Guide: Configuration and Build).
To avoid confusion and errors, the two methods should not be used together for
the same project. The one exception is for any configuration macro that is not
accessible through the project facility GUI (which may be the case, for example, for
some BSP driver parameters). You can use a Find Object dialog box to determine if
a macro is accessible or not (see Finding VxWorks Components and Configuration
Macros, p.118). If it is not accessible through the GUI, a configuration file must be
edited, and the project facility will implement the change in the subsequent build.
The order of precedence for determining configuration is (in descending order):
project facility
config.h
configAll.h
For any macro that is exposed through the project facility GUI, changes made after
creation of a project in either of the configuration files will not appear in the project.
Terminology
There are several key terms that you must understand before you can use the
project facility effectively:
Downloadable application
A downloadable application consists of one or more relocateable object
modules, 1 which can be downloaded and dynamically linked to VxWorks, and
then started from the shell or debugger. A novel aspect of the Tornado
development environment is the dynamic loader, which allows objects to be
loaded onto a running system. This provides much faster debug cycles
compared with having to rebuild and re-link the entire operating system. A
downloadable application can consist of a single file containing a simple “hello
1. The text and data sections of a relocateable object module are in transitory form. Because of
the nature of a cross-development environment, some addresses cannot be known at time
of compilation. These sections are modified (relocated or linked) by the Tornado objectmodule
loader when it inserts the modules into the target system.
92