Hi Xiaofan, The second part of the patch is most certainly critical to Linux and Mac OS X systems. I am less sure about Windows since I don't have anything to test. If the usb_reset instruction is removed, you will find that the intermittent start-up failures that went away with the patch will be back.
Other then the "reset halt" command being broken, my V8 debugger works well and I have experienced no startup failures since. As for the "reset halt" problem I am trying to find out what is causing that. Gary Gary Carlson Gary Carlson, MSEE Principal Engineer Carlson-Minot Inc. On 7/7/09 7:46 PM, "Xiaofan Chen" <xiaof...@gmail.com> wrote: > On Wed, Jul 8, 2009 at 12:06 AM, Gary Carlson<gcarl...@carlson-minot.com> > wrote: >> I actually do development on Mac OS X rather then windows. The particular >> problem I am seeing after generating a "reset" is: >> >> jlink_usb_message failed with result=1) >> jlink_tap_execute, wrong result -107 (expected 1) >> JTAG tap: at91sam9260.cpu tap/device found: 0x0792603f (mfg: 0x01f, part: >> 0x7926, ver: 0x0) >> JTAG Tap/device matched >> jlink_usb_message failed with result=1) >> jlink_tap_execute, wrong result -107 (expected 1) >> BUG: unknown debug reason: 0x0 >> >> I have a V8 J-link dongle, so I will take a look at some of the proposed >> patches and start troubleshooting this morning. > > Just to be clear, did your J-Link V8 work under Mac OS X with your patch? > It seems to work under Linux but breaks Windows. > > If you remove the 2nd part of your patch (usb_reset), what happens? _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
