View All Attachments for Bug 264723

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Attachment #125537
Proposed service extensions	patch	2009-02-12 12:18:13 EST	10.97 KB	no flags	Details

Attachment #125542
Memory service definition with patch applied	text/html	2009-02-12 12:52:05 EST	20.84 KB	no flags	Details

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <title>Target Communication Framework Services - Memory</title>
</head>

<body lang='EN-US'>
  
<h1>Target Communication Framework Services - Memory</h1>
 
<ul>
    <li><a href='#Cmds'>Commands</a>
    <ul>
        <li><a href='#CmdGetContext'>Get Context</a>
        <li><a href='#CmdGetChildren'>Get Children</a>
        <li><a href='#CmdSetMemory'>Set Memory</a>
        <li><a href='#CmdGetMemory'>Get Memory</a>
        <li><a href='#CmdFillMemory'>Fill Memory</a>
    </ul>
    <li><a href='#Events'>Events</a>
    <li><a href='#API'>API</a>
</ul>

<h1>Memory Service</h1>

<p>The service provides basic operations to read/write memory on a target. Command
and event parameters are encoded as zero terminated <a href='TCF Specification.html#JSON'>JSON</a> strings.</p>

<p>The service uses standard format for error reports,
see <a href='TCF Services.html#ErrorFormat'>Error Report Format</a>.</p>
 
<p>A single memory access can succeed for some addresses and fail for others. In such
situation result message can contain partially valid data. Array of error addresses,
in addition to error report, describes data validity on per byte basis:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
<i>&lt;array of error addresses&gt;</i>
    &rArr; null
    &rArr; [ <i>&lt;error address list&gt;</i> ]
  
<i>&lt;error address list&gt;</i>
    &rArr; <i>&lt;error address&gt;</i>
    &rArr; <i>&lt;error address list&gt;</i> , <i>&lt;error address&gt;</i>
  
<i>&lt;error address&gt;</i>
    &rArr; { "addr" : <i>&lt;int: range starting address&gt;</i> , "size" : <i>&lt;int: range length in bytes&gt;</i> , "stat" : <i>&lt;int: status code&gt;</i> , "msg" : <i>&lt;object: error description&gt;</i> }
</font></b></pre>

<p>If there is no entry in error addresses array for a data byte, then status of such
byte is defined by main error report.</p>

<p>Status code is bitwise or of status flags:</p>
<dl>
    <dt><code><b>BYTE_VALID        = 0x00</b></code> <dd>no error for this byte
    <dt><code><b>BYTE_UNKNOWN      = 0x01</b></code> <dd>status is unknown
    <dt><code><b>BYTE_INVALID      = 0x02</b></code> <dd>byte value in invalid, error message describes the problem
    <dt><code><b>BYTE_CANNOT_READ  = 0x04</b></code> <dd>cannot read the byte
    <dt><code><b>BYTE_CANNOT_WRITE = 0x08</b></code> <dd>cannot write the byte
</dl>

<h2><a name='Cmds'>Commands</a></h2>

<h3><a name='CmdGetContext'>Get Context</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Memory &bull; getContext &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>The command retrieves context info for given context ID. A context corresponds to an
execution thread, process, address space, etc. Exact
meaning of a context depends on the target. Target agent should define contexts hierarchy
that is:</p>
 
<ul type='disc'>
    <li>Sufficient to resolve possible ambiguity of a memory address;
 
    <li>Adequately reflects target memory management strategy;
 
    <li>Intuitive to a user.
</ul>
 
<p>For traditional OS, like UNIX, memory access context can be one of:</p>
 
<ul type='disc'>
    <li>Kernel address space;
 
    <li>A process.
</ul>

<p>Reply:</p>

<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;context data&gt;</i> &bull;

<i>&lt;context data&gt;</i>
    &rArr; null
    &rArr; <i>&lt;object&gt;</i>
</font></b></pre>

<p>Context data object should, at least, contain member
<b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;.</i></font></b>
Context data is expected to be cached by clients.
Service sends contextChanged event to notify changes in context data.</p>

<p>Predefined memory context properties are:</p>
<ul>
    <li><code><b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of the context, same as getContext command argument.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ParentID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of a parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"BigEndian" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if memory is big-endian.

    <li><code><b><font face="Courier New" size=2 color=#333399>"AddressSize" : <i>&lt;int&gt;</i></font></b></code>
    - size of memory address in bytes.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Name" : <i>&lt;int&gt;</i></font></b></code>
    - name of the context, can be used for UI purposes.

    <li><code><b><font face="Courier New" size=2 color=#333399>"LowAddress" : <i>&lt;int&gt;</i></font></b></code>
    - lowest address (inclusive) which is valid for the context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"HighAddress" : <i>&lt;int&gt;</i></font></b></code>
    - highest address (inclusive) which is valid for the context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"AccessMode" : <i>&lt;array of strings&gt;</i></font></b></code>
    - Defines the access modes allowed for this context.
    <p>Predefined access modes are:</p>
    <ul>
        <li><code><b><font face="Courier New" size=2 color=#333399>"instruction"</font></b></code>
        - Context can contain instructions to execute.

        <li><code><b><font face="Courier New" size=2 color=#333399>"data"</font></b></code>
        - Context can contain data.

        <li><code><b><font face="Courier New" size=2 color=#333399>"IOAccess"</font></b></code>
        - Context can IO peripherals.

        <li><code><b><font face="Courier New" size=2 color=#333399>"userMode"</font></b></code>
        - Context represents a user mode (e.g. application running in Linux) view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"supervisorMode"</font></b></code>
        - Context represents a supervisor (e.g. Linux kernel) mode view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"hypervisorMode"</font></b></code>
        - Context represents a hypervisor mode view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"virtual"</font></b></code>
        - Context uses virtual addresses.

        <li><code><b><font face="Courier New" size=2 color=#333399>"physical"</font></b></code>
        - Context uses physical addresses.

        <li><code><b><font face="Courier New" size=2 color=#333399>"guestPhysical"</font></b></code>
        - Context uses guest physical addresses.

    </ul>

<h3><a name='CmdGetChildren'>Get Children</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Memory &bull; getChildren &bull; <i>&lt;string: parent context ID&gt;</i> &bull;
</font></b></pre>

<p>The command requests a list of contexts available for memory access commands.</p>
 
<p>Parent context ID can be null &ndash; to retrieve top level of the hierarchy, can be one
of context IDs retrieved by previous getChildren commands, or it can be obtained from another service.
Contexts hierarchy can be simple plain list or it can form a tree. It is up to target agent developers to
choose layout that is most descriptive for a given target.</p>
 
<p>Reply:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context IDs&gt;</i> &bull;<i></i>

<i>&lt;array of context IDs&gt;</i>
    &rArr; null
    &rArr; [ ]
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>

</font></b></pre>

<h3><a name='CmdSetMemory'>Set Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; set &bull; 
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    <i>&lt;int: byte count&gt;</i> &bull; <i>&lt;int: mode&gt;</i> &bull; <i>&lt;string: BASE64 encoded byte array&gt;</i> &bull;
</font></b></pre>

<p>Writes data bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". Context ID must be one returned by getContexts.
Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after writing by reading back and compare
</ul>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be written into memory.</p>

<h3><a name='CmdGetMemory'>Get Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; get &bull;
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    <i>&lt;int: byte count&gt;</i> &bull; <i>&lt;int: mode&gt;</i> &bull;
</font></b></pre>

<p>Reads data bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". Context ID must be one returned by getContexts.
Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after reading by re-reading and compare
</ul>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;string: BASE64 encoded byte array&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be retrieved from memory.</p>

<h3><a name='CmdFillMemory'>Fill Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; fill &bull; 
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    &lt;int: byte count&gt; &bull; <i>&lt;int: mode&gt;</i> &bull; <i>&lt;array: array of pattern bytes&gt;</i> &bull;
</font></b></pre>

<p>Writes pattern bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". If "byte count" is bigger then pattern size, then
pattern is repeated necessary number of times. Context ID must be one returned by
getContexts. Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after writing by reading back and compare
</ul>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be written into memory.</p>

<h2><a name='Events'>Events</a></h2>
 
<p>Memory service broadcasts notification events when memory contexts are added, removed
or changed, and when memory content is altered by "set" or "fill" commands.</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
E &bull; Memory &bull; contextAdded &bull; <i>&lt;array of context data&gt;</i> &bull;
E &bull; Memory &bull; contextChanged &bull; <i>&lt;array of context data&gt;</i> &bull;
E &bull; Memory &bull; contextRemoved &bull; <i>&lt;array of context IDs&gt;</i> &bull;
E &bull; Memory &bull; memoryChanged &bull; <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;array of address ranges&gt;</i> &bull;
  
<i>&lt;array of context data&gt;</i> <font face="Times New Roman" size=3>- see Get Contexts command.</font>
  
<i>&lt;array of context IDs&gt;</i>
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>
  
<i>&lt;array of address ranges&gt;</i>
    &rArr; null
    &rArr; [ <i>&lt;address ranges list&gt;</i> ]
  
<i>&lt;address ranges list&gt;</i>
    &rArr; <i>&lt;address range&gt;</i>
    &rArr; <i>&lt;address ranges list&gt;</i> , <i>&lt;address range&gt;</i>

<i>&lt;address range&gt;</i>
    &rArr; { "addr" : <i>&lt;int: range starting address&gt;</i> , "size" : <i>&lt;int: range length in bytes&gt;</i> }
</font></b></pre>

<h2><a name='API'>API</a></h2>
 
<pre>
<font color=#3F5FBF>/**
 * IMemory service provides basic operations to read/write memory on a target.
 */</font>
