wtdoc.html

vxworks相关论文

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxMemWidthRead <i>address</i> <i>nBytes</i> [<i>width</i>]
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
The block of target memory starting at <i>address</i> and spanning <i>nBytes</i> is
read on <i>width</i> bytes large into a memory block.  The handle of the memory 
block is returned. <i>width</i> can be set to 1 (byte), 2 (word) or 4 (long
word), by default <i>width</i> is set to 4.
<p>
</blockquote><h4>CAVEAT</h4><blockquote><p>
Because this request is not implemented on WDB side, wtxMemWidthRead uses
<b><a href="../wdbpcl/wdb.html#WDB_MEM_READ" >WDB_MEM_READ</a></b> and the <i>width</i> parameter is simply ignored.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
A memory block handle.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_MEM_WIDTH_READ" >WTX_MEM_WIDTH_READ</a></b>, wtxtcl, wtxMemWidthWrite, memBlockCreate, memBlockGet

<hr>
<a name="wtxMemMove"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxMemMove</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxMemMove</strong> - move a block of memory on the target</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxMemMove <i>source</i> <i>destination</i> <i>nBytes</i>
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
The block of memory starting at <i>source</i> and spanning <i>nBytes</i> is moved
to <i>destination</i>.  Note that the source and destination buffers may
overlap.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
WTX Status.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_MEM_MOVE" >WTX_MEM_MOVE</a></b>, wtxtcl, wtxMemRead, wtxMemWrite

<hr>
<a name="wtxRegsGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxRegsGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxRegsGet</strong> - read a block of register data from the target</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxRegsGet <i>CONTEXT_TYPE</i> <i>contextId</i> <i>REG_SET_TYPE</i> <i>offset</i> <i>nBytes</i>
</pre>

</blockquote><h4>DESCRIPTION </h4><blockquote><p>
This command reads a section of raw (target format) register data for the
given context. <i>CONTEXT_TYPE</i> is one of the values given in the entry for
<b><a href="../wtxpcl/wtx.html#top" >WTX</a></b> in the
<i>API Reference Manual: WTX Protocol </i>.
(Use wtxEnumInfo with an argument of <b>CONTEXT_TYPE</b> for
information on possible types).  Typically the type is <b>CONTEXT_TASK</b>.
<i>ContextId</i> is the ID of the task whose register block is to be read.
<i>REG_SET_TYPE</i> is the type of register block to read (usually <b>REG_SET_IU</b>
or <b>REG_SET_FPU</b>; use wtxEnumInfo with an argument of <b>REG_SET_TYPE</b> for
information on other possible types).  <i>Offset</i> and <i>nBytes</i> delimit the
section of the register block to read.  The layout of the register blocks
is dependent on the target kernel; for VxWorks, these are the same as
the <b>REG_SET</b> layout in the task control block.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
A memory-block handle with the uploaded register data.  See memBlockCreate
for information about memory block handles.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_REGS_GET" >WTX_REGS_GET</a></b>, wtxtcl, wtxRegsSet, memBlockCreate

<hr>
<a name="wtxRegsSet"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxRegsSet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxRegsSet</strong> - write a block of register data to the target</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxRegsSet <i>CONTEXT_TYPE</i> <i>contextId</i> <i>REG_SET_TYPE</i> <i>offset</i> <i>nBytes</i> <i>blockId</i>
</pre>

</blockquote><h4>DESCRIPTION </h4><blockquote><p>
This command writes a section of raw (target format) register data for 
the given context. <i>CONTEXT_TYPE</i> is one of the values given in the entry
for <b><a href="../wtxpcl/wtx.html#top" >WTX</a></b> in the
<i>API Reference Manual: WTX Protocol </i>.
(Use wtxEnumInfo with an argument of <b>CONTEXT_TYPE</b> for information
on possible types).  Typically the type is <b>CONTEXT_TASK</b>.  <i>ContextId</i> is
the ID of the task whose register block is to be written.  <i>REG_SET_TYPE</i>
is the type of register block to write (usually <b>REG_SET_IU</b> or <b>REG_SET_FPU</b>;
use wtxEnumInfo with an argument of <b>REG_SET_TYPE</b> for information on other
possible types).  <i>Offset</i> and <i>nBytes</i> delimit the section of the
register block to write.  The layout of the register blocks is dependent
on the target kernel; for VxWorks, these are the same as the <b>REG_SET</b>
layout in the task control block.  The register block receives data from
the memory block <i>blockId</i>.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<dl>
<dt>
block not found
<dd>

The block ID does not exist.
<p>
<dt>
block too small to write that many registers
<dd>
 The block is too small for the requested data.
<p>
</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, * <b><a href="../wtxpcl/wtx.html#WTX_REGS_SET" >WTX_REGS_SET</a></b>, wtxtcl, wtxRegsSet, memBlockCreate

<hr>
<a name="wtxEventpointAdd"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxEventpointAdd</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxEventpointAdd</strong> - add an agent eventpoint</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxEventpointAdd <i>EVENT_TYPE</i> <i>eventArg0</i> [...<i>eventArgN</i>] <i>CONTEXT_TYPE</i> <i>contextId</i> <i>ACTION_TYPE</i> <i>actionArg</i> <i>callRtn</i> <i>callArg</i>
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This function adds an agent eventpoint.  <i>DETECTION_TYPE</i>, 
<i>EVENT_TYPE</i>, <i>CONTEXT_TYPE</i>,
and <i>ACTION_TYPE</i> are all WTX constants described in the 
<i>WTX Protocol </i>
reference. Use wtxEnumInfo with one of the constants to find out what
values you can supply in Tcl.  For example:
<p>
<pre>wtxtcl.ex&gt;wtxEnumInfo CONTEXT_TYPE
CONTEXT_SYSTEM 0x1
CONTEXT_GROUP 0x2
CONTEXT_ANY 0x3
CONTEXT_TASK 0x4
CONTEXT_ANY_TASK 0x5
CONTEXT_ISR 0x6
CONTEXT_ISR_ANY 0x7
</pre>

