michal smulski wrote: > Here is a patch against r2715 that makes the arm11 memwrite burst work > again with Olimex JTAG. > > As far I can see in the code, the original ft2232_add_pathmove() > function was split into two ft2232_add_pathmove & clock_tms(). I think > that clock_tms() is working ok as it is used elsewhere. So the bug must > be in the ft2232_add_pathmove(). > > Perhaps it is worth committing this and having people comment if it > breaks or fixes some of their problems. > > Ideally, the person that wrote the r1825 patch should comment on this or > help fix. > > > On Wed, 2009-09-16 at 09:18 +0200, Øyvind Harboe wrote: > >> Create a patch that reverts the change to ft2232_add_pathmove()? >> >> As a first step you should make as *few* changes as possible, including >> not messing with formatting. >> >> >From there the community could submit incremental patches that tinker >> with formatting, precise implementation, etc. >> >> That's my thinking anyway.... >> >> >> As far as I know there are two parts of OpenOCD that makes significant use of path_move's and that is ARM11 and the XSVF/SVF player code. So I think changes/patches should be tested against them.
Are there any core developers left here that know these things ?? Best regards, Magnus _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
