Hello Gary, On 7/13/09, Gary Carlson <[email protected]> wrote: > > > > On 7/13/09 3:06 PM, "Alan Carvalho de Assis" <[email protected]> wrote: > >> Hi Gary, >> >> On 7/10/09, Gary Carlson <[email protected]> wrote: >>> >>> Try the V4 patch. >>> >> >> Same behavior: >> >> # openocd -f interface/jlink.cfg -f board/imx27ads.cfg >> Open On-Chip Debugger 0.2.0-in-development (2009-07-13-18:53) svn:2513 >> $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ >> For bug reports, read >> http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS >> dcc downloads are enabled >> Info : J-Link initialization started / target CPU reset initiated >> Info : J-Link ARM V6 compiled Jan 13 2009 15:40:53 >> Info : JLink caps 0x19ff7bbf >> Info : JLink hw version 60000 >> Info : JLink max mem block 8968 >> Info : Vref = 2.653 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 >> >> Info : J-Link JTAG Interface ready >> Error: jlink_usb_message failed with result=1) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Error: jlink_usb_message failed with result=1) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Error: jlink_usb_message failed with result=1) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Error: jlink_usb_message failed with result=1) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Error: jlink_usb_message failed with result=1) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> >> I am testing using i.MX27ADS Rev 3.0. >> >> I think this board never worked with JLink, but works fine with FTDI >> based JTAG interfaces. >> >> Regards, >> >> Alan > > OK that helps. Here are some additional questions: > > What is the host-operating system you are using (Windows, Mac OS X, Linux, > etc)? >
I am running Linux Ubuntu 9.04, gcc 4.3.3, etc :-) > Does this error show up 100% of the time at startup or is it intermittent? > It happen 100% of my attempts :-( > If you have another type of target, does it work with the same J-Link dongle > or does it do the same thing? > Using this same JLink interface on Olimex LPC-2378-STK: # openocd -f interface/jlink.cfg -f target/lpc2378.cfg Open On-Chip Debugger 0.2.0-in-development (2009-07-13-18:53) svn:2513 $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS jtag_nsrst_delay: 200 jtag_ntrst_delay: 200 500 kHz Info : J-Link initialization started / target CPU reset initiated Info : J-Link ARM V6 compiled Jan 13 2009 15:40:53 Info : JLink caps 0x19ff7bbf Info : JLink hw version 60000 Info : JLink max mem block 8968 Info : Vref = 3.261 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 Info : J-Link JTAG Interface ready Info : JTAG tap: lpc2378.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4) Info : JTAG Tap/device matched Warn : EmbeddedICE version 7 detected, EmbeddedICE handling might be broken Then I think this issue just happen when using OpenOCD + JLink + i.MX27ADS board. Is there someone else with jlink interface and i.MX27ADS board to test openocd? Best Regards, Alan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
