Version differences?

Development Boards MicroMod
1

I have been using the 2006-10-12 version of openocd that was installed by yagarto as part of the full install. Everything worked great on the basic blink project and I was able to flash and debug. I started a new project based on FreeRTOS and flashed it (maybe) and ever since I have been unable to halt the running program or flash anything new.

As I am just learning my Olimex LPC2148 board and the tools I am sure I did something wrong. OpenOCD reports timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0 frequently and then dies.

I saw another topic that suggested a newer version of openocd so I downloaded and installed the 2007-04-16 version (r141-rc01). With that version it doesn’t recognize the jtag interface (ARM-OCD-TINY).

Both are using the same configuration file as provided with the sample blink project and I’ll include below.

Does anyone have an idea what I could have done to break the working interface? What is the difference in the two versions of openocd that would not recognize my jtag interface in the new version?

Many thanks!

dave

#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 1

#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst separate

#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 <type> <startup mode>
#target arm7tdmi <reset mode> <chainpos> <endianness> <variant>
target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
run_and_halt_time 0 30

#target_script 0 reset oocd_flash2138.script
working_area 0 0x40000000 0x40000 nobackup

#flash configuration
flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v2 0 14765 calc_checksum

# For more information about the configuration files, take a look at:
# http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger

[/code][/quote]

2

While waiting for someone to have an idea on this problem, I have uninstalled the Olimex install and started over with the yagarto stuff. Unfortunately I cannot get the older 3.1.6 OCD driver to install with the Olimex “Tiny” interface. The 3.1.7 version from the CD does install.

Still, after the clean install, I get the following results (debugging enabled)

C:>openocd-ftd2xx -f lpc2xxx_armusbocd_tiny.cfg -d 3
Info:    openocd.c:86 main(): Open On-Chip Debugger (2007-04-16 19:30 CEST)
Debug:   jtag.c:1335 jtag_init(): -
Debug:   ft2232.c:1242 ft2232_init_ftd2xx(): 'ft2232' interface using FTD2XX wit
h 'olimex-jtag' layout (15ba:0004)
Debug:   ft2232.c:1331 ft2232_init_ftd2xx(): current latency timer: 2
Debug:   ft2232.c:1678 olimex_jtag_init(): 80 08 1b
Debug:   ft2232.c:1721 olimex_jtag_init(): 82 09 0f
Debug:   ft2232.c:249 ft2232_speed(): 86 01 00
Debug:   jtag.c:278 jtag_call_event_callbacks(): jtag event: TRST asserted
Debug:   jtag.c:1126 jtag_reset_callback(): -
Debug:   jtag.c:278 jtag_call_event_callbacks(): jtag event: TRST asserted
Debug:   jtag.c:1126 jtag_reset_callback(): -
Error:   jtag.c:1182 jtag_examine_chain(): JTAG communication failure, check con
nection, JTAG interface, target power etc.

Is the newer driver not supported with 2007-04-16 openocd? Or is there a way to get the older driver installed. Windows just says it can’t find what it needs to install in the directory provided.

Thoughts? I sure could use some help getting my environment back running.

Thanks!!!

dave[/code]