On Fri, 10 Jul 2009, Øyvind Harboe wrote:
It's trivial in the sense that there's absolutely no way the adapter can
work with the short transition table,
Could you elaborate on this for those that read up on this thread later on?
The USBprog adapter expects 7-bit sequences to be sent as part of its
TMS_CHAIN command. More than one JTAG state transition from the table can
be sent in a single USB command, but the adapter then treats each byte as
a 7-bit TMS sequence to follow. Thus sending the shorter sequences from
the short table results in the wrong transitions (e.g. IDLE -> DRSHIFT =
B8(001, 3) is interpreted as 0000001, and 4 incorrect shifts of data out
of DR are done and lost).
By sticking to the old table (for this adapter only) with 7-bit
transitions everywhere, this adapter that requires 7-bit transitions works.
and some degree of getting it working with the original long one.
I've added an item in TODO for this problem w/link to this
thread.
The patch will not be applied before 0.2 as there is a workaround.
What workaround? Expecting anyone that uses it to work out that they
need an extra line in their config file? At least we should make this
adapter default to the correct table, so that no-one is caught out.
I believe the fix for USBprog belongs inside the C code rather than
in the config script.
I agree, but I'd rather see 0.2.0 go out more likely to work out of the
box than not... The C fixes are longer, more involved and you are right
that they are inappropriate to happen before the release.
It's a US Robotics USR8200 router, with an IXP422 processor. I can
successfully bring it up into 'reset halt', and then can single step. I
haven't tested the flash reading and writing yet, but will soon.
I have USBprog and (temporarily) J-Link V6 adapters to compare.
I don't know if J-Link will work for 0.2. If nothing drastic happens
in the 24 hours, it won't make it.
My J-Link V6 is working under debian squeeze as of SVN r2503, with my
target. I appreciate that some of the other stuff recently discussed about
the J-Link may not make it, but at least we can say "works under some
circumstances, on some platforms".
--
Peter
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
