wdb.html

vxworks相关论文

    TGT_ADDR_T	 	evtptId;	/* eventpoint ID */
    } WDB_EVTPT_DEL_DESC;</pre>

<p>
<b>evtType</b> specifies the type of eventpoint to delete.
<b>evtptId</b> specifies the eventpoint to delete. (<b>-1</b>
means delete all eventpoints of the given type.)
<p>
</blockquote><h4>NOTE</h4><blockquote><p>
Context-specific eventpoints are automatically deleted when the
context exits. Otherwise eventpoints are persistent 
until <b><a href="./wdb.html#WDB_EVENTPOINT_DELETE">WDB_EVENTPOINT_DELETE</a></b> is called to delete them.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_INVALID_EVENTPOINT</b>
<dd>

The eventpoint specified does not exist.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_EVENT_GET"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_EVENT_GET</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_EVENT_GET</strong> - upload an event from the target</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: )
OUTPUT: INPUT:
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine uploads an asynchronous target event to the host.
The return value, <b>WDB_EVT_DATA</b>, is:
<p>
<pre>
typedef struct wdb_evt_data		/* reply to a WDB_EVENT_GET */
    {
    WDB_EVT_TYPE 	evtType;	/* event type detected */
    union 				/* eventType specific info */
	{
	WDB_MEM_XFER		vioWriteInfo;	/* vio write event data */
	WDB_CALL_RET_INFO	callRetInfo;	/* call return event data */
	WDB_EVT_INFO		evtInfo;	/* any other event info */
	} eventInfo;
    } WDB_EVT_DATA;</pre>

<p>
The type of event uploaded can be determined by the
value of <b>evtType</b>.
<p>
</blockquote><h4>NOTE</h4><blockquote><p>
It is not necessary to poll for target events. Notification
of events is given as described in the "ASYNCHRONOUS NOTIFICATION SENT BY
THE AGENT" section of the WDB man page.  Call <b><a href="./wdb.html#WDB_EVENT_GET">WDB_EVENT_GET</a></b> to retrieve 
the event data after being notified that an event has occurred.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_FUNC_CALL"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_FUNC_CALL</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_FUNC_CALL</strong> - call a function on the target</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_CTX_CREATE_DESC
OUTPUT: UINT32
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine calls a function on the target. 
The call is not made directly by the WDB agent, but
rather from a task created for the purpose.
The <b>WDB_CTX_CREATE_DESC</b> structure describes how to create the context for
invoking the function:
<p>
<pre>
typedef struct wdb_ctx_create_desc	/* how to create a context */
    {
    WDB_CTX_TYPE	contextType;	/* task or system context */

    /* the following are used for task and system contexts */

    TGT_ADDR_T		stackBase;	/* bottom of stack (NULL = malloc) */
    UINT32		stackSize;	/* stack size */
    TGT_ADDR_T 		entry;		/* context entry point */
    TGT_INT_T		args[10];	/* arguments */

    /* the following are only used for task contexts */

    WDB_STRING_T	name;		/* name */
    TGT_INT_T		priority;	/* priority */
    TGT_INT_T		options;	/* options */
    TGT_INT_T		redirIn;	/* redirect input file (or 0) */
    TGT_INT_T		redirOut;	/* redirect output file (or 0) */
    TGT_INT_T		redirErr;	/* redirect error output file (or 0) */
    } WDB_CTX_CREATE_DESC;</pre>

<p>
The return value is the task ID of the task which executes the
function.
The actual return value of the function is passed back to the host as
an asynchronous event of event type <b>WDB_EVT_CALL_RET</b>. See <b><a href="./wdb.html#WDB_EVENT_GET">WDB_EVENT_GET</a></b>
for details.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_AGENT_MODE</b>
<dd>

This command cannot be executed in system mode.
<p>
<dt>
<b>WDB_ERR_NO_RT_PROC</b>
<dd>

The agent does not support this service.
<p>
<dt>
<b>WDB_ERR_RT_ERROR</b>
<dd>

