From 2b3492b0ef0f4082e0e92dcba2d3531beea89954 Mon Sep 17 00:00:00 2001 From: oharboe Date: Thu, 24 Apr 2008 09:21:42 +0000 Subject: Edgar's new test cases. git-svn-id: svn://svn.berlios.de/openocd/trunk@613 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- testing/examples/SAM7S256Test/results/607.html | 698 +++++++++++++++++++++++++ 1 file changed, 698 insertions(+) create mode 100644 testing/examples/SAM7S256Test/results/607.html (limited to 'testing/examples') diff --git a/testing/examples/SAM7S256Test/results/607.html b/testing/examples/SAM7S256Test/results/607.html new file mode 100644 index 00000000..570b3b34 --- /dev/null +++ b/testing/examples/SAM7S256Test/results/607.html @@ -0,0 +1,698 @@ + + +Test results for revision 607 + + + +

Test cases

Test case results

+The test results are stored in seperate documents. One document for +each subversion number. + + + + +

Test results	comment
607
template	Test results template

+ +

SAM7S64

+ +

Connectivity

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	Interface	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
CON001	SAM7S64	ZY1000	Telnet connection	Power on, jtag target attached	On console, type `telnet ip port`	`Open On-Chip Debugger >`	`Open On-Chip Debugger >`	PASS
CON002	SAM7S64	ZY1000	GDB server connection	Power on, jtag target attached	On GDB console, type `target remote ip:port`	`Remote debugging using 10.0.0.73:3333`	`Remote debugging using 10.0.0.73:3333`	PASS

+ +

Reset

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	Interface	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
RES001	SAM7S64	ZY1000	Reset halt on a blank target	Erase all the content of the flash	Connect via the telnet interface and type `reset halt`	Reset should return without error and the output should contain `target state: halted pc = 0`	+ `+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3) + nSRST pulls nTRST, falling back to "reset run_and_halt" + target state: halted + target halted in ARM state due to debug request, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00100178 +` +	PASS
RES002	SAM7S64	ZY1000	Reset init on a blank target	Erase all the content of the flash	Connect via the telnet interface and type `reset init`	Reset should return without error and the output should contain `executing reset script 'name_of_the_script'`	+ `+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3) + nSRST pulls nTRST, falling back to "reset run_and_init" + target state: halted + target halted in ARM state due to debug request, current mode: Supervisor + cpsr: 0x600000d3 pc: 0x00003e24 + executing reset script 'event/sam7s256_reset.script' +` +	PASS
RES003	SAM7S64	ZY1000	Reset after a power cycle of the target	Reset the target then power cycle the target	Connect via the telnet interface and type `reset halt` after the power was detected	Reset should return without error and the output should contain `target state: halted`	+ `+ JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3) + nSRST pulls nTRST, falling back to "reset run_and_halt" + target state: halted + target halted in ARM state due to debug request, current mode: Supervisor + cpsr: 0x300000d3 pc: 0x00003a38 +` +	PASS

+ +

JTAG Speed

+ + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	ZY1000	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
RES001	SAM7S64	ZY1000	16MHz on normal operation	Reset init the target according to RES002	Exercise a memory access over the JTAG, for example `mdw 0x0 32`	The command should run without any errors. If any JTAG checking errors happen, the test failed	+ `+ > jtag_khz 16000 + > mdw 0 32 + 0x00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff +` +	PASS

+ +

