On Sat, 11 Jul 2009, Øyvind Harboe wrote:
On Sat, Jul 11, 2009 at 10:24 AM, Peter Denison<open...@marshadder.org> wrote:
On Sat, 11 Jul 2009, Øyvind Harboe wrote:
If I could return to the original point of this thread - getting the USBprog
adapter to work at all - in the light of the other comments, are you going
to let the one-line "make it work for now" fix in before 0.2?
The downside to slipping in this fix is that it will be harder
to retire the undocumented tms_sequence command
and who's going to put in the work to fix it on the C side now?
In return for putting the quick fix in, I will volunteer to step up to the
plate for that. It will take some time though, because it will need to be
coordinated with the USBprog firmware development.
Also, I find it strange, but I'm not going to dive into USBprog,
that it is possible to support pathmove, but not short
sequences...
Pathmove is done by sending the individual TMS and TCK line transitions.
"Normal" state transitions are done by the TMS_CHAIN command, which does
multiples of 7 bits.
Now I'm fairly sure that the only reason USBprog did sets of 7 bits is
because that was how OpenOCD originally did it internally, so the whole
thing is ripe for improvement (along with other things such as abstracting
runtest, and pushing that down as a single command, etc.). However, it
will need careful interface versioning, and agreement from both sides.
There is also plenty of scope for batching up commands as is done on other
adapters. I will start the process of planning this with USBprog
developers.
--
Peter
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