The runtime callouts failed.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_MEM_CACHE_TEXT_UPDATE"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_MEM_CACHE_TEXT_UPDATE</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_MEM_CACHE_TEXT_UPDATE</strong> - synchronize cache after writing to the target</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_MEM_REGION
OUTPUT: (
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine is used to synchronize the data and instruction caches after
writing text to the target.  <b>WDB_MEM_REGION</b> defines the input parameters:
<p>
<pre>
typedef struct wdb_mem_region		/* a region of target memory */
    {
    TGT_ADDR_T		baseAddr;	/* memory region base address */
    TGT_INT_T		numBytes;	/* memory region size */
    UINT32		param;		/* proc dependent parameter */
    } WDB_MEM_REGION;</pre>

<p>
<b>baseAddr</b> and <b>numBytes</b> specify the
region of memory to update.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_MEM_ACCES</b>
<dd>

The memory region is invalid.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_MEM_CHECKSUM"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_MEM_CHECKSUM</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_MEM_CHECKSUM</strong> - checksum a block of target memory</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_MEM_REGION
OUTPUT: UINT32
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request performs a standard TCP/IP checksum (it sums 16-bit words 
using one-compliment arithmetic and returns the one-compliment of the result).
<p>
<pre>
typedef struct wdb_mem_region		/* a region of target memory */
    {
    TGT_ADDR_T		baseAddr;	/* memory region base address */
    TGT_INT_T		numBytes;	/* memory region size */
    UINT32		param;		/* proc dependent parameter */
    } WDB_MEM_REGION;</pre>

<p>
where <b>baseAddr</b> and <b>numBytes</b> specify the source region.  The checksum 
is returned as a 32-bit integer.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_MEM_ACCES</b>
<dd>

The target memory cannot be read.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_MEM_FILL"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_MEM_FILL</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_MEM_FILL</strong> - fill target memory with a pattern</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_MEM_REGION
OUTPUT: (
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request fills the specified area of target memory with a pattern.  
The input parameter is <b>WDB_MEM_REGION</b>:
<p>
<pre>
typedef struct wdb_mem_region		/* a region of target memory */
    {
    TGT_ADDR_T		baseAddr;	/* memory region base address */
    TGT_INT_T		numBytes;	/* memory region size */
    UINT32		param;		/* proc dependent parameter */
    } WDB_MEM_REGION;</pre>

<p>
<b>baseAddr</b> and <b>numBytes</b> specify the region of target memory to fill.
<b>param</b> specifies the 4-byte pattern used to fill the region.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_MEM_ACCES</b>
<dd>

The target memory cannot be written.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_MEM_MOVE"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

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

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_MEM_REGION
OUTPUT: (
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine requests the agent to move the contents of the specified 
area of memory to another memory location.  <b>WDB_MEM_REGION</b> specifies 
the various parameters:
<p>
<pre>
typedef struct wdb_mem_region		/* a region of target memory */
    {
    TGT_ADDR_T		baseAddr;	/* memory region base address */
    TGT_INT_T		numBytes;	/* memory region size */
    UINT32		param;		/* proc dependent parameter */
    } WDB_MEM_REGION;</pre>

<p>
where <b>baseAddr</b> and <b>numBytes</b> specify the source region and <b>param</b>
specifies where to move the contents to.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_MEM_ACCES</b>
<dd>

The target memory cannot be read/written.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.
<p>

</dl>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wdb.html#top">WDB</a></b>

<hr>
<a name="WDB_MEM_PROTECT"></a>
<p align=right>
<a href="rtnIndex.html"><i>WDB Protocol :  Requests</i></a></p>

</blockquote><h1>WDB_MEM_PROTECT</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WDB_MEM_PROTECT</strong> - write enable/disable a region of target memory</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WDB_MEM_REGION
OUTPUT: (
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request enables or disables write protection for a region of target
memory.  The input parameters are contained in <b>WDB_MEM_REGION</b>:
<p>
<pre>
typedef struct wdb_mem_region		/* a region of target memory */
    {
    TGT_ADDR_T		baseAddr;	/* memory region base address */
    TGT_INT_T		numBytes;	/* memory region size */
    UINT32		param;		/* proc dependent parameter */
    } WDB_MEM_REGION;</pre>

<p>
<b>baseAddr</b> and <b>numBytes</b> specify the region of target memory affected.  
To write-enable the region, set <b>param</b> to 0.  To write-protect the
region, set <b>param</b> to a non-zero value.
<p>
</blockquote><h4>NOTE</h4><blockquote><p>
This routine will affect an entire MMU page on the target.
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WDB_ERR_NO_RT_PROC</b>
<dd>

The target runtime has no procedure to support write protection.
<p>
<dt>
<b>WDB_ERR_MEM_ACCES</b>
<dd>

The protection routine failed.
<p>
<dt>
WDB and RPC errors
<dd>
 As described in the "REPLY ERRORS" section of the WDB
man page.