summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEdgar Grimberg <edgar.grimberg@zylin.com>2010-01-29 09:46:11 +0100
committerØyvind Harboe <oyvind.harboe@zylin.com>2010-02-01 15:44:06 +0100
commitbef37ceba2bde6a34d003762bced007bed894bc7 (patch)
tree2fd6f002700b982979bb2fdff429ae859c6b019d
parent91e3268737b578a182cb661d60551657f799ab3c (diff)
downloadopenocd+libswd-bef37ceba2bde6a34d003762bced007bed894bc7.tar.gz
openocd+libswd-bef37ceba2bde6a34d003762bced007bed894bc7.tar.bz2
openocd+libswd-bef37ceba2bde6a34d003762bced007bed894bc7.tar.xz
openocd+libswd-bef37ceba2bde6a34d003762bced007bed894bc7.zip
Test cases ran on v0.4.0-rc1
Test cases ran on v0.4.0-rc1 for a number of targets: AT91FR40162 LPC2148 SAM7 STR710 STR912 The goal of the testing session was to prove basic functionality of OpenOCD for different targets. Signed-off-by: Edgar Grimberg <edgar.grimberg@zylin.com>
Diffstat
-rwxr-xr-xtesting/results/v0.4.0-rc1/AT91FR40162.html856
-rwxr-xr-xtesting/results/v0.4.0-rc1/LPC2148.html933
-rwxr-xr-xtesting/results/v0.4.0-rc1/SAM7.html853
-rwxr-xr-xtesting/results/v0.4.0-rc1/STR710.html907
-rwxr-xr-xtesting/results/v0.4.0-rc1/STR912.html1008
5 files changed, 4557 insertions, 0 deletions
diff --git a/testing/results/v0.4.0-rc1/AT91FR40162.html b/testing/results/v0.4.0-rc1/AT91FR40162.html
new file mode 100755
index 00000000..0baa31e6
--- /dev/null
+++ b/testing/results/v0.4.0-rc1/AT91FR40162.html
@@ -0,0 +1,856 @@
+<html>
+<head>
+<title>Test results for revision 1.62</title>
+</head>
+
+<body>
+
+<H1>SAM7</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>AT91FR40162</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>AT91FR40162</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>
+ (gdb) tar remo 10.0.0.138:3333<br>
+ Remote debugging using 10.0.0.138:3333<br>
+ 0x000155b8 in ?? ()<br>
+ </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>AT91FR40162</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</code></td>
+ <td>
+ <code>
+ > mdw 0x01000000 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<br>
+ > reset halt<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x00008a70<br>
+ > <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>AT91FR40162</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>
+ > reset init<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x00008ea4<br>
+ > <br>
+ </code>
+ </td>
+ <td>PASS<br>
+ NOTE! Even if there is no message, the reset script is being executed (proved by side effects)</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>AT91FR40162</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>
+ Sensed nSRST asserted<br>
+ Sensed power dropout.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0xd5dff7e6<br>
+ Sensed power restore.<br>
+ Sensed nSRST deasserted<br>
+ > reset halt<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x0000072c<br>
+ ><br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</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>
+ > reset halt<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x00008b38<br>
+ > <br>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target using return clock</td>
+ <td>Erase all the content of the flash, set the configuration script to use RCLK</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</code></td>
+ <td>
+ <code>
+ N/A, At91EB40A does <bold>NOT</bold> have support for RCLK
+ </code>
+ </td>
+ <td>N/A</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"/>SPD001</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ > reset halt<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x00008ae8<br>
+ > jtag_khz 16000 <br>
+ jtag_speed 4 => JTAG clk=16.000000<br>
+ 16000 kHz<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 <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD002"/>SPD002</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>8MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ > reset halt <br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x00008c14<br>
+ > jtag_khz 8000 <br>
+ jtag_speed 8 => JTAG clk=8.000000<br>
+ 8000 kHz<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 <br>
+ > <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD003"/>SPD003</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>4MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ > reset halt <br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x00008bc4<br>
+ > jtag_khz 4000<br>
+ jtag_speed 16 => JTAG clk=4.000000<br>
+ 4000 kHz<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 <br>
+ > <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD004"/>SPD004</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>2MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ > reset halt<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x00009678<br>
+ > jtag_khz 2000<br>
+ jtag_speed 32 => JTAG clk=2.000000<br>
+ 2000 kHz<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 <br>
+ > <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD005"/>SPD005</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>RCLK on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 0<br>
+ RCLK - adaptive<br>
+ RCLK timeout<br>
+ </code>
+ N/A for this target
+ </td>
+ <td>N/A for this target</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>AT91FR40162</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-none-eabi-gdb redboot_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 .rom_vectors, size 0x40 lma 0xc000<br>
+ Loading section .text, size 0x103e8 lma 0xc040<br>
+ Loading section .rodata, size 0x1a84 lma 0x1c428<br>
+ Loading section .data, size 0x3ec lma 0x1deac<br>
+ Start address 0xc040, load size 74392<br>
+ Transfer rate: 572 KB/sec, 9299 bytes/write.<br>
+ (gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>Software breakpoint</td>
+ <td>Load the redboot_ram.elf application, use instructions from GDB001</td>
+ <td>In the GDB console:<br>
+ <code>
+ (gdb) monitor arm7_9 dbgrq enable<br>
+ software breakpoints enabled<br>
+ (gdb) break cyg_start<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>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) monitor arm7_9 dbgrq enable<br>
+ use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled<br>
+ (gdb) break cyg_start<br>
+ <br>
+ Breakpoint 1 at 0x155b8: file /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c, line 264.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, cyg_start ()<br>
+ at /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c:264<br>
+ 264 CYGACC_CALL_IF_MONITOR_VERSION_SET(RedBoot_version);<br>
+ (gdb) <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>AT91FR40162</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>
+ 70 DWORD b = 2;
+
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) step<br>
+ 266 CYGACC_CALL_IF_MONITOR_RETURN_SET(return_to_redboot);<br>
+ (gdb)<br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>AT91FR40162</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 init<br>
+ (gdb) load<br>
+ (gdb) continue<br>
+ </code></td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code>
+ </td>
+ <td><code>
+ (gdb) moni reset init<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x00008ae8<br>
+ (gdb) load<br>
+ Loading section .rom_vectors, size 0x40 lma 0xc000<br>
+ Loading section .text, size 0x103e8 lma 0xc040<br>
+ Loading section .rodata, size 0x1a84 lma 0x1c428<br>
+ Loading section .data, size 0x3ec lma 0x1deac<br>
+ Start address 0xc040, load size 74392<br>
+ Transfer rate: 576 KB/sec, 9299 bytes/write.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, cyg_start ()<br>
+ at /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c:264<br>
+ 264 CYGACC_CALL_IF_MONITOR_VERSION_SET(RedBoot_version);<br>
+ (gdb) <br>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>AT91FR40162</td>
+ <td>ZY1000</td>
+ <td>Hardware breakpoint</td>
+ <td>Flash the redboot_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 init<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) load<br>
+ Loading section .rom_vectors, size 0x40 lma 0x1000000<br>
+ Loading section .text, size 0x10638 lma 0x1000040<br>
+ Loading section .rodata, size 0x1a84 lma 0x1010678<br>
+ Loading section .data, size 0x428 lma 0x10120fc<br>
+ Start address 0x1000040, load size 75044<br>
+ Transfer rate: 33 KB/sec, 9380 bytes/write.<br>
+ (gdb) break cyg_start<br>
+ Breakpoint 1 at 0x100979c: file /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c, line 264.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ Note: automatically using hardware breakpoints for read-only addresses.<br>
+ <br>
+ Breakpoint 1, cyg_start () at /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c:264<br>
+ 264 CYGACC_CALL_IF_MONITOR_VERSION_SET(RedBoot_version);<br>
+ (gdb) <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>AT91FR40162</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>
+ (gdb) moni reset init<br>
+ JTAG tap: zy1000.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x1)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x200000d3 pc: 0x01000200<br>
+ (gdb) moni reg pc 0x1000000<br>
+ pc (/32): 0x01000000<br>
+ (gdb) c<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, cyg_start () at /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c:264<br>
+ 264 CYGACC_CALL_IF_MONITOR_VERSION_SET(RedBoot_version);<br>
+ (gdb) <br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>AT91FR40162</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>
+ Breakpoint 1, cyg_start () at /home/edgar/temp/ecosboard/packages/redboot/current/src/main.c:264<br>
+ 264 CYGACC_CALL_IF_MONITOR_VERSION_SET(RedBoot_version);<br>
+ (gdb) step<br>
+ 266 CYGACC_CALL_IF_MONITOR_RETURN_SET(return_to_redboot);<br>
+ </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>AT91FR40162</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 0 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: 15aadc6d 425b6f33 e789f955 d390dcc2 00080017 010067b4 010067b4 010067b4 <br>
+ 0x00000060: 010067b4 00006e74 00006e74 010067b4 010067b4 010067b4 010067b4 010067b4 <br>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM002"/>RAM002</td>
+ <td>AT91FR40162</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 0 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br>
+ </code></td>
+ <td>PASS<br>There is a problem with the formatting of the output</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>AT91FR40162</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 0x0 0xab 16<br>
+ > mdb 0x0 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</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>AT91FR40162</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
+ flash 'ecosflash' found at 0x01000000
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>AT91FR40162</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 0x100000 0xdeadbeef 16
+ </code>
+ </td>
+ <td>The commands should execute without error. The output looks like:<br>
+ <code>
+ wrote 64 bytes to 0x0100000 in 11.610000s (0.091516 kb/s)
+ </code><br>
+ To verify the contents of the flash:<br>
+ <code>
+ > mdw 0x100000 32<br>
+ 0x0100000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x0100020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x0100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td><code>
+ > flash fillw 0x01000000 0xdeadbeef 16 <br>
+ wrote 64 bytes to 0x01000000 in 0.010000s (6.250 kb/s)<br>
+ > 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 <br>
+ >
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>AT91FR40162</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 0x100000 0x2000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x0100000 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 0x100000 32<br>
+ 0x0100000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td><code>
+ > flash erase_address 0x1000000 0x10000<br>
+ erased address 0x01000000 (length 65536) in 0.840000s (76.190 kb/s)<br>
+ > 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 <br>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>AT91FR40162</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 halt<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 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 .rom_vectors, size 0x40 lma 0x1000000<br>
+ Loading section .text, size 0x10638 lma 0x1000040<br>
+ Loading section .rodata, size 0x1a84 lma 0x1010678<br>
+ Loading section .data, size 0x428 lma 0x10120fc<br>
+ Start address 0x1000040, load size 75044<br>
+ Transfer rate: 34 KB/sec, 9380 bytes/write.<br>
+ (gdb) moni verify_image /tftp/10.0.0.190/redboot_rom.elf<br>
+ keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1820). Workaround: increase "set remotetimeout" in GDB<br>
+ verified 75044 bytes in 1.960000s (37.390 kb/s)<br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+</body>
+</html> \ No newline at end of file
diff --git a/testing/results/v0.4.0-rc1/LPC2148.html b/testing/results/v0.4.0-rc1/LPC2148.html
new file mode 100755
index 00000000..425b5248
--- /dev/null
+++ b/testing/results/v0.4.0-rc1/LPC2148.html
@@ -0,0 +1,933 @@
+<html>
+<head>
+<title>Test results for revision 1.62</title>
+</head>
+
+<body>
+
+<H1>LPC2148</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>LPC2148</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>LPC2148</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>
+ (gdb) tar remo 10.0.0.73:3333<br>
+ Remote debugging using 10.0.0.73:3333<br>
+ 0x00000000 in ?? ()<br>
+ </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>LPC2148</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</code></td>
+ <td>
+ <code>
+ > 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<br>
+ > reset halt<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>LPC2148</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>
+ > reset init<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2da<br>
+ core state: ARM<br>
+ >
+ </code>
+ </td>
+ <td>PASS<br>
+ NOTE! Even if there is no message, the reset script is being executed (proved by side effects)</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>LPC2148</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>
+ nsed nSRST asserted.<br>
+ nsed power dropout.<br>
+ nsed power restore.<br>
+ SRST took 186ms to deassert<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ core state: ARM<br>
+ > reset halt<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>LPC2148</td>
+ <td>ZY1000</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>
+ <code>
+ > reset halt<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target using return clock</td>
+ <td>Erase all the content of the flash, set the configuration script to use RCLK</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</code></td>
+ <td>
+ <code>
+ > jtag_khz 0<br>
+ RCLK - adaptive<br>
+ > reset init<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ core state: ARM<br>
+ >
+ </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"/>SPD001</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ jtag_speed 4 => JTAG clk=16.000000<br>
+ 16000 kHz<br>
+ > reset halt<br>
+ JTAG scan chain interrogation failed: all zeroes<br>
+ Check JTAG interface, timings, target power, etc.<br>
+ error: -100<br>
+ Command handler execution failed<br>
+ in procedure 'reset' called at file "command.c", line 638<br>
+ called at file "/home/laurentiu/workspace/zy1000/build/../openocd/src/helper/command.c", line 352<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ ThumbEE -- incomplete support<br>
+ target state: halted<br>
+ target halted in ThumbEE state due to debug-request, current mode: System<br>
+ cpsr: 0x1fffffff pc: 0xfffffffa<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: System<br>
+ cpsr: 0xc00003ff pc: 0xfffffff0<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ ThumbEE -- incomplete support<br>
+ target state: halted<br>
+ target halted in ThumbEE state due to debug-request, current mode: System<br>
+ cpsr: 0xffffffff pc: 0xfffffffa<br>
+ >
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></td>
+ </tr>
+ <tr>
+ <td><a name="SPD002"/>SPD002</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>8MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 8000<br>
+ jtag_speed 8 => JTAG clk=8.000000<br>
+ 8000 kHz<br>
+ > reset halt<br>
+ JTAG scan chain interrogation failed: all zeroes<br>
+ Check JTAG interface, timings, target power, etc.<br>
+ error: -100<br>
+ Command handler execution failed<br>
+ in procedure 'reset' called at file "command.c", line 638<br>
+ called at file "/home/laurentiu/workspace/zy1000/build/../openocd/src/helper/command.c", line 352<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ invalid mode value encountered 0<br>
+ cpsr contains invalid mode value - communication failure<br>
+ >
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></td>
+ </tr>
+ <tr>
+ <td><a name="SPD003"/>SPD003</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>4MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 4000<br>
+ jtag_speed 16 => JTAG clk=4.000000<br>
+ 4000 kHz<br>
+ > reset halt<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0xc79f0f87 (mfg: 0x7c3, part: 0x79f0, ver: 0xc)<br>
+ JTAG tap: lpc2148.cpu UNEXPECTED: 0xc79f0f87 (mfg: 0x7c3, part: 0x79f0, ver: 0xc)<br>
+ JTAG tap: lpc2148.cpu expected 1 of 1: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ Unexpected idcode after end of chain: 64 0x0000007f<br>
+ Unexpected idcode after end of chain: 160 0x0000007f<br>
+ Unexpected idcode after end of chain: 192 0x0000007f<br>
+ Unexpected idcode after end of chain: 320 0x0000007f<br>
+ Unexpected idcode after end of chain: 352 0x0000007f<br>
+ Unexpected idcode after end of chain: 384 0x0000007f<br>
+ Unexpected idcode after end of chain: 480 0x0000007f<br>
+ Unexpected idcode after end of chain: 512 0x0000007f<br>
+ Unexpected idcode after end of chain: 544 0x0000007f<br>
+ double-check your JTAG setup (interface, speed, missing TAPs, ...)<br>
+ error: -100<br>
+ Command handler execution failed<br>
+ in procedure 'reset' called at file "command.c", line 638<br>
+ called at file "/home/laurentiu/workspace/zy1000/build/../openocd/src/helper/command.c", line 352<br>
+ >
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></td>
+ </tr>
+ <tr>
+ <td><a name="SPD004"/>SPD004</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>2MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 2000<br>
+ jtag_speed 32 => JTAG clk=2.000000<br>
+ 2000 kHz<br>
+ > reset halt<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2da<br>
+ > mdw 0 32<br>
+ 0x00000000: e59f4034 e3a05002 e5845000 e3a05003 e5845004 e59f201c e3a03000 e1020093<br>
+ 0x00000020: e2822028 e1021093 e3c03007 e5023028 e51ff004 7fffd1c4 e002c014 e01fc000<br>
+ 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD005"/>SPD005</td>
+ <td>LPC2148</td>
+ <td>ZY1000</td>
+ <td>RCLK on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 0<br>
+ RCLK - adaptive<br>
+ > mdw 0 32<br>
+ 0x00000000: e59f4034 e3a05002 e5845000 e3a05003 e5845004 e59f201c e3a03000 e1020093<br>
+ 0x00000020: e2822028 e1021093 e3c03007 e5023028 e51ff004 7fffd1c4 e002c014 e01fc000<br>
+ 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ >
+ </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>LPC2148</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 0x16c lma 0x40000000<br>
+ Start address 0x40000040, load size 364<br>
+ Transfer rate: 32 KB/sec, 364 bytes/write.<br>
+ (gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>LPC2148</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 gdb_breakpoint_override soft<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) monitor gdb_breakpoint_override soft<br>
+ force soft breakpoints<br>
+ Current language: auto<br>
+ The current source language is "auto; currently asm".<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x4000010c: file src/main.c, line 71.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;<br>
+ Current language: auto<br>
+ The current source language is "auto; currently c".<br>
+ (gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>LPC2148</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>
+ 72 DWORD b = 2;<br>
+ (gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>LPC2148</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 init<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 init<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in Thumb state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0xa00000f3 pc: 0x7fffd2d6<br>
+ core state: ARM<br>
+ (gdb) load<br>
+ Loading section .text, size 0x16c lma 0x40000000<br>
+ Start address 0x40000040, load size 364<br>
+ Transfer rate: 27 KB/sec, 364 bytes/write.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;<br>
+ (gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>LPC2148</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 init<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 gdb_breakpoint_override hard<br>
+ force hard breakpoints<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) monitor gdb_breakpoint_override hard<br>
+ force hard breakpoints<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x10c: file src/main.c, line 71.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ Note: automatically using hardware breakpoints for read-only addresses.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;<br>
+ Current language: auto<br>
+ The current source language is "auto; currently c".<br>
+ (gdb)
+ </code>
+ </td>
+ <td>PASS <font color=red>NOTE: This test is failing from time to time, not able to describe a cause</font></td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>LPC2148</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>
+ (gdb) monitor reset init<br>
+ JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00000160<br>
+ core state: ARM<br>
+ (gdb) monitor reg pc 0x40<br>
+ pc (/32): 0x00000040<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;<br>
+ (gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>LPC2148</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 gdb_breakpoint_override hard<br>
+ force hard breakpoints<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) load<br>
+ Loading section .text, size 0x16c lma 0x0<br>
+ Start address 0x40, load size 364<br>
+ Transfer rate: 637 bytes/sec, 364 bytes/write.<br>
+ (gdb) monitor gdb_breakpoint_override hard<br>
+ force hard breakpoints<br>
+ Current language: auto<br>
+ The current source language is "auto; currently asm".<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x10c: file src/main.c, line 71.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ Note: automatically using hardware breakpoints for read-only addresses.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:71<br>
+ 71 DWORD a = 1;<br>
+ Current language: auto<br>
+ The current source language is "auto; currently c".<br>
+ (gdb) step<br>
+ 72 DWORD b = 2;<br>
+ (gdb)
+
+ </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>LPC2148</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 0x40000000 0xdeadbeef 16<br>
+ > mdw 0x40000000 32<br>
+ 0x40000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x40000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x40000040: e1a00000 e1a00000 e1a00000 e1a00000 e1a00000 e1a00000 e1a00000 e1a00000<br>
+ 0x40000060: e321f0db e59fd07c e321f0d7 e59fd078 e321f0d1 e59fd074 e321f0d2 e59fd070<br>
+ >
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM002"/>RAM002</td>
+ <td>LPC2148</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 0x40000000 0xbeef 16<br>
+ > mdh 0x40000000 32<br>
+ 0x40000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+ 0x40000020: beef dead beef dead beef dead beef dead beef dead beef dead beef dead beef dead<br>
+ >
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>LPC2148</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 0x40000000 0xab 16
+ > mdb 0x40000000 32
+ 0x40000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ef be ef be ef be ef be ef be ef be ef be ef be
+ >
+
+ </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>LPC2148</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 'lpc2000' found at 0x00000000
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>LPC2148</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 0x0 0xdeadbeef 16<br>
+ Verification will fail since checksum in image (0xdeadbeef) to be written to flash is different from calculated vector checksum (0xe93fc777).<br>
+ To remove this warning modify build tools on developer PC to inject correct LPC vector checksum.<br>
+ wrote 64 bytes to 0x00000000 in 0.040000s (1.563 kb/s)<br>
+ > mdw 0 32<br>
+ 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef e93fc777 deadbeef deadbeef<br>
+ 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ >
+ </code></td>
+ <td><font color=red>FAIL</font></td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>LPC2148</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 0 0x2000<br>
+ erased address 0x00000000 (length 8192) in 0.510000s (15.686 kb/s)<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<br>
+ >
+ </code></td>
+ <td>PASS</td>
+
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>LPC2148</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) moni verify_image /tftp/10.0.0.194/test_rom.elf<br>
+ checksum mismatch - attempting binary compare<br>
+ Verify operation failed address 0x00000014. Was 0x58 instead of 0x60<br>
+ <br>
+ Command handler execution failed<br>
+ in procedure 'verify_image' called at file "command.c", line 647<br>
+ called at file "command.c", line 361<br>
+ (gdb)
+ </code>
+ </td>
+ <td><font color=red>FAIL</font></td>
+ </tr>
+</table>
+
+</body>
+</html> \ No newline at end of file
diff --git a/testing/results/v0.4.0-rc1/SAM7.html b/testing/results/v0.4.0-rc1/SAM7.html
new file mode 100755
index 00000000..a400a476
--- /dev/null
+++ b/testing/results/v0.4.0-rc1/SAM7.html
@@ -0,0 +1,853 @@
+<html>
+<head>
+<title>Test results for revision 1.62</title>
+</head>
+
+<body>
+
+<H1>SAM7</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>
+ (gdb) tar remo 10.0.0.73:3333<br>
+ Remote debugging using 10.0.0.73:3333<br>
+ 0x00100174 in ?? ()<br>
+ </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</code></td>
+ <td>
+ <code>
+ > 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<br>
+ > reset halt<br>
+ SRST took 2ms to deassert<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x000003c4<br>
+ >
+ </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>
+ > reset init<br>
+ SRST took 2ms to deassert<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x000003c0<br>
+ >
+ </code>
+ </td>
+ <td>PASS<br>
+ NOTE! Even if there is no message, the reset script is being executed (proved by side effects)</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>
+ Sensed nSRST asserted<br>
+ Sensed power dropout.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0xd5dff7e6<br>
+ Sensed power restore.<br>
+ Sensed nSRST deasserted<br>
+ > reset halt<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0xf00000d3 pc: 0x0000072c<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</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>
+ <code>
+ > reset halt<br>
+ SRST took 2ms to deassert<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x300000d3 pc: 0x000003c0
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target using return clock</td>
+ <td>Erase all the content of the flash, set the configuration script to use RCLK</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</code></td>
+ <td>
+ <code>
+ > jtag_khz 0<br>
+ jtag_khz: 0<br>
+ > reset init<br>
+ SRST took 2ms to deassert<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x300000d3 pc: 0x000003c0<br>
+ executing event/sam7s256_reset.script<br>
+ >
+ </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"/>SPD001</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+ jtag_speed 4 => JTAG clk=16.000000<br>
+ 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<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD002"/>SPD002</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>8MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 8000<br>
+ jtag_speed 8 => JTAG clk=8.000000<br>
+ jtag_khz: 8000<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<br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD003"/>SPD003</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>4MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 4000<br>
+ jtag_speed 16 => JTAG clk=4.000000<br>
+ jtag_khz: 4000<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<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD004"/>SPD004</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>2MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 2000<br>
+ jtag_speed 32 => JTAG clk=2.000000<br>
+ jtag_khz: 2000<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<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD005"/>SPD005</td>
+ <td>SAM7S64</td>
+ <td>ZY1000</td>
+ <td>RCLK on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 0<br>
+ jtag_khz: 0<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<br>
+ >
+ </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: 443 bytes/sec, 404 bytes/write.<br>
+ (gdb)
+ </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 dbgrq 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>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) monitor arm7_9 dbgrq enable<br>
+ use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled<br>
+ (gdb) break main<br>
+ Breakpoint 1 at 0x200134: file src/main.c, line 69.<br>
+ (gdb) c<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ Current language: auto<br>
+ The current source language is "auto; currently c".<br>
+ (gdb)
+ </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>
+ 70 DWORD b = 2;
+
+ </code>
+ </td>
+ <td>
+ <code>
+ (gdb) step<br>
+ 70 DWORD b = 2;
+ (gdb)
+ </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 init<br>
+ (gdb) load<br>
+ (gdb) continue<br>
+ </code></td>
+ <td>The breakpoint should be reached, typical output:<br>
+ <code>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;
+ </code>
+ </td>
+ <td><code>
+ (gdb) monitor reset init<br>
+ JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug-request, current mode: Supervisor<br>
+ cpsr: 0x600000d3 pc: 0x0000031c<br>
+ (gdb) load<br>
+ Loading section .text, size 0x194 lma 0x200000<br>
+ Start address 0x200040, load size 404<br>
+ Transfer rate: 26 KB/sec, 404 bytes/write.<br>
+ (gdb) continue<br>
+ Continuing.<br>
+ <br>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ (gdb)
+ </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 init<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) 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>
+ Note: automatically using hardware breakpoints for read-only addresses.<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;<br>
+ (gdb)
+ </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>
+ (gdb) monitor reset init<br>
+ SRST took 3ms to deassert<br>
+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)<br>
+ srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+ target state: halted<br>
+ target halted in ARM state due to debug request, current mode: Supervisor<br>
+ cpsr: 0x60000013 pc: 0x00100168<br>
+ executing event/sam7s256_reset.script<br>
+ (gdb) monitor reg pc 0x100000<br>
+ pc (/32): 0x00100000<br>
+ (gdb) continue<br>
+ 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;<br>
+ (gdb)
+ </code>
+ </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>
+ Breakpoint 1, main () at src/main.c:69<br>
+ 69 DWORD a = 1;<br>
+ (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;<br>
+ (gdb)
+ </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 0x100000 0xdeadbeef 16
+ </code>
+ </td>
+ <td>The commands should execute without error. The output looks like:<br>
+ <code>
+ wrote 64 bytes to 0x0100000 in 11.610000s (0.091516 kb/s)
+ </code><br>
+ To verify the contents of the flash:<br>
+ <code>
+ > mdw 0x100000 32<br>
+ 0x0100000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x0100020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x0100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+ </code>
+ </td>
+ <td><code>
+ > flash fillw 0x100000 0xdeadbeef 16<br>
+ wrote 64 bytes to 0x00100000 in 0.040000s (26.562500 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<br>
+ >
+ </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 0x100000 0x2000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x0100000 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 0x100000 32<br>
+ 0x0100000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x0100060: 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.020000s<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 halt<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 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: 4 KB/sec, 404 bytes/write.<br>
+ (gdb) moni verify_image /tftp/10.0.0.9/c:/temp/testing/examples/SAM7S256Test/test_rom.elf<br>
+ verified 404 bytes in 0.570000s
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+</body>
+</html> \ No newline at end of file
diff --git a/testing/results/v0.4.0-rc1/STR710.html b/testing/results/v0.4.0-rc1/STR710.html
new file mode 100755
index 00000000..1a18ad0e
--- /dev/null
+++ b/testing/results/v0.4.0-rc1/STR710.html
@@ -0,0 +1,907 @@
+<html>
+<head>
+<title>Test results for version 1.62</title>
+</head>
+
+<body>
+
+<H1>STR710</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>STR912</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>> telnet 10.0.0.142<br>
+ Trying 10.0.0.142...<br>
+ Connected to 10.0.0.142.<br>
+ Escape character is '^]'.<br>
+ Open On-Chip Debugger<br>
+ >
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="CON002"/>CON002</td>
+ <td>STR912</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>
+ (gdb) tar remo 10.0.0.142:3333<br>
+ Remote debugging using 10.0.0.142:3333<br>
+ 0x00016434 in ?? ()<br>
+ (gdb)
+ </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>STR912</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</code></td>
+ <td>
+ <code>
+> mdw 0 32<br>
+0x00000000: 75755000 8a930104 65696f65 939a3e98 214751f1 fa0edb9b 6664686d 931a989e<br>
+0x00000020: 676c65e4 9a0a0982 25653445 da02ba90 c4ed3165 9b9a8a9a 65676365 01981292<br>
+0x00000040: 212e0982 82ba3f8b 34674765 96ba1a9a 6175e7e5 9b9ab91a 0789644d 120a9a18<br>
+0x00000060: 65446167 80d20982 6d6d6565 187090ca 65277d65 9a9a0b81 6960416c 9ffe88b8<br>
+> reset<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+><br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>STR912</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>
+> reset init<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Undefined instruction<br>
+cpsr: 0xf00000db pc: 0x00000004<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>STR912</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>
+ nsed power dropout.<br>
+ nsed power dropout.<br>
+ nsed nSRST deasserted.<br>
+ invalid mode value encountered 0<br>
+cpsr contains invalid mode value - communication failure<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x100000d3 pc: 0x0000001c<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz<br>
+ nsed power restore.<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x500000d3 pc: 0x00000000<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz<br>
+> reset init<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x500000d3 pc: 0x00000000<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>STR912</td>
+ <td>ZY1000</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</code></td>
+ <td>
+ <code>
+> reset halt<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x200000d3 pc: 0xfe50cba4<br>
+>
+</code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target using return clock</td>
+ <td>Erase all the content of the flash, set the configuration script to use RCLK</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</code></td>
+ <td>
+ <code>
+ > jtag_khz 0<br>
+RCLK - adaptive<br>
+RCLK timeout<br>
+RCLK timeout<br>
+RCLK timeout<br>
+ > reset halt<br>
+ RCLK timeout<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x200000d3 pc: 0xfe50cb50<br>
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></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"/>SPD001</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+jtag_speed 4 => JTAG clk=16.000000<br>
+16000 kHz<br>
+> mdw 0 32<br>
+0x00000000: 75755000 8a930104 65696f65 939a3e98 214751f1 fa0edb9b 6664686d 931a989e<br>
+0x00000020: 676c65e4 9a0a0982 25653445 da02ba90 c4ed3165 9b9a8a9a 65676365 01981292<br>
+0x00000040: 212e0982 82ba3f8b 34674765 96ba1a9a 6175e7e5 9b9ab91a 0789644d 120a9a18<br>
+0x00000060: 65446167 80d20982 6d6d6565 187090ca 65277d65 9a9a0b81 6960416c 9ffe88b8<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD002"/>SPD002</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>8MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 8000<br>
+jtag_speed 8 => JTAG clk=8.000000<br>
+8000 kHz<br>
+> mdw 0 32<br>
+0x00000000: 75755000 8a930104 65696f65 939a3e98 214751f1 fa0edb9b 6664686d 931a989e<br>
+0x00000020: 676c65e4 9a0a0982 25653445 da02ba90 c4ed3165 9b9a8a9a 65676365 01981292<br>
+0x00000040: 212e0982 82ba3f8b 34674765 96ba1a9a 6175e7e5 9b9ab91a 0789644d 120a9a18<br>
+0x00000060: 65446167 80d20982 6d6d6565 187090ca 65277d65 9a9a0b81 6960416c 9ffe88b8<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD003"/>SPD003</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>4MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 4000<br>
+jtag_speed 16 => JTAG clk=4.000000<br>
+4000 kHz<br>
+> mdw 0 32<br>
+0x00000000: 75755000 8a930104 65696f65 939a3e98 214751f1 fa0edb9b 6664686d 931a989e<br>
+0x00000020: 676c65e4 9a0a0982 25653445 da02ba90 c4ed3165 9b9a8a9a 65676365 01981292<br>
+0x00000040: 212e0982 82ba3f8b 34674765 96ba1a9a 6175e7e5 9b9ab91a 0789644d 120a9a18<br>
+0x00000060: 65446167 80d20982 6d6d6565 187090ca 65277d65 9a9a0b81 6960416c 9ffe88b8<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD004"/>SPD004</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>2MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 2000<br>
+jtag_speed 32 => JTAG clk=2.000000<br>
+2000 kHz<br>
+> mdw 0 32<br>
+0x00000000: 75755000 8a930104 65696f65 939a3e98 214751f1 fa0edb9b 6664686d 931a989e<br>
+0x00000020: 676c65e4 9a0a0982 25653445 da02ba90 c4ed3165 9b9a8a9a 65676365 01981292<br>
+0x00000040: 212e0982 82ba3f8b 34674765 96ba1a9a 6175e7e5 9b9ab91a 0789644d 120a9a18<br>
+0x00000060: 65446167 80d20982 6d6d6565 187090ca 65277d65 9a9a0b81 6960416c 9ffe88b8<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD005"/>SPD005</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>RCLK on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 0<br>
+RCLK - adaptive<br>
+RCLK timeout<br>
+RCLK timeout<br>
+RCLK timeout
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></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>STR912</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 0x1cc lma 0x20000000<br>
+Loading section .vectors, size 0x40 lma 0x200001cc<br>
+Loading section .rodata, size 0x4 lma 0x2000020c<br>
+Start address 0x20000000, load size 528<br>
+Transfer rate: 64 KB/sec, 176 bytes/write.<br>
+(gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>STR912</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 gdb_breakpoint_override soft<br>
+ force soft breakpoints<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) monitor gdb_breakpoint_override soft<br>
+force soft breakpoints<br>
+Current language: auto<br>
+The current source language is "auto; currently asm".<br>
+(gdb) break main<br>
+Breakpoint 1 at 0x20000170: file src/main.c, line 69.<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>STR912</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>
+ 70 DWORD b = 2;<br>
+ (gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>STR912</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 init<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) monitor reset init<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x60000013 pc: 0x200001bc<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz<br>
+(gdb) load<br>
+Loading section .text, size 0x1cc lma 0x20000000<br>
+Loading section .vectors, size 0x40 lma 0x200001cc<br>
+Loading section .rodata, size 0x4 lma 0x2000020c<br>
+Start address 0x20000000, load size 528<br>
+Transfer rate: 64 KB/sec, 176 bytes/write.<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+(gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>STR912</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 init<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 gdb_breakpoint_override hard<br>
+ force hard breakpoints<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) monitor gdb_breakpoint_override hard<br>
+force hard breakpoints<br>
+(gdb) break main<br>
+Breakpoint 1 at 0x40000170: file src/main.c, line 69.<br>
+(gdb) c<br>
+Continuing.<br>
+Note: automatically using hardware breakpoints for read-only addresses.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>STR912</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>
+(gdb) monitor reset init<br>
+jtag_speed 6400 => JTAG clk=0.010000<br>
+10 kHz<br>
+JTAG tap: str710.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)<br>
+srst pulls trst - can not reset into halted mode. Issuing halt after reset.<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Undefined instruction<br>
+cpsr: 0x400000db pc: 0x010aea80<br>
+jtag_speed 10 => JTAG clk=6.400000<br>
+6400 kHz<br>
+(gdb) monitor reg pc 0x40000000<br>
+pc (/32): 0x40000000<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>STR912</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>
+Breakpoint 2, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb) step<br>
+70 DWORD b = 2;<br>
+(gdb)
+ </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>STR912</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 0x20000000 0xdeadbeef 16<br>
+> mdw 0x20000000 32<br>
+0x20000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x20000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x20000040: e3a0020a e3a01073 e5801018 e5901008 e3110002 0afffffc e3a0020a e59f10d0<br>
+0x20000060: e5801008 e321f0db e59fd0c8 e321f0d7 e59fd0c4 e321f0d1 e59fd0c0 e321f0d2<br>
+>
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM002"/>RAM002</td>
+ <td>STR912</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 0x20000000 0xbeef 16<br>
+> mdh 0x20000000 32<br>
+0x20000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+0x20000020: beef dead beef dead beef dead beef dead beef dead beef dead beef dead beef dead<br>
+>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>STR912</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 0x20000000 0xab 16<br>
+> mdb 0x20000000 32<br>
+0x20000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ef be ef be ef be ef be ef be ef be ef be ef be<br>
+>
+ </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>STR912</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 'str7x' found at 0x40000000<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>STR912</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 0x40000000 0xdeadbeef 16<br>
+ wrote 64 bytes to 0x40000000 in 0.000000s (inf kb/s)<br>
+ > mdw 0x40000000 32<br>
+ 0x40000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x40000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+ 0x40000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ 0x40000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+ >
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>STR912</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 0x40000000 0x2000<br>
+erased address 0x40000000 (length 8192) in 0.270000s (29.630 kb/s)<br>
+> mdw 0x40000000 32 <br>
+0x40000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+0x40000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+0x40000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+0x40000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+>
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>STR912</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 0x1cc lma 0x40000000<br>
+Loading section .vectors, size 0x40 lma 0x400001cc<br>
+Loading section .rodata, size 0x4 lma 0x4000020c<br>
+Start address 0x40000000, load size 528<br>
+Transfer rate: 53 bytes/sec, 176 bytes/write.<br>
+(gdb) monitor verify_image /tftp/10.0.0.194/test_rom.elf<br>
+verified 528 bytes in 4.760000s (0.108 kb/s)<br>
+Current language: auto<br>
+The current source language is "auto; currently asm".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+</body>
+</html> \ No newline at end of file
diff --git a/testing/results/v0.4.0-rc1/STR912.html b/testing/results/v0.4.0-rc1/STR912.html
new file mode 100755
index 00000000..c8df0348
--- /dev/null
+++ b/testing/results/v0.4.0-rc1/STR912.html
@@ -0,0 +1,1008 @@
+<html>
+<head>
+<title>Test results for version 1.62</title>
+</head>
+
+<body>
+
+<H1>STR912</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>STR912</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>> telnet 10.0.0.142<br>
+ Trying 10.0.0.142...<br>
+ Connected to 10.0.0.142.<br>
+ Escape character is '^]'.<br>
+ Open On-Chip Debugger<br>
+ >
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="CON002"/>CON002</td>
+ <td>STR912</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>
+ (gdb) tar remo 10.0.0.142:3333<br>
+ Remote debugging using 10.0.0.142:3333<br>
+ 0x00016434 in ?? ()<br>
+ (gdb)
+ </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>STR912</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</code></td>
+ <td>
+ <code>
+> reset halt<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES002"/>RES002</td>
+ <td>STR912</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>
+> reset init<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+cleared protection for sectors 0 through 7 on flash bank 0<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES003"/>RES003</td>
+ <td>STR912</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>
+ nsed nSRST asserted.<br>
+ nsed power dropout.<br>
+ nsed power restore.<br>
+RCLK - adaptive<br>
+SRST took 85ms to deassert<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+cleared protection for sectors 0 through 7 on flash bank 0<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+> reset halt<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES004"/>RES004</td>
+ <td>STR912</td>
+ <td>ZY1000</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>
+ <code>
+> reset halt<br>
+ RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (Manufacturer: 0x020, Part: 0x4570, Version: 0x0)<br>
+JTAG Tap/device matched<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (Manufacturer: 0x020, Part: 0x5966, Version: 0x2)<br>
+JTAG Tap/device matched<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (Manufacturer: 0x020, Part: 0x457f, Version: 0x2)<br>
+JTAG Tap/device matched<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RES005"/>RES005</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>Reset halt on a blank target using return clock</td>
+ <td>Erase all the content of the flash, set the configuration script to use RCLK</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</code></td>
+ <td>
+ <code>
+ > reset halt<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+>
+ </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"/>SPD001</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>16MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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>
+jtag_speed 4 => JTAG clk=16.000000<br>
+16000 kHz<br>
+ThumbEE -- incomplete support<br>
+target state: halted<br>
+target halted in ThumbEE state due to debug-request, current mode: System<br>
+cpsr: 0xfdfdffff pc: 0xfdfdfff9<br>
+> mdw 0 32 <br>
+0x00000000: 00000000 00000000 ffffffff ffffffff 00000001 ffffffff 00000001 ffffffff<br>
+0x00000020: 00000001 00000001 00000001 00000001 00000001 fffffffe fffffffe 00000001<br>
+0x00000040: fffffffe 00000000 00000000 00000000 00000000 00000000 00000000 00000000<br>
+0x00000060: 00000000 00000000 00000000 00000000 ffffffff ffffffff 00000001 00000000<br>
+invalid mode value encountered 0<br>
+cpsr contains invalid mode value - communication failure<br>
+ThumbEE -- incomplete support<br>
+target state: halted<br>
+target halted in ThumbEE state due to debug-request, current mode: System<br>
+cpsr: 0xffffffff pc: 0xfffffff8<br>
+>
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></td>
+ </tr>
+ <tr>
+ <td><a name="SPD002"/>SPD002</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>8MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 8000<br>
+jtag_speed 8 => JTAG clk=8.000000<br>
+8000 kHz<br>
+> halt <br>
+invalid mode value encountered 0<br>
+cpsr contains invalid mode value - communication failure<br>
+Command handler execution failed<br>
+in procedure 'halt' called at file "command.c", line 647<br>
+called at file "command.c", line 361<br>
+Halt timed out, wake up GDB.<br>
+>
+ </code>
+ </td>
+ <td><font color=red><b>FAIL</b></font></td>
+ </tr>
+ <tr>
+ <td><a name="SPD003"/>SPD003</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>4MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 4000<br>
+jtag_speed 16 => JTAG clk=4.000000<br>
+4000 kHz<br>
+> halt <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<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD004"/>SPD004</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>2MHz on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 2000<br>
+jtag_speed 32 => JTAG clk=2.000000<br>
+2000 kHz<br>
+> halt<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<br>
+>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="SPD005"/>SPD005</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>RCLK on normal operation</td>
+ <td>Reset init the target according to RES002 </td>
+ <td>Change speed and 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 0<br>
+RCLK - adaptive<br>
+> halt <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<br>
+>
+ </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>STR912</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 0x1a0 lma 0x4000000<br>
+Loading section .rodata, size 0x4 lma 0x40001a0<br>
+Start address 0x4000000, load size 420<br>
+Transfer rate: 29 KB/sec, 210 bytes/write.<br>
+(gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+
+ <tr>
+ <td><a name="DBG002"/>DBG002</td>
+ <td>STR912</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 gdb_breakpoint_override soft<br>
+ force soft breakpoints<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) monitor gdb_breakpoint_override soft<br>
+force soft breakpoints<br>
+Current language: auto<br>
+The current source language is "auto; currently asm".<br>
+(gdb) break main<br>
+Breakpoint 1 at 0x4000144: file src/main.c, line 69.<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+warning: Source file is more recent than executable.<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG003"/>DBG003</td>
+ <td>STR912</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>
+ 70 DWORD b = 2;<br>
+ (gdb)<br>
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG004"/>DBG004</td>
+ <td>STR912</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 init<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) monitor reset init<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+cleared protection for sectors 0 through 7 on flash bank 0<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+(gdb) load<br>
+Loading section .text, size 0x1a0 lma 0x4000000<br>
+Loading section .rodata, size 0x4 lma 0x40001a0<br>
+Start address 0x4000000, load size 420<br>
+Transfer rate: 25 KB/sec, 210 bytes/write.<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+(gdb)
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG005"/>DBG005</td>
+ <td>STR912</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 init<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 gdb_breakpoint_override hard<br>
+ force hard breakpoints<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) monitor reset init<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+cleared protection for sectors 0 through 7 on flash bank 0<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+(gdb) load<br>
+Loading section .text, size 0x1a0 lma 0x0<br>
+Loading section .rodata, size 0x4 lma 0x1a0<br>
+Start address 0x0, load size 420<br>
+Transfer rate: 426 bytes/sec, 210 bytes/write.<br>
+(gdb) monitor gdb_breakpoint_override hard<br>
+force hard breakpoints<br>
+(gdb) break main<br>
+Breakpoint 1 at 0x144: file src/main.c, line 69.<br>
+(gdb) continue<br>
+Continuing.<br>
+Note: automatically using hardware breakpoints for read-only addresses.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+warning: Source file is more recent than executable.<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG006"/>DBG006</td>
+ <td>STR912</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>
+(gdb) monitor reset init<br>
+RCLK - adaptive<br>
+SRST took 2ms to deassert<br>
+JTAG tap: str912.flash tap/device found: 0x04570041 (mfg: 0x020, part: 0x4570, ver: 0x0)<br>
+JTAG tap: str912.cpu tap/device found: 0x25966041 (mfg: 0x020, part: 0x5966, ver: 0x2)<br>
+JTAG tap: str912.bs tap/device found: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs UNEXPECTED: 0x2457f041 (mfg: 0x020, part: 0x457f, ver: 0x2)<br>
+JTAG tap: str912.bs expected 1 of 1: 0x1457f041 (mfg: 0x020, part: 0x457f, ver: 0x1)<br>
+Trying to use configured scan chain anyway...<br>
+Bypassing JTAG setup events due to errors<br>
+SRST took 2ms to deassert<br>
+target state: halted<br>
+target halted in ARM state due to debug-request, current mode: Supervisor<br>
+cpsr: 0x000000d3 pc: 0x00000000<br>
+cleared protection for sectors 0 through 7 on flash bank 0<br>
+NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.<br>
+(gdb) c<br>
+Continuing.<br>
+<br>
+Breakpoint 1, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="DBG007"/>DBG007</td>
+ <td>STR912</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) c<br>
+Continuing.<br>
+<br>
+Breakpoint 2, main () at src/main.c:69<br>
+69 DWORD a = 1;<br>
+Current language: auto<br>
+The current source language is "auto; currently c".<br>
+(gdb) step<br>
+70 DWORD b = 2;<br>
+(gdb)
+ </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>STR912</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 0x4000000 0xdeadbeef 16<br>
+> mdw 0x4000000 32 <br>
+0x04000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x04000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x04000040: e580100c e3a01802 e5801010 e3a01018 e5801018 e59f00a8 e59f10a8 e5801000<br>
+0x04000060: e3a00806 ee2f0f11 e321f0d7 e59fd098 e321f0db e59fd094 e321f0d3 e59fd090<br>
+>
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM002"/>RAM002</td>
+ <td>STR912</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 0x4000000 0xbeef 16<br>
+> mdh 0x4000000 32<br>
+0x04000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef<br>
+0x04000020: beef dead beef dead beef dead beef dead beef dead beef dead beef dead beef dead<br>
+>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="RAM003"/>RAM003</td>
+ <td>STR912</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 0x4000000 0xab 16<br>
+> mdb 0x4000000 32<br>
+0x04000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ef be ef be ef be ef be ef be ef be ef be ef be<br>
+>
+ </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>STR912</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 'str9x' found at 0x00000000<br>
+ >
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA002"/>FLA002</td>
+ <td>STR912</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 0x0 0xdeadbeef 16 <br>
+wrote 64 bytes to 0x00000000 in 0.020000s (3.125 kb/s)<br>
+> mdw 0 32<br>
+0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef<br>
+0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff<br>
+>
+ </code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA003"/>FLA003</td>
+ <td>STR912</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 0x20000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x01000000 length 131072 in 4.970000s<br>
+ </code>
+ To check that the flash has been erased, read at different addresses. The result should always be 0xff.<br>
+ <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 0 0x20000<br>
+erased address 0x00000000 (length 131072) in 1.970000s (64.975 kb/s)<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<br>
+>
+</code></td>
+ <td>PASS</td>
+ </tr>
+ <tr>
+ <td><a name="FLA004"/>FLA004</td>
+ <td>STR912</td>
+ <td>ZY1000</td>
+ <td>Entire flash erase</td>
+ <td>Reset init is working, flash is probed</td>
+ <td>On the telnet interface<br>
+ <code> > flash erase_address 0x0 0x80000
+ </code>
+ </td>
+ <td>The commands should execute without error.<br>
+ <code>
+ erased address 0x01000000 length 8192 in 4.970000s<br>
+ </code>
+ To check that the flash has been erased, read at different addresses. The result should always be 0xff.<br>
+ <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 0 0x80000<br>
+ erased address 0x00000000 length 524288 in 1.020000s<br>
+<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>
+ <tr>
+ <td><a name="FLA005"/>FLA005</td>
+ <td>STR912</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 0x1a0 lma 0x0<br>
+Loading section .rodata, size 0x4 lma 0x1a0<br>
+Start address 0x0, load size 420<br>
+Transfer rate: 425 bytes/sec, 210 bytes/write.<br>
+(gdb) moni verify_image /tftp/10.0.0.194/test_rom.elf<br>
+verified 420 bytes in 0.350000s (1.172 kb/s)<br>
+(gdb)
+ </code>
+ </td>
+ <td>PASS</td>
+ </tr>
+</table>
+
+</body>
+</html> \ No newline at end of file
generated by cgit v1.2.3 (git 2.46.0) at 2024-12-22 23:46:34 +0000