On Wed, Jul 6, 2011 at 8:51 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Thu, Jul 7, 2011 at 1:27 AM, Jean-Christophe PLAGNIOL-VILLARD > <plagn...@jcrosoft.com> wrote: >> On 23:05 Wed 06 Jul , Xiaofan Chen wrote: >>> Try to update the libusb-win32 version to see if that helps. >>> >>> On the other hand, this may have something to do with either >>> your J-Link version or your target. >>> >>> I just tried J-Link V7 and LPC-2148 target under Windows 7 32bit >>> and it is okay. I am using libusb-win32 1.2.4.7 snapshot >>> edition and Freddie's latest development version binary. >>> So it is not the latest git version but you can try it. >>> >>> I also tried the same binary under Windows 7 64bit a few >>> days ago without an issue. >> Check the firmware version >> maybe too recent > > Indeed. I do not have a V8 for testing right now. I will try > to borrow one. We have many J-Links at work, some of > them V6, some of them V8, and there is a J-Link Pro. > > Info : J-Link initialization started / target CPU reset initiated > Info : J-Link ARM V8 compiled Apr 27 2011 20:42:35 > Info : J-Link caps 0xb9ff7bbf > Info : J-Link hw version 80000 > Info : J-Link hw type J-Link > Info : J-Link max mem block 8384 > > -- > Xiaofan
Alright, I uninstalled libusb-win32 0.1 and installed 1.2.4.0, and installed filters for the J-Link device. Still the same result. I tried Freddie's binary. Still the same result. It is beginning to look like a firmware version problem. I guess I'm disappointed, but not actually surprised, that it's not compliant with Segger's J-Link documentation: http://www.segger.com/cms/admin/uploads/productDocs/RM08001_JLinkUSBProtocol.pdf Thanks, ~Eric _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
