tgtsvr.html

vxworks相关论文

Using <b>-redirectShell</b>, if the shell cannot be redirected to the target 
server console, the characters typed in the console window won't be echoed, 
since that the shell's job to echo each typed characters. 
</ul>

<p>

<p>
</blockQuote><h4>Target Server File System (TSFS)</h4><blockQuote>
Other virtual I/O channels are available for general file I/O.  Target
tasks can use these channels to access the host's file system just
as they would access target connected file systems.  This type of
virtual I/O is referred to as the Target Server File System or TSFS.
<p>
The part of the host's file system visible to targets using the TSFS is 
specified with the <b>-R <i>root</i></b> option.  For example, if a root of
"/users/john" is specified, the target will only be able to access files
on the host's file system within and below /users/john.
<p>
By default, the host's files are accessible for reading only by target
processes using the TSFS.  To make the files accessble for reading and
writing, <b>-RW</b> should be specified.  When <b>-RW</b> is specified, access to
the target server is automatically restricted to host processes with the
same user ID as the target server, as if the <b>-L</b> option was specified.
<p>
</blockquote><h4>OPTIONS</h4><blockquote><p>
<dl>
<dt>
<b>-A | -Allsyms</b>
<dd>

Include all local and global core-file symbols in the target symbol table.
<p>
<dt>
<b>-B <i>backendName</i> | -Backend <i>backendName</i></b>
<dd>

Specify an alternative back end to communicate with the target
agent.  The default is a back end using the WDB protocol based on the
RPC/XDR mechanism.  Back end names can be deduced from the names of the files
in <b><$<b>WIND_BASE</b>>/host/<$<b>WIND_HOST_TYPE</b>>/lib/backend</b> (just remove the extension).
<p>
<dt>
<b>-Bd <i>fileName</i> | -Bdebug <i>fileName</i></b>
<dd>

Log every WDB request sent to the target agent in the specified file. If the 
file already exists, log messages will be appened to it (unless the <b>-Bm</b> 
flag is set).  Back ends that are not based on WDB RPC ignore this option.
<p>
<dt>
<b>-Bm <i>size</i> | -Bmax <i>size</i></b>
<dd>

Max size in bytes for the WDB logging file. If this flag is set, 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 begining. If the file
exists, it will be erased. So, be aware that if the target server restarts (due
to a target reboot, for example), the WDB log file will be reset. 
<p>
<dt>
<b>-b <i>linespeed</i> | -bps <i>linespeed</i></b>
<dd>

Specify the speed of a serial link used to communicate with a target agent.
The default value is 9600 bps.
<p>
<dt>
<b>-Br <i>number</i> | -Bresend <i>number</i></b>
<dd>

Specify the number of times the back end should attempt to repeat a
request to the target agent, if a transmission fails.  Default: three
retries.  Some back ends may ignore this option.
<p>
<dt>
<b>-Bt <i>timeout</i> | -Btimeout <i>timeout</i></b>
<dd>

Specify the timeout, in seconds, for back-end transactions with the target
agent.  Default: one second.  Some back ends may ignore this option.
<p>
<dt>
<b>-C | -Console</b>
<dd>

Start a console window.  Target tasks can perform I/O through this
window using virtual channel 0.
<p>
<dt>
<b>-c <i>fileName</i> | -core <i>fileName</i></b>
<dd>

By default, the target server gets the name of the core file (the
executable initially running on the target) from the target agent.  If
the target agent does not have this information (or if its information
is out of date), use this option to specify a path to the core file
explicitly.
<p>
<dt>
<b>-d device | -device <i>device</i></b>
<dd>

Specify the tty device used to communicate with a target agent.  The default
device is "/dev/ttya" on Solaris, "/dev/tty0p0" on HP-UX and "COM2" on Windows.
<p>
<dt>
<b>-display <i>hostName:0</i></b>
<dd>

(UNIX only) Specify the X server to contact in order to display the virtual 
console window.
<p>
<dt>
<b>-f <i>formatName</i> | -format <i>formatName</i></b>
<dd>

Name of the alternate object module format (for example, a.out or COFF) that
will be managed by the target server.
<p>
<dt>
<b>-h | -help</b>
<dd>

Print a help message summarizing <b><a href="./tgtsvr.html#top">tgtsvr</a></b> usage and options.
<p>
<dt>
<b>-hfc</b>
<dd>

Activate hardware flow control on a serial link using "RTS", "CTS" and "DTR"
signals. This option is available only with the <b>wdbserial</b> back end.
<p>
<dt>
<b>-L | -Lock</b>
<dd>

Restrict access to this target server to processes running under the
same user ID as the server.
<p>
<dt>
<b>-m <i>nbytes</i> | -memory <i>nbytes</i></b>
<dd>

Set the size of the agent memory pool cache managed by the target server
(default is 1 MB).
<p>
<dt>
<b>-n <i>serverName</i> | -name <i>serverName</i></b>
<dd>

