On Apr 12, 2009, at 1:20 PM, Øyvind Harboe wrote:

On Sun, Apr 12, 2009 at 9:43 PM, Rick Altherr <kc8...@kc8apf.net> wrote:

On Apr 11, 2009, at 11:48 PM, Øyvind Harboe wrote:

- Changing JTAG state transitions to use shortest path rather than 7
clocks
- Fixing all the drivers that assumed 7 clocks per transition

Why would you want to change this? We've got pathmove for those cases
where the path matters...?


Performance is certainly one reason. Getting correct behavior without using pathmove is another. The target that started all this doesn't _work_ unless you use the shortest path between states. pathmove is fine for special circumstances, but when a variant of a target needs the shortest path, either the target gets changed to use pathmove for everything or you just
make normal state movement work better.


Good enough for me.

So ultimately a new table will
be formulated for the TMS values and possibly a table with
# TMS values to clock out?

--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html


In fact, this has already been done for the most part. The problem has been that many of the interface drivers assume 7 clocks per move. Duane has been working on fixing that.

--
Rick Altherr
kc8...@kc8apf.net

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to