X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=testing%2Fsmoketests.html;h=7d5efc1cb3ae19af20890633c43b069c3f927b4d;hb=ae3baa9d5a09fa6b3ef23c74ea16f7a10b8a6406;hp=3d5cd9623d1906bbf36b57cfd30a4607c764b9c0;hpb=040e25424314b49e35eb158eb88e287c76e50596;p=openocd.git diff --git a/testing/smoketests.html b/testing/smoketests.html index 3d5cd9623d..7d5efc1cb3 100644 --- a/testing/smoketests.html +++ b/testing/smoketests.html @@ -4,7 +4,8 @@

OpenOCD smoketest results

- These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN. + These tests can be performed on any JTAG device as long as they are + executed using the unmodified code from git.

The latest version in which the test is known to have passed is in the table below.

Vocabulary

@@ -90,91 +91,91 @@ - + - + - + - + - + - + - + - + - + - + - + - + - +
bdte-ram1 str710 ram debugging JTAGkey536657 n/a
bdte-rom2 str710 rom debugging JTAGkey536657 n/a
bdte-ram3 str912 ram debugging JTAGkey536657 n/a
bdte-rom4 str912 rom debugging JTAGkey536657 n/a
bdte-ram5 lpc2148 ram debugging JTAGkey536657 n/a
bdte-rom6 lpc2148 rom debugging JTAGkey536657 n/a
bdte-ram7 lpc2294 ram debugging JTAGkey536657 n/a
bdte-rom8 lpc2294 rom debugging JTAGkey536657 n/a
bdte-ram9 sam7s256 ram debugging JTAGkey536657 n/a
bdte-rom10 sam7s256 rom debugging JTAGkey536657 n/a
bdte-ram11 sam7x256 ram debugging JTAGkey517657 n/a
bdte-rom12 sam7x256 rom debugging JTAGkey517657 n/a
bdte-ram13 at91r40008 ram debugging JTAGkey536657 n/a
@@ -182,7 +183,7 @@

OpenOCD JTAG device test results

Each JTAG device must be tested - + @@ -199,19 +200,19 @@ - + - + - + @@ -239,6 +240,8 @@ + + @@ -249,6 +252,8 @@ + + @@ -259,6 +264,8 @@ + + @@ -269,15 +276,27 @@ + +
ID
jtag2 JTAGkey536657 n/a
jtag3 Turtelizer2536657 n/a
jtag4 JTAGkey536657 n/a
r459 r517 r536r651r657
speed193 93 93162165
speed2n/a 52 52110111
speed3n/a n/a n/an/an/a

Policy on removing features from OpenOCD

- 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. -

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.

+ 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 mainline. The threshold for temporarily removing + something from OpenOCD mainline is low to ease maintainence and place the burden of maintainence on those that care about a feature. +

Note that code is never deleted from OpenOCD git, it remains in the + repository 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 + mainline. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.

Policy on adding features from OpenOCD

- 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. + 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 + mainline.

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.

ocd4 - ARM7 debugging

@@ -312,4 +331,4 @@

- \ No newline at end of file +