<font color=#7F0055>public interface</font> Memory <font color=#7F0055>extends</font> Service {
  
    <font color=#7F0055>static final</font> String NAME = "Memory";

    <font color=#3F5FBF>/**
     * Retrieve context info for given context ID.
     *   
     * <font color=#7F9FBF>@param</font> id &ndash; context ID. 
     * <font color=#7F9FBF>@param</font> done - callback interface called when operation is completed.
     */</font>
    IToken getContext(String id, DoneGetContext done);

    <font color=#3F5FBF>/**
     * Client callback interface for getContext().
     */</font>
    <font color=#7F0055>interface</font> DoneGetContext {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context &ndash; context data.
         */</font>
        <font color=#7F0055>void</font> doneGetContext(IToken token, Exception error, MemoryContext context);
    }

    <font color=#3F5FBF>/**
     * Retrieve contexts available for memory commands.
     * A context corresponds to an execution thread, process, address space, etc.
     * A context can belong to a parent context. Contexts hierarchy can be simple
     * plain list or it can form a tree. It is up to target agent developers to choose
     * layout that is most descriptive for a given target. Context IDs are valid across
     * all services. In other words, all services access same hierarchy of contexts,
     * with same IDs, however, each service accesses its own subset of context's
     * attributes and functionality, which is relevant to that service.
     *  
     * <font color=#7F9FBF>@param</font> parent_context_id &ndash; parent context ID. Can be null &ndash;
     * to retrieve top level of the hierarchy, or one of context IDs retrieved
     * by previous getContexts commands.
     * <font color=#7F9FBF>@param</font> done - callback interface called when operation is completed.
     */</font>
    IToken getChildren(String parent_context_id, DoneGetChildren done);

    <font color=#3F5FBF>/**
     * Client callback interface for getChildren().
     */</font>
    <font color=#7F0055>interface</font> DoneGetChildren {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> contexts &ndash; array of available context IDs.
         */</font>
        <font color=#7F0055>void</font> doneGetChildren(IToken token, Exception error, String[] context_ids);
    }

    <font color=#3F5FBF>/**
     * Memory access mode:
     * Carry on when some of the memory cannot be accessed and
     * return MemoryError at the end if any of the bytes
     * were not processed correctly.
     */</font>
    <font color=#7F0055>final static int</font> MODE_CONTINUEONERROR = 0x1;
 
    <font color=#3F5FBF>/**
     * Memory access mode:
     * Verify result of memory operations (by reading and comparing).
     */</font>
    <font color=#7F0055>final static int</font> MODE_VERIFY = 0x2;
 
    <font color=#7F0055>interface</font> MemoryContext {
 
        <font color=#3F5FBF>/** 
         * Retrieve context ID.
         * Same as getProperties().get("id")
         */</font>
        String getID();
 
        <font color=#3F5FBF>/** 
         * Return true if the context has children.
         * Same as getProperties().get("has_children")
         * Children can be retrieved by getContexts call.
         */</font>
        <font color=#7F0055>boolean</font> hasChildren();
 
        <font color=#3F5FBF>/** 
         * Retrieve context properties.
         */</font>
        Map&lt;String,Object&gt; getProperties();
 
        <font color=#3F5FBF>/**
         * Set target memory.
         * If 'word_size' is 0 it means client does not care about word size.
         */</font>
        <font color=#7F0055>void</font> set(long addr, <font color=#7F0055>int</font> word_size, byte[] buf,
                         <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
 
        <font color=#3F5FBF>/**
         * Read target memory.
         */</font>
        <font color=#7F0055>void</font> get(long addr, <font color=#7F0055>int</font> word_size, byte[] buf,
                         <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
 
        <font color=#3F5FBF>/**
         * Fill target memory with given pattern.
         * 'size' is number of bytes to fill.
         */</font>
        <font color=#7F0055>void</font> fill(long addr, <font color=#7F0055>int</font> word_size, byte[] value,
                          <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
    
        <font color=#3F5FBF>/**
         * Client callback interface for set(), get() and fill().
         */</font>
        <font color=#7F0055>interface</font> DoneMemory {
            <font color=#7F0055>void</font> doneMemory(MemoryError error);
        }
    }
 
    <font color=#7F0055>class</font> MemoryError <font color=#7F0055>extends</font> Exception {
    }
  
    <font color=#3F5FBF>/**
     * ErrorOffset interface can be implemented by MemoryError object,
     * which is returned by get, set and fill commands.
     *
     * get/set/fill () returns this exception when reading failed
     * for some but not all bytes, and MODE_CONTINUEONERROR
     * has been set in mode. (For example, when only part of the request
     * translates to valid memory addresses.)
     * Exception.getMessage can be used for generalized message of the
     * possible reasons of partial memory operation.
     */</font>
    <font color=#7F0055>interface</font> ErrorOffset {
        
        // Error may have per byte information
        <font color=#7F0055>final static int</font> 
            BYTE_VALID        = 0x00,
            BYTE_UNKNOWN      = 0x01, // e.g. out of range
            BYTE_INVALID      = 0x02,
            BYTE_CANNOT_READ  = 0x04,
            BYTE_CANNOT_WRITE = 0x08;
 
        <font color=#7F0055>int</font> getStatus(<font color=#7F0055>int</font> offset);
 
        <font color=#3F5FBF>/**
         * Returns the detail message string about the
         * byte associated with specified location.
         * <font color=#7F9FBF>@return</font>  the detail error message string.
         */</font>
        String getMessage(<font color=#7F0055>int</font> offset);
        
    }
 
    <font color=#7F0055>void</font> addListener(MemoryListener listener);
 
    <font color=#7F0055>interface</font> MemoryListener {
 
        <font color=#3F5FBF>/**
         * Called when a new memory access context(s) is created.
         */</font>
        <font color=#7F0055>void</font> contextAdded(Context[] contexts);
 
        <font color=#3F5FBF>/**
         * Called when a new memory access context(s) properties changed.
         */</font>
        <font color=#7F0055>void</font> contextChanged(Context[] contexts);
 
        <font color=#3F5FBF>/**
         * Called when memory access context(s) is removed.
         */</font>
        <font color=#7F0055>void</font> contextRemoved(String[] context_ids);
 
        <font color=#3F5FBF>/**
         * Called when target memory content was changed and clients 
         * need to update themselves. Clients, at least, should invalidate
         * corresponding cached memory data.
         * Not every change is notified - it is not possible,
         * only those, which are not caused by normal execution of the debuggee.
         * &lsquo;addr&rsquo; and &lsquo;size&rsquo; can be null if unknown.
         */</font>
        <font color=#7F0055>void</font> memoryChanged(String context_id,
               long[] addr, long[] size);
    }
}
</pre>

</body>
</html>

Attachment #125543
Registers service definition with patch applied	text/html	2009-02-12 12:52:40 EST	30.07 KB	no flags	Details

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <title>Target Communication Framework Services - Registers</title>
</head>

<body lang='EN-US'>
  
<h1>Target Communication Framework Services - Registers</h1>
 
<ul>
    <li><a href='#Cmds'>Commands</a>
    <ul>
        <li><a href='#CmdGetContext'>Get Context</a>
        <li><a href='#CmdGetChildren'>Get Children</a>
        <li><a href='#CmdSetRegister'>Set Register</a>
        <li><a href='#CmdGetRegister'>Get Register</a>
        <li><a href='#CmdSetMultiple'>Set Multiple Registers</a>
        <li><a href='#CmdGetMultiple'>Get Multiple Registers</a>
        <li><a href='#CmdSearch'>Search for Registers</a>
    </ul>
    <li><a href='#Events'>Events</a>
    <li><a href='#API'>API</a>
</ul>

<h1>Registers Service</h1>

<p>The service provides basic operations to read/write CPU and hardware registers. Command
and event parameters are encoded as zero terminated <a href='TCF Specification.html#JSON'>JSON</a> strings.</p>

<p>The service uses standard format for error reports,
see <a href='TCF Services.html#ErrorFormat'>Error Report Format</a>.</p>

In addition to commands that can set/get individual register context values, the service defines commands to set/get values at
multiple locations. This allows:
<ol>
    <li> to get/set multiple register contexts in one command
    <li> to specify offset and size for get/set on large register groups
    <li> to get/set truncated register values, e.g. only the low 32 bits of a 64-bit register
</ol>
 
<h2><a name='Cmds'>Commands</a></h2>

<h3><a name='CmdGetContext'>Get Context</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Registers &bull; getContext &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>The command retrieves context info for given context ID. A context corresponds to an
register, register group, register bit field, etc. Exact meaning of a context depends on the target.
Target agent should define contexts hierarchy that is:</p>
 
<ul type='disc'>
    <li>Adequately reflects target hardware registers layout;
    <li>Consistent with the lingo/terminology of the processor manuals;
    <li>Intuitive to a user.
</ul>
 
<p>Reply:</p>

<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;context data&gt;</i> &bull;

<i>&lt;context data&gt;</i>
    &rArr; null
    &rArr; <i>&lt;object&gt;</i>
</font></b></pre>

<p>Context data object should, at least, contain member
<b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;.</i></font></b>
Context data is expected to be cached by clients.
Service sends contextChanged event to notify changes in context data.</p>

<p>Predefined register context properties are:</p>
<ul>
    <li><code><b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of the context, same as getContext command argument.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ParentID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of a parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ProcessID" : <i>&lt;string&gt;</i></font></b></code>
    - process ID.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Name" : <i>&lt;string&gt;</i></font></b></code>
    - context name.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Description" : <i>&lt;string&gt;</i></font></b></code>
    - context description.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Size" : <i>&lt;int&gt;</i></font></b></code>
    - context size in bytes. Byte arrays in get/set commands should be same size.
    Hardware register can be smaller then this size, for example in case
    when register size is not an even number of bytes. In such case implementation
    should add/remove padding that consists of necessary number of zero bits.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Readable" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if context value can be read.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ReadOnce" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if reading the context (register) destroys its current value - it can be read only once.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Writeable" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if context value can be written.

    <li><code><b><font face="Courier New" size=2 color=#333399>"WriteOnce" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if register value can not be overwritten - every write counts.

    <li><code><b><font face="Courier New" size=2 color=#333399>"SideEffects" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if writing the context can change values of other registers.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Volatile" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the register value can change even when target is stopped.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Float" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the register value is a floating-point value.

    <li><code><b><font face="Courier New" size=2 color=#333399>"BigEndian" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if big endian, which means decreasing numeric significance with increasing bit number.
    If absent default if false, which implies little endianess. The endianess is used to encode and decode values of get, getm, set and setm commands.

    <li><code><b><font face="Courier New" size=2 color=#333399>"LeftToRight" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the lowest numbered bit (i.e. bit #0 or bit #1, depending on "FirstBit" value) should be shown to user as the left-most bit.

    <li><code><b><font face="Courier New" size=2 color=#333399>"FirstBit" : <i>&lt;int&gt;</i></font></b></code>
    - 0 or 1. If the context has bit field children, bit positions of the fields can be zero-based or 1-based.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Bits" : <i>&lt;array of int&gt;</i></font></b></code>
    - if context is a bit field, contains the field bit numbers in the parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Values" : <i>&lt;array of named values&gt;</i></font></b></code>
    - predefined names (mnemonics) for some of context values.

    <li><code><b><font face="Courier New" size=2 color=#333399>"MemoryAddress" : <i>&lt;int&gt;</i></font></b></code>
    - The address of a memory mapped register. If MemoryContext is provided, the address is referring into that context.
    
    <li><code><b><font face="Courier New" size=2 color=#333399>"MemoryContext" : <i>&lt;string&gt;</i></font></b></code>
    - The context id of a memory context in which a memory mapped register is located. Used together with MemoryAddress to inform where in memory memory mapped registers are located.
      If absent and MemoryAddress is defined, the context id of this context is used as default.

    <li><code><b><font face="Courier New" size=2 color=#333399>"CanSearch" : <i>&lt;string&gt;</i></font></b></code>
    - A list of attribute names which can be searched for starting on this context.
      If absent the context does not support search.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Role" : <i>&lt;string&gt;</i></font></b></code>
    - one of the predefined roles. The role property is optional.    
    
    <p>Predefined register role strings are:</p>
    <ul>
        <li><code><b><font face="Courier New" size=2 color=#333399>"PC"</font></b></code>
        - Program counter. Defines instruction to execute next.

        <li><code><b><font face="Courier New" size=2 color=#333399>"SP"</font></b></code>
        - Register defining the current stack pointer location.

        <li><code><b><font face="Courier New" size=2 color=#333399>"FP"</font></b></code>
        - Register defining the current frame pointer location.

        <li><code><b><font face="Courier New" size=2 color=#333399>"ReturnRegister"</font></b></code>
        - Register used to store the return address for calls.

        <li><code><b><font face="Courier New" size=2 color=#333399>"CoreRegister"</font></b></code>
        - Register which belongs to the core state. Commonly set for general purpose registers, condition code and other registers which are of special interest for determinig the state.
    </ul>