Debugging

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	Interface	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
DBG001	SAM7S64	ZY1000	Load is working	Reset init is working, RAM is accesible, GDB server is started	On the console of the OS: + `arm-elf-gdb test_ram.elf` + `(gdb) target remote ip:port` + `(gdb) load +`	Load should return without error, typical output looks like: + `+ Loading section .text, size 0x14c lma 0x0 + Start address 0x40, load size 332 + Transfer rate: 180 bytes/sec, 332 bytes/write. +` +	`+ (gdb) load + Loading section .text, size 0x194 lma 0x200000 + Start address 0x200040, load size 404 + Transfer rate: 17470 bits/sec, 404 bytes/write. +`	PASS
DBG002	SAM7S64	ZY1000	Software breakpoint	Load the test_ram.elf application, use instructions from GDB001	In the GDB console: + `+ (gdb) monitor arm7_9 sw_bkpts enable + software breakpoints enabled + (gdb) break main + Breakpoint 1 at 0xec: file src/main.c, line 71. + (gdb) continue + Continuing. +` +	The software breakpoint should be reached, a typical output looks like: + `+ target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x000000d3 pc: 0x000000ec + + Breakpoint 1, main () at src/main.c:71 + 71 DWORD a = 1; +` +	+ `+ (gdb) break main + Breakpoint 2 at 0x200134: file src/main.c, line 69. + (gdb) c + Continuing. + target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00200134 + + Breakpoint 2, main () at src/main.c:69 + 69 DWORD a = 1; +` +	PASS
DBG003	SAM7S64	ZY1000	Single step in a RAM application	Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002	In GDB, type `(gdb) step`	The next instruction should be reached, typical output: + `+ (gdb) step + target state: halted + target halted in ARM state due to single step, current mode: Abort + cpsr: 0x20000097 pc: 0x000000f0 + target state: halted + target halted in ARM state due to single step, current mode: Abort + cpsr: 0x20000097 pc: 0x000000f4 + 72 DWORD b = 2; +` +	+ `+ (gdb) step + target state: halted + target halted in ARM state due to single step, current mode: Abort + cpsr: 0x20000097 pc: 0x000000f0 + target state: halted + target halted in ARM state due to single step, current mode: Abort + cpsr: 0x20000097 pc: 0x000000f4 + 72 DWORD b = 2; +` +	PASS
DBG004	SAM7S64	ZY1000	Software break points are working after a reset	Load the test_ram.elf application, use instructions from GDB001, break in main using the instructions from GDB002	In GDB, type `+ (gdb) monitor reset + (gdb) load + (gdb) continue +`	The breakpoint should be reached, typical output: + `+ target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x000000d3 pc: 0x000000ec + + Breakpoint 1, main () at src/main.c:71 + 71 DWORD a = 1; +` +	+ (gdb) moni reset + JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3) + target state: halted + target halted in ARM state due to debug request, current mode: Supervisor + cpsr: 0x600000d3 pc: 0x00003e28 + executing reset script 'event/sam7s256_reset.script' + (gdb) load + Loading section .text, size 0x194 lma 0x200000 + Start address 0x200040, load size 404 + Transfer rate: 20455 bits/sec, 404 bytes/write. + (gdb) continue + Continuing. + target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00200134 + + Breakpoint 2, main () at src/main.c:69 + 69 DWORD a = 1; +	PASS
DBG005	SAM7S64	ZY1000	Hardware breakpoint	Flash the test_rom.elf application. Make this test after FLA004 has passed	Be sure that `gdb_memory_map` and `gdb_flash_program` are enabled. In GDB, type + `+ (gdb) monitor reset + (gdb) load + Loading section .text, size 0x194 lma 0x100000 + Start address 0x100040, load size 404 + Transfer rate: 179 bytes/sec, 404 bytes/write. + (gdb) monitor arm7_9 force_hw_bkpts enable + force hardware breakpoints enabled + (gdb) break main + Breakpoint 1 at 0x100134: file src/main.c, line 69. + (gdb) continue +` +	The breakpoint should be reached, typical output: + `+ Continuing. + + Breakpoint 1, main () at src/main.c:69 + 69 DWORD a = 1; +` +	+ `+ (gdb) break main + Breakpoint 1 at 0x100134: file src/main.c, line 69. + (gdb) c + Continuing. + target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00100134 + + Breakpoint 1, main () at src/main.c:69 + 69 DWORD a = 1; +` +	PASS
DBG006	SAM7S64	ZY1000	Hardware breakpoint is set after a reset	Follow the instructions to flash and insert a hardware breakpoint from DBG005	In GDB, type + `+ (gdb) monitor reset + (gdb) monitor reg pc 0x100000 + pc (/32): 0x00100000 + (gdb) continue +` + where the value inserted in PC is the start address of the application +	The breakpoint should be reached, typical output: + `+ Continuing. + + Breakpoint 1, main () at src/main.c:69 + 69 DWORD a = 1; +` +	+ `+ Continuing. + target state: halted + target halted in ARM state due to single step, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00100040 + target state: halted + target halted in ARM state due to breakpoint, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00100134 + + Breakpoint 1, main () at src/main.c:69 + 69 DWORD a = 1; +` + Aren't there too many "halted" signs? +	PASS
DBG007	SAM7S64	ZY1000	Single step in ROM	Flash the test_rom.elf application and set a breakpoint in main, use DBG005. Make this test after FLA004 has passed	Be sure that `gdb_memory_map` and `gdb_flash_program` are enabled. In GDB, type + `+ (gdb) monitor reset + (gdb) load + Loading section .text, size 0x194 lma 0x100000 + Start address 0x100040, load size 404 + Transfer rate: 179 bytes/sec, 404 bytes/write. + (gdb) monitor arm7_9 force_hw_bkpts enable + force hardware breakpoints enabled + (gdb) break main + Breakpoint 1 at 0x100134: file src/main.c, line 69. + (gdb) continue + Continuing. + + Breakpoint 1, main () at src/main.c:69 + 69 DWORD a = 1; + (gdb) step +` +	The breakpoint should be reached, typical output: + `+ target state: halted + target halted in ARM state due to single step, current mode: Supervisor + cpsr: 0x60000013 pc: 0x0010013c + 70 DWORD b = 2; +` +	`+ (gdb) step + target state: halted + target halted in ARM state due to single step, current mode: Supervisor + cpsr: 0x60000013 pc: 0x00100138 + target state: halted + target halted in ARM state due to single step, current mode: Supervisor + cpsr: 0x60000013 pc: 0x0010013c + 70 DWORD b = 2; +`	PASS

+ +

RAM access