Specify an alternative name for the target server (instead of the
default, based on the target's name). Target server's name should be constituted
by alphanumeric characters only.
<p>
<dt>
<b>-N | -Nosyms</b>
<dd>

Do not use a core file to build the target symbol table.
<p>
<dt>
<b>-p <i>portNumber</i> | -port <i>portNumber</i></b>
<dd>

Specify the UDP port number to communicate with a target agent when the <b>wdbrpc</b>
back end is used. The default port number is 0x4321.
<p>
<dt>
<b>-R <i>root</i></b>
<dd>

Establish the root of the host's file system visible to target processes
using the Target Server File System.
<p>
<dt>
<b>-redirectIO</b>
<dd>

Redirect the target global stdin, stdout and stderr in the target server. If
<b>-C</b> flag is not set, WTX events will be sent to all WTX tools when characters
come from the target.
<p>
<dt>
<b>-redirectShell</b>
<dd>

Start a console window with target shell stdin, stdout and stderr redirected in
it. This flag is valid only if <b>-C</b> flag is set.
<p>
<dt>
<b>-RW</b>
<dd>

Allow read and write access to host files by target processes using the 
Target Server File System.  When this option is specified, access to the
target server is restricted as if <b>-L</b> were also specified.
<p>
<dt>
<b>-s | -synchro</b>
<dd>

Synchronize target and host symbol tables.  The symbol table synchronization
facility must also be included in the target image; see the reference entry
for <b><a href="../../vxworks/ref/symSyncLib.html#top" >symSyncLib</a></b>.
<p>
<dt>
<b>-use_portmapper</b>
<dd>

Use the local portmapper to register the target server rpc services. This flag
<b>MUST</b> be set if tornado tools version 1.x have to connect to this target
server.
<p>
<dt>
<b>-u <i>fileName</i> | -users <i>fileName</i></b>
<dd>

Specify a file containing a list of authorized users.  Only users whose 
IDs appear as lines in this file will be able to connect tools to the
target server, unless the file contains the character <b>+</b> on a line by 
itself (which authorizes all users).
<p>
<dt>
<b>-V | -Verbose</b>
<dd>

Turn on the target server's verbose mode.  By default, the target
server is silent.  In verbose mode, it displays information, warning
and error messages on the standard output.
<p>
<dt>
<b>-v | -version</b>
<dd>

Identify the version of the target server.
<p>
<dt>
<b>-Wd <i>fileName</i> | -Wdebug <i>fileName</i></b>
<dd>

Log every WTX request sent to the target server in the specified file. If the 
file exists, log messages will be appened to it (unless the <b>-Wm</b> flag is set).
<p>
<dt>
<b>-Wf <i>request</i> | -Wfilter <i>request</i></b>
<dd>

Remove WTX <i>request</i> from the WTX log file. The default WTX log behaviour
is to log every requests the target server is servicing. This may lead to
a huge file. 
This flag allows to reduce the amount of information by giving a regular
expression to filter out WTX requests.
<p>
<dt>
<b>-Wm <i>size</i> | -Wmax <i>size</i></b>
<dd>

Max size in bytes for the WTX logging file. If this flag is set, 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 begining. If the file
exists, it will be erased. So, be aware that if the target server restarts (due
to a target reboot, for example), the WTX log file will be reset.  
</dl>

<p>

</blockquote><h4>EXAMPLES</h4><blockquote><p>
Start a target server on target with IP address equal to "147.108.108.1" in verbose mode and give it the name "myTargetServer".
<pre>    tgtsvr -V -name myTargetServer 147.108.108.1
</pre>
Display the flags handled by the "wdbpipe" backend.
<pre>    tgtsvr -h -B wdbpipe
</pre>
Start a target server named "myTargetServer" on VxWorks simulator number "0" 
with WDB request log going to file "/tmp/vxsim0Wdb.log"
<pre>    tgtsvr -B wdbpipe -Bd /tmp/vxsim0Wdb.log vxsim0 -n myTargetServer
</pre>
Specify a core file to the target server attached to a serial line
on COM2 at 38400 bauds (Windows). Note that the target name flag can be 
anything in this case it is only used to build the target server name.
<pre>    tgtsvr -c D:\tornado\target\config\mv1604\vxWorks -V -B wdbserial -b 38400 myTarget
</pre>
Start a target server with a target shell console on target called "arm7tBoard".
VxWorks should be configured to include the target shell for this to work.
<pre>    tgtsvr -C -redirectShell -V arm7tBoard 
</pre>
Start a target server in verbose mode on target called "arm7tBoard" with 
all target I/O redirected in the target server's console.
<pre>    tgtsvr -C -redirectIO -V arm7tBoard 
</pre>

</blockquote><h4>ENVIRONMENT VARIABLES</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WIND_BASE</b>
<dd>

root location of the Tornado tree.
<p>
<dt>
<b>WIND_REGISTRY</b>
<dd>

host on which the Tornado Registry daemon runs (see <b><a href="./wtxregd.html#top">wtxregd</a></b>). 
</dl>

<p>

</blockquote><h4>FILES</h4><blockquote><p>
The following resource files are required by the target server:
<dl>
<dt>
<b>$<b>WIND_BASE</b>/.wind/userlock</b>
<dd>

default authorization file (list of authorized users).
<p>
<dt>
<b>$<b>WIND_BASE</b>/host/resource/target/architecturedb</b>
<dd>

supported targets resource base. 
</dl>

<p>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./tgtsvr.html#top">tgtsvr</a></b>, <b><a href="./wtxregd.html#top">wtxregd</a></b>,  
<b><a href="./launch.html#top">launch</a></b>,  
<b><a href="./browser.html#top">browser</a></b>,  
<b><a href="./windsh.html#top">windsh</a></b>,  
<i>Tornado User's Guide </i>,  
<i>Tornado API Guide </i>
<p>

<p>

</body>
</html>