</ul>

<h3><a name='CmdGetChildren'>Get Children</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Registers &bull; getChildren &bull; <i>&lt;string: parent context ID&gt;</i> &bull;
</font></b></pre>

<p>The command requests a list of contexts available for registers access commands.</p>
 
<p>Parent context ID is usually a thread ID retrieved through Run Control Service or one
of context IDs retrieved by previous getChildren commands.
Contexts hierarchy can be simple plain list of registers, or it can form a tree of register groups, registers and bit fields.
It is up to target agent developers to choose layout that is most descriptive for a given target.</p>
 
<p>Reply:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context IDs&gt;</i> &bull;<i></i>

<i>&lt;array of context IDs&gt;</i>
    &rArr; null
    &rArr; [ ]
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>

</font></b></pre>

<h3><a name='CmdSetRegister'>Set Register</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; set &bull; <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Writes value into given register context. Context ID must be one returned by getContexts.
Value is BASE64 encoded byte array of binary data. Array size should match the size of the register.</p>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error.</p>

<h3><a name='CmdGetRegister'>Get Register</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; get &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>Reads register value from given register context. Context ID must be one returned by getContexts.
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Value is BASE64 encoded byte array of binary data. Array size should match the size of the register.</p>

<h3><a name='CmdSetMultiple'>Set Multiple Registers</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; setm &bull; <i>&lt;array of locations&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;

<i>&lt;array of locations&gt;</i>
    &rArr; [ <i>&lt;location list&gt;</i> ]

<i>&lt;location list&gt;</i>
    &rArr; <i>&lt;location&gt;</i>
    &rArr; <i>&lt;location list&gt;</i> , <i>&lt;location&gt;</i>
  
<i>&lt;location&gt;</i>
    &rArr; [ <i>&lt;string: register context ID&gt;</i> , <i>&lt;int: offset in bytes&gt;</i> , <i>&lt;int: size in bytes&gt;</i> ]
</font></b></pre>

<p>Writes value into given list of locations in registers. Each location is represented by 3-element array that consists of
context ID, offset in the context in bytes and value size in bytes.
Value is BASE64 encoded byte array of binary data. Byte array size should match the sum of location sizes.</p>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error.</p>

<h3><a name='CmdGetMultiple'>Get Multiple Registers</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; getm &bull; <i>&lt;array of locations&gt;</i> &bull;

<i>&lt;array of locations&gt;</i>
    &rArr; [ <i>&lt;location list&gt;</i> ]

<i>&lt;location list&gt;</i>
    &rArr; <i>&lt;location&gt;</i>
    &rArr; <i>&lt;location list&gt;</i> , <i>&lt;location&gt;</i>
  
<i>&lt;location&gt;</i>
    &rArr; [ <i>&lt;string: register context ID&gt;</i> , <i>&lt;int: offset in bytes&gt;</i> , <i>&lt;int: size in bytes&gt;</i> ]
</font></b></pre>

<p>Reads register values from given list of locations in registers. Each location is represented by 3-element array that consists of
context ID, offset in the context in bytes and value size in bytes.
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Value is BASE64 encoded byte array of binary data. Byte array size should match the sum of location sizes.</p>

<h3><a name='CmdSearch'>Search for Registers</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; search &bull; <i>&lt;string: start context ID&gt; &bull; &lt;filter properties object&gt;</i> &bull;

<i>&lt;filter properties object&gt;</i>
    &rArr; { <i>&lt;filter properties&gt;</i> }

<i>&lt;filter properties&gt;</i>
    &rArr; <i>null</i>
    &rArr; <i>&lt;filter property&gt;</i>
    &rArr; <i>&lt;filter properties&gt;</i> , <i>&lt;filter property&gt;</i>
  
<i>&lt;filter property&gt;</i>
    &rArr; <i>&lt;string: property name&gt;</i> , <i>&lt;value: property value&gt;</i>
</font></b></pre>

<p>Search returns context ids for all register contexts with properties matching to the given filter. 
    Search is only supported for properties listed in the CanSearch property of a context.
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context IDs&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation of error.
Array of context IDs is a JSON array containing all context IDs of matching contexts.


<h2><a name='Events'>Events</a></h2>
 
<p>Registers service broadcasts notification events when registers contexts are changed, and when
a register content is altered by "set" commands.</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
E &bull; Registers &bull; contextChanged &bull;
E &bull; Registers &bull; registerChanged &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<h2><a name='API'>API</a></h2>
 
<pre>
<font color=#3F5FBF>/**
 * IRegisters service provides access to target CPU register values and properties.
 */</font>