+Note: these tests are not designed to test/debug the target, but to test functionalities! + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	Interface	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
RAM001	SAM7S64	ZY1000	32 bit Write/read RAM	Reset init is working	On the telnet interface + `> mww ram_address 0xdeadbeef 16 + > mdw ram_address 32 +` +	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. + `+ > mww 0x0 0xdeadbeef 16 + > mdw 0x0 32 + 0x00000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00000040: e1a00000 e59fa51c e59f051c e04aa000 00080017 00009388 00009388 00009388 + 0x00000060: 00009388 0002c2c0 0002c2c0 000094f8 000094f4 00009388 00009388 00009388 +` +	+ `+ > mww 0x00200000 0xdeadbeef 16 + > mdw 0x00200000 32 + 0x00200000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00200020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00200040: e59f10b4 e3a00902 e5810004 e59f00ac e59f10ac e5810000 e3e010ff e59f00a4 + 0x00200060: e5810060 e59f10a0 e3e00000 e5810130 e5810124 e321f0db e59fd090 e321f0d7 +` +	PASS
RAM002	SAM7S64	ZY1000	16 bit Write/read RAM	Reset init is working	On the telnet interface + `> mwh ram_address 0xbeef 16 + > mdh ram_address 32 +` +	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. + `+ > mwh 0x0 0xbeef 16 + > mdh 0x0 32 + 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef + 0x00000020: 00e0 0000 021c 0000 0240 0000 026c 0000 0288 0000 0000 0000 0388 0000 0350 0000 + > +` +	`+ > mwh 0x00200000 0xbeef 16 + > mdh 0x00200000 32 + 0x00200000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef + 0x00200020: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 +`	PASS
RAM003	SAM7S64	ZY1000	8 bit Write/read RAM	Reset init is working	On the telnet interface + `> mwb ram_address 0xab 16 + > mdb ram_address 32 +` +	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. + `+ > mwb ram_address 0xab 16 + > mdb ram_address 32 + 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 + > +` +	`+ > mwb 0x00200000 0xab 16 + > mdb 0x00200000 32 + 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 +`	PASS

+ + + +

Flash access

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

ID	Target	Interface	Description	Initial state	Input	Expected output	Actual output	Pass/Fail
FLA001	SAM7S64	ZY1000	Flash probe	Reset init is working	On the telnet interface: + `> flash probe 0` +	The command should execute without error. The output should state the name of the flash and the starting address. An example of output: + `flash 'ecosflash' found at 0x01000000` +	+ `+ > flash probe 0 + flash 'at91sam7' found at 0x00100000 +` +	PASS
FLA002	SAM7S64	ZY1000	flash fillw	Reset init is working, flash is probed	On the telnet interface + `> flash fillw 0x1000000 0xdeadbeef 16 +` +	The commands should execute without error. The output looks like: + `+ wrote 64 bytes to 0x01000000 in 11.610000s (0.091516 kb/s) +` + To verify the contents of the flash: + `+ > mdw 0x1000000 32 + 0x01000000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x01000020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff +` +	`+ > flash fillw 0x100000 0xdeadbeef 16 + wrote 64 bytes to 0x00100000 in 1.110000s (0.957207 kb/s) + > mdw 0x100000 32 + 0x00100000: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00100020: deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef deadbeef + 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff +`	PASS
FLA003	SAM7S64	ZY1000	Flash erase	Reset init is working, flash is probed	On the telnet interface + `> flash erase_address 0x1000000 0x2000 +` +	The commands should execute without error. + `+ erased address 0x01000000 length 8192 in 4.970000s +` + To check that the flash has been erased, read at different addresses. The result should always be 0xff. + `+ > mdw 0x1000000 32 + 0x01000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x01000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x01000040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x01000060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff +` +	`+ > flash erase_address 0x100000 0x2000 + erased address 0x00100000 length 8192 in 0.510000s + > mdw 0x100000 32 + 0x00100000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00100020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00100040: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + 0x00100060: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff + > +`	PASS
FLA004	SAM7S64	ZY1000	Loading to flash from GDB	Reset init is working, flash is probed, connectivity to GDB server is working	Start GDB using a ROM elf image, eg: arm-elf-gdb test_rom.elf. + `+ (gdb) target remote ip:port + (gdb) monitor reset + (gdb) load + Loading section .text, size 0x194 lma 0x100000 + Start address 0x100040, load size 404 + Transfer rate: 179 bytes/sec, 404 bytes/write. + (gdb) monitor verify_image path_to_elf_file +` +	The output should look like: + `+ verified 404 bytes in 5.060000s +` + The failure message is something like: + `Verify operation failed address 0x00200000. Was 0x00 instead of 0x18` +	+ `+ (gdb) load + Loading section .text, size 0x194 lma 0x100000 + Start address 0x100040, load size 404 + Transfer rate: 1540 bits/sec, 404 bytes/write. + (gdb) monitor verify_image /tftp/10.0.0.9/c:\workspace/ecosboard/ecosboard/phi/openocd/rep/testing/examples/SAM7S256Test/test_rom.elf + verified 404 bytes in 4.860000s +` +	PASS

+ + + \ No newline at end of file -- cgit v1.2.3