- added test result for str710, and test description
[openocd.git] / testing / index.html
index 8aabcd44868a53bf91d4d7fc54a0e983320219c2..066a0c7ec39050f3188d2faf3fc89679d3a1b537 100644 (file)
 <html>
 <html>
-<body>
-<h1>Testing</h1>
-A test should be done on code committed to svn. Commit, then test. That way
-one can know for sure *what* code was actually tested.
-<h1>Release procedure</h1>
-OpenOCD trunk is work in progress. Expect it to change daily and to have
-some work in progress.
-<p>
-If you need the latest released and tested version, look for binary snapshots of
-OpenOCD. Worst case look up the test result table below for the features
-that are important to you and extract and build the version that has the right
-cocktail of working features for you. You can also work with the community
-to address the problems you are seing. Testing work and bug reports are
-highly appreciated.
-<p>
-The OpenOCD community may decide to create release branches. If
-this happens, then a branch will be created from OpenOCD trunk. The particular
-version to create that branch might be an older version rather than the latest
-and greatest. Fixes are then ported to that release branch from OpenOCD trunk.
-<h2>Vocabulary</h2>
-<table border=1>
-<tr><td>Passed version</td><td>The latest version on which the test is known to pass</td></tr>
-<tr><td>Broken version</td><td>The latest version on which the test is known to fail. n/a when older than passed version.</td></tr>
-<tr><td>ID</td><td>A unqiue ID to refer to a test. The unique numbers are maintained in this file.</td></tr>
-</table>
 
 
-<h1>OpenOCD test results</h1>
-These tests can be performed on any JTAG device as long
-as they are executed using the unmodified code from SVN.
-<p>
-The latest version in which the test is known to have
-passed is in the table below.
-<table border=1>
-       <tr><th>ID</th><th>Synopsis</th><th>Passed version</th><th>Broken version</th></tr>
-       <tr><td>ocd1</td><td>Telnet Windows</td><td>291</td><td>n/a</td></tr>
-       <tr><td>ocd2</td><td>Telnet Linux</td><td>291</td><td>n/a</td></tr>
-       <tr><td>ocd3</td><td>Telnet Cygwin</td><td>291</td><td>n/a</td></tr>
-       <tr><td><a href="#test_ocd4">ocd4</a></td><td>ARM7 debugging</td><td>291</td></tr>
-       <tr><td>xscale1</a></td><td>XScale debugging</td><td>291</td></tr>
-       <tr><td>xscale2</a></td><td>XScale MMU</td><td>291</td></tr>
-</table>
-<h1>OpenOCD JTAG device test results</h1>
-Each JTAG device must be tested
-<table border=1>
-       <tr><th>ID</th><th>Synopsis</th><th>Passed version</th><th>Broken version</th></tr>
-       <tr><td>jtag1</td><td>Wiggler</td><td>291</td><td>n/a</td></tr>
-       <tr><td>jtag2</td><td>Parport</td><td>291</td><td>n/a</td></tr>
-       <tr><td>jtag3</td><td>...</td><td>291</td><td>n/a</td></tr>
-</table>
+       <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
 
 
-<h1>Policy on removing features from OpenOCD</h1>
-If a feature in OpenOCD is known to be broken and nobody has
-submitted a fix and the feature is causing trouble for
-maintainence, it can be removed from OpenOCD trunk. The threshold
-for temporarily removing something from OpenOCD trunk is low to
-ease maintainence and place the burden of maintainence on
-those that care about a feature.
-<p>
-Note that code is never deleted from OpenOCD svn, it remains
-in svn so if somebody sees a feature removed that they would
-like kept, they have but to port and fix that feature
-back up to main trunk. This document can be helpful in this
-regard in that the latest working version and the known broken
-version may be listed.
-<h1>Policy on adding features from OpenOCD</h1>
-To add a feature to OpenOCD, generally  it should not break any existing
-features and it should be functional and the code reasonably readable
-and useful to others in the OpenOCD community. The code does not
-have to be completed. Work in progress is fine for OpenOCD trunk.
-<p>
-Also new tests should be defined. Note that the code does not have
-to pass all the tests. In fact it can be helpful to have tests
-to describe facets that really should be working, but aren't
-done yet.
-<a name="test_ocd4">
-<h1>ocd4 - ARM7 debugging</h1>
-Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step.
-</body>
-</html>
+       <body>
+               <h1>Testing</h1>
+               A test should be done on code committed to svn. Commit, then test. That way one can know for sure *what* code was actually tested.
+               <h1>Release procedure</h1>
+               OpenOCD trunk is work in progress. Expect it to change daily and to have some work in progress.
+               <p>If you need the latest released and tested version, look for binary snapshots of OpenOCD. Worst case look up the test result table below for the features that are important to you and extract and build the version that has the right cocktail of working features for you. You can also work with the community to address the problems you are seing. Testing work and bug reports are highly appreciated.</p>
+               <p>The OpenOCD community may decide to create release branches. If this happens, then a branch will be created from OpenOCD trunk. The particular version to create that branch might be an older version rather than the latest and greatest. Fixes are then ported to that release branch from OpenOCD trunk.</p>
+               <h2>Vocabulary</h2>
+               <table border="1">
+                       <tr>
+                               <td width="100">Passed version</td>
+                               <td>The latest version on which the test is known to pass</td>
+                       </tr>
+                       <tr>
+                               <td width="100">Broken version</td>
+                               <td>The latest version on which the test is known to fail. n/a when older than passed version.</td>
+                       </tr>
+                       <tr>
+                               <td width="100">ID</td>
+                               <td>A unqiue ID to refer to a test. The unique numbers are maintained in this file.</td>
+                       </tr>
+               </table>
+               <p></p>
+               <hr>
+               <h1>OpenOCD test results</h1>
+               These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN.
+               <p>The latest version in which the test is known to have passed is in the table below.</p>
+               <table border="1">
+                       <tr>
+                               <th width="65">ID</th>
+                               <th width="150">Synopsis</th>
+                               <th align="center" width="110">Passed version</th>
+                               <th align="center" width="110">Broken version</th>
+                       </tr>
+                       <tr>
+                               <td width="65">ocd1</td>
+                               <td width="150">Telnet Windows</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65">ocd2</td>
+                               <td width="150">Telnet Linux</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65">ocd3</td>
+                               <td width="150">Telnet Cygwin</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65"><a href="#test_ocd4">ocd4</a></td>
+                               <td width="150">ARM7 debugging</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65">xscale1</td>
+                               <td width="150">XScale debugging</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65">xscale2</td>
+                               <td width="150">XScale MMU</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65"><a href="#bdte-ram">bdte-ram</a></td>
+                               <td width="150">str710 ram debugging</td>
+                               <td align="center" width="110">320</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="65"><a href="#bdte-rom">bdte-rom</a></td>
+                               <td width="150">str710 rom debugging</td>
+                               <td align="center" width="110">320</td>
+                               <td align="center" width="110"><b>406</b></td>
+                       </tr>
+               </table>
+               <p></p>
+               <hr>
+               <h1>OpenOCD JTAG device test results</h1>
+               Each JTAG device must be tested
+               <table border="1">
+                       <tr>
+                               <th align="center" width="45">ID</th>
+                               <th width="65">Synopsis</th>
+                               <th width="110">Passed version</th>
+                               <th width="110">Broken version</th>
+                       </tr>
+                       <tr>
+                               <td width="45">jtag1</td>
+                               <td width="65">Wiggler</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="45">jtag2</td>
+                               <td width="65">Parport</td>
+                               <td align="center" width="110">291</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+                       <tr>
+                               <td width="45">jtag3</td>
+                               <td width="65">JTAGkey</td>
+                               <td align="center" width="110">406</td>
+                               <td align="center" width="110">n/a</td>
+                       </tr>
+               </table>
+               <p></p>
+               <hr>
+               <h1>Policy on removing features from OpenOCD</h1>
+               If a feature in OpenOCD is known to be broken and nobody has submitted a fix and the feature is causing trouble for maintainence, it can be removed from OpenOCD trunk. The threshold for temporarily removing something from OpenOCD trunk is low to ease maintainence and place the burden of maintainence on those that care about a feature.
+               <p>Note that code is never deleted from OpenOCD svn, it remains in svn so if somebody sees a feature removed that they would like kept, they have but to port and fix that feature back up to main trunk. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.</p>
+               <h1>Policy on adding features from OpenOCD</h1>
+               To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk.
+               <p>Also new tests should be defined. Note that the code does not have to pass all the tests. In fact it can be helpful to have tests to describe facets that really should be working, but aren't done yet. </p>
+               <hr>
+               <h1>ocd4 - ARM7 debugging<a name="test_ocd4"></a></h1>
+               Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step.
+               <hr>
+               <h1>bdte-ram (Basic debugging test with Eclipse in RAM)<a id="bdte-ram" name="bdte-ram"></a></h1>
+               <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_ram.gdb</b> file.</p>
+               <p>Start debugging,  the debugger should stop at main. set some breakpoints and &quot;Resume&quot;. If the debugger hit a breakpoint check if the &quot;Variables&quot; looks correct. Remove some breakpoints and &quot;Resume&quot; again. If the target is running, use the &quot;Suspend&quot; function and use &quot;Step Into&quot; or &quot;Step Over&quot; through the source. Even open the &quot;Disassembly&quot; view and enable the &quot;Instruction Stepping Mode&quot;. Now you can single step through the assembler source. Use &quot;Resume&quot; again to run the program, set a breakpoint while the target is running. Check if  you can inspect the variables with the mouse over. Play a little with the target...</p>
+               <hr>
+               <h1>bdte-rom (Basic debugging test with Eclipse in ROM)<a id="bdte-rom" name="bdte-rom"></a></h1>
+               <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_rom.gdb</b> file.</p>
+               <p>Start debugging, the debugger should download and store the program in the flash of the target.</p>
+               <p>Now you can make some tests like described in the <a href="#bdte-ram">bdte-ram</a> section above too.</p>
+               <p></p>
+               <p></p>
+       </body>
+
+</html>
\ No newline at end of file

