aboutsummaryrefslogtreecommitdiff
path: root/testing
diff options
context:
space:
mode:
authorntfreak <ntfreak@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2008-04-24 11:09:28 +0000
committerntfreak <ntfreak@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2008-04-24 11:09:28 +0000
commit040e25424314b49e35eb158eb88e287c76e50596 (patch)
treed1ce68d4db10cdd9868ab9bf73e7b04c92f50efb /testing
parent6ef27f4534b7a8926866b1156b6a309fc7c3d300 (diff)
- added svn props for newly added files
git-svn-id: svn://svn.berlios.de/openocd/trunk@615 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'testing')
-rw-r--r--testing/examples/SAM7S256Test/results/607.html1394
-rw-r--r--testing/results/template.html34
-rw-r--r--testing/smoketests.html628
-rw-r--r--testing/testcases.html1154
4 files changed, 1605 insertions, 1605 deletions
diff --git a/testing/examples/SAM7S256Test/results/607.html b/testing/examples/SAM7S256Test/results/607.html
index 570b3b34..852c0ad6 100644
--- a/testing/examples/SAM7S256Test/results/607.html
+++ b/testing/examples/SAM7S256Test/results/607.html
@@ -1,698 +1,698 @@
-<html>
-<head>
-<title>Test results for revision 607</title>
-</head>
-
-<body>
-<H1>Test cases</H1>
-<H2>Test case results</H2>
-The test results are stored in seperate documents. One document for
-each subversion number.
-<table border="1">
- <tr><td>Test results</td><td>comment</td></tr>
- <tr><td>607</a></td><td></td></tr>
- <tr><td><a href="results/template.html">template</a></td><td>Test results template</td></tr>
-</table>
-
-<H1>SAM7S64</H1>
-
-<H2>Connectivity</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="CON001"/>CON001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Telnet connection</td>
- <td>Power on, jtag target attached</td>
- <td>On console, type<br><code>telnet ip port</code></td>
- <td><code>Open On-Chip Debugger<br>></code></td>
- <td><code>Open On-Chip Debugger<br>></code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="CON002"/>CON002</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>GDB server connection</td>
- <td>Power on, jtag target attached</td>
- <td>On GDB console, type<br><code>target remote ip:port</code></td>
- <td><code>Remote debugging using 10.0.0.73:3333</code></td>
- <td><code>Remote debugging using 10.0.0.73:3333</code></td>
- <td>PASS</td>
- </tr>
-</table>
-
-<H2>Reset</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="RES001"/>RES001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Reset halt on a blank target</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
- <td>
- <code>
- JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
- nSRST pulls nTRST, falling back to "reset run_and_halt"<br>
- target state: halted<br>
- target halted in ARM state due to debug request, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00100178
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="RES002"/>RES002</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Reset init on a blank target</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset init</code></td>
- <td>Reset should return without error and the output should contain <br><code>executing reset script 'name_of_the_script'</code></td>
- <td>
- <code>
- JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
- nSRST pulls nTRST, falling back to "reset run_and_init"<br>
- target state: halted<br>
- target halted in ARM state due to debug request, current mode: Supervisor<br>
- cpsr: 0x600000d3 pc: 0x00003e24<br>
- executing reset script 'event/sam7s256_reset.script'
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="RES003"/>RES003</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Reset after a power cycle of the target</td>
- <td>Reset the target then power cycle the target</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code> after the power was detected</td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted</code></td>
- <td>
- <code>
- JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
- nSRST pulls nTRST, falling back to "reset run_and_halt"<br>
- target state: halted<br>
- target halted in ARM state due to debug request, current mode: Supervisor<br>
- cpsr: 0x300000d3 pc: 0x00003a38
- </code>
- </td>
- <td>PASS</td>
- </tr>
-</table>
-
-<H2>JTAG Speed</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>ZY1000</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="SPD001"/>RES001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>16MHz on normal operation</td>
- <td>Reset init the target according to RES002 </td>
- <td>Exercise a memory access over the JTAG, for example <br><code>mdw 0x0 32</code></td>
- <td>The command should run without any errors. If any JTAG checking errors happen, the test failed</td>
- <td>
- <code>
- > jtag_khz 16000<br>
- > mdw 0 32<br>
- 0x00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code>
- </td>
- <td>PASS</td>
- </tr>
-</table>
-
-<H2>Debugging</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="DBG001"/>DBG001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Load is working</td>
- <td>Reset init is working, RAM is accesible, GDB server is started</td>
- <td>On the console of the OS: <br>
- <code>arm-elf-gdb test_ram.elf</code><br>
- <code>(gdb) target remote ip:port</code><br>
- <code>(gdb) load</load>
- </td>
- <td>Load should return without error, typical output looks like:<br>
- <code>
- Loading section .text, size 0x14c lma 0x0<br>
- Start address 0x40, load size 332<br>
- Transfer rate: 180 bytes/sec, 332 bytes/write.<br>
- </code>
- </td>
- <td><code>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x200000<br>
- Start address 0x200040, load size 404<br>
- Transfer rate: 17470 bits/sec, 404 bytes/write.
- </code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG002"/>DBG002</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Software breakpoint</td>
- <td>Load the test_ram.elf application, use instructions from GDB001</td>
- <td>In the GDB console:<br>
- <code>
- (gdb) monitor arm7_9 sw_bkpts enable<br>
- software breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0xec: file src/main.c, line 71.<br>
- (gdb) continue<br>
- Continuing.
- </code>
- </td>
- <td>The software breakpoint should be reached, a typical output looks like:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x000000d3 pc: 0x000000ec<br>
- <br>
- Breakpoint 1, main () at src/main.c:71<br>
- 71 DWORD a = 1;
- </code>
- </td>
- <td>
- <code>
- (gdb) break main<br>
- Breakpoint 2 at 0x200134: file src/main.c, line 69.<br>
- (gdb) c<br>
- Continuing.<br>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00200134<br>
- <br>
- Breakpoint 2, main () at src/main.c:69<br>
- 69 DWORD a = 1;
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG003"/>DBG003</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Single step in a RAM application</td>
- <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
- <td>In GDB, type <br><code>(gdb) step</code></td>
- <td>The next instruction should be reached, typical output:<br>
- <code>
- (gdb) step<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f0<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f4<br>
- 72 DWORD b = 2;
- </code>
- </td>
- <td>
- <code>
- (gdb) step<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f0<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f4<br>
- 72 DWORD b = 2;
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG004"/>DBG004</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Software break points are working after a reset</td>
- <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
- <td>In GDB, type <br><code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- (gdb) continue<br>
- </code></td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x000000d3 pc: 0x000000ec<br>
- <br>
- Breakpoint 1, main () at src/main.c:71<br>
- 71 DWORD a = 1;
- </code>
- </td>
- <td><code>
- (gdb) moni reset<br>
- JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
- target state: halted<br>
- target halted in ARM state due to debug request, current mode: Supervisor<br>
- cpsr: 0x600000d3 pc: 0x00003e28<br>
- executing reset script 'event/sam7s256_reset.script'<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x200000<br>
- Start address 0x200040, load size 404<br>
- Transfer rate: 20455 bits/sec, 404 bytes/write.<br>
- (gdb) continue<br>
- Continuing.<br>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00200134<br>
- <br>
- Breakpoint 2, main () at src/main.c:69<br>
- 69 DWORD a = 1;
- </code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG005"/>DBG005</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Hardware breakpoint</td>
- <td>Flash the test_rom.elf application. Make this test after FLA004 has passed</td>
- <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
- (gdb) monitor arm7_9 force_hw_bkpts enable<br>
- force hardware breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
- (gdb) continue<br>
- </code>
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- </code>
- </td>
- <td>
- <code>
- (gdb) break main<br>
- Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
- (gdb) c<br>
- Continuing.<br>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00100134<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG006"/>DBG006</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Hardware breakpoint is set after a reset</td>
- <td>Follow the instructions to flash and insert a hardware breakpoint from DBG005</td>
- <td>In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) monitor reg pc 0x100000<br>
- pc (/32): 0x00100000<br>
- (gdb) continue
- </code><br>
- where the value inserted in PC is the start address of the application
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- </code>
- </td>
- <td>
- <code>
- Continuing.<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00100040<br>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00100134<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;
- </code><br>
- <b>Aren't there too many "halted" signs?</b>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="DBG007"/>DBG007</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Single step in ROM</td>
- <td>Flash the test_rom.elf application and set a breakpoint in main, use DBG005. Make this test after FLA004 has passed</td>
- <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
- (gdb) monitor arm7_9 force_hw_bkpts enable<br>
- force hardware breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
- (gdb) continue<br>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- (gdb) step
- </code>
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x0010013c<br>
- 70 DWORD b = 2;<br>
- </code>
- </td>
- <td><code>
- (gdb) step<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x00100138<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x0010013c<br>
- 70 DWORD b = 2;
- </code></td>
- <td>PASS</td>
- </tr>
-</table>
-
-<H2>RAM access</H2>
-Note: these tests are not designed to test/debug the target, but to test functionalities!
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="RAM001"/>RAM001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>32 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mww ram_address 0xdeadbeef 16<br>
- > mdw ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 32bit long containing 0xdeadbeef.<br>
- <code>
- > mww 0x0 0xdeadbeef 16<br>
- > mdw 0x0 32<br>
- 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00000040: e1a00000 e59fa51c e59f051c e04aa000 00080017 00009388 00009388 00009388<br>
- 0x00000060: 00009388 0002c2c0 0002c2c0 000094f8 000094f4 00009388 00009388 00009388<br>
- </code>
- </td>
- <td>
- <code>
- > mww 0x00200000 0xdeadbeef 16<br>
- > mdw 0x00200000 32<br>
- 0x00200000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00200020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00200040: e59f10b4 e3a00902 e5810004 e59f00ac e59f10ac e5810000 e3e010ff e59f00a4<br>
- 0x00200060: e5810060 e59f10a0 e3e00000 e5810130 e5810124 e321f0db e59fd090 e321f0d7
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="RAM002"/>RAM002</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>16 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mwh ram_address 0xbeef 16<br>
- > mdh ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 16bit long containing 0xbeef.<br>
- <code>
- > mwh 0x0 0xbeef 16<br>
- > mdh 0x0 32<br>
- 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
- 0x00000020: 00e0 0000 021c 0000 0240 0000 026c 0000 0288 0000 0000 0000 0388 0000 0350 0000<br>
- >
- </code>
- </td>
- <td><code>
- > mwh 0x00200000 0xbeef 16<br>
- > mdh 0x00200000 32<br>
- 0x00200000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
- 0x00200020: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
- </code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="RAM003"/>RAM003</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>8 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mwb ram_address 0xab 16<br>
- > mdb ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 8bit long containing 0xab.<br>
- <code>
- > mwb ram_address 0xab 16<br>
- > mdb ram_address 32<br>
- 0x00000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>
- >
- </code>
- </td>
- <td><code>
- > mwb 0x00200000 0xab 16<br>
- > mdb 0x00200000 32<br>
- 0x00200000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- </code></td>
- <td>PASS</td>
- </tr>
-</table>
-
-
-
-<H2>Flash access</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Actual output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="FLA001"/>FLA001</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Flash probe</td>
- <td>Reset init is working</td>
- <td>On the telnet interface:<br>
- <code> > flash probe 0</code>
- </td>
- <td>The command should execute without error. The output should state the name of the flash and the starting address. An example of output:<br>
- <code>flash 'ecosflash' found at 0x01000000</code>
- </td>
- <td>
- <code>
- > flash probe 0<br>
- flash 'at91sam7' found at 0x00100000
- </code>
- </td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="FLA002"/>FLA002</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>flash fillw</td>
- <td>Reset init is working, flash is probed</td>
- <td>On the telnet interface<br>
- <code> > flash fillw 0x1000000 0xdeadbeef 16
- </code>
- </td>
- <td>The commands should execute without error. The output looks like:<br>
- <code>
- wrote 64 bytes to 0x01000000 in 11.610000s (0.091516 kb/s)
- </code><br>
- To verify the contents of the flash:<br>
- <code>
- > mdw 0x1000000 32<br>
- 0x01000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x01000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code>
- </td>
- <td><code>
- > flash fillw 0x100000 0xdeadbeef 16<br>
- wrote 64 bytes to 0x00100000 in 1.110000s (0.957207 kb/s)<br>
- > mdw 0x100000 32<br>
- 0x00100000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00100020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="FLA003"/>FLA003</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Flash erase</td>
- <td>Reset init is working, flash is probed</td>
- <td>On the telnet interface<br>
- <code> > flash erase_address 0x1000000 0x2000
- </code>
- </td>
- <td>The commands should execute without error.<br>
- <code>
- erased address 0x01000000 length 8192 in 4.970000s
- </code>
- To check that the flash has been erased, read at different addresses. The result should always be 0xff.
- <code>
- > mdw 0x1000000 32<br>
- 0x01000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code>
- </td>
- <td><code>
- > flash erase_address 0x100000 0x2000<br>
- erased address 0x00100000 length 8192 in 0.510000s<br>
- > mdw 0x100000 32<br>
- 0x00100000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00100020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- >
- </code></td>
- <td>PASS</td>
- </tr>
- <tr>
- <td><a name="FLA004"/>FLA004</td>
- <td>SAM7S64</td>
- <td>ZY1000</td>
- <td>Loading to flash from GDB</td>
- <td>Reset init is working, flash is probed, connectivity to GDB server is working</td>
- <td>Start GDB using a ROM elf image, eg: arm-elf-gdb test_rom.elf. <br>
- <code>
- (gdb) target remote ip:port<br>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.
- (gdb) monitor verify_image path_to_elf_file
- </code>
- </td>
- <td>The output should look like:<br>
- <code>
- verified 404 bytes in 5.060000s
- </code><br>
- The failure message is something like:<br>
- <code>Verify operation failed address 0x00200000. Was 0x00 instead of 0x18</code>
- </td>
- <td>
- <code>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 1540 bits/sec, 404 bytes/write.<br>
- (gdb) monitor verify_image /tftp/10.0.0.9/c:\workspace/ecosboard/ecosboard/phi/openocd/rep/testing/examples/SAM7S256Test/test_rom.elf<br>
- verified 404 bytes in 4.860000s
- </code>
- </td>
- <td>PASS</td>
- </tr>
-</table>
-
-</body>
+<html>
+<head>
+<title>Test results for revision 607</title>
+</head>
+
+<body>
+<H1>Test cases</H1>
+<H2>Test case results</H2>
+The test results are stored in seperate documents. One document for
+each subversion number.
+<table border="1">
+ <tr><td>Test results</td><td>comment</td></tr>
+ <tr><td>607</a></td><td></td></tr>
+ <tr><td><a href="results/template.html">template</a></td><td>Test results template</td></tr>
+</table>
+
+<H1>SAM7S64</H1>
+
+<H2>Connectivity</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="CON001"/>CON001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Telnet connection</td>
+ <td>Power on, jtag target attached</td>
+ <td>On console, type<br><code>telnet ip port</code></td>
+ <td><code>Open On-Chip Debugger<br>></code></td>
+ <td><code>Open On-Chip Debugger<br>></code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="CON002"/>CON002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>GDB server connection</td>
+ <td>Power on, jtag target attached</td>
+ <td>On GDB console, type<br><code>target remote ip:port</code></td>
+ <td><code>Remote debugging using 10.0.0.73:3333</code></td>
+ <td><code>Remote debugging using 10.0.0.73:3333</code></td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+<H2>Reset</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="RES001"/>RES001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
+ <td>
+ <code>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ nSRST pulls nTRST, falling back to "reset run_and_halt"<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100178
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Reset init on a blank target</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset init</code></td>
+ <td>Reset should return without error and the output should contain <br><code>executing reset script 'name_of_the_script'</code></td>
+ <td>
+ <code>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ nSRST pulls nTRST, falling back to "reset run_and_init"<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x00003e24<br>
+ executing reset script 'event/sam7s256_reset.script'
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Reset after a power cycle of the target</td>
+ <td>Reset the target then power cycle the target</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code> after the power was detected</td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted</code></td>
+ <td>
+ <code>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ nSRST pulls nTRST, falling back to "reset run_and_halt"<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x300000d3 pc: 0x00003a38
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+<H2>JTAG Speed</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>ZY1000</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="SPD001"/>RES001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Exercise a memory access over the JTAG, for example <br><code>mdw 0x0 32</code></td>
+ <td>The command should run without any errors. If any JTAG checking errors happen, the test failed</td>
+ <td>
+ <code>
+ > jtag_khz 16000<br>
+ > mdw 0 32<br>
+ 0x00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+<H2>Debugging</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="DBG001"/>DBG001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Load is working</td>
+ <td>Reset init is working, RAM is accesible, GDB server is started</td>
+ <td>On the console of the OS: <br>
+ <code>arm-elf-gdb test_ram.elf</code><br>
+ <code>(gdb) target remote ip:port</code><br>
+ <code>(gdb) load</load>
+ </td>
+ <td>Load should return without error, typical output looks like:<br>
+ <code>
+ Loading section .text, size 0x14c lma 0x0<br>
+ Start address 0x40, load size 332<br>
+ Transfer rate: 180 bytes/sec, 332 bytes/write.<br>
+ </code>
+ </td>
+ <td><code>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x200000<br>
+ Start address 0x200040, load size 404<br>
+ Transfer rate: 17470 bits/sec, 404 bytes/write.
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Software breakpoint</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001</td>
+ <td>In the GDB console:<br>
+ <code>
+ (gdb) monitor arm7_9 sw_bkpts enable<br>
+ software breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0xec: file src/main.c, line 71.<br>
+ (gdb) continue<br>
+ Continuing.
+ </code>
+ </td>
+ <td>The software breakpoint should be reached, a typical output looks like:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x000000d3 pc: 0x000000ec<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) break main<br>
+ Breakpoint 2 at 0x200134: file src/main.c, line 69.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00200134<br>
+ <br>
+ Breakpoint 2, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Single step in a RAM application</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
+ <td>In GDB, type <br><code>(gdb) step</code></td>
+ <td>The next instruction should be reached, typical output:<br>
+ <code>
+ (gdb) step<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f0<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f4<br>
+ 72 DWORD b = 2;
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) step<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f0<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f4<br>
+ 72 DWORD b = 2;
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Software break points are working after a reset</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
+ <td>In GDB, type <br><code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ (gdb) continue<br>
+ </code></td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x000000d3 pc: 0x000000ec<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;
+ </code>
+ </td>
+ <td><code>
+ (gdb) moni reset<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x00003e28<br>
+ executing reset script 'event/sam7s256_reset.script'<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x200000<br>
+ Start address 0x200040, load size 404<br>
+ Transfer rate: 20455 bits/sec, 404 bytes/write.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00200134<br>
+ <br>
+ Breakpoint 2, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Hardware breakpoint</td>
+ <td>Flash the test_rom.elf application. Make this test after FLA004 has passed</td>
+ <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
+ (gdb) monitor arm7_9 force_hw_bkpts enable<br>
+ force hardware breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
+ (gdb) continue<br>
+ </code>
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100134<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Hardware breakpoint is set after a reset</td>
+ <td>Follow the instructions to flash and insert a hardware breakpoint from DBG005</td>
+ <td>In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) monitor reg pc 0x100000<br>
+ pc (/32): 0x00100000<br>
+ (gdb) continue
+ </code><br>
+ where the value inserted in PC is the start address of the application
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>
+ <code>
+ Continuing.<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100040<br>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100134<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code><br>
+ <b>Aren't there too many "halted" signs?</b>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Single step in ROM</td>
+ <td>Flash the test_rom.elf application and set a breakpoint in main, use DBG005. Make this test after FLA004 has passed</td>
+ <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
+ (gdb) monitor arm7_9 force_hw_bkpts enable<br>
+ force hardware breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ (gdb) step
+ </code>
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x0010013c<br>
+ 70 DWORD b = 2;<br>
+ </code>
+ </td>
+ <td><code>
+ (gdb) step<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100138<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x0010013c<br>
+ 70 DWORD b = 2;
+ </code></td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+<H2>RAM access</H2>
+Note: these tests are not designed to test/debug the target, but to test functionalities!
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="RAM001"/>RAM001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>32 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mww ram_address 0xdeadbeef 16<br>
+ > mdw ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 32bit long containing 0xdeadbeef.<br>
+ <code>
+ > mww 0x0 0xdeadbeef 16<br>
+ > mdw 0x0 32<br>
+ 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00000040: e1a00000 e59fa51c e59f051c e04aa000 00080017 00009388 00009388 00009388<br>
+ 0x00000060: 00009388 0002c2c0 0002c2c0 000094f8 000094f4 00009388 00009388 00009388<br>
+ </code>
+ </td>
+ <td>
+ <code>
+ > mww 0x00200000 0xdeadbeef 16<br>
+ > mdw 0x00200000 32<br>
+ 0x00200000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00200020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00200040: e59f10b4 e3a00902 e5810004 e59f00ac e59f10ac e5810000 e3e010ff e59f00a4<br>
+ 0x00200060: e5810060 e59f10a0 e3e00000 e5810130 e5810124 e321f0db e59fd090 e321f0d7
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM002"/>RAM002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>16 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mwh ram_address 0xbeef 16<br>
+ > mdh ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 16bit long containing 0xbeef.<br>
+ <code>
+ > mwh 0x0 0xbeef 16<br>
+ > mdh 0x0 32<br>
+ 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+ 0x00000020: 00e0 0000 021c 0000 0240 0000 026c 0000 0288 0000 0000 0000 0388 0000 0350 0000<br>
+ >
+ </code>
+ </td>
+ <td><code>
+ > mwh 0x00200000 0xbeef 16<br>
+ > mdh 0x00200000 32<br>
+ 0x00200000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+ 0x00200020: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>8 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mwb ram_address 0xab 16<br>
+ > mdb ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 8bit long containing 0xab.<br>
+ <code>
+ > mwb ram_address 0xab 16<br>
+ > mdb ram_address 32<br>
+ 0x00000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>
+ >
+ </code>
+ </td>
+ <td><code>
+ > mwb 0x00200000 0xab 16<br>
+ > mdb 0x00200000 32<br>
+ 0x00200000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ </code></td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+
+
+<H2>Flash access</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Actual output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="FLA001"/>FLA001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Flash probe</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface:<br>
+ <code> > flash probe 0</code>
+ </td>
+ <td>The command should execute without error. The output should state the name of the flash and the starting address. An example of output:<br>
+ <code>flash 'ecosflash' found at 0x01000000</code>
+ </td>
+ <td>
+ <code>
+ > flash probe 0<br>
+ flash 'at91sam7' found at 0x00100000
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>flash fillw</td>
+ <td>Reset init is working, flash is probed</td>
+ <td>On the telnet interface<br>
+ <code> > flash fillw 0x1000000 0xdeadbeef 16
+ </code>
+ </td>
+ <td>The commands should execute without error. The output looks like:<br>
+ <code>
+ wrote 64 bytes to 0x01000000 in 11.610000s (0.091516 kb/s)
+ </code><br>
+ To verify the contents of the flash:<br>
+ <code>
+ > mdw 0x1000000 32<br>
+ 0x01000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x01000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td><code>
+ > flash fillw 0x100000 0xdeadbeef 16<br>
+ wrote 64 bytes to 0x00100000 in 1.110000s (0.957207 kb/s)<br>
+ > mdw 0x100000 32<br>
+ 0x00100000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00100020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Flash erase</td>
+ <td>Reset init is working, flash is probed</td>
+ <td>On the telnet interface<br>
+ <code> > flash erase_address 0x1000000 0x2000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x01000000 length 8192 in 4.970000s
+ </code>
+ To check that the flash has been erased, read at different addresses. The result should always be 0xff.
+ <code>
+ > mdw 0x1000000 32<br>
+ 0x01000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td><code>
+ > flash erase_address 0x100000 0x2000<br>
+ erased address 0x00100000 length 8192 in 0.510000s<br>
+ > mdw 0x100000 32<br>
+ 0x00100000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00100020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ >
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Loading to flash from GDB</td>
+ <td>Reset init is working, flash is probed, connectivity to GDB server is working</td>
+ <td>Start GDB using a ROM elf image, eg: arm-elf-gdb test_rom.elf. <br>
+ <code>
+ (gdb) target remote ip:port<br>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.
+ (gdb) monitor verify_image path_to_elf_file
+ </code>
+ </td>
+ <td>The output should look like:<br>
+ <code>
+ verified 404 bytes in 5.060000s
+ </code><br>
+ The failure message is something like:<br>
+ <code>Verify operation failed address 0x00200000. Was 0x00 instead of 0x18</code>
+ </td>
+ <td>
+ <code>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 1540 bits/sec, 404 bytes/write.<br>
+ (gdb) monitor verify_image /tftp/10.0.0.9/c:\workspace/ecosboard/ecosboard/phi/openocd/rep/testing/examples/SAM7S256Test/test_rom.elf<br>
+ verified 404 bytes in 4.860000s
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+</body>
</html> \ No newline at end of file
diff --git a/testing/results/template.html b/testing/results/template.html
index 90692587..286bf2e3 100644
--- a/testing/results/template.html
+++ b/testing/results/template.html
@@ -1,18 +1,18 @@
-<html>
-
- <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
-
- <body>
- <a href="../testcases.html">Testcases</a>
- <table border="1">
- <tr><td>Test</td><td>Interface</td><td>Target</td><td>Result</td></tr>
- <tr><td><a href="../testcases.html#CON001">CON001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- <tr><td><a href="../testcases.html#CON002">CON002</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- <tr><td><a href="../testcases.html#RES001">RES001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- <tr><td><a href="../testcases.html#RES002">RES002</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- <tr><td><a href="../testcases.html#RES003">RES003</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- <tr><td><a href="../testcases.html#DBG001">DBG001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
- </table>
- </body>
-
+<html>
+
+ <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
+
+ <body>
+ <a href="../testcases.html">Testcases</a>
+ <table border="1">
+ <tr><td>Test</td><td>Interface</td><td>Target</td><td>Result</td></tr>
+ <tr><td><a href="../testcases.html#CON001">CON001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ <tr><td><a href="../testcases.html#CON002">CON002</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ <tr><td><a href="../testcases.html#RES001">RES001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ <tr><td><a href="../testcases.html#RES002">RES002</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ <tr><td><a href="../testcases.html#RES003">RES003</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ <tr><td><a href="../testcases.html#DBG001">DBG001</a></td><td> FILL IN! </td><td>FILL IN!</td><td>PASS/FAIL</td></tr>
+ </table>
+ </body>
+
</html> \ No newline at end of file
diff --git a/testing/smoketests.html b/testing/smoketests.html
index cc8a553e..3d5cd962 100644
--- a/testing/smoketests.html
+++ b/testing/smoketests.html
@@ -1,315 +1,315 @@
-<html>
-
- <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
-
- <body>
- <h1>OpenOCD smoketest results</h1>
- These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN.
- <p>The latest version in which the test is known to have passed is in the table below.</p>
- <h2>Vocabulary</h2>
- <table border="1">
- <tr>
- <td width="100">Passed version</td>
- <td>The latest branch and version on which the test is known to pass</td>
- </tr>
- <tr>
- <td width="100">Broken version</td>
- <td>The latest branch and version on which the test is known to fail. n/a when older than passed version.</td>
- </tr>
- <tr>
- <td width="100">ID</td>
- <td>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. </td>
- </tr>
- </table>
- <p></p>
- <table border="1">
- <tr>
- <th width="100">Unique ID</th>
- <th width="165">Synopsis</th>
- <th align="center" width="110">JTAG device</th>
- <th align="center" width="110">Passed version</th>
- <th align="center" width="110">Broken version</th>
- </tr>
- <tr>
- <td >fill_malloc</td>
- <td width="165">Fill malloc() memory with garbage</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td >ocd1</td>
- <td width="165">Telnet Windows</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td >ocd2</td>
- <td width="165">Telnet Linux</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td >ocd3</td>
- <td width="165">Telnet Cygwin</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#test_ocd4">ocd4</a></td>
- <td width="165">ARM7 debugging</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td >SAM9260</td>
- <td width="165">SAM9260 debugging</td>
- <td align="center">ft2232 </td>
- <td align="center">500</td>
- <td align="center">n/a</td>
- </tr>
- <tr>
- <td >xscale1</td>
- <td width="165">XScale debugging</td>
- <td align="center" >bitbang</td>
- <td align="center" >505</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td >xscale2</td>
- <td width="165">XScale debugging</td>
- <td align="center" >FT2232</td>
- <td align="center" >202</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram1</a></td>
- <td width="165">str710 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom2</a></td>
- <td width="165">str710 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram3</a></td>
- <td width="165">str912 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom4</a></td>
- <td width="165">str912 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram5</a></td>
- <td width="165">lpc2148 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom6</a></td>
- <td width="165">lpc2148 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram7</a></td>
- <td width="165">lpc2294 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom8</a></td>
- <td width="165">lpc2294 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram9</a></td>
- <td width="165">sam7s256 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom10</a></td>
- <td width="165">sam7s256 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram11</a></td>
- <td width="165">sam7x256 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >517</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-rom">bdte-rom12</a></td>
- <td width="165">sam7x256 rom debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >517</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td ><a href="#bdte-ram">bdte-ram13</a></td>
- <td width="165">at91r40008 ram debugging</td>
- <td align="center" >JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- </table>
- <p></p>
- <hr>
- <h1>OpenOCD JTAG device test results</h1>
- Each JTAG device must be tested
-
- <table border="1">
- <tr>
- <th align="center" width="40">ID</th>
- <th width="90">Synopsis</th>
- <th >Passed version</th>
- <th >Broken version</th>
- </tr>
- <tr>
- <td width="40">jtag1</td>
- <td width="90">Parport</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td width="40">jtag2</td>
- <td width="90">JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td width="40">jtag3</td>
- <td width="90">Turtelizer2</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td width="40">jtag4</td>
- <td width="90">JTAGkey</td>
- <td align="center" >536</td>
- <td align="center" >n/a</td>
- </tr>
- <tr>
- <td width="40">jtag5</td>
- <td width="90">add new one</td>
- <td align="center" >n/a</td>
- <td align="center" >n/a</td>
- </tr>
- </table>
- <p>jtag1:</p>
- <p>jtag2: Tested on Windows XP Prof. (SP2) with original FTDI&nbsp;driver.</p>
- <p>jtag3: Tested on Windows XP Prof. (SP2) with original FTDI&nbsp;driver.</p>
- <p>jtag4: Tested on Mac OS X (10.5.2, Intel) with libftdi-0.10 and libusb-0.1.12</p>
- <p>jtag5:</p>
- <hr>
- <h1>OpenOCD JTAG device speed test result</h1>
- <p>The test result is in KB/sec.</p>
- <table border="1">
- <tr>
- <th align="center" width="50">ID</th>
- <th width="90">Synopsis</th>
- <th width="40">r320</th>
- <th width="40">r420</th>
- <th width="40">r423</th>
- <th width="40">r459</th>
- <th width="40">r517</th>
- <th width="40">r536</th>
- </tr>
- <tr>
- <td width="50"><a href="#speed1">speed1</a></td>
- <td width="90">JTAGkey</td>
- <td align="center" width="40">93</td>
- <td align="center" width="40">64 </td>
- <td align="center" width="40">93</td>
- <td align="center" width="40">93</td>
- <td align="center" width="40">93</td>
- <td align="center" width="40">93</td>
- </tr>
- <tr>
- <td width="50"><a href="#speed2">speed2</a></td>
- <td width="90">JTAGkey</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">52</td>
- <td align="center" width="40">52</td>
- </tr>
- <tr>
- <td width="50">speed3</td>
- <td width="90">add new one</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- <td align="center" width="40">n/a</td>
- </tr>
- </table>
- <p></p>
- <hr>
- <h1>Policy on removing features from OpenOCD</h1>
- 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.
- <p>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.</p>
- <h1>Policy on adding features from OpenOCD</h1>
- To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk.
- <p>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. </p>
- <hr>
- <h1>ocd4 - ARM7 debugging<a name="test_ocd4"></a></h1>
- Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step.
- <hr>
- <h1>bdte-ram (Basic debugging test with Eclipse in RAM)<a id="bdte-ram" name="bdte-ram"></a></h1>
- <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_ram.gdb</b> file.</p>
- <p>Start debugging, the debugger should stop at main. set some breakpoints and &quot;Resume&quot;. If the debugger hit a breakpoint check if the &quot;Variables&quot; looks correct. Remove some breakpoints and &quot;Resume&quot; again. If the target is running, use the &quot;Suspend&quot; function and use &quot;Step Into&quot; or &quot;Step Over&quot; through the source. Even open the &quot;Disassembly&quot; view and enable the &quot;Instruction Stepping Mode&quot;. Now you can single step through the assembler source. Use &quot;Resume&quot; again to run the program, set a breakpoint while the target is running. Check if you can inspect the variables with the mouse over. Play a little with the target...</p>
- <hr>
- <h1>bdte-rom (Basic debugging test with Eclipse in ROM)<a id="bdte-rom" name="bdte-rom"></a></h1>
- <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_rom.gdb</b> file.</p>
- <p>Start debugging, the debugger should download and store the program in the flash of the target.</p>
- <p>Now you can make some tests like described in the <a href="#bdte-ram">bdte-ram</a> section above too.</p>
- <hr>
- <h1>speed1 - Download speed test<a id="speed1" name="speed1"></a></h1>
- <p>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&nbsp;can look like:</p>
- <p>Loading section .text, size 0x6019c lma 0x62000000<br>
- Start address 0x62000040, load size 393628<br>
- Transfer rate: 93 KB/sec, 2008 bytes/write.</p>
- <p>In this example a speed of 93 KB/sec was reached. The hardware which was used for the test can be found <a href="http://www.yagarto.de/projects/str7usbmsd/index.html" target="new">here</a>.</p>
- <p>The test was made on Windows XP Prof. (SP2) with a JTAGkey and the original FTDI driver.</p>
- <hr>
- <h1>speed2 - Download speed test<a id="speed2" name="speed2"></a></h1>
- <p>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&nbsp;can look like:</p>
- <p>Loading section .text, size 0x6019c lma 0x62000000<br>
- Start address 0x62000040, load size 393628<br>Transfer rate: 52 KB/sec, 2008 bytes/write.</p>
- <p>In this example a speed of 52 KB/sec was reached. The hardware which was used for the test can be found <a href="http://www.yagarto.de/projects/str7usbmsd/index.html" target="new">here</a>.</p>
- <p>The test was made on Mac OS X (10.5.2, Intel) with a JTAGkey and the following driver:</p>
- <p>- libftdi 0.10<br>
- - libusb 0.1.12</p>
- <p></p>
- <p></p>
- </body>
-
+<html>
+
+ <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
+
+ <body>
+ <h1>OpenOCD smoketest results</h1>
+ These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN.
+ <p>The latest version in which the test is known to have passed is in the table below.</p>
+ <h2>Vocabulary</h2>
+ <table border="1">
+ <tr>
+ <td width="100">Passed version</td>
+ <td>The latest branch and version on which the test is known to pass</td>
+ </tr>
+ <tr>
+ <td width="100">Broken version</td>
+ <td>The latest branch and version on which the test is known to fail. n/a when older than passed version.</td>
+ </tr>
+ <tr>
+ <td width="100">ID</td>
+ <td>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. </td>
+ </tr>
+ </table>
+ <p></p>
+ <table border="1">
+ <tr>
+ <th width="100">Unique ID</th>
+ <th width="165">Synopsis</th>
+ <th align="center" width="110">JTAG device</th>
+ <th align="center" width="110">Passed version</th>
+ <th align="center" width="110">Broken version</th>
+ </tr>
+ <tr>
+ <td >fill_malloc</td>
+ <td width="165">Fill malloc() memory with garbage</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td >ocd1</td>
+ <td width="165">Telnet Windows</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td >ocd2</td>
+ <td width="165">Telnet Linux</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td >ocd3</td>
+ <td width="165">Telnet Cygwin</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#test_ocd4">ocd4</a></td>
+ <td width="165">ARM7 debugging</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td >SAM9260</td>
+ <td width="165">SAM9260 debugging</td>
+ <td align="center">ft2232 </td>
+ <td align="center">500</td>
+ <td align="center">n/a</td>
+ </tr>
+ <tr>
+ <td >xscale1</td>
+ <td width="165">XScale debugging</td>
+ <td align="center" >bitbang</td>
+ <td align="center" >505</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td >xscale2</td>
+ <td width="165">XScale debugging</td>
+ <td align="center" >FT2232</td>
+ <td align="center" >202</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram1</a></td>
+ <td width="165">str710 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom2</a></td>
+ <td width="165">str710 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram3</a></td>
+ <td width="165">str912 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom4</a></td>
+ <td width="165">str912 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram5</a></td>
+ <td width="165">lpc2148 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom6</a></td>
+ <td width="165">lpc2148 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram7</a></td>
+ <td width="165">lpc2294 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom8</a></td>
+ <td width="165">lpc2294 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram9</a></td>
+ <td width="165">sam7s256 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom10</a></td>
+ <td width="165">sam7s256 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram11</a></td>
+ <td width="165">sam7x256 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >517</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-rom">bdte-rom12</a></td>
+ <td width="165">sam7x256 rom debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >517</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td ><a href="#bdte-ram">bdte-ram13</a></td>
+ <td width="165">at91r40008 ram debugging</td>
+ <td align="center" >JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ </table>
+ <p></p>
+ <hr>
+ <h1>OpenOCD JTAG device test results</h1>
+ Each JTAG device must be tested
+
+ <table border="1">
+ <tr>
+ <th align="center" width="40">ID</th>
+ <th width="90">Synopsis</th>
+ <th >Passed version</th>
+ <th >Broken version</th>
+ </tr>
+ <tr>
+ <td width="40">jtag1</td>
+ <td width="90">Parport</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td width="40">jtag2</td>
+ <td width="90">JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td width="40">jtag3</td>
+ <td width="90">Turtelizer2</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td width="40">jtag4</td>
+ <td width="90">JTAGkey</td>
+ <td align="center" >536</td>
+ <td align="center" >n/a</td>
+ </tr>
+ <tr>
+ <td width="40">jtag5</td>
+ <td width="90">add new one</td>
+ <td align="center" >n/a</td>
+ <td align="center" >n/a</td>
+ </tr>
+ </table>
+ <p>jtag1:</p>
+ <p>jtag2: Tested on Windows XP Prof. (SP2) with original FTDI&nbsp;driver.</p>
+ <p>jtag3: Tested on Windows XP Prof. (SP2) with original FTDI&nbsp;driver.</p>
+ <p>jtag4: Tested on Mac OS X (10.5.2, Intel) with libftdi-0.10 and libusb-0.1.12</p>
+ <p>jtag5:</p>
+ <hr>
+ <h1>OpenOCD JTAG device speed test result</h1>
+ <p>The test result is in KB/sec.</p>
+ <table border="1">
+ <tr>
+ <th align="center" width="50">ID</th>
+ <th width="90">Synopsis</th>
+ <th width="40">r320</th>
+ <th width="40">r420</th>
+ <th width="40">r423</th>
+ <th width="40">r459</th>
+ <th width="40">r517</th>
+ <th width="40">r536</th>
+ </tr>
+ <tr>
+ <td width="50"><a href="#speed1">speed1</a></td>
+ <td width="90">JTAGkey</td>
+ <td align="center" width="40">93</td>
+ <td align="center" width="40">64 </td>
+ <td align="center" width="40">93</td>
+ <td align="center" width="40">93</td>
+ <td align="center" width="40">93</td>
+ <td align="center" width="40">93</td>
+ </tr>
+ <tr>
+ <td width="50"><a href="#speed2">speed2</a></td>
+ <td width="90">JTAGkey</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">52</td>
+ <td align="center" width="40">52</td>
+ </tr>
+ <tr>
+ <td width="50">speed3</td>
+ <td width="90">add new one</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ <td align="center" width="40">n/a</td>
+ </tr>
+ </table>
+ <p></p>
+ <hr>
+ <h1>Policy on removing features from OpenOCD</h1>
+ 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.
+ <p>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.</p>
+ <h1>Policy on adding features from OpenOCD</h1>
+ To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk.
+ <p>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. </p>
+ <hr>
+ <h1>ocd4 - ARM7 debugging<a name="test_ocd4"></a></h1>
+ Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step.
+ <hr>
+ <h1>bdte-ram (Basic debugging test with Eclipse in RAM)<a id="bdte-ram" name="bdte-ram"></a></h1>
+ <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_ram.gdb</b> file.</p>
+ <p>Start debugging, the debugger should stop at main. set some breakpoints and &quot;Resume&quot;. If the debugger hit a breakpoint check if the &quot;Variables&quot; looks correct. Remove some breakpoints and &quot;Resume&quot; again. If the target is running, use the &quot;Suspend&quot; function and use &quot;Step Into&quot; or &quot;Step Over&quot; through the source. Even open the &quot;Disassembly&quot; view and enable the &quot;Instruction Stepping Mode&quot;. Now you can single step through the assembler source. Use &quot;Resume&quot; again to run the program, set a breakpoint while the target is running. Check if you can inspect the variables with the mouse over. Play a little with the target...</p>
+ <hr>
+ <h1>bdte-rom (Basic debugging test with Eclipse in ROM)<a id="bdte-rom" name="bdte-rom"></a></h1>
+ <p>This test was made under Eclipse with the Zylin Embedded CDT&nbsp;plugin. For the GDB &quot;Initialize commands&quot; take a look in the examples/&lt;target&gt;/prj/<b>eclipse_rom.gdb</b> file.</p>
+ <p>Start debugging, the debugger should download and store the program in the flash of the target.</p>
+ <p>Now you can make some tests like described in the <a href="#bdte-ram">bdte-ram</a> section above too.</p>
+ <hr>
+ <h1>speed1 - Download speed test<a id="speed1" name="speed1"></a></h1>
+ <p>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&nbsp;can look like:</p>
+ <p>Loading section .text, size 0x6019c lma 0x62000000<br>
+ Start address 0x62000040, load size 393628<br>
+ Transfer rate: 93 KB/sec, 2008 bytes/write.</p>
+ <p>In this example a speed of 93 KB/sec was reached. The hardware which was used for the test can be found <a href="http://www.yagarto.de/projects/str7usbmsd/index.html" target="new">here</a>.</p>
+ <p>The test was made on Windows XP Prof. (SP2) with a JTAGkey and the original FTDI driver.</p>
+ <hr>
+ <h1>speed2 - Download speed test<a id="speed2" name="speed2"></a></h1>
+ <p>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&nbsp;can look like:</p>
+ <p>Loading section .text, size 0x6019c lma 0x62000000<br>
+ Start address 0x62000040, load size 393628<br>Transfer rate: 52 KB/sec, 2008 bytes/write.</p>
+ <p>In this example a speed of 52 KB/sec was reached. The hardware which was used for the test can be found <a href="http://www.yagarto.de/projects/str7usbmsd/index.html" target="new">here</a>.</p>
+ <p>The test was made on Mac OS X (10.5.2, Intel) with a JTAGkey and the following driver:</p>
+ <p>- libftdi 0.10<br>
+ - libusb 0.1.12</p>
+ <p></p>
+ <p></p>
+ </body>
+
</html> \ No newline at end of file
diff --git a/testing/testcases.html b/testing/testcases.html
index df8bfe71..a3cc9eb6 100644
--- a/testing/testcases.html
+++ b/testing/testcases.html
@@ -1,578 +1,578 @@
-<html>
-<head>
-<title>Test cases</title>
-</head>
-
-<body>
-<H1>Test cases</H1>
-<H2>Test case results</H2>
-The test results are stored in seperate documents. One document for
-each subversion number.
-<table border="1">
- <tr><td>Test results</td><td>comment</td></tr>
- <tr><td><a href="examples/SAM7S256Test/results/607.html">607</a></td><td></td></tr>
- <tr><td><a href="results/template.html">template</a></td><td>Test results template</td></tr>
-</table>
-
-<H2>Vocabulary</H2>
-<table border="1">
- <tr>
- <td width="100">Passed version</td>
-
- <td>The latest branch and version on which the test is known to pass</td>
- </tr>
- <tr>
- <td width="100">Broken version</td>
- <td>The latest branch and version on which the test is known to fail. n/a when older than passed version.</td>
- </tr>
- <tr>
- <td width="100">ID</td>
- <td>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. </td>
- </tr>
- <tr>
- <td width="100">Test case</td>
- <td>An atomic entity that describes the operations needed to test a feature or only a part of it. The test case should:
- <ul>
- <li>be uniquely identifiable</li>
- <li>define the complete prerequisites of the test (eg: the target, the interface, the initial state of the system)</li>
- <li>define the input to be applied to the system in order to execute the test</li>
- <li>define the expected output</li>
- <li>contain the output resulted by running the test case</li>
- <li>contain the result of the test (pass/fail)</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td width="100">Test suite</td>
- <td>A (completable) collection of test cases</td>
- </tr>
- <tr>
- <td width="100">Testing</td>
- <td>Testing refers to running the test suite for a specific revision of the software,
- for one or many targets, using one or many JTAG interfaces. Testing should be be stored
- along with all the other records for that specific revision. For releases, the results
- can be stored along with the binaries</td>
- </tr>
- <tr>
- <td width="100">Target = ANY</td>
- <td>Any target can be used for this test</td>
- </tr>
- <tr>
- <td width="100">Interface = ANY</td>
- <td>Any interface can be used for this test</td>
- </tr>
- <tr>
- <td width="100">Target = "reset_config srst_and_trst"</td>
- <td>Any target which supports the reset_config above</td>
- </tr>
-</table>
-
-<H1>Test cases</H1>
-
-<H2>Connectivity</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="CON001"/>CON001</td>
- <td>ALL</td>
- <td>ALL</td>
- <td>Telnet connection</td>
- <td>Power on, jtag target attached</td>
- <td>On console, type<br><code>telnet ip port</code></td>
- <td><code>Open On-Chip Debugger<br>></code></td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="CON002"/>CON002</td>
- <td>ALL</td>
- <td>ALL</td>
- <td>GDB server connection</td>
- <td>Power on, jtag target attached</td>
- <td>On GDB console, type<br><code>target remote ip:port</code></td>
- <td><code>Remote debugging using 10.0.0.73:3333</code></td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-<H2>Reset</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="RES001"/>RES001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Reset halt on a blank target</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RES002"/>RES002</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Reset init on a blank target</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset init</code></td>
- <td>Reset should return without error and the output should contain <br><code>executing reset script 'name_of_the_script'</code></td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RES003"/>RES003</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Reset after a power cycle of the target</td>
- <td>Reset the target then power cycle the target</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code> after the power was detected</td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted</code></td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RES004"/>RES004</td>
- <td>ARM7/9,reset_config srst_and_trst</td>
- <td>ANY</td>
- <td>Reset halt on a blank target where reset halt is supported</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RES005"/>RES005</td>
- <td>arm926ejs,reset_config srst_and_trst</td>
- <td>ANY</td>
- <td>Reset halt on a blank target where reset halt is supported. This target has problems with the reset vector catch being disabled by TRST</td>
- <td>Erase all the content of the flash</td>
- <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
- <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-<H2>JTAG Speed</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="SPD001"/>RES001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>16MHz on normal operation</td>
- <td>Reset init the target according to RES002 </td>
- <td>Exercise a memory access over the JTAG, for example <br><code>mdw 0x0 32</code></td>
- <td>The command should run without any errors. If any JTAG checking errors happen, the test failed</td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-<H2>Debugging</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="DBG001"/>DBG001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Load is working</td>
- <td>Reset init is working, RAM is accesible, GDB server is started</td>
- <td>On the console of the OS: <br>
- <code>arm-elf-gdb test_ram.elf</code><br>
- <code>(gdb) target remote ip:port</code><br>
- <code>(gdb) load</load>
- </td>
- <td>Load should return without error, typical output looks like:<br>
- <code>
- Loading section .text, size 0x14c lma 0x0<br>
- Start address 0x40, load size 332<br>
- Transfer rate: 180 bytes/sec, 332 bytes/write.<br>
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG002"/>DBG002</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Software breakpoint</td>
- <td>Load the test_ram.elf application, use instructions from GDB001</td>
- <td>In the GDB console:<br>
- <code>
- (gdb) monitor arm7_9 sw_bkpts enable<br>
- software breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0xec: file src/main.c, line 71.<br>
- (gdb) continue<br>
- Continuing.
- </code>
- </td>
- <td>The software breakpoint should be reached, a typical output looks like:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x000000d3 pc: 0x000000ec<br>
- <br>
- Breakpoint 1, main () at src/main.c:71<br>
- 71 DWORD a = 1;
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG003"/>DBG003</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Single step in a RAM application</td>
- <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
- <td>In GDB, type <br><code>(gdb) step</code></td>
- <td>The next instruction should be reached, typical output:<br>
- <code>
- (gdb) step<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f0<br>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Abort<br>
- cpsr: 0x20000097 pc: 0x000000f4<br>
- 72 DWORD b = 2;
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG004"/>DBG004</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Software break points are working after a reset</td>
- <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
- <td>In GDB, type <br><code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- (gdb) continue<br>
- </code></td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to breakpoint, current mode: Supervisor<br>
- cpsr: 0x000000d3 pc: 0x000000ec<br>
- <br>
- Breakpoint 1, main () at src/main.c:71<br>
- 71 DWORD a = 1;
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG005"/>DBG005</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Hardware breakpoint</td>
- <td>Flash the test_rom.elf application. Make this test after FLA004 has passed</td>
- <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
- (gdb) monitor arm7_9 force_hw_bkpts enable<br>
- force hardware breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
- (gdb) continue<br>
- </code>
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG006"/>DBG006</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Hardware breakpoint is set after a reset</td>
- <td>Follow the instructions to flash and insert a hardware breakpoint from DBG005</td>
- <td>In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) monitor reg pc 0x100000<br>
- pc (/32): 0x00100000<br>
- (gdb) continue
- </code>
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="DBG007"/>DBG007</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Single step in ROM</td>
- <td>Flash the test_rom.elf application and set a breakpoint in main, use DBG005. Make this test after FLA004 has passed</td>
- <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
- <code>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
- (gdb) monitor arm7_9 force_hw_bkpts enable<br>
- force hardware breakpoints enabled<br>
- (gdb) break main<br>
- Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
- (gdb) continue<br>
- Continuing.<br>
- <br>
- Breakpoint 1, main () at src/main.c:69<br>
- 69 DWORD a = 1;<br>
- (gdb) step
- </code>
- </td>
- <td>The breakpoint should be reached, typical output:<br>
- <code>
- target state: halted<br>
- target halted in ARM state due to single step, current mode: Supervisor<br>
- cpsr: 0x60000013 pc: 0x0010013c<br>
- 70 DWORD b = 2;<br>
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-<H2>RAM access</H2>
-Note: these tests are not designed to test/debug the target, but to test functionalities!
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="RAM001"/>RAM001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>32 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mww ram_address 0xdeadbeef 16<br>
- > mdw ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 32bit long containing 0xdeadbeef.<br>
- <code>
- > mww 0x0 0xdeadbeef 16<br>
- > mdw 0x0 32<br>
- 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x00000040: e1a00000 e59fa51c e59f051c e04aa000 00080017 00009388 00009388 00009388<br>
- 0x00000060: 00009388 0002c2c0 0002c2c0 000094f8 000094f4 00009388 00009388 00009388<br>
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RAM001"/>RAM001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>16 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mwh ram_address 0xbeef 16<br>
- > mdh ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 16bit long containing 0xbeef.<br>
- <code>
- > mwh 0x0 0xbeef 16<br>
- > mdh 0x0 32<br>
- 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
- 0x00000020: 00e0 0000 021c 0000 0240 0000 026c 0000 0288 0000 0000 0000 0388 0000 0350 0000<br>
- >
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="RAM003"/>RAM003</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>8 bit Write/read RAM</td>
- <td>Reset init is working</td>
- <td>On the telnet interface<br>
- <code> > mwb ram_address 0xab 16<br>
- > mdb ram_address 32
- </code>
- </td>
- <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 8bit long containing 0xab.<br>
- <code>
- > mwh 0x0 0x0 16<br>
- > mwb ram_address 0xab 16<br>
- > mdb ram_address 32<br>
- 0x00000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>
- >
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-
-
-<H2>Flash access</H2>
-<table border=1>
- <tr>
- <td>ID</td>
- <td>Target</td>
- <td>Interface</td>
- <td>Description</td>
- <td>Initial state</td>
- <td>Input</td>
- <td>Expected output</td>
- <td>Pass/Fail</td>
- </tr>
- <tr>
- <td><a name="FLA001"/>FLA001</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Flash probe</td>
- <td>Reset init is working</td>
- <td>On the telnet interface:<br>
- <code> > flash probe 0</code>
- </td>
- <td>The command should execute without error. The output should state the name of the flash and the starting address. An example of output:<br>
- <code>flash 'ecosflash' found at 0x01000000</code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="FLA002"/>FLA002</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>flash fillw</td>
- <td>Reset init is working, flash is probed</td>
- <td>On the telnet interface<br>
- <code> > flash fillw 0x1000000 0xdeadbeef 16
- </code>
- </td>
- <td>The commands should execute without error. The output looks like:<br>
- <code>
- wrote 64 bytes to 0x01000000 in 11.610000s (0.091516 kb/s)
- </code><br>
- To verify the contents of the flash:<br>
- <code>
- > mdw 0x1000000 32<br>
- 0x01000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x01000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
- 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="FLA003"/>FLA003</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Flash erase</td>
- <td>Reset init is working, flash is probed</td>
- <td>On the telnet interface<br>
- <code> > flash erase_address 0x1000000 0x2000
- </code>
- </td>
- <td>The commands should execute without error.<br>
- <code>
- erased address 0x01000000 length 8192 in 4.970000s
- </code>
- To check that the flash has been erased, read at different addresses. The result should always be 0xff.
- <code>
- > mdw 0x1000000 32<br>
- 0x01000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
- 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
- </code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
- <tr>
- <td><a name="FLA004"/>FLA004</td>
- <td>Fill in!</td>
- <td>Fill in!</td>
- <td>Loading to flash from GDB</td>
- <td>Reset init is working, flash is probed, connectivity to GDB server is working</td>
- <td>Start GDB using a ROM elf image, eg: arm-elf-gdb test_rom.elf. <br>
- <code>
- (gdb) target remote ip:port<br>
- (gdb) monitor reset<br>
- (gdb) load<br>
- Loading section .text, size 0x194 lma 0x100000<br>
- Start address 0x100040, load size 404<br>
- Transfer rate: 179 bytes/sec, 404 bytes/write.
- (gdb) monitor verify_image path_to_elf_file
- </code>
- </td>
- <td>The output should look like:<br>
- <code>
- verified 404 bytes in 5.060000s
- </code><br>
- The failure message is something like:<br>
- <code>Verify operation failed address 0x00200000. Was 0x00 instead of 0x18</code>
- </td>
- <td>PASS/FAIL</td>
- </tr>
-</table>
-
-</body>
+<html>
+<head>
+<title>Test cases</title>
+</head>
+
+<body>
+<H1>Test cases</H1>
+<H2>Test case results</H2>
+The test results are stored in seperate documents. One document for
+each subversion number.
+<table border="1">
+ <tr><td>Test results</td><td>comment</td></tr>
+ <tr><td><a href="examples/SAM7S256Test/results/607.html">607</a></td><td></td></tr>
+ <tr><td><a href="results/template.html">template</a></td><td>Test results template</td></tr>
+</table>
+
+<H2>Vocabulary</H2>
+<table border="1">
+ <tr>
+ <td width="100">Passed version</td>
+
+ <td>The latest branch and version on which the test is known to pass</td>
+ </tr>
+ <tr>
+ <td width="100">Broken version</td>
+ <td>The latest branch and version on which the test is known to fail. n/a when older than passed version.</td>
+ </tr>
+ <tr>
+ <td width="100">ID</td>
+ <td>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. </td>
+ </tr>
+ <tr>
+ <td width="100">Test case</td>
+ <td>An atomic entity that describes the operations needed to test a feature or only a part of it. The test case should:
+ <ul>
+ <li>be uniquely identifiable</li>
+ <li>define the complete prerequisites of the test (eg: the target, the interface, the initial state of the system)</li>
+ <li>define the input to be applied to the system in order to execute the test</li>
+ <li>define the expected output</li>
+ <li>contain the output resulted by running the test case</li>
+ <li>contain the result of the test (pass/fail)</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td width="100">Test suite</td>
+ <td>A (completable) collection of test cases</td>
+ </tr>
+ <tr>
+ <td width="100">Testing</td>
+ <td>Testing refers to running the test suite for a specific revision of the software,
+ for one or many targets, using one or many JTAG interfaces. Testing should be be stored
+ along with all the other records for that specific revision. For releases, the results
+ can be stored along with the binaries</td>
+ </tr>
+ <tr>
+ <td width="100">Target = ANY</td>
+ <td>Any target can be used for this test</td>
+ </tr>
+ <tr>
+ <td width="100">Interface = ANY</td>
+ <td>Any interface can be used for this test</td>
+ </tr>
+ <tr>
+ <td width="100">Target = "reset_config srst_and_trst"</td>
+ <td>Any target which supports the reset_config above</td>
+ </tr>
+</table>
+
+<H1>Test cases</H1>
+
+<H2>Connectivity</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="CON001"/>CON001</td>
+ <td>ALL</td>
+ <td>ALL</td>
+ <td>Telnet connection</td>
+ <td>Power on, jtag target attached</td>
+ <td>On console, type<br><code>telnet ip port</code></td>
+ <td><code>Open On-Chip Debugger<br>></code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="CON002"/>CON002</td>
+ <td>ALL</td>
+ <td>ALL</td>
+ <td>GDB server connection</td>
+ <td>Power on, jtag target attached</td>
+ <td>On GDB console, type<br><code>target remote ip:port</code></td>
+ <td><code>Remote debugging using 10.0.0.73:3333</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+<H2>Reset</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="RES001"/>RES001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Reset halt on a blank target</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Reset init on a blank target</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset init</code></td>
+ <td>Reset should return without error and the output should contain <br><code>executing reset script 'name_of_the_script'</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Reset after a power cycle of the target</td>
+ <td>Reset the target then power cycle the target</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code> after the power was detected</td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>ARM7/9,reset_config srst_and_trst</td>
+ <td>ANY</td>
+ <td>Reset halt on a blank target where reset halt is supported</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>arm926ejs,reset_config srst_and_trst</td>
+ <td>ANY</td>
+ <td>Reset halt on a blank target where reset halt is supported. This target has problems with the reset vector catch being disabled by TRST</td>
+ <td>Erase all the content of the flash</td>
+ <td>Connect via the telnet interface and type <br><code>reset halt</code></td>
+ <td>Reset should return without error and the output should contain<br><code>target state: halted<br>pc = 0</code></td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+<H2>JTAG Speed</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="SPD001"/>RES001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Exercise a memory access over the JTAG, for example <br><code>mdw 0x0 32</code></td>
+ <td>The command should run without any errors. If any JTAG checking errors happen, the test failed</td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+<H2>Debugging</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="DBG001"/>DBG001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Load is working</td>
+ <td>Reset init is working, RAM is accesible, GDB server is started</td>
+ <td>On the console of the OS: <br>
+ <code>arm-elf-gdb test_ram.elf</code><br>
+ <code>(gdb) target remote ip:port</code><br>
+ <code>(gdb) load</load>
+ </td>
+ <td>Load should return without error, typical output looks like:<br>
+ <code>
+ Loading section .text, size 0x14c lma 0x0<br>
+ Start address 0x40, load size 332<br>
+ Transfer rate: 180 bytes/sec, 332 bytes/write.<br>
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Software breakpoint</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001</td>
+ <td>In the GDB console:<br>
+ <code>
+ (gdb) monitor arm7_9 sw_bkpts enable<br>
+ software breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0xec: file src/main.c, line 71.<br>
+ (gdb) continue<br>
+ Continuing.
+ </code>
+ </td>
+ <td>The software breakpoint should be reached, a typical output looks like:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x000000d3 pc: 0x000000ec<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Single step in a RAM application</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
+ <td>In GDB, type <br><code>(gdb) step</code></td>
+ <td>The next instruction should be reached, typical output:<br>
+ <code>
+ (gdb) step<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f0<br>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Abort<br>
+ cpsr: 0x20000097 pc: 0x000000f4<br>
+ 72 DWORD b = 2;
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Software break points are working after a reset</td>
+ <td>Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002</td>
+ <td>In GDB, type <br><code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ (gdb) continue<br>
+ </code></td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to breakpoint, current mode: Supervisor<br>
+ cpsr: 0x000000d3 pc: 0x000000ec<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Hardware breakpoint</td>
+ <td>Flash the test_rom.elf application. Make this test after FLA004 has passed</td>
+ <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
+ (gdb) monitor arm7_9 force_hw_bkpts enable<br>
+ force hardware breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
+ (gdb) continue<br>
+ </code>
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Hardware breakpoint is set after a reset</td>
+ <td>Follow the instructions to flash and insert a hardware breakpoint from DBG005</td>
+ <td>In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) monitor reg pc 0x100000<br>
+ pc (/32): 0x00100000<br>
+ (gdb) continue
+ </code>
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Single step in ROM</td>
+ <td>Flash the test_rom.elf application and set a breakpoint in main, use DBG005. Make this test after FLA004 has passed</td>
+ <td>Be sure that <code>gdb_memory_map</code> and <code>gdb_flash_program</code> are enabled. In GDB, type <br>
+ <code>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.<br>
+ (gdb) monitor arm7_9 force_hw_bkpts enable<br>
+ force hardware breakpoints enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x100134: file src/main.c, line 69.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ (gdb) step
+ </code>
+ </td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ target state: halted<br>
+ target halted in ARM state due to single step, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x0010013c<br>
+ 70 DWORD b = 2;<br>
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+<H2>RAM access</H2>
+Note: these tests are not designed to test/debug the target, but to test functionalities!
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="RAM001"/>RAM001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>32 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mww ram_address 0xdeadbeef 16<br>
+ > mdw ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 32bit long containing 0xdeadbeef.<br>
+ <code>
+ > mww 0x0 0xdeadbeef 16<br>
+ > mdw 0x0 32<br>
+ 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00000040: e1a00000 e59fa51c e59f051c e04aa000 00080017 00009388 00009388 00009388<br>
+ 0x00000060: 00009388 0002c2c0 0002c2c0 000094f8 000094f4 00009388 00009388 00009388<br>
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RAM001"/>RAM001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>16 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mwh ram_address 0xbeef 16<br>
+ > mdh ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 16bit long containing 0xbeef.<br>
+ <code>
+ > mwh 0x0 0xbeef 16<br>
+ > mdh 0x0 32<br>
+ 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+ 0x00000020: 00e0 0000 021c 0000 0240 0000 026c 0000 0288 0000 0000 0000 0388 0000 0350 0000<br>
+ >
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>8 bit Write/read RAM</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface<br>
+ <code> > mwb ram_address 0xab 16<br>
+ > mdb ram_address 32
+ </code>
+ </td>
+ <td>The commands should execute without error. A clear failure is a memory access exception. The result of running the commands should be a list of 16 locations 8bit long containing 0xab.<br>
+ <code>
+ > mwh 0x0 0x0 16<br>
+ > mwb ram_address 0xab 16<br>
+ > mdb ram_address 32<br>
+ 0x00000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>
+ >
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+
+
+<H2>Flash access</H2>
+<table border=1>
+ <tr>
+ <td>ID</td>
+ <td>Target</td>
+ <td>Interface</td>
+ <td>Description</td>
+ <td>Initial state</td>
+ <td>Input</td>
+ <td>Expected output</td>
+ <td>Pass/Fail</td>
+ </tr>
+ <tr>
+ <td><a name="FLA001"/>FLA001</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Flash probe</td>
+ <td>Reset init is working</td>
+ <td>On the telnet interface:<br>
+ <code> > flash probe 0</code>
+ </td>
+ <td>The command should execute without error. The output should state the name of the flash and the starting address. An example of output:<br>
+ <code>flash 'ecosflash' found at 0x01000000</code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>flash fillw</td>
+ <td>Reset init is working, flash is probed</td>
+ <td>On the telnet interface<br>
+ <code> > flash fillw 0x1000000 0xdeadbeef 16
+ </code>
+ </td>
+ <td>The commands should execute without error. The output looks like:<br>
+ <code>
+ wrote 64 bytes to 0x01000000 in 11.610000s (0.091516 kb/s)
+ </code><br>
+ To verify the contents of the flash:<br>
+ <code>
+ > mdw 0x1000000 32<br>
+ 0x01000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x01000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Flash erase</td>
+ <td>Reset init is working, flash is probed</td>
+ <td>On the telnet interface<br>
+ <code> > flash erase_address 0x1000000 0x2000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x01000000 length 8192 in 4.970000s
+ </code>
+ To check that the flash has been erased, read at different addresses. The result should always be 0xff.
+ <code>
+ > mdw 0x1000000 32<br>
+ 0x01000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>Fill in!</td>
+ <td>Fill in!</td>
+ <td>Loading to flash from GDB</td>
+ <td>Reset init is working, flash is probed, connectivity to GDB server is working</td>
+ <td>Start GDB using a ROM elf image, eg: arm-elf-gdb test_rom.elf. <br>
+ <code>
+ (gdb) target remote ip:port<br>
+ (gdb) monitor reset<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x100000<br>
+ Start address 0x100040, load size 404<br>
+ Transfer rate: 179 bytes/sec, 404 bytes/write.
+ (gdb) monitor verify_image path_to_elf_file
+ </code>
+ </td>
+ <td>The output should look like:<br>
+ <code>
+ verified 404 bytes in 5.060000s
+ </code><br>
+ The failure message is something like:<br>
+ <code>Verify operation failed address 0x00200000. Was 0x00 instead of 0x18</code>
+ </td>
+ <td>PASS/FAIL</td>
+ </tr>
+</table>
+
+</body>
</html> \ No newline at end of file
generated by cgit v1.2.3-18-g5258 (git 2.32.0) at 2024-11-21 20:50:04 +0000