Tornado

2
Setup and Startup
The most common VxWorks communication path—both for server-agent
communications during development, and for applications—is IP networking
over Ethernet. That connection method provides a very high bandwidth, as well as
all the advantages of a network connection.
Nevertheless, there are situations where you may wish to use a non-network
connection, such as a serial line without general-purpose IP, or a NetROM
connection. For example, if you have a memory-constrained application that does
not require networking, you may wish to remove the VxWorks network code from
the target system during development. Also, if you wish to perform system-mode
debugging, you need a communication path that can work in polled mode.
VxWorks network interface drivers that do not support polled operations (older
versions) cannot be used as a connection for system-mode debugging.
Note that the target-server back end connection is not always the same as the
connection used to load the VxWorks image into target memory. For example, you
can boot VxWorks over Ethernet, but use a serial line connection to perform
system-mode debugging. You can also use a non-default method of getting the
run-time system itself into your target board. For example, you might burn your
VxWorks run-time system directly into target ROM, as described in VxWorks
Programmer’s Guide: Configuration and Build. Alternatively, you can use a ROM
emulator such as NetROM to quickly download new VxWorks images to the
target’s ROM sockets. Another possibility is to boot from a disk locally attached to
the target; see VxWorks Programmer’s Guide: Local File Systems. You can also boot
from a host disk over a serial connection using the Target Server File System; see
2.6.7 Booting a Target Without a Network, p.53. Certain BSPs may provide other
alternatives, such as flash memory. See the reference information for your BSP;
Help>Manuals contents>BSP Reference in the Tornado Launcher (or the file
wind/docs/BSP_Reference.html).
Connecting the target server to the target requires a little work on both the host and
target. The next few subsections describe the details for the standard target-server
back end connections.
2
2.5.1 Network Connections
A network connection is the easiest to set up and use, because most VxWorks
targets already use the network (for example, to boot); thus, no additional target
set-up is required. Furthermore, a network interface is typically a board’s fastest
physical communication channel.
When VxWorks is configured and built with a network interface for the target
agent (the default configuration), the target server can connect to the target agent
33