Hej Olof, olof.tang...@telia.com wrote: > Hi there. > I need some help to find the root cause of my problems with > OpenOCD/JTAG interface/processor. > > I have a brand new Olimex ARM-USM-TINY-H JTAG interface and a > Olimex LPC-H2148 prototype board.
I've been using an FT2232 JTAG interface with the LPC-H2148 for a while, and can confirm that it works fine. A small note is that if the firmware generates a CPU exception very early then OpenOCD won't manage to take control over the CPU, as the current git code stands. I've sent a patch for this but I have a slightly updated patch pending. > The board has been programmed using the built in boot loader and > works but I can't get OpenOCD up and running. FWIW I'm using OpenOCD git source circa commit f8cc725e0ea with libftdi-0.16 on Linux. This version of libftdi uses the libusb-0.1 API, which is provided on my system by libusb-1.0 together with libusb-compat-0.1 on my system. Your setup on Windows sounds pretty right, and I think it should work. You could of course try updating OpenOCD. You could also try libusb-compat-0.1 together with libusb-1.0, but I'm not sure if libusb-compat-0.1 can be built for Windows at the moment. We'll get to this at some point I'm sure. If you're able to help that's fantastic. > C:\Documents and Settings\olof>openocd -f interface/olimex-arm-usb-tiny-h.cfg > -f target/lpc2148.cfg I might suggest making your own openocd.cfg file in the project directory, which sources the interface and target cfg files. --8<-- source [find interface/usbprog.cfg] source [find target/lpc2148.cfg] arm7_9 dcc_downloads enable arm7_9 fast_memory_access enable -->8-- should work I think. Instead of [find ..] you could also provide the filename including an absolute path. //Peter _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
