BSP Developer's Guide

A
Upgrading a BSP for Tornado 2.0
A.3 Project Issues
The project facility is the major difference between Tornado 1.0.1 and Tornado 2.0.
For command-line operations, there is no difference between a Tornado 1.0.1 and
a Tornado 2.0 BSP. In Tornado 2.0, project builds are completely new, and they do
not involve files in target/config/all. The old usrConfig.c file has been pulled apart
into initialization groups and component configlettes, which are compiled and
linked together by the project build mechanism. Building with the project facility
differs greatly from building from the command line.
Building from the command line uses the BSP Makefile as well as the config.h and
configAll.h header files to control most of the configuration of the object being
built. When building from the project facility, the configuration is determined by
the project header files instead. Project building does not involve the BSP makefile.
If there is an item in config.h or configAll.h that is described to the project facility
through a CDF file, that item is controlled solely by the project information;
changes to config.h and configAll.h do not affect it, nor do they affect an existing
project.
Note, if there is something in config.h or configAll.h that the project tool is not
aware of, then the config.h and configAll.h selections will prevail during project
builds.
There are two methods for generating a default project from a BSP
■
Invoke the project facility wizard. To open the wizard, select the File>New
Project command from the menubar, or, if the Create Project or Open Workspace
window is open, select the New tab.
■
Use the command line, as follows:
A
make release
A.4 Product Contents
The most obvious change for version 1.2 BSPs is the product contents list, which is
provided in M. BSP Product Contents.
In Tornado 1.0.1, each BSP product carried a large number of driver files that were
also delivered as part of the base Tornado product. This redundancy caused
problems for customers, who were uncertain what version of a file was being used.
205