<font color=#7F0055>public interface</font> IRegisters <font color=#7F0055>extends</font> IService {

    <font color=#7F0055>static final</font> String NAME = "Registers";

    <font color=#3F5FBF>/**
     * Context property names.
     */</font>
    <font color=#7F0055>static final</font> String
        PROP_ID = "ID",
        PROP_PARENT_ID = "ParentID",
        PROP_PROCESS_ID = "ProcessID",
        PROP_NAME = "Name",
        PROP_DESCRIPTION = "Description",
        PROP_SIZE = "Size",
        PROP_READBLE = "Readable",
        PROP_READ_ONCE = "ReadOnce",
        PROP_WRITEABLE = "Writeable",
        PROP_WRITE_ONCE = "WriteOnce",
        PROP_SIDE_EFFECTS = "SideEffects",
        PROP_VOLATILE = "Volatile",
        PROP_FLOAT = "Float",
        PROP_BIG_ENDIAN = "BigEndian",
        PROP_LEFT_TO_RIGHT = "LeftToRight",
        PROP_FIST_BIT = "FirstBit",
        PROP_BITS = "Bits",
        PROP_VALUES = "Values",
        PROP_VALUES = "Role",
        PROP_VALUES = "MemoryAddress",
        PROP_VALUES = "MemoryContext",
        PROP_VALUES = "CanSearch";

    <font color=#3F5FBF>/**
     * Role property names.
     */</font>
    <font color=#7F0055>static final</font> String
        PROP_ROLE_PC = "PC",
        PROP_ROLE_SP = "SP",
        PROP_ROLE_FP = "FP",
        PROP_ROLE_RR = "ReturnRegister",
        PROP_ROLE_CR = "CoreRegister";

    <font color=#3F5FBF>/**
     * Retrieve context info for given context ID.
     *   
     * <font color=#7F9FBF>@param</font> id &ndash; context ID. 
     * <font color=#7F9FBF>@param</font> done - call back interface called when operation is completed.
     */</font>
    IToken getContext(String id, DoneGetContext done);

    <font color=#3F5FBF>/**
     * Client call back interface for getContext().
     */</font>
    <font color=#7F0055>interface</font> DoneGetContext {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context &ndash; context data.
         */</font>
        <font color=#7F0055>void</font> doneGetContext(IToken token, Exception error, RegistersContext context);
    }

    <font color=#3F5FBF>/**
     * Retrieve contexts available for registers commands.
     * A context corresponds to an execution thread, stack frame, registers group, etc.
     * A context can belong to a parent context. Contexts hierarchy can be simple
     * plain list or it can form a tree. It is up to target agent developers to choose
     * layout that is most descriptive for a given target. Context IDs are valid across
     * all services. In other words, all services access same hierarchy of contexts,
     * with same IDs, however, each service accesses its own subset of context's
     * attributes and functionality, which is relevant to that service.
     *  
     * <font color=#7F9FBF>@param</font> parent_context_id &ndash; parent context ID. Can be null &ndash;
     * to retrieve top level of the hierarchy, or one of context IDs retrieved
     * by previous getChildren commands.
     * <font color=#7F9FBF>@param</font> done - call back interface called when operation is completed.
     */</font>
    IToken getChildren(String parent_context_id, DoneGetChildren done);

    <font color=#3F5FBF>/**
     * Client call back interface for getChildren().
     */</font>
    <font color=#7F0055>interface</font> DoneGetChildren {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context_ids &ndash; array of available context IDs.
         */</font>
        <font color=#7F0055>void</font> doneGetChildren(IToken token, Exception error, String[] context_ids);
    }
    
    <font color=#3F5FBF>/**
     * RegistersContext objects represent register groups, registers and bit fields. 
     */</font>
    <font color=#7F0055>interface</font> RegistersContext {
        <font color=#3F5FBF>/**
         * Get Context ID.
         * <font color=#7F9FBF>@return</font> context ID.
         */</font>
        String getID();
        
        <font color=#3F5FBF>/**
         * Get parent context ID.
         * <font color=#7F9FBF>@return</font> parent context ID.
         */</font>
        String getParentID();
        
        <font color=#3F5FBF>/**
         * Get context (register, register group, bit field) name.
         * <font color=#7F9FBF>@return</font> context name.
         */</font>
        String getName();
        
        <font color=#3F5FBF>/**
         * Get context description.
         * <font color=#7F9FBF>@return</font> context description.
         */</font>
        String getDescription();
        
        <font color=#3F5FBF>/**
         * Get context size in bytes.
         * Byte arrays in get()/set() methods should be same size.
         * Hardware register can be smaller then this size, for example in case
         * when register size is not an even number of bytes. In such case implementation
         * should add/remove padding that consists of necessary number of zero bits.
         * @return context size in bytes.
         */</font>
        <font color=#7F0055>int</font> getSize();
        
        <font color=#3F5FBF>/**
         * Check if context value can be read.
         * <font color=#7F9FBF>@return</font> true if can read value of the context.
         */</font>
        <font color=#7F0055>boolean</font> isReadable();
        
        <font color=#3F5FBF>/**
         * Check if reading the context (register) destroys its current value -
         * it can be read only once.
         * <font color=#7F9FBF>@return</font> true if read-once register.
         */</font>
        <font color=#7F0055>boolean</font> isReadOnce();
        
        <font color=#3F5FBF>/**
         * Check if context value can be written.
         * <font color=#7F9FBF>@return</font> true if can write value of the context.
         */</font>
        <font color=#7F0055>boolean</font> isWriteable();
        
        <font color=#3F5FBF>/**
         * Check if register value can not be overwritten - every write counts.
         * <font color=#7F9FBF>@return</font> true if write-once register.
         */</font>
        <font color=#7F0055>boolean</font> isWriteOnce();
        
        <font color=#3F5FBF>/**
         * Check if writing the context can change values of other registers. 
         * <font color=#7F9FBF>@return</font> true if has side effects.
         */</font>
        <font color=#7F0055>boolean</font> hasSideEffects();
        
        <font color=#3F5FBF>/**
         * Check if the register value can change even when target is stopped.
         * <font color=#7F9FBF>@return</font> true if the register value can change at any time.
         */</font>
        <font color=#7F0055>boolean</font> isVolatile();
        
        <font color=#3F5FBF>/**
         * Check if the register value is a floating-point value.
         * <font color=#7F9FBF>@return</font> true if a floating-point register.
         */</font>
        <font color=#7F0055>boolean</font> isFloat();
        
        <font color=#3F5FBF>/**
         * Check endianess of the context.
         * Big endian means decreasing numeric significance with increasing bit number. 
         * <font color=#7F9FBF>@return</font> true if big endian.
         */</font>
        <font color=#7F0055>boolean</font> isBigEndian();
        
        <font color=#3F5FBF>/**
         * Check if the lowest numbered bit (i.e. bit #0 or bit #1 depending on
         * getFirstBitNumber() value) should be shown to user as the left-most bit or
         * the right-most bit.
         * <font color=#7F9FBF>@return</font> true if the first bit is left-most bit.
         */</font>
        <font color=#7F0055>boolean</font> isLeftToRight();
        
        <font color=#3F5FBF>/**
         * If the context has bit field children, bit positions of the fields
         * can be zero-based or 1-based.
         * <font color=#7F9FBF>@return</font> first bit position - 0 or 1.
         */</font>
        <font color=#7F0055>int</font> getFirstBitNumber();
        
        <font color=#3F5FBF>/**
         * If context is a bit field, get the field bit numbers in parent context. 
         * <font color=#7F9FBF>@return</font> array of bit numbers.
         */</font>
        <font color=#7F0055>int</font>[] getBitNumbers();
        
        <font color=#3F5FBF>/**
         * A context can have predefined names (mnemonics) for some its values.
         * This method returns a list of such named values.
         * <font color=#7F9FBF>@return</font> array of named values or null.
         */</font>
        NamedValue[] getNamedValues();
        
        <font color=#3F5FBF>/**
         * Get complete map of context properties.
         * <font color=#7F9FBF>@return</font> map of context properties.
         */</font>
        Map&lt;String,Object&gt; getProperties();
        
        <font color=#3F5FBF>/**
         * Read value of the context.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
        IToken get(DoneGet done);
        
        <font color=#3F5FBF>/**
         * Set value of the context.
         * <font color=#7F9FBF>@param</font> value - value to write into the context.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
        IToken set(byte[] value, DoneSet done);

       <font color=#3F5FBF>/**
         * Search for contexts matching a filter.
         * <font color=#7F9FBF>@param</font> filter - map of name value pairs to search for.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
         IToken search(Map&lt;String,Object&gt; filter, DoneSearch done);
    }

    <font color=#3F5FBF>/**
     * A register context can have predefined names (mnemonics) for some its values.
     * NamedValue objects represent such values. 
     */</font>
    <font color=#7F0055>interface</font> NamedValue {
        <font color=#3F5FBF>/**
         * Get value associated with the name.
         * <font color=#7F9FBF>@return</font> the value as an array of bytes.
         */</font>
        byte[] getValue();
        
        <font color=#3F5FBF>/**
         * Get name (mnemonic) of the value.
         * <font color=#7F9FBF>@return</font> value name.
         */</font>
        String getName();
        
        <font color=#3F5FBF>/**
         * Get human readable description of the value.
         * <font color=#7F9FBF>@return</font> value description.
         */</font>
        String getDescription();
    }
    
    <font color=#3F5FBF>/**
     * Read values of multiple locations in registers.
     * <font color=#7F9FBF>@param</font> locs - array of data locations.
     * <font color=#7F9FBF>@param</font> done - call back object.
     * <font color=#7F9FBF>@return</font> - pending command handle.
     */</font>
    IToken getm(Location[] locs, DoneGet done);
    
    <font color=#3F5FBF>/**
     * Set values of multiple locations in registers.
     * <font color=#7F9FBF>@param</font> locs - array of data locations.
     * <font color=#7F9FBF>@param</font> value - value to write into the context.
     * <font color=#7F9FBF>@param</font> done - call back object.
     * <font color=#7F9FBF>@return</font> - pending command handle.
     */</font>
    IToken setm(Location[] locs, byte[] value, DoneSet done);
    <font color=#3F5FBF>/**
     * Class Location represents value location in register context
     */</font>
    <font color=#7F0055>final class</font> Location {
        <font color=#3F5FBF>/** Register context ID */</font>
        <font color=#7F0055>public final</font> String id; 

        <font color=#3F5FBF>/** offset in the context, in bytes */</font>
        <font color=#7F0055>public final int</font> offs;

        <font color=#3F5FBF>/** value size in bytes */</font>
        <font color=#7F0055>public final int</font> size;

        <font color=#7F0055>public</font> Location(String id, <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size) {
            <font color=#7F0055>this</font>.id = id;
            <font color=#7F0055>this</font>.offs = offs;
            <font color=#7F0055>this</font>.size = size;
        }
    }

    <font color=#3F5FBF>/**
     * 'get' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneGet {
        <font color=#7F0055>void</font> doneGet(IToken token, Exception error, byte[] value);
    }
    
    <font color=#3F5FBF>/**
     * 'set' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneSet {
        <font color=#7F0055>void</font> doneSet(IToken token, Exception error);
    }

    <font color=#3F5FBF>/**
     * 'search' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneSearch {
        <font color=#7F0055>void</font> doneSearch(IToken token, String[] contexts);
    }

    <font color=#3F5FBF>/**
     * Add registers service event listener.
     * <font color=#7F9FBF>@param</font> listener - event listener implementation.
     */</font>
    <font color=#7F0055>void</font> addListener(RegistersListener listener);

    <font color=#3F5FBF>/**
     * Remove registers service event listener.
     * <font color=#7F9FBF>@param</font> listener - event listener implementation.
     */</font>
    <font color=#7F0055>void</font> removeListener(RegistersListener listener);

    <font color=#3F5FBF>/**
     * Registers event listener is notified when registers context hierarchy
     * changes, and when a register is modified by the service commands. 
     */</font>
    <font color=#7F0055>interface</font> RegistersListener {

        <font color=#3F5FBF>/**
         * Called when register context properties changed.
         * Most targets have static set of registers and register properties.
         * Such targets never generate this event. However, some targets,
         * for example, JTAG probes, allow user to modify register definitions.
         * Clients should flush all cached register context data. 
         */</font>
        <font color=#7F0055>void</font> contextChanged();

        <font color=#3F5FBF>/**
         * Called when register content was changed and clients 
         * need to update themselves. Clients, at least, should invalidate
         * corresponding cached registers data.
         * Not every change is notified - it is not possible,
         * only those, which are not caused by normal execution of the debuggee.
         */</font>
        <font color=#7F0055>void</font> registerChanged(String context_id);
    }
}
</pre>

</body>
</html>

Attachment #125560
Adapted memory service definition according to phone discussion	patch	2009-02-12 14:10:32 EST	11.03 KB	no flags	Details

Attachment #125561
Memory service with patch applied.	text/html	2009-02-12 14:11:12 EST	20.90 KB	no flags	Details

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <title>Target Communication Framework Services - Memory</title>
</head>

<body lang='EN-US'>
  
<h1>Target Communication Framework Services - Memory</h1>
 
<ul>
    <li><a href='#Cmds'>Commands</a>
    <ul>
        <li><a href='#CmdGetContext'>Get Context</a>
        <li><a href='#CmdGetChildren'>Get Children</a>
        <li><a href='#CmdSetMemory'>Set Memory</a>
        <li><a href='#CmdGetMemory'>Get Memory</a>
        <li><a href='#CmdFillMemory'>Fill Memory</a>
    </ul>
    <li><a href='#Events'>Events</a>
    <li><a href='#API'>API</a>
</ul>

<h1>Memory Service</h1>

<p>The service provides basic operations to read/write memory on a target. Command
and event parameters are encoded as zero terminated <a href='TCF Specification.html#JSON'>JSON</a> strings.</p>

<p>The service uses standard format for error reports,
see <a href='TCF Services.html#ErrorFormat'>Error Report Format</a>.</p>
 
<p>A single memory access can succeed for some addresses and fail for others. In such
situation result message can contain partially valid data. Array of error addresses,
in addition to error report, describes data validity on per byte basis:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
<i>&lt;array of error addresses&gt;</i>
    &rArr; null
    &rArr; [ <i>&lt;error address list&gt;</i> ]
  
<i>&lt;error address list&gt;</i>
    &rArr; <i>&lt;error address&gt;</i>
    &rArr; <i>&lt;error address list&gt;</i> , <i>&lt;error address&gt;</i>
  
<i>&lt;error address&gt;</i>
    &rArr; { "addr" : <i>&lt;int: range starting address&gt;</i> , "size" : <i>&lt;int: range length in bytes&gt;</i> , "stat" : <i>&lt;int: status code&gt;</i> , "msg" : <i>&lt;object: error description&gt;</i> }
</font></b></pre>

<p>If there is no entry in error addresses array for a data byte, then status of such
byte is defined by main error report.</p>

