wtx.html

vxworks相关论文

then only breakpoints in context task can be added.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
The ID of the new breakpoint or <b>WTX_ERROR</b> if the add fails.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="../wtxpcl/wtx.html#WTX_EVENTPOINT_ADD" >WTX_EVENTPOINT_ADD</a></b>, <b><i><a href="./wtx.html#wtxEventpointAdd">wtxEventpointAdd</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxEventpointDelete">wtxEventpointDelete</a></i>(&nbsp;)</b>,  
<b><i><a href="./wtx.html#wtxEventpointList">wtxEventpointList</a></i>(&nbsp;)</b>

<hr>
<a name="wtxCacheTextUpdate"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX C Library :  Routines</i></a></p>

</blockquote><h1><i>wtxCacheTextUpdate</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>wtxCacheTextUpdate</i>(&nbsp;)</strong> - synchronize the instruction and data caches.</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS wtxCacheTextUpdate
    (
    HWTX       hWtx,  /* WTX API handle */
    TGT_ADDR_T addr,  /* remote addr to update */
    UINT32     nBytes /* number of bytes to update */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This function flushes the data chache, then invalidates the instruction cache.
This operation forces the instruction cache to fetch code that may have been 
created via the data path.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WTX_ERR_API_INVALID_ARG</b>
<dd>
 <i>nBytes</i> is invalid.
<p>
</dl>

</blockquote><h4>RETURNS</h4><blockquote><p>
<p>
&nbsp;<b>WTX_OK</b>&nbsp;or&nbsp;<b>WTX_ERROR</b>&nbsp;if&nbsp;exchange&nbsp;failed.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="../wtxpcl/wtx.html#WTX_CACHE_TEXT_UPDATE" >WTX_CACHE_TEXT_UPDATE</a></b>, <b><i><a href="./wtx.html#wtxMemRead">wtxMemRead</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxMemWrite">wtxMemWrite</a></i>(&nbsp;)</b>

<hr>
<a name="wtxCommandSend"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX C Library :  Routines</i></a></p>

</blockquote><h1><i>wtxCommandSend</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>wtxCommandSend</i>(&nbsp;)</strong> - Pass a string to be interpreted by the target server</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>char * wtxCommandSend
    (
    HWTX   hWtx,         /* WTX API handle */
    char * commandString /* String to be interpreted */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This function is used to control the target server behavior.
Services availables are: <b><i><a href="./wtx.html#wtxTsKill">wtxTsKill</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTsRestart">wtxTsRestart</a></i>(&nbsp;)</b>, wtxLogging (),
<b><i><a href="./wtx.html#wtxTsLock">wtxTsLock</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTsUnlock">wtxTsUnlock</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTargetReset">wtxTargetReset</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxAsyncNotifyEnable">wtxAsyncNotifyEnable</a></i>(&nbsp;)</b>,
<b><i><a href="./wtx.html#wtxAsyncNotifyDisable">wtxAsyncNotifyDisable</a></i>(&nbsp;)</b>.
<p>
This service sends a string to the target server which interprets it.
If the requested service is not known by <b><i>tsWtxCommandSend</i>(&nbsp;)</b>, then
the string is sent back to the client.
<p>
</blockquote><h4>EXAMPLE</h4><blockquote><p>
The following is a sample of string
<p>
<pre>   commandString = "wtxTsLock_30";    /* lock the target server for 30s */
   commandString = "wtxTsUnlock";     /* Unlock the target server */
   commandString = "wtxLoggingOn_/folk/pascal/wtx.txt"; /* wtx log started */
</pre>

</blockquote><h4>NOTE</h4><blockquote><p>
<p>
A separator is used ("_") and only some command strings can be 
recognized by the target server (plus options if needed):
<dl>
<dt>
wdbLoggingOn
<dd>

Open the file and log all WDB requests.
<p>
<dt>
wdbLoggingOff
<dd>

Close the file and stop the log.
<p>
<dt>
wtxLoggingOn
<dd>

Open the file and log all WTX requests.
<p>
<dt>
wtxLoggingOff
<dd>

Close the file and stop the log.
<p>
<dt>
allLoggingOff
<dd>

Stop WDB and WTX log.
<p>
<dt>
wtxAsyncNotifyEnable
<dd>

Start the asynchronous notification of events.
<p>
<dt>
wtxAsyncNotifyDisable
<dd>

Stop the asynchronous notification of events.
<p>
<dt>
wtxObjKillDestroy
<dd>

Kill the target server.
<p>
<dt>
wtxObjKillRestart
<dd>

Restart the target server.
<p>
<dt>
wtxTsLock
<dd>

Lock the target server.
<p>
<dt>
wtxTsUnlock
<dd>

Unlock the target server.
<p>
<dt>
wtxTargetReset
<dd>

Reset the target.
<p>
<dt>
wtxTargetIpAddressGet
<dd>
 Get the target's IP address (if applicable) in <b>a.b.c</b>.d form.
<p>
</dl>

</blockquote><h4>RETURNS</h4><blockquote><p>
<p>
&nbsp;string&nbsp;containing&nbsp;the&nbsp;command's&nbsp;result.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><i><a href="./wtx.html#wtxTsKill">wtxTsKill</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTsRestart">wtxTsRestart</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxLogging">wtxLogging</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTsLock">wtxTsLock</a></i>(&nbsp;)</b>,  
<b><i><a href="./wtx.html#wtxTsUnlock">wtxTsUnlock</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxTargetReset">wtxTargetReset</a></i>(&nbsp;)</b>, <b><i><a href="./wtx.html#wtxAsyncNotifyEnable">wtxAsyncNotifyEnable</a></i>(&nbsp;)</b>,  
<b><i><a href="./wtx.html#wtxAsyncNotifyDisable">wtxAsyncNotifyDisable</a></i>(&nbsp;)</b>

<hr>
<a name="wtxTargetIpAddressGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX C Library :  Routines</i></a></p>

</blockquote><h1><i>wtxTargetIpAddressGet</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>wtxTargetIpAddressGet</i>(&nbsp;)</strong> - gets target IP address.</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>UINT32 wtxTargetIpAddressGet
    (
    HWTX hWtx /* WTX API handle */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine returns the target's IP address in network byte order. The
returned address is the one used by the target server to connect the target.
<p>
On error (the target have no IP address), this value will be (UINT32) 0.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
the target's IP address in network byte order or 0 on error.
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtx.html#top">wtx</a></b>

<hr>
<a name="wtxCpuInfoGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX C Library :  Routines</i></a></p>

</blockquote><h1><i>wtxCpuInfoGet</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>wtxCpuInfoGet</i>(&nbsp;)</strong> - gets cpu related information from architecturedb file</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>char * wtxCpuInfoGet
    (
    int      cpuNum,     /* cpu number to get info on */
    CPU_INFO cpuInfoType /* cpu info type to get */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This function allows to get target CPU related informations. <i>cpuNum</i>
specifies the CPU number in data base, while <i>cpuInfoType</i> specifies which
parameter to get.
<p>
<i>cpuInfoType</i> can be from the following type
<p>
<pre>
typedef enum cpu_info		/* available cpu information types */
    {
    CPU_INFO_NONE	= 0,	/* no info needed                  */
    ARCH_DIR		= 1,	/* target architecture directory   */
    LEADING_CHAR	= 2,	/* symbols prepended character     */
    DEMANGLER		= 3,	/* target symbol demangler name    */
    CPU_NAME		= 4	/* target CPU name                 */
    } CPU_INFO;</pre>

<p>
</blockquote><h4>NOTE</h4><blockquote><p>
<p>
returned value if not NULL should be freed by caller
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a string containing parameter in string format or NULL.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><i><a href="./wtx.html#wtxTsInfoGet">wtxTsInfoGet</a></i>(&nbsp;)</b>

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

</blockquote><h1><i>wtxEventpointAdd</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>wtxEventpointAdd</i>(&nbsp;)</strong> - create a new WTX eventpoint</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>UINT32 wtxEventpointAdd
    (
    HWTX          hWtx,  /* WTX API handle */
    WTX_EVTPT_2 * pEvtpt /* eventpoint descriptor */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine creates a new eventpoint on the target. This routine is a
generic facility for setting breakpoints. An eventpoint specifies the
context to which it applies, the type of event to detect (for example 
breakpoint, context exit), and the action to be taken upon detection of 
the event (for example, notify the target server of the event).
<p>
The target server maintains a list of eventpoints created on the target
and this can be queried using <b><i><a href="./wtx.html#wtxEventpointList">wtxEventpointList</a></i>(&nbsp;)</b>.  When a context is
destroyed on the target or the target is reset, eventpoints are deleted
automatically without intervention from the creator.
<p>
When <i>pEvtpt-</i>context.contextType> is set to <b>WTX_CONTEXT_SYSTEM</b>, then 
only eventpoints in system mode can be added. 
When <i>pEvtpt-</i>context.contextType> is set to <b>WTX_CONTEXT_TASK</b>, then only 
eventpoints in context task can be added.
<p>
The eventpoint parameters are grouped into the structure:
<p>
<pre>
typedef struct wtx_evtpt_2              /* Eventpoint desc. version 2 */
    {
    WTX_EVENT_2         event;          /* Event to detect version 2  */
    WTX_CONTEXT         context;        /* Context descriptor         */
    WTX_ACTION          action;