Gary, I just tested this patch here. I like how it looks, and it "works for me" in my tests. You seem to have done your research, in so far as you conveyed a number of key technical details to the list in your message and patch. Moreover, your changes and their reasoning make sense to me.
If others report lack of regressions and improvements, then I am inclined to take the patch for 0.2.0. Cheers, Zach On Sun, 2009-07-05 at 13:56 -0700, Gary Carlson wrote: > Hi Xiaofan, > > I have a second-generation patch that I would like you to try. Using it I > have started my emulator over a thousand times now without a single > communication failure. Using subversion 2348 as a baseline, I went from a > 43% emulator startup failure rate to zero. > > It was very fortunate that you happened to mention earlier that you observed > the host build modulates the problem. That critical insight clued me into a > strikingly similar USB problem I ran into a couple years earlier on another > project. > > So try this patch and let me know what happens. With a little luck I am > hoping that it will permanently banish the intermittent j-link usb failures > for good. > > Only time will tell, however! :) > > Gary > > > On 7/5/09 7:41 AM, "Xiaofan Chen" <[email protected]> wrote: > > > On Sun, Jul 5, 2009 at 9:53 PM, Xiaofan Chen<[email protected]> wrote: > >> On Sun, Jul 5, 2009 at 10:29 AM, Xiaofan Chen<[email protected]> wrote: > >>> It does not help me for the V3 and V7 I tried. Strangely the Linux distros > >>> play a part as well. It seems to be more stable under Ubuntu 9.04 than > >>> Arch Linux. > >>> > >> > >> For example, I've no problems with the STM3210E-Eavl board under > >> Ubuntu 9.04. But it does not seem to work under Arch Linux (with > >> J-Link V3 and V7). > > > > Under Arch Linux and OpenSuse 11.1, J-Link does not seem to work now > > with SVN2462. > > > > Under Ubuntu 9.04 and Fedora 10, J-Link works most of the time. > > > > [mc...@ubuntu904 jlinkv7]$ openocd -f stm3210e.cfg > > Open On-Chip Debugger 0.2.0-in-development (2009-07-05-22:29) svn:2462 > > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ > > For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS > > 1000 kHz > > jtag_nsrst_delay: 100 > > jtag_ntrst_delay: 100 > > Info : J-Link ARM V7 compiled May 27 2009 17:29:25 > > Info : JLink caps 0xb9ff7bbf > > Info : JLink hw version 70000 > > Info : JLink max mem block 9120 > > Info : Vref = 3.261 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 1 TRST = 1 > > > > Info : J-Link JTAG Interface ready > > Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, > > part: 0xba00, ver: 0x3) > > Info : JTAG Tap/device matched > > Info : JTAG tap: stm32.bs tap/device found: 0x06414041 (mfg: 0x020, > > part: 0x6414, ver: 0x0) > > Info : JTAG Tap/device matched > > > > But sometimes it does not work, unplug and plug in J-Link seems to fix > > the problem. > > > > > > > > Gary Carlson > > Gary Carlson, MSEE > Principal Engineer > Carlson-Minot Inc. > > > > > > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