<p>Status code is bitwise or of status flags:</p>
<dl>
    <dt><code><b>BYTE_VALID        = 0x00</b></code> <dd>no error for this byte
    <dt><code><b>BYTE_UNKNOWN      = 0x01</b></code> <dd>status is unknown
    <dt><code><b>BYTE_INVALID      = 0x02</b></code> <dd>byte value in invalid, error message describes the problem
    <dt><code><b>BYTE_CANNOT_READ  = 0x04</b></code> <dd>cannot read the byte
    <dt><code><b>BYTE_CANNOT_WRITE = 0x08</b></code> <dd>cannot write the byte
</dl>

<h2><a name='Cmds'>Commands</a></h2>

<h3><a name='CmdGetContext'>Get Context</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Memory &bull; getContext &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>The command retrieves context info for given context ID. A context corresponds to an
execution thread, process, address space, etc. Exact
meaning of a context depends on the target. Target agent should define contexts hierarchy
that is:</p>
 
<ul type='disc'>
    <li>Sufficient to resolve possible ambiguity of a memory address;
 
    <li>Adequately reflects target memory management strategy;
 
    <li>Intuitive to a user.
</ul>
 
<p>For traditional OS, like UNIX, memory access context can be one of:</p>
 
<ul type='disc'>
    <li>Kernel address space;
 
    <li>A process.
</ul>

<p>Reply:</p>

<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;context data&gt;</i> &bull;

<i>&lt;context data&gt;</i>
    &rArr; null
    &rArr; <i>&lt;object&gt;</i>
</font></b></pre>

<p>Context data object should, at least, contain member
<b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;.</i></font></b>
Context data is expected to be cached by clients.
Service sends contextChanged event to notify changes in context data.</p>

<p>Predefined memory context properties are:</p>
<ul>
    <li><code><b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of the context, same as getContext command argument.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ParentID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of a parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"BigEndian" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if memory is big-endian.

    <li><code><b><font face="Courier New" size=2 color=#333399>"AddressSize" : <i>&lt;int&gt;</i></font></b></code>
    - size of memory address in bytes.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Name" : <i>&lt;int&gt;</i></font></b></code>
    - name of the context, can be used for UI purposes.

    <li><code><b><font face="Courier New" size=2 color=#333399>"StartBound" : <i>&lt;int&gt;</i></font></b></code>
    - lowest address (inclusive) which is valid for the context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"EndBound" : <i>&lt;int&gt;</i></font></b></code>
    - highest address (inclusive) which is valid for the context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"AccessTypes" : <i>&lt;array of strings&gt;</i></font></b></code>
    - Defines the access types allowed for this context.
    <p>Predefined access types are:</p>
    <ul>
        <li><code><b><font face="Courier New" size=2 color=#333399>"instruction"</font></b></code>
        - Context can contain instructions to execute.

        <li><code><b><font face="Courier New" size=2 color=#333399>"data"</font></b></code>
        - Context can contain data.

        <li><code><b><font face="Courier New" size=2 color=#333399>"io"</font></b></code>
        - Context can IO peripherals.

        <li><code><b><font face="Courier New" size=2 color=#333399>"user"</font></b></code>
        - Context represents a user (e.g. application running in Linux) view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"supervisor"</font></b></code>
        - Context represents a supervisor (e.g. Linux kernel) view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"hypervisor"</font></b></code>
        - Context represents a hypervisor view to memory.

        <li><code><b><font face="Courier New" size=2 color=#333399>"virtual"</font></b></code>
        - Context uses virtual addresses.

        <li><code><b><font face="Courier New" size=2 color=#333399>"physical"</font></b></code>
        - Context uses physical addresses.

        <li><code><b><font face="Courier New" size=2 color=#333399>"cache"</font></b></code>
        - Context is a cache.

        <li><code><b><font face="Courier New" size=2 color=#333399>"tlb"</font></b></code>
        - Context is a tlb memory.
    </ul>

<h3><a name='CmdGetChildren'>Get Children</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Memory &bull; getChildren &bull; <i>&lt;string: parent context ID&gt;</i> &bull;
</font></b></pre>

<p>The command requests a list of contexts available for memory access commands.</p>
 
<p>Parent context ID can be null &ndash; to retrieve top level of the hierarchy, can be one
of context IDs retrieved by previous getChildren commands, or it can be obtained from another service.
Contexts hierarchy can be simple plain list or it can form a tree. It is up to target agent developers to
choose layout that is most descriptive for a given target.</p>
 
<p>Reply:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context IDs&gt;</i> &bull;<i></i>

<i>&lt;array of context IDs&gt;</i>
    &rArr; null
    &rArr; [ ]
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>

</font></b></pre>

<h3><a name='CmdSetMemory'>Set Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; set &bull; 
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    <i>&lt;int: byte count&gt;</i> &bull; <i>&lt;int: mode&gt;</i> &bull; <i>&lt;string: BASE64 encoded byte array&gt;</i> &bull;
</font></b></pre>

<p>Writes data bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". Context ID must be one returned by getContexts.
Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after writing by reading back and compare
</ul>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be written into memory.</p>

<h3><a name='CmdGetMemory'>Get Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; get &bull;
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    <i>&lt;int: byte count&gt;</i> &bull; <i>&lt;int: mode&gt;</i> &bull;
</font></b></pre>

<p>Reads data bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". Context ID must be one returned by getContexts.
Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after reading by re-reading and compare
</ul>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;string: BASE64 encoded byte array&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be retrieved from memory.</p>

<h3><a name='CmdFillMemory'>Fill Memory</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Memory &bull; fill &bull; 
    <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;int: address&gt;</i> &bull; <i>&lt;int: word size&gt;</i> &bull;
    &lt;int: byte count&gt; &bull; <i>&lt;int: mode&gt;</i> &bull; <i>&lt;array: array of pattern bytes&gt;</i> &bull;
</font></b></pre>

<p>Writes pattern bytes at given address in memory, "word size" bytes at a time. Address
should be aligned by "word size". If "byte count" is bigger then pattern size, then
pattern is repeated necessary number of times. Context ID must be one returned by
getContexts. Mode is logical OR of any combination of:</p>
 
<ul type='disc'>
    <li>0x1 &ndash; continue on error (like bus error or page fault)
 
    <li>0x2 &ndash; verify data after writing by reading back and compare
</ul>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of error addresses&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Error addresses, when present, let client know which bytes of data failed
to be written into memory.</p>

<h2><a name='Events'>Events</a></h2>
 
<p>Memory service broadcasts notification events when memory contexts are added, removed
or changed, and when memory content is altered by "set" or "fill" commands.</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
E &bull; Memory &bull; contextAdded &bull; <i>&lt;array of context data&gt;</i> &bull;
E &bull; Memory &bull; contextChanged &bull; <i>&lt;array of context data&gt;</i> &bull;
E &bull; Memory &bull; contextRemoved &bull; <i>&lt;array of context IDs&gt;</i> &bull;
E &bull; Memory &bull; memoryChanged &bull; <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;array of address ranges&gt;</i> &bull;
  
<i>&lt;array of context data&gt;</i> <font face="Times New Roman" size=3>- see Get Contexts command.</font>
  
<i>&lt;array of context IDs&gt;</i>
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>
  
<i>&lt;array of address ranges&gt;</i>
    &rArr; null
    &rArr; [ <i>&lt;address ranges list&gt;</i> ]
  
<i>&lt;address ranges list&gt;</i>
    &rArr; <i>&lt;address range&gt;</i>
    &rArr; <i>&lt;address ranges list&gt;</i> , <i>&lt;address range&gt;</i>

<i>&lt;address range&gt;</i>
    &rArr; { "addr" : <i>&lt;int: range starting address&gt;</i> , "size" : <i>&lt;int: range length in bytes&gt;</i> }
</font></b></pre>

<h2><a name='API'>API</a></h2>
 
<pre>
<font color=#3F5FBF>/**
 * IMemory service provides basic operations to read/write memory on a target.
 */</font>