Linking to existing account procedure

If you already have an account and want to add another login method you MUST first sign in with your existing account and then change URL to read https://review.openocd.org/login/?link to get to this page again but this time it'll work for linking. Thank you.

SSH host keys fingerprints

1024 SHA256:YKx8b7u5ZWdcbp7/4AeXNaqElP49m6QrwfXaqQGJAOk gerrit-code-review@openocd.zylin.com (DSA)
384 SHA256:jHIbSQa4REvwCFG4cq5LBlBLxmxSqelQPem/EXIrxjk gerrit-code-review@openocd.org (ECDSA)
521 SHA256:UAOPYkU9Fjtcao0Ul/Rrlnj/OsQvt+pgdYSZ4jOYdgs gerrit-code-review@openocd.org (ECDSA)
256 SHA256:A13M5QlnozFOvTllybRZH6vm7iSt0XLxbA48yfc2yfY gerrit-code-review@openocd.org (ECDSA)
256 SHA256:spYMBqEYoAOtK7yZBrcwE8ZpYt6b68Cfh9yEVetvbXg gerrit-code-review@openocd.org (ED25519)
+--[ED25519 256]--+
|=..              |
|+o..   .         |
|*.o   . .        |
|+B . . .         |
|Bo. = o S        |
|Oo.+ + =         |
|oB=.* = . o      |
| =+=.+   + E     |
|. .=o   . o      |
+----[SHA256]-----+
2048 SHA256:0Onrb7/PHjpo6iVZ7xQX2riKN83FJ3KGU0TvI0TaFG4 gerrit-code-review@openocd.zylin.com (RSA)