On Mon, Nov 3, 2008 at 1:00 PM, Peter Hettkamp
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Sun, Nov 02, 2008 at 08:04:21PM +0100, ?yvind Harboe wrote:
>> > I guess that a move to TLR must be handled not by jtag_add_pathmove but
>> > rather by jtag_add_tlr?
>>
>> That's correct.
> Ok, I've put together a preliminary patch that tries to keep TAP_TLR out of
> the calls to jtag_add_pathmove, calling jtag_add_tlr instead.

committed.

I've modified the patch to treat the current formatting with a bit more
respect :-)

> This gets rid of the annoying BUG messages with the accompanying shutdown of
> openocd. But it still does not allow me to use the xsvf player.
>
> As Øyvind pointed out, jtag_add_tlr does more than just moving the TAP
> statemachine to the TLR state, incidentally setting all devices to bypass.
>
> Now, I've identified two places where the the TLR state is used inside the
> xsvf player. One is in the XSTATE command. If and when XSTATE 00 is coded in
> the xsvf file, my patch issues jtag_add_tlr, even if it's in the middle of
> other XSTATE commands.
> The other place is within the xsvf_add_statemove. I need to investigate this
> further, but my target seems to have blown a gasket. This will have to be
> fixed first.

Keep up the good work! Looking forward to hearing more from you!



-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to