Zach Welch wrote: > On Tue, 2009-05-12 at 17:59 -0400, Gene Smith wrote: >> Someone loaned me an IAR evaluation board STR712 (made by Olimex) and a >> yellow IAR J-link (marked J-LINK-ARM-KS on bottom). I had seen quite a >> bit of mention on this list about jlink and thought I would give it a >> try. I was at r1567 on my initial try (after rebuilding with >> --enable-jlink configured). >> >> I am starting openocd like this: >> sudo ./openocd -f target/interface/jlink -f target/target/str710.cfg >> >> str710.cfg seems as close to the actual str712 as there is in the cfg files. >> >> When it starts I see: >> Error: J-Link Command 0x01 failed (-2) >> Error: J-Link command EMU_CMD_VERSION failed (-110) >> <repeated 3 times> > > The ENOENT error (translated via errno.h) seems to indicate that the > device is not connected. I remember having similar problems, but I do > not immediately recall what the problem was. It may have been an > improper connections (e.g. a pair of reversed pins) between the J-Link > header and my target device, or it might have been a configuration issue > with my host system. I do not believe it was directly OpenOCD's fault, > but I do wish it could more informative here. > > Cheers, > > Zach
Well, I now see that I get the same result with the target board powered off or with the 20-pin jtag ribbon cable disconnected! So definitely a lack of communication. I was told that the target power supply in the jlink got blown and I am powering the str712 board with an external supply. I wonder if that supply in jlink also does something important in the jlink, jtag wise. I was told that it still worked with the IAR/STMicro Kickstart windows software. Don't think cables or pins are backwards (just jtag and usb). Leds come on on the board. ??? If you think of anything let me know. Thanks. -gene _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
