[Openocd-development] Fwd: Re: Still J-Link problems

2011-11-04 Thread Vaclav Peroutka
Hello, in the meantime, I connected "broken" JLink to the good one to read the firmware. But I could not init the target. I got following: D:\projects\arm-CortexM3>openocd -f sam7x256.cfg Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://

Re: [Openocd-development] Still J-Link problems

2011-11-03 Thread Vaclav Peroutka
> 4.35h is a beta version, probably you can try the new release version > which is 4.36g. > http://www.segger.com/jlink-software.html > > Or you can try to the old version to get OpenOCD to work again. > http://www.segger.com/j-link-older-versions.html In the meantime I tried versions 4.34, 4.14

[Openocd-development] Still J-Link problems

2011-11-03 Thread Vaclav Peroutka
Hello all, I noticed that people use new firmware because of problems. I got FW 4.35h and tried to update it. With really bad results. Before, OpenOCD wrote: Info : J-Link initialization started / target CPU reset initiated Info : J-Link ARM V8 compiled Dec 1 2009 11:42:48 Info : JLink caps 0xb

Re: [Openocd-development] SVF player - fail to run command

2010-02-16 Thread Vaclav Peroutka
MASK > > (0FFF) > > > > > > But one command after that will fail, not fail to do JTAG, but fail to > > > receive the right TDO value from the target. > > > To check the reason why it fails, you will have to log the waveform on > > the > > > JTAG

Re: [Openocd-development] SVF player - fail to run command

2010-02-15 Thread Vaclav Peroutka
ls, you will have to log the waveform on the > JTAG pins. > > BTW: You can try a slower speed first. > 2010/2/15 Vaclav Peroutka > > > Hello Simon, > > > > attached is log1.log and the SVF file itself. > >