diff --git a/testing/index.html b/testing/index.html index c30ec1954..df9e81a1a 100644 --- a/testing/index.html +++ b/testing/index.html @@ -33,121 +33,141 @@
ID | -Synopsis | +ID | +Synopsis | Passed version | Broken version | |
---|---|---|---|---|---|---|
jtag1 | -Wiggler | -291 | +jtag1 | +Parport | +n/a | n/a |
jtag2 | -Parport | -291 | +jtag2 | +JTAGkey | +432 | n/a |
jtag3 | -JTAGkey | -320 | +jtag3 | +Turtelizer2 | +432 | n/a |
jtag4 | -Turtelizer2 | -320 | +jtag4 | +add new one | n/a | +n/a | +
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 |
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.
- +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.