X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;ds=inline;f=testing%2Findex.html;h=267c2a7be33353dd467296ffc5a1c6d857d44aaa;hb=6c1d9b7245e19a3305fe78037bd69fb04808e0b7;hp=716eb8082a83a05ae917f786a0be430b6377b63a;hpb=44ab4ec6cebcfb6a552c752a08123f8379d0cc05;p=openocd.git diff --git a/testing/index.html b/testing/index.html index 716eb8082a..267c2a7be3 100644 --- a/testing/index.html +++ b/testing/index.html @@ -3,8 +3,18 @@ -

Testing

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

Release testing

+ A release test must be done on code committed to svn. Commit, then test. That way one can know for sure *what* code was actually tested. +

+ Note that this testing document does not have anything to do with testing that is done + before committing to svn. It is a test document for released code. Pre-commit testing + is done mostly by the developer who has written the change. Release testing is + done on code believed to be stable, often a couple of weeks old, and not by + the developers, but rather users and community testers who has the requisite hardware + and test setup. Also the testing can take place over an extended period of time. +

+ All of the above makes it imperative that there can be no doubt about *which* code + is tested and thus all tests refer to committed code by subversion number.

Release procedure

OpenOCD trunk is work in progress. Expect it to change daily and to have some work in progress.

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.

@@ -32,92 +42,142 @@ - + + - - + + + - - + + + - - + + + - - + + + - - + + + - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - + + + - - - + + + + - - + + + - - + + + - - + + + - - + + + - - + + + - - + + + + + + + + + +

ID	Synopsis	Synopsis	JTAG device	Passed version	Broken version
ocd1	Telnet Windows	291	Telnet Windows	n/a	n/a	n/a
ocd2	Telnet Linux	291	Telnet Linux	n/a	n/a	n/a
ocd3	Telnet Cygwin	291	Telnet Cygwin	n/a	n/a	n/a
ocd4	ARM7 debugging	291	ARM7 debugging	n/a	n/a	n/a
xscale1	XScale debugging	291	XScale debugging	n/a	n/a	n/a
xscale2	XScale MMU	291	XScale MMU	n/a	n/a	n/a
bdte-ram	str710 ram debugging	JTAGkey	423	n/a
bdte-rom	str710 rom debugging	JTAGkey	423	n/a
bdte-ram	str912 ram debugging	JTAGkey	423	n/a
bdte-rom	str912 rom debugging	JTAGkey	423	n/a
bdte-ram	str710 ram debugging	320	lpc2148 ram debugging	JTAGkey	423	n/a
bdte-rom	str710 rom debugging	320	406	lpc2148 rom debugging	JTAGkey	423	n/a
bdte-ram	str912 ram debugging	320	lpc2294 ram debugging	JTAGkey	423	n/a
bdte-rom	str912 rom debugging	320	lpc2294 rom debugging	JTAGkey	423	n/a
bdte-ram	lpc2148 ram debugging	320	sam7s256 ram debugging	JTAGkey	423	n/a
bdte-rom	lpc2148 rom debugging	320	sam7s256 rom debugging	JTAGkey	423	n/a
bdte-ram	lpc2294 ram debugging	320	sam7x256 ram debugging	JTAGkey	423	n/a
bdte-rom	lpc2294 rom debugging	320	sam7x256 rom debugging	JTAGkey	423	n/a
bdte-ram	at91r40008 ram debugging	JTAGkey	423	n/a

@@ -125,34 +185,68 @@

OpenOCD JTAG device test results

Each JTAG device must be tested + - - + + - - - + + + + + + + + + - - - + + + - - - + + +

ID	Synopsis	ID	Synopsis	Passed version	Broken version
jtag1	Wiggler	291	jtag1	Parport	n/a	n/a
jtag2	JTAGkey	432	n/a
jtag2	Parport	291	jtag3	Turtelizer2	432	n/a
jtag3	JTAGkey	406	jtag4	add new one	n/a	n/a

OpenOCD JTAG device speed test result

The test result is in KB/sec.

+ + + + + + + + + + + + + + + + + + + + + + +

ID	Synopsis	r320	r420	r423
speed1	JTAGkey	93	64	93
speed2	add new one	n/a	n/a	n/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.

@@ -171,7 +265,13 @@

This test was made under Eclipse with the Zylin Embedded CDT plugin. For the GDB "Initialize commands" take a look in the examples/<target>/prj/eclipse_rom.gdb file.

Start debugging, the debugger should download and store the program in the flash of the target.

Now you can make some tests like described in the bdte-ram section above too.

speed1 - Download speed test

For this test a STR710 with external memory was used. The example project can be found under examples/STR710JtagSpeed. Here Eclipse or the arm-elf-gdb can be used to download the test.elf file into the RAM. The result of the GDB can look like:

Loading section .text, size 0x6019c lma 0x62000000
+ Start address 0x62000040, load size 393628
+ Transfer rate: 93 KB/sec, 2008 bytes/write.

In this example a speed of 93 KB/sec was reached. The hardware which was used for the test can be found here.