On Wed, Jul 8, 2009 at 2:11 PM, Gary Carlson<gcarl...@carlson-minot.com> wrote:
> You asked me what the result of Spencer's patch was under Mac OS X.  I
> tested it against my system this evening and as you will see below, it
> caused a number of startup faults.  It also appears to make the j-link
> dongle completely unresponsive thereafter.
>
> I guess the bigger question is this.  Did the Windows version ever suffer
> from the intermittent startup problem or was this exclusively a problem with
> Linux/Mac systems?

I have not tried J-Link under Windows recently. At home, I run Linux
more often than Windows. But I tried to remove your line of usb_reset()
patch and the startup error comes back from time to time.
It is not a fatal error but certainly not that nice.

So indeed your patch is necessary. But maybe there is a better way
to do it without affecting the usb_handle. I will try out some other
ideas.

mc...@ubuntu904:~/Desktop/build/openocd/jlinkv3$ openocd -f lpc-p2148.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-07-08-22:36) svn:2498M
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
RCLK - adaptive
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
Info : J-Link initialization started / target CPU reset initiated
Error: J-Link command EMU_CMD_VERSION impossible return length 0x2d4a
Error: J-Link command EMU_CMD_VERSION failed (-110)

Info : J-Link JTAG Interface ready
Info : JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787,
part: 0xf1f0, ver: 0x4)
Info : JTAG Tap/device matched


> If Windows doesn't need the usb_reset and doesn't suffer from the
> intermittent issue, doesn't it make more sense to put a conditional around
> it that excludes that step for windows rather then forcing the device search
> again?

Maybe Spen can answer this.


-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to