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.
+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.
| 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 unique 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 | +trunk (version?) | +||||
| 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 | -str710 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram1 | +str710 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -str710 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom2 | +str710 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -str912 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram3 | +str912 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -str912 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom4 | +str912 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -lpc2148 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram5 | +lpc2148 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -lpc2148 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom6 | +lpc2148 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -lpc2294 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram7 | +lpc2294 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -lpc2294 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom8 | +lpc2294 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -sam7s256 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram9 | +sam7s256 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -sam7s256 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom10 | +sam7s256 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -sam7x256 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram11 | +sam7x256 ram debugging | +JTAGkey | +517 | +n/a |
| bdte-rom | -sam7x256 ROM debugging | -JTAGkey | -423 | -n/a | +bdte-rom12 | +sam7x256 rom debugging | +JTAGkey | +517 | +n/a |
| bdte-ram | -at91r40008 RAM debugging | -JTAGkey | -423 | -n/a | +bdte-ram13 | +at91r40008 ram debugging | +JTAGkey | +517 | +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,8 @@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.
-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.
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_ram.gdb file.
@@ -279,7 +311,18 @@ Start address 0x62000040, load size 393628In 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