Hi Spencer, I will do some more digging. It sounds like you have a Windows test platform. Was the intermittent startup issue ever a problem on this operating system?
Based on Xiaofan's recent digging it sounds like the usb_reset solution is a temporary fix that is going to cause future problems for upcoming kernels. That is too bad, because I have used that on other tools to fix bad USB behavior. To me this says that libusb is broken. Something is not always being initialized properly by usb_open when it is first called. The other question that might shed some light that I am hoping someone else on the list can answer is whether the intermittent startup issue plagues other non-jlink USB dongles. Gary Gary Carlson Gary Carlson, MSEE Principal Engineer Carlson-Minot Inc. On 7/8/09 8:18 AM, "Spencer Oliver" <s...@spen-soft.co.uk> 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? >> >> 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? >> >> >> Info : J-Link initialization started / target CPU reset initiated >> Error: J-Link command 0xde failed (-13) >> Error: J-Link command 0xdc failed (-13) >> Error: J-Link command 0x01 failed (-13) >> Error: J-Link command EMU_CMD_VERSION failed (-13) >> >> Info : J-Link JTAG Interface ready >> Error: J-Link command 0xdd failed (-13) >> Error: J-Link command 0xdf failed (-13) >> Error: J-Link setting speed failed (-13) >> Error: usb_bulk_write failed (requested=6, result=-13) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Error: usb_bulk_write failed (requested=6, result=-13) >> Error: jlink_tap_execute, wrong result -107 (expected 1) . >> . >> . >> > > Strange, i fail to see why my patch would cause this. > I have only tested the patch on linux and win32 and it works fine on these. > > All the patch does is re-enumerate after the usb_reset. > Could you step through and see that a valid handle is returned? > > Cheers > Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
