Thanks for your concern. I have wanted a long time now to verify that my target is Ok. That is is why I made some new efforts with my wiggler clone. In a post some days ago I described that this test gave the same disappointing result, reading nothing but zeros.
I had hoped to borrow a BDI2000 from my job over the weekend but as usual it's occupied in a project for some time and I don't know when I can get access to it. I don't want to disturb my colleagues work. I also have two AVR CAN128 boards with JTAG which might be used to verify that the two interfaces can at least scan the JTAG chain but the connector layout is different and is take some time to get those boards powered properly. Nor am I sure that the JTAG interface is internally enabled on the processors. So there are some problems ahead with that test too. I also started to doubt that openocd actually could work with the LPC2148 since Macraigor OCDCommander seems to be working at least with the wiggler clone. And it is strange that proprietary drivers seems to be the involved your setup. I might give a shot with the AVR boards anyway. Any tips on how to run openocd properly without any particular target processor and just scan the JTAG chain is welcome. On Fri, 2010-08-13 at 20:54 +0800, Xiaofan Chen wrote: > On Wed, Aug 4, 2010 at 10:23 PM, Olof Tångrot <olof.tang...@telia.com> wrote: > > I get the same semi functional result as on Fedora 12 (same hardware) > > before as shown below. I also observed that not using the '-c "jtag_khz > > 1000"' locks the (FT2232H ?) hardware somehow. After that my JTAG > > interface won't respond the correct command line until it has been > > disconnected and reinsterted. This happens both with Linux and > > WindowsXP. > > > > The following may not help you, but just give you some hints. > > I just got an Amontec Amontec JTAGkey2 (FT2232H based) > and tried it with the Olimex LPC-P2148 board I have. It seems > to work fine. > > The LPC-P2148 board should be similar to what you have > (LPC-H2148), just with more stuffs. So maybe it is something > strange with Olimex ARM-USM-TINY-H JTAG. > > I am using the original OpenOCD binaries from Freddie Chopin > under 32bit Vista. The driver is the original Amontec driver > (WHQL, based on FTDI's 2.06.00 version) and libusb-win32 > filter driver 1.2.1.0. The two config files are also unmodified. > > C:\Program Files\OpenOCD\0.4.0\bin>openocd -f interface/jtagkey2.cfg > -f board/olimex_lpc_h2148.cfg > Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > RCLK - adaptive > jtag_nsrst_delay: 200 > jtag_ntrst_delay: 200 > trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain > Info : max TCK change to: 30000 kHz > Info : RCLK (adaptive clock speed) > Info : JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: > 0xf > 1f0, ver: 0x4) > Info : Embedded ICE version 4 > Info : lpc2148.cpu: hardware has 2 breakpoint/watchpoint units > > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development