zcy
/
tinyriscv-openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Cosmetic fixes from Uwe Hermann 

git-svn-id: svn://svn.berlios.de/openocd/trunk@460 b42882b7-edfa-0310-969c-e2dbd0fdcd60
__archive__
oharboe 2008-03-07 06:58:31 +00:00
parent d74d72c73a
commit 55b4d9a984
1 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
testing/index.html
View File

@ -17,13 +17,13 @@
is tested and thus all tests refer to committed code by subversion number.
<h1>Release procedure</h1>
OpenOCD trunk is work in progress. Expect it to change daily and to have some quirks.
<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>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 seeing. 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>
<td>The latest version on which the test is known to pass.</td>
</tr>
<tr>
<td width="100">Broken version</td>
@ -31,7 +31,7 @@
</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>
<td>A unique ID to refer to a test. The unique numbers are maintained in this file.</td>
</tr>
</table>
<p></p>
@ -98,91 +98,91 @@
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">str710 ram debugging</td>
<td width="165">str710 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">str710 rom debugging</td>
<td width="165">str710 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">str912 ram debugging</td>
<td width="165">str912 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">str912 rom debugging</td>
<td width="165">str912 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">lpc2148 ram debugging</td>
<td width="165">lpc2148 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">lpc2148 rom debugging</td>
<td width="165">lpc2148 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">lpc2294 ram debugging</td>
<td width="165">lpc2294 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">lpc2294 rom debugging</td>
<td width="165">lpc2294 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">sam7s256 ram debugging</td>
<td width="165">sam7s256 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">sam7s256 rom debugging</td>
<td width="165">sam7s256 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">sam7x256 ram debugging</td>
<td width="165">sam7x256 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
<td width="165">sam7x256 rom debugging</td>
<td width="165">sam7x256 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
<td width="165">at91r40008 ram debugging</td>
<td width="165">at91r40008 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
@ -257,12 +257,12 @@
<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>
<h1>Policy on adding features to 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.
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>
@ -282,4 +282,4 @@
<p></p>
</body>
</html>
</html>