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. Also as a reference point for everyone, the at91sam9G20 I am using is based on an arm926ejs core. Gary Gary Carlson Gary Carlson, MSEE Principal Engineer Carlson-Minot Inc. On 7/7/09 4:59 AM, "Spencer Oliver" <[email protected]> wrote: >>>>> For info this breaks my v5 and v6 jlinks (tested stm32). >>>>> Not sure if any one else is having trouble? >>>> >>>> How does it break? >>>> >>> >>> All read/writes fail as the usb handle is invalid after the >> usb_reset >>> is performed. >>> Perhaps the win32 libusb does a reset whereas the linux one >> does not? >>> >> >> Are you saying you have problems under Windows but not Linux? >> > > yes, linux works win32 is broken. > The attached patch fixes the problem, but i do not like waiting for the > re-enumeration under win32 - > linux does not suffer the same fate. > > do we know whether the v8 has the same behaviour under win32? > if not then making this conditional would be better. > > Cheers > Spen _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