<font color=#7F0055>public interface</font> Memory <font color=#7F0055>extends</font> Service {
  
    <font color=#7F0055>static final</font> String NAME = "Memory";

    <font color=#3F5FBF>/**
     * Retrieve context info for given context ID.
     *   
     * <font color=#7F9FBF>@param</font> id &ndash; context ID. 
     * <font color=#7F9FBF>@param</font> done - callback interface called when operation is completed.
     */</font>
    IToken getContext(String id, DoneGetContext done);

    <font color=#3F5FBF>/**
     * Client callback interface for getContext().
     */</font>
    <font color=#7F0055>interface</font> DoneGetContext {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context &ndash; context data.
         */</font>
        <font color=#7F0055>void</font> doneGetContext(IToken token, Exception error, MemoryContext context);
    }

    <font color=#3F5FBF>/**
     * Retrieve contexts available for memory commands.
     * A context corresponds to an execution thread, process, address space, etc.
     * A context can belong to a parent context. Contexts hierarchy can be simple
     * plain list or it can form a tree. It is up to target agent developers to choose
     * layout that is most descriptive for a given target. Context IDs are valid across
     * all services. In other words, all services access same hierarchy of contexts,
     * with same IDs, however, each service accesses its own subset of context's
     * attributes and functionality, which is relevant to that service.
     *  
     * <font color=#7F9FBF>@param</font> parent_context_id &ndash; parent context ID. Can be null &ndash;
     * to retrieve top level of the hierarchy, or one of context IDs retrieved
     * by previous getContexts commands.
     * <font color=#7F9FBF>@param</font> done - callback interface called when operation is completed.
     */</font>
    IToken getChildren(String parent_context_id, DoneGetChildren done);

    <font color=#3F5FBF>/**
     * Client callback interface for getChildren().
     */</font>
    <font color=#7F0055>interface</font> DoneGetChildren {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> contexts &ndash; array of available context IDs.
         */</font>
        <font color=#7F0055>void</font> doneGetChildren(IToken token, Exception error, String[] context_ids);
    }

    <font color=#3F5FBF>/**
     * Memory access mode:
     * Carry on when some of the memory cannot be accessed and
     * return MemoryError at the end if any of the bytes
     * were not processed correctly.
     */</font>
    <font color=#7F0055>final static int</font> MODE_CONTINUEONERROR = 0x1;
 
    <font color=#3F5FBF>/**
     * Memory access mode:
     * Verify result of memory operations (by reading and comparing).
     */</font>
    <font color=#7F0055>final static int</font> MODE_VERIFY = 0x2;
 
    <font color=#7F0055>interface</font> MemoryContext {
 
        <font color=#3F5FBF>/** 
         * Retrieve context ID.
         * Same as getProperties().get("id")
         */</font>
        String getID();
 
        <font color=#3F5FBF>/** 
         * Return true if the context has children.
         * Same as getProperties().get("has_children")
         * Children can be retrieved by getContexts call.
         */</font>
        <font color=#7F0055>boolean</font> hasChildren();
 
        <font color=#3F5FBF>/** 
         * Retrieve context properties.
         */</font>
        Map&lt;String,Object&gt; getProperties();
 
        <font color=#3F5FBF>/**
         * Set target memory.
         * If 'word_size' is 0 it means client does not care about word size.
         */</font>
        <font color=#7F0055>void</font> set(long addr, <font color=#7F0055>int</font> word_size, byte[] buf,
                         <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
 
        <font color=#3F5FBF>/**
         * Read target memory.
         */</font>
        <font color=#7F0055>void</font> get(long addr, <font color=#7F0055>int</font> word_size, byte[] buf,
                         <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
 
        <font color=#3F5FBF>/**
         * Fill target memory with given pattern.
         * 'size' is number of bytes to fill.
         */</font>
        <font color=#7F0055>void</font> fill(long addr, <font color=#7F0055>int</font> word_size, byte[] value,
                          <font color=#7F0055>int</font> size, <font color=#7F0055>int</font> mode, DoneMemory done);
    
        <font color=#3F5FBF>/**
         * Client callback interface for set(), get() and fill().
         */</font>
        <font color=#7F0055>interface</font> DoneMemory {
            <font color=#7F0055>void</font> doneMemory(MemoryError error);
        }
    }
 
    <font color=#7F0055>class</font> MemoryError <font color=#7F0055>extends</font> Exception {
    }
  
    <font color=#3F5FBF>/**
     * ErrorOffset interface can be implemented by MemoryError object,
     * which is returned by get, set and fill commands.
     *
     * get/set/fill () returns this exception when reading failed
     * for some but not all bytes, and MODE_CONTINUEONERROR
     * has been set in mode. (For example, when only part of the request
     * translates to valid memory addresses.)
     * Exception.getMessage can be used for generalized message of the
     * possible reasons of partial memory operation.
     */</font>
    <font color=#7F0055>interface</font> ErrorOffset {
        
        // Error may have per byte information
        <font color=#7F0055>final static int</font> 
            BYTE_VALID        = 0x00,
            BYTE_UNKNOWN      = 0x01, // e.g. out of range
            BYTE_INVALID      = 0x02,
            BYTE_CANNOT_READ  = 0x04,
            BYTE_CANNOT_WRITE = 0x08;
 
        <font color=#7F0055>int</font> getStatus(<font color=#7F0055>int</font> offset);
 
        <font color=#3F5FBF>/**
         * Returns the detail message string about the
         * byte associated with specified location.
         * <font color=#7F9FBF>@return</font>  the detail error message string.
         */</font>
        String getMessage(<font color=#7F0055>int</font> offset);
        
    }
 
    <font color=#7F0055>void</font> addListener(MemoryListener listener);
 
    <font color=#7F0055>interface</font> MemoryListener {
 
        <font color=#3F5FBF>/**
         * Called when a new memory access context(s) is created.
         */</font>
        <font color=#7F0055>void</font> contextAdded(Context[] contexts);
 
        <font color=#3F5FBF>/**
         * Called when a new memory access context(s) properties changed.
         */</font>
        <font color=#7F0055>void</font> contextChanged(Context[] contexts);
 
        <font color=#3F5FBF>/**
         * Called when memory access context(s) is removed.
         */</font>
        <font color=#7F0055>void</font> contextRemoved(String[] context_ids);
 
        <font color=#3F5FBF>/**
         * Called when target memory content was changed and clients 
         * need to update themselves. Clients, at least, should invalidate
         * corresponding cached memory data.
         * Not every change is notified - it is not possible,
         * only those, which are not caused by normal execution of the debuggee.
         * &lsquo;addr&rsquo; and &lsquo;size&rsquo; can be null if unknown.
         */</font>
        <font color=#7F0055>void</font> memoryChanged(String context_id,
               long[] addr, long[] size);
    }
}
</pre>

</body>
</html>

Attachment #125712
Patch with register service changes	patch	2009-02-14 02:59:00 EST	13.11 KB	eugene: iplog+	Details

Attachment #125713
HTML version of register service	text/html	2009-02-14 02:59:54 EST	31.78 KB	no flags	Details

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <title>Target Communication Framework Services - Registers</title>
</head>

<body lang='EN-US'>
  
<h1>Target Communication Framework Services - Registers</h1>
 
<ul>
    <li><a href='#Cmds'>Commands</a>
    <ul>
        <li><a href='#CmdGetContext'>Get Context</a>
        <li><a href='#CmdGetChildren'>Get Children</a>
        <li><a href='#CmdSetRegister'>Set Register</a>
        <li><a href='#CmdGetRegister'>Get Register</a>
        <li><a href='#CmdSetMultiple'>Set Multiple Registers</a>
        <li><a href='#CmdGetMultiple'>Get Multiple Registers</a>
        <li><a href='#CmdSearch'>Search for Registers</a>
    </ul>
    <li><a href='#Events'>Events</a>
    <li><a href='#API'>API</a>
</ul>

<h1>Registers Service</h1>

<p>The service provides basic operations to read/write CPU and hardware registers. Command
and event parameters are encoded as zero terminated <a href='TCF Specification.html#JSON'>JSON</a> strings.</p>

<p>The service uses standard format for error reports,
see <a href='TCF Services.html#ErrorFormat'>Error Report Format</a>.</p>

In addition to commands that can set/get individual register context values, the service defines commands to set/get values at
multiple locations. This allows:
<ol>
    <li> to get/set multiple register contexts in one command
    <li> to specify offset and size for get/set on large register groups
    <li> to get/set truncated register values, e.g. only the low 32 bits of a 64-bit register
</ol>
 
<h2><a name='Cmds'>Commands</a></h2>

<h3><a name='CmdGetContext'>Get Context</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Registers &bull; getContext &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>The command retrieves context info for given context ID. A context corresponds to an
register, register group, register bit field, etc. Exact meaning of a context depends on the target.
Target agent should define contexts hierarchy that is:</p>
 
<ul type='disc'>
    <li>Adequately reflects target hardware registers layout;
    <li>Consistent with the lingo/terminology of the processor manuals;
    <li>Intuitive to a user.
</ul>
 
<p>Reply:</p>

<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;context data&gt;</i> &bull;

<i>&lt;context data&gt;</i>
    &rArr; null
    &rArr; <i>&lt;object&gt;</i>
</font></b></pre>

<p>Context data object should, at least, contain member
<b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;.</i></font></b>
Context data is expected to be cached by clients.
Service sends contextChanged event to notify changes in context data.</p>