For a complete discussion of events and using wtxtcl to work with them, 
see the 
<i>API Programmer's Guide: The WTX Protocol </i>.
<p>
When <i>CONTEXT_TYPE</i> is set to <b>WTX_CONTEXT_SYSTEM</b>, then only eventpoints
in system mode can be added. 
When <i>CONTEXT_TYPE</i> is set to <b>WTX_CONTEXT_TASK</b>, then only eventpoints
in context task can be added.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
The eventpoint number, which can be used as a key to wtxEventpointDelete.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_EVENTPOINT_ADD_2" >WTX_EVENTPOINT_ADD_2</a></b>, wtxtcl, wtxEventpointDelete, wtxEventpointList,  
<b><a href="../wtxpcl/wtx.html#top" >WTX</a></b> entry in the
<i>API Reference Manual: WTX Protocol </i>,  
<i>API Programmer's Guide: The WTX Protocol </i>

<hr>
<a name="wtxEventpointList"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxEventpointList</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxEventpointList</strong> - list the eventpoints known to the agent</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxEventpointList 
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This command returns a list of all eventpoints installed in the agent.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
Each item in the returned list has four elements, one for each of the
arguments to the wtxEventpointAdd command:  <b>DETECTION_TYPE</b>,
<b>EVENT_TYPE</b>, <b>CONTEXT_TYPE</b>, and <b>ACTION_TYPE</b>.  Each of these lists in
turn has two elements, the WTX type and the additional argument.
<p>
</blockquote><h4>CAVEATS</h4><blockquote><p>
The returned events are not keyed to eventpoint number.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_EVENTPOINT_LIST" >WTX_EVENTPOINT_LIST</a></b>, wtxtcl, wtxEventpointAdd, wtxEventpointDelete

<hr>
<a name="wtxEventpointListGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxEventpointListGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxEventpointListGet</strong> - list the eventpoints known to the agent</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxEventpointListGet
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This command returns an eventpoints info list installed in the agent.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
Each item in the returned list has five elements: three elements, 
one for each of the arguments to the wtxEventpointAdd command:  
<b>EVENT_TYPE</b>, <b>CONTEXT_TYPE</b>, and <b>ACTION_TYPE</b>; and two more elements for the
tool identifier and the eventpoint identifier.
<p>
<b>CONTEXT_TYPE</b> and <b>ACTION_TYPE</b> lists in has two elements, the WTX type
and the additional argument. 
<b>EVENT_TYPE</b> lists in may have more than two elements, the WTX type
and the additional arguments.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_EVENTPOINT_LIST_GET" >WTX_EVENTPOINT_LIST_GET</a></b>, wtxtcl, wtxEventpointAdd, wtxEventpointDelete

<hr>
<a name="wtxEventpointDelete"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxEventpointDelete</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxEventpointDelete</strong> - delete an eventpoint</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxEventpointDelete <i>epNum</i>
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This function removes the eventpoint numbered <i>epNum</i> from the agent.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_EVENTPOINT_DELETE" >WTX_EVENTPOINT_DELETE</a></b>, wtxtcl, wtxEventpointAdd, wtxEventpointList

<hr>
<a name="wtxOpen"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Tcl Library :  Tcl Procedures</i></a></p>

</blockquote><h1>wtxOpen</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>wtxOpen</strong> - open a file for use with virtual I/O</p>

<p>

</blockquote><h4>LOCALE</h4><blockquote><p>
WTX Tcl
<p>
</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>wtxOpen [-channel <i>chan</i>] <i>filename</i> <i>flags</i> <i>mode</i>
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This command causes the target server to open a file with the given
<i>filename</i>, <i>flags</i>, and <i>mode</i>.  The flags parameter can be
<b>WTX_O_RDONLY</b> or <b>WTX_O_WRONLY</b> or'ed with <b>WTX_O_CREAT</b>.
<i>flags</i> can also be an integer as defined in <b>sys/fcntl.h</b> but
this is only for backward compatibility and should not be used.
<p>
If <b>-channel</b> is specified, virtual I/O on the given channel is
redirected to the file.
<p>
</blockquote><h4>EXAMPLE</h4><blockquote><p>
On UNIX, to create and open the file <b>/tmp/myFile</b> in read-only mode 
with permissions set to "-r--------" use:
<pre>wtxOpen /tmp/myFile WTX_O_CREAT|WTX_O_RDONLY 0400
</pre>

</blockquote><h4>RETURNS</h4><blockquote><p>
An integer file descriptor, which can be used with other VIO commands.
<p>
</blockquote><h4>CAVEATS</h4><blockquote><p>
The <i>flags</i> and <i>mode</i> parameters are host-dependent.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtdoc.html#top">wtxtcl Library Part I</a></b>, <b><a href="../wtxpcl/wtx.html#WTX_OPEN" >WTX_OPEN</a></b>, wtxtcl, wtxClose, wtxVioCtl

<hr>