From: mifi Date: Sat, 1 Mar 2008 20:25:29 +0000 (+0000) Subject: - added test result for r423 X-Git-Tag: v0.1.0~864 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=71e3bb892f4ddc8424e3a75211c78f9c10477a62;p=openocd - added test result for r423 git-svn-id: svn://svn.berlios.de/openocd/trunk@425 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- diff --git a/testing/index.html b/testing/index.html index c30ec195..df9e81a1 100644 --- a/testing/index.html +++ b/testing/index.html @@ -33,121 +33,141 @@ ID Synopsis + JTAG device Passed version Broken version ocd1 Telnet Windows - 291 + n/a + n/a n/a ocd2 Telnet Linux - 291 + n/a + n/a n/a ocd3 Telnet Cygwin - 291 + n/a + n/a n/a ocd4 ARM7 debugging - 291 + n/a + n/a n/a xscale1 XScale debugging - 291 + n/a + n/a n/a xscale2 XScale MMU - 291 + n/a + n/a n/a bdte-ram str710 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom str710 rom debugging - 320 - 406 + JTAGkey + 423 + n/a bdte-ram str912 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom str912 rom debugging - 320 + JTAGkey + 423 n/a bdte-ram lpc2148 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom lpc2148 rom debugging - 320 + JTAGkey + 423 n/a bdte-ram lpc2294 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom lpc2294 rom debugging - 320 + JTAGkey + 423 n/a bdte-ram sam7s256 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom sam7s256 rom debugging - 320 + JTAGkey + 423 n/a bdte-ram sam7x256 ram debugging - 320 + JTAGkey + 423 n/a bdte-rom sam7x256 rom debugging - 320 + JTAGkey + 423 n/a bdte-ram at91r40008 ram debugging - 320 + JTAGkey + 423 n/a @@ -155,40 +175,68 @@

OpenOCD JTAG device test results

Each JTAG device must be tested + - - + + - - - + + + - - - + + + - - - + + + - - - + + +
IDSynopsisIDSynopsis Passed version Broken version
jtag1Wiggler291jtag1Parportn/a n/a
jtag2Parport291jtag2JTAGkey432 n/a
jtag3JTAGkey320jtag3Turtelizer2432 n/a
jtag4Turtelizer2320jtag4add new onen/a n/a

+

OpenOCD JTAG device speed test result

+

The test result is in KB/sec.

+ + + + + + + + + + + + + + + + + + + + + + +
IDSynopsisr320r420r423
speed1JTAGkey9364 93
speed2add new onen/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.

@@ -207,7 +255,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.