I can confirm the problem. I have tried versions V4.44d, V4.46e, V4.46f (latest stable). All of them have identical firmware: Firmware: J-Link ARM V8 compiled May 3 2012 18:36:22
The latest working version I have found is: Firmware: J-Link ARM V8 compiled Feb 8 2012 14:30:39 Unfortunately, I could not figure out which release contains this firmware, looks like V4.42. Regards, Alex. 2012/5/22 Liviu Ionescu <[email protected]>: > > On May 22, 2012, at 04:11 , Xiaofan Chen wrote: > >> Hmm, I believe the issue has been solved by updating to the latest >> Segger firmware. What is the version you are updating to? > > the latest, May 3, 2012, packed within Setup_JLinkARM_V446f.zip > > Info : J-Link initialization started / target CPU reset initiated > Info : J-Link ARM V8 compiled May 3 2012 18:36:22 > Info : J-Link caps 0xb9ff7bbf > Info : J-Link hw version 80000 > Info : J-Link hw type J-Link > Info : J-Link max mem block 9336 > Info : J-Link configuration > Info : USB-Address: 0x0 > Info : Kickstart power on JTAG-pin 19: 0xffffffff > Info : Vref = 3.274 TCK = 1 TDI = 1 TDO = 1 TMS = 1 SRST = 0 TRST = 1 > Info : J-Link JTAG Interface ready > Info : clock speed 1000 kHz > Error: JTAG scan chain interrogation failed: all ones > Error: Check JTAG interface, timings, target power, etc. > Error: Trying to use configured scan chain anyway... > Error: stm32.cpu: IR capture error; saw 0x0f not 0x01 > Warn : Bypassing JTAG setup events due to errors > Warn : Invalid ACK 0x7 in JTAG-DP transaction > Polling target failed, GDB will be halted. Polling again in 100ms > Polling target failed, GDB will be halted. Polling again in 300ms > > there is also a V446g beta, but I did not try it. > > anyway, I don't think we should expect Segger to update their firmware to > work with OpenOCD, we should update OpenOCD to make it work with all Segger > firware versions. > > I'd be happy if Segger would just disclose the changes in the USB protocol, > so we don't have to reverse engineer it. > > do we have any contacts at Segger? > > I would first write to Segger and try to get an official statement from them. > >> Last time Segger did spend time to fix the issue and when I tried it, >> 4.33h beta firmware solved the problem > > there are no 4.33[a-z] at all on the Segger site > (http://www.segger.com/j-link-older-versions.html), from 4.32b they jump to > 4.34. > > I currently have two J-Link V8 probes, one running the latest v6.46f and the > other running the old 4.14g, so it is relatively simple to run comparison > tests. > > any other comments on how to proceed? > > regards, > > Liviu > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > OpenOCD-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openocd-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
