Ok,
Here is the script I run on various builds (svn 1504 - 1900)

init
halt
reset init
memwrite burst enable
load_image   ./images/test.bin 0x80000000 bin
verify_image ./images/test.bin 0x80000000 bin
exit


Here are some results:
# svn 1600
#downloaded 88 byte in 0.008575s
#verified 88 bytes in 0.047004s

# svn 1700
#downloaded 88 byte in 0.031902s
#verified 88 bytes in 0.066361s

# svn 1800
#downloaded 88 byte in 0.014126s
#verified 88 bytes in 0.057677s

# svn 1815
#downloaded 88 byte in 0.013145s
#verified 88 bytes in 0.052042s

# svn 1816, 1817

#U    src/jtag/jtag.c
#U    src/svf/svf.c

# svn 1900, 1850, 1825, 1822
# failed


So r1817 passed but r1822 does not. r1817-r1821 do not compile.

There are a lot of changes to jtag.c file here between r1817 - r1822.
Anybody?

Also note degraded performance between r1504 and later revisions ( I run
each revision a couple of times to be sure that my PC was not causing
the delays).

--Michal




On Sat, 2009-09-12 at 13:14 +0200, Daniel Bäder wrote:
> Øyvind Harboe schrieb:
> >> So, every data word is written but at every other address.
> > 
> > Not so quick! :-)
> > 
> > Is 0 being written to every other address, or is every other address
> > being written to?
> > 
> > See this comment from the arm11 code:
> > 
> >  *  The repeated TAP_IDLE's do not cause a repeated execution
> >  *  if passed without leaving the state.
> 
> I reported this bug some time ago.
> 
> Please see thread "memwrite with burst enabled not working anymore" for 
> details.
> I had not time to analyse the problem further but the regression was 
> somwhere between SVN 1504 an SVN 2485.
> Since the arm11 code did not change significantly the problem seems to be in 
> the jtag/ft2232 code.
> _______________________________________________
> Openocd-development mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/openocd-development

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to