Committed.
Thanks!
Hopefully the test results over the next days & weeks will be positive.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.
> 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 ??
the xsvf & svf code is
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
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
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 thin
On Tue, Sep 15, 2009 at 6:46 PM, michal smulski wrote:
>
> 'tms_sequence long' is not a valid command on r1824 or r1825. On r2709
> produces error during burst write.
>
> Is there anything else I can try?
break apart 1824-1825 into a series of patches.
--
Øyvind Harboe
Embedded software and har
'tms_sequence long' is not a valid command on r1824 or r1825. On r2709
produces error during burst write.
Is there anything else I can try?
--Michal
On Tue, 2009-09-15 at 09:55 +0200, Magnus Lundin wrote:
> Øyvind Harboe wrote:
> > On Tue, Sep 15, 2009 at 6:18 AM, michal smulski
> > wrote:
> >
Øyvind Harboe wrote:
> On Tue, Sep 15, 2009 at 6:18 AM, michal smulski
> wrote:
>
>> I noticed that something was not right with my svn repo after doing
>> various up-rev's and down-rev's and decided to start fresh.
>>
>> It turns out that last 'memwrite burst' working is actually rev 1824 an
