Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-25 Thread Xiaofan Chen
On Fri, Aug 19, 2011 at 9:03 PM, Antonio Borneo
borneo.anto...@gmail.com wrote:
 On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
 [...]
 Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
 fixed the issue with OpenOCD for V8 version of J-Link. Thanks for the
 help again.

 Very good news!

 Since the issue seams identified, can Segger suggest how to fix
 OpenOCD to support the versions after V4.14g and before V4.33h ?

That would be nice.

 Otherwise I propose to let OpenOCD detect the incompatible versions
 and quit after an error message.

Maybe this is the way to go for now.

 I think that the only way to check firmware version is through the
 date in the string
   Info : J-Link ARM V8 compiled Aug 18 2011 19:52:49
 correct?

Seems to be the case.

Eg: From J-Link Commander under Windows.

J-Linkf
Firmware: J-Link ARM Lite V8 compiled Jan 31 2011 18:38:46
Hardware: V8.00



-- 
Xiaofan
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-25 Thread Jean-Christophe PLAGNIOL-VILLARD
On 16:52 Thu 25 Aug , Xiaofan Chen wrote:
 On Fri, Aug 19, 2011 at 9:03 PM, Antonio Borneo
 borneo.anto...@gmail.com wrote:
  On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
  [...]
  Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
  fixed the issue with OpenOCD for V8 version of J-Link. Thanks for the
  help again.
 
  Very good news!
 
  Since the issue seams identified, can Segger suggest how to fix
  OpenOCD to support the versions after V4.14g and before V4.33h ?
 
 That would be nice.
can we have a sumurize e-mail of which version work on which hardware

after I'll do the update in the c code

Best Regards,
J.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-19 Thread Xiaofan Chen
On Fri, Aug 19, 2011 at 2:29 PM, SEGGER - Support J-Link (AG)
support_jl...@segger.com wrote:

 On Fri, Aug 19, 2011 at 3:17 AM, SEGGER - Support J-Link (AG)
 support_jl...@segger.com  wrote:

 Hi Eric,

 We have built a new beta version (V4.33h) which comes with a new firmware
 for J-Link in which the problem regarding OpenOCD has been fixed.

 Could you please give the new version a try and provide some feedback?

 Download-Link: http://www.segger.com/download_jlink_beta.html


 For now we only updated the firmware of the standard J-Link products (V8,
 Pro, Ultra, ...) which are directly sold to the customer.
 Firmware fixes for J-Link OB and Lite will follow shortly.


Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
fixed the issue with OpenOCD for V8 version of J-Link. Thanks for the
help again.

D:\work\openocd\openocd_0.5.0_mingw\binopenocd_d2xx.exe -f
ek-lm3s1968_jlink.cfg
Open On-Chip Debugger 0.5.0 (2011-08-12-12:04)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Warn : Adapter driver 'jlink' did not declare which transports it
allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
500 kHz
Info : J-Link initialization started / target CPU reset initiated
Info : J-Link ARM V8 compiled Aug 18 2011 19:52:49
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 8
Info : J-Link hw type J-Link
Info : J-Link max mem block 9424
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0xff01
Info : Vref = 3.222 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0
Info : J-Link JTAG Interface ready
Info : clock speed 500 kHz
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints



-- 
Xiaofan
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-19 Thread Antonio Borneo
On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
 [...]
 Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
 fixed the issue with OpenOCD for V8 version of J-Link. Thanks for the
 help again.

Very good news!

Since the issue seams identified, can Segger suggest how to fix
OpenOCD to support the versions after V4.14g and before V4.33h ?

Otherwise I propose to let OpenOCD detect the incompatible versions
and quit after an error message.
I think that the only way to check firmware version is through the
date in the string
   Info : J-Link ARM V8 compiled Aug 18 2011 19:52:49
correct?

Best Regards,
Antonio Borneo
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-19 Thread Eric Wetzel
On Fri, Aug 19, 2011 at 9:03 AM, Antonio Borneo
borneo.anto...@gmail.com wrote:
 On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
 [...]
 Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
 fixed the issue with OpenOCD for V8 version of J-Link. Thanks for the
 help again.

 Very good news!

 Since the issue seams identified, can Segger suggest how to fix
 OpenOCD to support the versions after V4.14g and before V4.33h ?

 Otherwise I propose to let OpenOCD detect the incompatible versions
 and quit after an error message.
 I think that the only way to check firmware version is through the
 date in the string
   Info : J-Link ARM V8 compiled Aug 18 2011 19:52:49
 correct?

I have also confirmed that the new firmware fixes the problems we've
been having with the J-Link V8 hardware.

And while I am addicted to firmware updates, and I shall always avoid
using an older firmware revision (unless there is some sort of
functional defect), I too would like to know what was causing the
problem, and what we can do to support those older products. This
might just be a cover for my curiosity about EMU_CMD_REGISTER and the
other undocumented commands.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Fwd: Re: JLink woes

2011-08-18 Thread Xiaofan Chen
On Fri, Aug 19, 2011 at 3:17 AM, SEGGER - Support J-Link (AG)
support_jl...@segger.com wrote:

 Hi Eric,

 We have built a new beta version (V4.33h) which comes with a new firmware for 
 J-Link
 in which the problem regarding OpenOCD has been fixed.

 Could you please give the new version a try and provide some feedback?

 Download-Link: http://www.segger.com/download_jlink_beta.html


 Best regards

   Alexander Grüner - J-Link Development / Support


I will try with a real V8. But for a V8 Lite, the new version does not
contain the new
firmware and thus OpenOCD will still fail.




--
Xiaofan
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development