On Nov 18, 2008, at 11:58 PM, Brian Wang wrote:
Debug: 71 12592 command.c:91 script_command(): script_command - halt Debug: 72 12592 command.c:108 script_command(): script_command - halt, argv[0]=ocd_halt Debug: 73 12592 target.c:1807 handle_halt_command(): -Debug: 74 12592 arm7_9_common.c:1065 arm7_9_halt(): target->state: running Debug: 75 12592 embeddedice.c:401 embeddedice_write_reg(): 0: 0x00000002Debug: 76 12598 target.c:1787 target_wait_state(): waiting for target halted... Error: 86 17594 target.c:1794 target_wait_state(): timed out while waiting for target haltedDebug: 87 17595 command.c:416 run_command(): Command failed with error code -4User: 88 17595 command.c:616 openocd_jim_vfprintf(): Runtime error, file "command.c", line 445: User: 89 17596 command.c:616 openocd_jim_vfprintf():
You sent halt via the telnet prompt (lines 1 and 2). The target ran the handler (line 3) which called into the arm7_9 common code to do a halt (line 4). That resulted in a register write (line 5). OpenOCD was then waiting for the target to respond as being halted. That never happened. I'm not very familiar with the arm7_9 code, but it looks like the write was a single register.
I would first check the board schematic and make sure all the JTAG lines are hooked up appropriately and have correct pull-up/downs where necessary. From there, you would need someone more familiar with the ARM7/9 JTAG commands to figure out what it is trying to do.
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development