X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=testing%2Findex.html;h=687bb90dd677e863cf6a5dc0588ab69dcd6808e8;hp=237f9e341cb34a16bf4f1539c94a133f13a5fcd0;hb=5a4525613dbd1b91ddbd9610e13b26eac6794f88;hpb=5a0910206cc96f7f48a48bfee2cc2720711f5b12 diff --git a/testing/index.html b/testing/index.html index 237f9e341c..687bb90dd6 100644 --- a/testing/index.html +++ b/testing/index.html @@ -3,25 +3,35 @@ -

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. + OpenOCD trunk is work in progress. Expect it to change daily and to have some quirks.

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.

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.

Vocabulary

- + - + - +
Passed versionThe latest version on which the test is known to passThe latest branch and version on which the test is known to pass
Broken versionThe latest version on which the test is known to fail. n/a when older than passed version.The latest branch and version on which the test is known to fail. n/a when older than passed version.
IDA unqiue ID to refer to a test. The unique numbers are maintained in this file.A unqiue ID to refer to a test. The unique numbers are maintained in this file. Note that the same test can be run on different hardware/interface. Each combination yields a unique id.

@@ -31,148 +41,247 @@

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

- + + - + + + + + + + + - - + + + - + - - + + + - + - - + + + - + - - + + + + + + + + + + - + - - + + + - - - - + + + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + - + - - + + + + + + + + + +
IDUnique ID SynopsisJTAG device Passed version Broken version
ocd1fill_mallocFill malloc() memory with garbagen/an/an/a
ocd1 Telnet Windows291n/an/an/an/a
ocd2ocd2 Telnet Linux291n/an/an/an/a
ocd3ocd3 Telnet Cygwin291n/an/an/an/a
ocd4ocd4 ARM7 debugging291n/an/an/an/a
SAM9260SAM9260 debuggingft2232 500trunk (version?)
xscale1xscale1 XScale debugging291n/abitbang505n/a
xscale2XScale MMU291n/axscale2XScale debuggingFT2232202n/a
bdte-rambdte-ram1 str710 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom2 str710 rom debugging320406JTAGkey517n/a
bdte-rambdte-ram3 str912 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom4 str912 rom debugging320n/aJTAGkey517n/a
bdte-rambdte-ram5 lpc2148 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom6 lpc2148 rom debugging320n/aJTAGkey517n/a
bdte-rambdte-ram7 lpc2294 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom8 lpc2294 rom debugging320n/aJTAGkey517n/a
bdte-rambdte-ram9 sam7s256 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom10 sam7s256 rom debugging320n/aJTAGkey517n/a
bdte-rambdte-ram11 sam7x256 ram debugging320n/aJTAGkey517n/a
bdte-rombdte-rom12 sam7x256 rom debugging320n/aJTAGkey517n/a
bdte-ram13at91r40008 ram debuggingJTAGkey517n/a

OpenOCD JTAG device test results

Each JTAG device must be tested + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
IDSynopsisPassed versionBroken version
jtag1Parportn/an/a
jtag2JTAGkey517n/a
jtag3Turtelizer2517n/a
jtag4JTAGkey517n/a
jtag5add new onen/an/a
+

jtag1:

+

jtag2: Tested on Windows XP Prof. (SP2) with original FTDI driver.

+

jtag3: Tested on Windows XP Prof. (SP2) with original FTDI driver.

+

jtag4: Tested on Mac OS X (10.5.2, Intel) with libftdi-0.10 and libusb-0.1.12

+

jtag5:

+
+

OpenOCD JTAG device speed test result

+

The test result is in KB/sec.

- - - - + + + + + + + - - - - + + + + + + + - - - - + + + + + + + - - - - + + + + + + +
IDSynopsisPassed versionBroken versionIDSynopsisr320r420r423r459r517
jtag1Wiggler291n/aspeed1JTAGkey9364 939393
jtag2Parport291n/aspeed2JTAGkeyn/an/an/an/a52
jtag3JTAGkey406n/aspeed3add new onen/an/an/an/an/a

@@ -195,6 +304,23 @@

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.

+

The test was made on Windows XP Prof. (SP2) with a JTAGkey and the original FTDI driver.

+
+

speed2 - 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: 52 KB/sec, 2008 bytes/write.

+

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

+

The test was made on Mac OS X (10.5.2, Intel) with a JTAGkey and the following driver:

+

- libftdi 0.10
+ - libusb 0.1.12