Tornado

2
Setup and Startup
it sees to the VxWorks console. If this process does not provide enough debug
information to resolve your problems, contact WRS technical support for more
troubleshooting assistance.
2
2.6 Booting VxWorks
Once you have correctly configured your host software and target hardware,
establish a terminal connection from your host to the target, using the serial port
that connects the two systems. 4 For example, the following command starts a tip
session for the second serial port at 9600 bps:
% tip /dev/ttyb -9600
See your BSP documentation for information about the bps rate
(Help>Manuals contents>BSP Reference in the Tornado Launcher, or see the file
wind/docs/BSP_Reference.html).
You are now ready to turn on the target system power and boot VxWorks.
2.6.1 Default Boot Process
When you boot VxWorks with the default boot program (from ROM, diskette, or
other medium), you must use the VxWorks command line to provide the boot
program with information that allows it to find the VxWorks image on the host and
load it onto the target. The default boot program is designed for a networked
target, and needs to have the correct host and target network addresses, the full
path and name of the file to be booted, the user name, and so on. 5
When you power on the target hardware (and each time you reset it), the target
system executes the boot program from ROM; during the boot process, the target
uses its serial port to communicate with your terminal or workstation. The boot
4. Commonly available terminal emulators are tip, cu, and kermit; consult your host reference
documentation.
5. Unless your target CPU has nonvolatile RAM (NVRAM), you will eventually find it useful
to build a new version of the boot loader that includes all parameters required for booting
a VxWorks image (see 4.7 Configuring and Building a VxWorks Boot Program, p.144). In the
course of your developing an application, you will also build bootable applications (see
4.4 Creating a Bootable Application, p.127).
45