Tornado

C
Tornado Tools Reference
WTX Protocol
Back Ends
Communication between the target server and the Tornado tools is done via the
RPC/XDR mechanism. Tools’ requests and target servers’ answers or events follow the
formats defined by the Wind River Tool Exchange (WTX) messaging protocol. There is no
requirement for the Tornado tools and the target server to operate from the same host
machine. They may be distributed across a network.
If the -Wd option is specified, all WTX requests are logged in a log file. The default
behavior is to append log messages at the end of the log file (if it does not exists, it will be
created). If the -Wm option is also specified, the file size will be limited to the given value,
and written as a circular file: i.e. when this value is reached, the file is rewritten from the
beginning. If the file exists, it will be erased.
Note that a tool can be connected to more than one target server allowing for managing
data coming from several remote target systems.
The -Wf option can be used to filter a particular WTX request in the log file. The default
filter is set to “WTX_EVENT_GET” to avoid thousands of such request when a wind shell
version 1 is connected to the target server.
The target server’s back end is the intermediary for all communication with the target
agent. Thus, the back end must be designed to use whatever communication protocol and
transport layer the agent uses. Because not all agents can use the default protocol (WDB
over RPC/XDR) and transport layer (Ethernet), alternative back ends can be specified
explicitly. Custom back ends are also possible.
The following back ends are supported by Wind River Systems (see
$WIND_BASE/host/$WIND_HOST_TYPE/lib/backend):
wdbrpc (default)
The Tornado WDB RPC back end. It is the most frequently used, and supports either
Ethernet or serial connections. This back end supports either system-level or tasklevel
views of the target.
wdbpipe
This back end is to be used on all simulators. It is based on named pipes on UNIX
hosts and mail slots for windows hosts.
wdbserial
A version of the WDB back end supporting only serial hardware connection. Note
that in order to use this back end the serial connection should only use the “Tx”, “Rx”
and “Gnd” signals by default. When the -hfc (hardware flow control) option is used,
the “RTS”, “CTS” and “DTR” signals are also supported.
netrom
A proprietary communications protocol for NetROM, a networked ROM emulator
from Applied Microsystems Corporation.
loopback
A testing back end. This back end is not useful for connecting to targets; it is used
only to exercise the target server daemon during tests.
C
357