<p>Predefined register context properties are:</p>
<ul>
    <li><code><b><font face="Courier New" size=2 color=#333399>"ID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of the context, same as getContext command argument.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ParentID" : <i>&lt;string&gt;</i></font></b></code>
    - ID of a parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ProcessID" : <i>&lt;string&gt;</i></font></b></code>
    - process ID.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Name" : <i>&lt;string&gt;</i></font></b></code>
    - context name.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Description" : <i>&lt;string&gt;</i></font></b></code>
    - context description.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Size" : <i>&lt;int&gt;</i></font></b></code>
    - context size in bytes. Byte arrays in get/set commands should be same size.
    Hardware register can be smaller then this size, for example in case
    when register size is not an even number of bytes. In such case implementation
    should add/remove padding that consists of necessary number of zero bits.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Readable" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if context value can be read.

    <li><code><b><font face="Courier New" size=2 color=#333399>"ReadOnce" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if reading the context (register) destroys its current value - it can be read only once.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Writeable" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if context value can be written.

    <li><code><b><font face="Courier New" size=2 color=#333399>"WriteOnce" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if register value can not be overwritten - every write counts.

    <li><code><b><font face="Courier New" size=2 color=#333399>"SideEffects" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if writing the context can change values of other registers.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Volatile" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the register value can change even when target is stopped.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Float" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the register value is a floating-point value.

    <li><code><b><font face="Courier New" size=2 color=#333399>"BigEndian" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if big endian, which means decreasing numeric significance with increasing bit number.
    If absent default if false, which implies little endianess. The endianess is used to encode and decode values of get, getm, set and setm commands.

    <li><code><b><font face="Courier New" size=2 color=#333399>"LeftToRight" : <i>&lt;boolean&gt;</i></font></b></code>
    - true if the lowest numbered bit (i.e. bit #0 or bit #1, depending on "FirstBit" value) should be shown to user as the left-most bit.

    <li><code><b><font face="Courier New" size=2 color=#333399>"FirstBit" : <i>&lt;int&gt;</i></font></b></code>
    - 0 or 1. If the context has bit field children, bit positions of the fields can be zero-based or 1-based.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Bits" : <i>&lt;array of int&gt;</i></font></b></code>
    - if context is a bit field, contains the field bit numbers in the parent context.

    <li><code><b><font face="Courier New" size=2 color=#333399>"Values" : <i>&lt;array of named values&gt;</i></font></b></code>
    - predefined names (mnemonics) for some of context values.

    <li><code><b><font face="Courier New" size="2" color="#333399">"MemoryAddress" : <i>&lt;int&gt;</i></font></b></code>
    - The address of a memory mapped register. If MemoryContext is provided, the address is referring into that context.
    </li>    
    <li><code><b><font face="Courier New" size="2" color="#333399">"MemoryContext" : <i>&lt;string&gt;</i></font></b></code>
    - The context id of a memory context in which a memory mapped register is located. Used together with MemoryAddress to inform where in memory memory mapped registers are located.
      If absent and MemoryAddress is defined, the context id of this context is used as default.
    </li>    
    <li><code><b><font face="Courier New" size="2" color="#333399">"CanSearch" : <i>&lt;array of strings&gt;</i></font></b></code>
    - A list of attribute names which can be searched for starting on this context.
      If absent the context does not support search.
    </li>    
    <li><code><b><font face="Courier New" size="2" color="#333399">"Role" : <i>&lt;string&gt;</i></font></b></code>
    - One of the predefined roles. The role property is optional.    
    </li>
    <p>Predefined register role strings are:</p>
    <ul>
        <li><code><b><font face="Courier New" size="2" color="#333399">"PC"</font></b></code>
        - Program counter. Defines instruction to execute next.
		</li>
        <li><code><b><font face="Courier New" size="2" color="#333399">"SP"</font></b></code>
        - Register defining the current stack pointer location.
		</li>
        <li><code><b><font face="Courier New" size="2" color="#333399">"FP"</font></b></code>
        - Register defining the current frame pointer location.
		</li>
        <li><code><b><font face="Courier New" size="2" color="#333399">"RET"</font></b></code>
        - Register used to store the return address for calls.
		</li>
        <li><code><b><font face="Courier New" size="2" color="#333399">"CORE"</font></b></code>
        - Indicates register or register groups which belong to the core state.
          Commonly set for general purpose registers,
          condition code and other registers which are of special
          interest for determining the state.
		</li>
    </ul>
</ul>

<h3><a name='CmdGetChildren'>Get Children</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; <i>&lt;token&gt;</i> &bull; Registers &bull; getChildren &bull; <i>&lt;string: parent context ID&gt;</i> &bull;
</font></b></pre>

<p>The command requests a list of contexts available for registers access commands.</p>
 
<p>Parent context ID is usually a thread ID retrieved through Run Control Service or one
of context IDs retrieved by previous getChildren commands.
Contexts hierarchy can be simple plain list of registers, or it can form a tree of register groups, registers and bit fields.
It is up to target agent developers to choose layout that is most descriptive for a given target.</p>
 
<p>Reply:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context IDs&gt;</i> &bull;<i></i>

<i>&lt;array of context IDs&gt;</i>
    &rArr; null
    &rArr; [ ]
    &rArr; [ <i>&lt;context ID list&gt;</i> ]
  
<i>&lt;context ID list&gt;</i>
    &rArr; <i>&lt;string: context ID&gt;</i>
    &rArr; <i>&lt;context ID list&gt;</i> , <i>&lt;string: context ID&gt;</i>

</font></b></pre>

<h3><a name='CmdSetRegister'>Set Register</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; set &bull; <i>&lt;string: context ID&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Writes value into given register context. Context ID must be one returned by getContexts.
Value is BASE64 encoded byte array of binary data. Array size should match the size of the register.</p>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error.</p>

<h3><a name='CmdGetRegister'>Get Register</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; get &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<p>Reads register value from given register context. Context ID must be one returned by getContexts.
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Value is BASE64 encoded byte array of binary data. Array size should match the size of the register.</p>

<h3><a name='CmdSetMultiple'>Set Multiple Registers</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; setm &bull; <i>&lt;array of locations&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;

<i>&lt;array of locations&gt;</i>
    &rArr; [ <i>&lt;location list&gt;</i> ]

<i>&lt;location list&gt;</i>
    &rArr; <i>&lt;location&gt;</i>
    &rArr; <i>&lt;location list&gt;</i> , <i>&lt;location&gt;</i>
  
<i>&lt;location&gt;</i>
    &rArr; [ <i>&lt;string: register context ID&gt;</i> , <i>&lt;int: offset in bytes&gt;</i> , <i>&lt;int: size in bytes&gt;</i> ]
</font></b></pre>

<p>Writes value into given list of locations in registers. Each location is represented by 3-element array that consists of
context ID, offset in the context in bytes and value size in bytes.
Value is BASE64 encoded byte array of binary data. Byte array size should match the sum of location sizes.</p>
  
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error.</p>

<h3><a name='CmdGetMultiple'>Get Multiple Registers</a></h3>
 
<pre><b><font face="Courier New" size=2 color=#333399>
C &bull; &lt;token&gt; &bull; Registers &bull; getm &bull; <i>&lt;array of locations&gt;</i> &bull;

<i>&lt;array of locations&gt;</i>
    &rArr; [ <i>&lt;location list&gt;</i> ]

<i>&lt;location list&gt;</i>
    &rArr; <i>&lt;location&gt;</i>
    &rArr; <i>&lt;location list&gt;</i> , <i>&lt;location&gt;</i>
  
<i>&lt;location&gt;</i>
    &rArr; [ <i>&lt;string: register context ID&gt;</i> , <i>&lt;int: offset in bytes&gt;</i> , <i>&lt;int: size in bytes&gt;</i> ]
</font></b></pre>

<p>Reads register values from given list of locations in registers. Each location is represented by 3-element array that consists of
context ID, offset in the context in bytes and value size in bytes.
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size=2 color=#333399>
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;string: value&gt;</i> &bull;
</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation
of error. Value is BASE64 encoded byte array of binary data. Byte array size should match the sum of location sizes.</p>

<h3><a name='CmdSearch'>Search for Registers</a></h3>
 
<pre><b><font face="Courier New" size="2" color="#333399">
C &bull; &lt;token&gt; &bull; Registers &bull; search &bull; <i>&lt;string: start context ID&gt; &bull; &lt;object:filter properties&gt;</i> &bull;
</font></b></pre>

<p>Search returns a path to each context with properties matching the filter. A path consists of a list of 
    context ids starting with a direct child of the start context up to the found context.
    Search is only supported for properties listed in the CanSearch property.

<p>Predefined filter object properties are:</p>
<ul>
    <li><code><b><font face="Courier New" size="2" color="#333399">"Name" : <i>&lt;string&gt;</i></font></b></code>
    - The name of the property this filter applies too. Must be one of the names listed in the CanSearch property.
	</li>
    <li><code><b><font face="Courier New" size="2" color="#333399">"EqualValue" : <i>&lt;string&gt;</i></font></b></code>
    - The value which is searched for.
	</li>
</ul>
</p>
 
<p>Result message:</p>
 
<pre><b><font face="Courier New" size="2" color="#333399">
R &bull; <i>&lt;token&gt;</i> &bull; <i>&lt;error report&gt;</i> &bull; <i>&lt;array of context Paths&gt;</i> &bull;

<i>&lt;array of context Paths&gt;</i>
    &rArr; null
    &rArr; [ ]
    &rArr; [ <i>&lt;context Path list&gt;</i> ]
  
<i>&lt;context Path list&gt;</i>
    &rArr; <i>&lt;array of context IDs&gt;</i>
    &rArr; <i>&lt;context Path list&gt;</i> , <i>&lt;array of context IDs&gt;</i>

</font></b></pre>

<p>Error report provides integer error code and a short, human readable explanation of error.
In the result, each matching context is provided with the path of parents starting with the direct
children of the starting node up to the matching node.
Multiple found entries are returned as an array of those paths.
</p>
Example Assume the following context hierarchy:

<pre><b><font face="Courier New" size="2">
{"Name" : "Core", "ID":"ID_C"}
	{"Name" : "Group0", "ID":"ID_G0", "Role":"CORE"}
		{"Name" : "PC", "ID":"ID_PC", "Role":"PC"}
		{"Name" : "SP", "ID":"ID_SP", "Role":"SP"}
	{"Name" : "Group1", "ID":"ID_G1"}
		{"Name" : "R0", "ID":"ID_R0"}
</font></b></pre>

With this setup, the following commands and responses could take place:

<pre><b><font face="Courier New" size="2">
C &bull; "1234" &bull; Registers &bull; search &bull; "ID_C" &bull; {"Name":"Name", "EqualValue":"PC"} &bull;

R &bull; "1234" &bull; [["ID_G0", "ID_PC"]] &bull;

C &bull; "1235" &bull; Registers &bull; search &bull; "ID_C" &bull; {"Name":"Role", "EqualValue":"CORE"} &bull;

R &bull; "1235" &bull; [["ID_G0"]] &bull;
</font></b></pre>

<h2><a name='Events'>Events</a></h2>
 
<p>Registers service broadcasts notification events when registers contexts are changed, and when
a register content is altered by "set" commands.</p>
 
<pre><b><font face="Courier New" size="2" color="#333399">
E &bull; Registers &bull; contextChanged &bull;
E &bull; Registers &bull; registerChanged &bull; <i>&lt;string: context ID&gt;</i> &bull;
</font></b></pre>

<h2><a name='API'>API</a></h2>
 
<pre>
<font color=#3F5FBF>/**
 * IRegisters service provides access to target CPU register values and properties.
 */</font>
<font color=#7F0055>public interface</font> IRegisters <font color=#7F0055>extends</font> IService {

    <font color=#7F0055>static final</font> String NAME = "Registers";

    <font color=#3F5FBF>/**
     * Context property names.
     */</font>
    <font color=#7F0055>static final</font> String
        PROP_ID = "ID",
        PROP_PARENT_ID = "ParentID",
        PROP_PROCESS_ID = "ProcessID",
        PROP_NAME = "Name",
        PROP_DESCRIPTION = "Description",
        PROP_SIZE = "Size",
        PROP_READBLE = "Readable",
        PROP_READ_ONCE = "ReadOnce",
        PROP_WRITEABLE = "Writeable",
        PROP_WRITE_ONCE = "WriteOnce",
        PROP_SIDE_EFFECTS = "SideEffects",
        PROP_VOLATILE = "Volatile",
        PROP_FLOAT = "Float",
        PROP_BIG_ENDIAN = "BigEndian",
        PROP_LEFT_TO_RIGHT = "LeftToRight",
        PROP_FIST_BIT = "FirstBit",
        PROP_BITS = "Bits",
        PROP_VALUES = "Values",
        PROP_VALUES = "Role",
        PROP_VALUES = "MemoryAddress",
        PROP_VALUES = "MemoryContext",
        PROP_VALUES = "CanSearch";

    <font color=#3F5FBF>/**
     * Role property names.
     */</font>
    <font color=#7F0055>static final</font> String
        PROP_ROLE_PC = "PC",
        PROP_ROLE_SP = "SP",
        PROP_ROLE_FP = "FP",
        PROP_ROLE_RR = "RET",
        PROP_ROLE_CR = "CORE";

    <font color=#3F5FBF>/**
     * Filter property names.
     */</font>
    <font color=#7F0055>static final</font> String
        PROP_ROLE_Name = "Name",
        PROP_ROLE_EqualValue = "EqualValue";

    <font color=#3F5FBF>/**
     * Retrieve context info for given context ID.
     *   
     * <font color=#7F9FBF>@param</font> id &ndash; context ID. 
     * <font color=#7F9FBF>@param</font> done - call back interface called when operation is completed.
     */</font>
    IToken getContext(String id, DoneGetContext done);

    <font color=#3F5FBF>/**
     * Client call back interface for getContext().
     */</font>
    <font color=#7F0055>interface</font> DoneGetContext {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context &ndash; context data.
         */</font>
        <font color=#7F0055>void</font> doneGetContext(IToken token, Exception error, RegistersContext context);
    }

    <font color=#3F5FBF>/**
     * Retrieve contexts available for registers commands.
     * A context corresponds to an execution thread, stack frame, registers group, etc.
     * A context can belong to a parent context. Contexts hierarchy can be simple
     * plain list or it can form a tree. It is up to target agent developers to choose
     * layout that is most descriptive for a given target. Context IDs are valid across
     * all services. In other words, all services access same hierarchy of contexts,
     * with same IDs, however, each service accesses its own subset of context's
     * attributes and functionality, which is relevant to that service.
     *  
     * <font color=#7F9FBF>@param</font> parent_context_id &ndash; parent context ID. Can be null &ndash;
     * to retrieve top level of the hierarchy, or one of context IDs retrieved
     * by previous getChildren commands.
     * <font color=#7F9FBF>@param</font> done - call back interface called when operation is completed.
     */</font>
    IToken getChildren(String parent_context_id, DoneGetChildren done);

    <font color=#3F5FBF>/**
     * Client call back interface for getChildren().
     */</font>
    <font color=#7F0055>interface</font> DoneGetChildren {
        <font color=#3F5FBF>/**
         * Called when contexts data retrieval is done.
         * <font color=#7F9FBF>@param</font> error &ndash; error description if operation failed, null if succeeded.
         * <font color=#7F9FBF>@param</font> context_ids &ndash; array of available context IDs.
         */</font>
        <font color=#7F0055>void</font> doneGetChildren(IToken token, Exception error, String[] context_ids);
    }
    
    <font color=#3F5FBF>/**
     * RegistersContext objects represent register groups, registers and bit fields. 
     */</font>
    <font color=#7F0055>interface</font> RegistersContext {
        <font color=#3F5FBF>/**
         * Get Context ID.
         * <font color=#7F9FBF>@return</font> context ID.
         */</font>
        String getID();
        
        <font color=#3F5FBF>/**
         * Get parent context ID.
         * <font color=#7F9FBF>@return</font> parent context ID.
         */</font>
        String getParentID();
        
        <font color=#3F5FBF>/**
         * Get context (register, register group, bit field) name.
         * <font color=#7F9FBF>@return</font> context name.
         */</font>
        String getName();
        
        <font color=#3F5FBF>/**
         * Get context description.
         * <font color=#7F9FBF>@return</font> context description.
         */</font>
        String getDescription();
        
        <font color=#3F5FBF>/**
         * Get context size in bytes.
         * Byte arrays in get()/set() methods should be same size.
         * Hardware register can be smaller then this size, for example in case
         * when register size is not an even number of bytes. In such case implementation
         * should add/remove padding that consists of necessary number of zero bits.
         * @return context size in bytes.
         */</font>
        <font color=#7F0055>int</font> getSize();
        
        <font color=#3F5FBF>/**
         * Check if context value can be read.
         * <font color=#7F9FBF>@return</font> true if can read value of the context.
         */</font>
        <font color=#7F0055>boolean</font> isReadable();
        
        <font color=#3F5FBF>/**
         * Check if reading the context (register) destroys its current value -
         * it can be read only once.
         * <font color=#7F9FBF>@return</font> true if read-once register.
         */</font>
        <font color=#7F0055>boolean</font> isReadOnce();
        
        <font color=#3F5FBF>/**
         * Check if context value can be written.
         * <font color=#7F9FBF>@return</font> true if can write value of the context.
         */</font>
        <font color=#7F0055>boolean</font> isWriteable();
        
        <font color=#3F5FBF>/**
         * Check if register value can not be overwritten - every write counts.
         * <font color=#7F9FBF>@return</font> true if write-once register.
         */</font>
        <font color=#7F0055>boolean</font> isWriteOnce();
        
        <font color=#3F5FBF>/**
         * Check if writing the context can change values of other registers. 
         * <font color=#7F9FBF>@return</font> true if has side effects.
         */</font>
        <font color=#7F0055>boolean</font> hasSideEffects();
        
        <font color=#3F5FBF>/**
         * Check if the register value can change even when target is stopped.
         * <font color=#7F9FBF>@return</font> true if the register value can change at any time.
         */</font>
        <font color=#7F0055>boolean</font> isVolatile();
        
        <font color=#3F5FBF>/**
         * Check if the register value is a floating-point value.
         * <font color=#7F9FBF>@return</font> true if a floating-point register.
         */</font>
        <font color=#7F0055>boolean</font> isFloat();
        
        <font color=#3F5FBF>/**
         * Check endianess of the context.
         * Big endian means decreasing numeric significance with increasing bit number. 
         * <font color=#7F9FBF>@return</font> true if big endian.
         */</font>
        <font color=#7F0055>boolean</font> isBigEndian();
        
        <font color=#3F5FBF>/**
         * Check if the lowest numbered bit (i.e. bit #0 or bit #1 depending on
         * getFirstBitNumber() value) should be shown to user as the left-most bit or
         * the right-most bit.
         * <font color=#7F9FBF>@return</font> true if the first bit is left-most bit.
         */</font>
        <font color=#7F0055>boolean</font> isLeftToRight();
        
        <font color=#3F5FBF>/**
         * If the context has bit field children, bit positions of the fields
         * can be zero-based or 1-based.
         * <font color=#7F9FBF>@return</font> first bit position - 0 or 1.
         */</font>
        <font color=#7F0055>int</font> getFirstBitNumber();
        
        <font color=#3F5FBF>/**
         * If context is a bit field, get the field bit numbers in parent context. 
         * <font color=#7F9FBF>@return</font> array of bit numbers.
         */</font>
        <font color=#7F0055>int</font>[] getBitNumbers();
        
        <font color=#3F5FBF>/**
         * A context can have predefined names (mnemonics) for some its values.
         * This method returns a list of such named values.
         * <font color=#7F9FBF>@return</font> array of named values or null.
         */</font>
        NamedValue[] getNamedValues();
        
        <font color=#3F5FBF>/**
         * Get complete map of context properties.
         * <font color=#7F9FBF>@return</font> map of context properties.
         */</font>
        Map&lt;String,Object&gt; getProperties();
        
        <font color=#3F5FBF>/**
         * Read value of the context.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
        IToken get(DoneGet done);
        
        <font color=#3F5FBF>/**
         * Set value of the context.
         * <font color=#7F9FBF>@param</font> value - value to write into the context.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
        IToken set(byte[] value, DoneSet done);

       <font color=#3F5FBF>/**
         * Search for contexts matching a filter.
         * <font color=#7F9FBF>@param</font> filter - map of name value pairs to search for.
         * <font color=#7F9FBF>@param</font> done - call back object.
         * <font color=#7F9FBF>@return</font> - pending command handle.
         */</font>
         IToken search(Map&lt;String,Object&gt; filter, DoneSearch done);
    }

    <font color=#3F5FBF>/**
     * A register context can have predefined names (mnemonics) for some its values.
     * NamedValue objects represent such values. 
     */</font>
    <font color=#7F0055>interface</font> NamedValue {
        <font color=#3F5FBF>/**
         * Get value associated with the name.
         * <font color=#7F9FBF>@return</font> the value as an array of bytes.
         */</font>
        byte[] getValue();
        
        <font color=#3F5FBF>/**
         * Get name (mnemonic) of the value.
         * <font color=#7F9FBF>@return</font> value name.
         */</font>
        String getName();
        
        <font color=#3F5FBF>/**
         * Get human readable description of the value.
         * <font color=#7F9FBF>@return</font> value description.
         */</font>
        String getDescription();
    }
    
    <font color=#3F5FBF>/**
     * Read values of multiple locations in registers.
     * <font color=#7F9FBF>@param</font> locs - array of data locations.
     * <font color=#7F9FBF>@param</font> done - call back object.
     * <font color=#7F9FBF>@return</font> - pending command handle.
     */</font>
    IToken getm(Location[] locs, DoneGet done);
    
    <font color=#3F5FBF>/**
     * Set values of multiple locations in registers.
     * <font color=#7F9FBF>@param</font> locs - array of data locations.
     * <font color=#7F9FBF>@param</font> value - value to write into the context.
     * <font color=#7F9FBF>@param</font> done - call back object.
     * <font color=#7F9FBF>@return</font> - pending command handle.
     */</font>
    IToken setm(Location[] locs, byte[] value, DoneSet done);
    <font color=#3F5FBF>/**
     * Class Location represents value location in register context
     */</font>
    <font color=#7F0055>final class</font> Location {
        <font color=#3F5FBF>/** Register context ID */</font>
        <font color=#7F0055>public final</font> String id; 

        <font color=#3F5FBF>/** offset in the context, in bytes */</font>
        <font color=#7F0055>public final int</font> offs;

        <font color=#3F5FBF>/** value size in bytes */</font>
        <font color=#7F0055>public final int</font> size;

        <font color=#7F0055>public</font> Location(String id, <font color=#7F0055>int</font> offs, <font color=#7F0055>int</font> size) {
            <font color=#7F0055>this</font>.id = id;
            <font color=#7F0055>this</font>.offs = offs;
            <font color=#7F0055>this</font>.size = size;
        }
    }

    <font color=#3F5FBF>/**
     * 'get' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneGet {
        <font color=#7F0055>void</font> doneGet(IToken token, Exception error, byte[] value);
    }
    
    <font color=#3F5FBF>/**
     * 'set' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneSet {
        <font color=#7F0055>void</font> doneSet(IToken token, Exception error);
    }

    <font color=#3F5FBF>/**
     * 'search' command call back interface.
     */</font>
    <font color=#7F0055>interface</font> DoneSearch {
        <font color=#7F0055>void</font> doneSearch(IToken token, String[][] contextPaths);
    }

    <font color=#3F5FBF>/**
     * Add registers service event listener.
     * <font color=#7F9FBF>@param</font> listener - event listener implementation.
     */</font>
    <font color=#7F0055>void</font> addListener(RegistersListener listener);

    <font color=#3F5FBF>/**
     * Remove registers service event listener.
     * <font color=#7F9FBF>@param</font> listener - event listener implementation.
     */</font>
    <font color=#7F0055>void</font> removeListener(RegistersListener listener);

    <font color=#3F5FBF>/**
     * Registers event listener is notified when registers context hierarchy
     * changes, and when a register is modified by the service commands. 
     */</font>
    <font color=#7F0055>interface</font> RegistersListener {

        <font color=#3F5FBF>/**
         * Called when register context properties changed.
         * Most targets have static set of registers and register properties.
         * Such targets never generate this event. However, some targets,
         * for example, JTAG probes, allow user to modify register definitions.
         * Clients should flush all cached register context data. 
         */</font>
        <font color=#7F0055>void</font> contextChanged();

        <font color=#3F5FBF>/**
         * Called when register content was changed and clients 
         * need to update themselves. Clients, at least, should invalidate
         * corresponding cached registers data.
         * Not every change is notified - it is not possible,
         * only those, which are not caused by normal execution of the debuggee.
         */</font>
        <font color=#7F0055>void</font> registerChanged(String context_id);
    }
}
</pre>

</body>
</html>