X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=testing%2Findex.html;h=85070ed5c8939f615082d471eee4728d4b732d78;hp=5bb321092c7036a236c45f06a5c0d8f9ba06556f;hb=32cc2202f0bd6a1d36f679008e965e5df68315ae;hpb=50f08f8f2ae2d4e439bca1760104bb54f0b6d07e diff --git a/testing/index.html b/testing/index.html index 5bb321092c..85070ed5c8 100644 --- a/testing/index.html +++ b/testing/index.html @@ -23,15 +23,15 @@
Passed version | -The latest version on which the test is known to pass | +The latest branch and version on which the test is known to pass |
Broken version | -The 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. |
ID | -A 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. |
The latest version in which the test is known to have passed is in the table below.
ID | +Unique ID | Synopsis | JTAG device | Passed version | Broken version | ||||
---|---|---|---|---|---|---|---|---|---|
fill_malloc | +fill_malloc | Fill malloc() memory with garbage | -n/a | -n/a | -n/a | +n/a | +n/a | +n/a | |
ocd1 | +ocd1 | Telnet Windows | -n/a | -n/a | -n/a | +n/a | +n/a | +n/a | |
ocd2 | +ocd2 | Telnet Linux | -n/a | -n/a | -n/a | +n/a | +n/a | +n/a | |
ocd3 | +ocd3 | Telnet Cygwin | -n/a | -n/a | -n/a | +n/a | +n/a | +n/a | |
ocd4 | +ocd4 | ARM7 debugging | -n/a | -n/a | -n/a | +n/a | +n/a | +n/a | |
xscale1 | +SAM9260 | +SAM9260 debugging | +ft2232 | +500 | +n/a | +||||
xscale1 | XScale debugging | -n/a | -n/a | -n/a | +bitbang | +505 | +n/a | ||
xscale2 | -XScale MMU | -n/a | -n/a | -n/a | +xscale2 | +XScale debugging | +FT2232 | +202 | +n/a |
bdte-ram | +bdte-ram1 | str710 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-rom | +bdte-rom2 | str710 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-ram | +bdte-ram3 | str912 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-rom | +bdte-rom4 | str912 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-ram | +bdte-ram5 | lpc2148 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-rom | +bdte-rom6 | lpc2148 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-ram | +bdte-ram7 | lpc2294 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-rom | +bdte-rom8 | lpc2294 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-ram | +bdte-ram9 | sam7s256 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-rom | +bdte-rom10 | sam7s256 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/a | |
bdte-ram | +bdte-ram11 | sam7x256 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +517 | +n/a | |
bdte-rom | +bdte-rom12 | sam7x256 rom debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +517 | +n/a | |
bdte-ram | +bdte-ram13 | at91r40008 ram debugging | -JTAGkey | -423 | -n/a | +JTAGkey | +536 | +n/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:
The test result is in KB/sec.
@@ -236,6 +253,9 @@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.
+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