I moved my development to a new PC and now I cannot get OpenOCD to work properly. When I run the config file on either a LPC2124 Olimex eval board or my own LPC2138 I get this result. (I also tried the latest OpenOCD version and get the same result. I down graded to see if there was any difference.)
Open On-Chip Debugger (2008-05-16 20:15) svn: 657
URL: http://svn.berlios.de/svnroot/repos/openocd/trunk
Info: options.c:50 configuration_output_handler(): jtag_speed: 3, 3
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger (2008-05-16 20:15) svn: 657
Info: jtag.c:1376 jtag_examine_chain(): JTAG device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
Info: jtag.c:1376 jtag_examine_chain(): JTAG device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
User: target.c:435 target_process_reset(): Timed out waiting for halt after reset
I can connect via telnet and issue commands but CPU ignores them. The poll command reports that the CPU is running, and the reset and halt commands simply time out.
My config file is very basic and worked before the computer upgrade.
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc “Olimex OpenOCD JTAG TINY A”
ft2232_layout “olimex-jtag”
ft2232_vid_pid 0x15BA 0x0004
jtag_speed 3
#delays on reset lines
jtag_nsrst_delay 200
jtag_ntrst_delay 200
#use combined on interfaces or targets that can’t set TRST/SRST separately
reset_config trst_and_srst srst_pulls_trst
#LPCs need reset pulled while RTCK is low. 0 to activate JTAG, power-on reset is not enough
jtag_reset 1 1
jtag_reset 0 0
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target
#target arm7tdmi
target arm7tdmi little run_and_init 0 arm7tdmi-s_r4
run_and_halt_time 0 30
working_area 0 0x40000000 0x4000 nobackup
#flash bank lpc2000 0 0 <target#>
flash bank lpc2000 0x0 0x7d000 0 0 0 lpc2000_v2 14765
For more information about the configuration files, take a
look at the “Open On-Chip Debugger (openocd)” documentation.
Any Suggestions?