On Dec 10, 2008, at 12:31 PM, Øyvind Harboe wrote:
would create a tap with 3 events available: matched-id-$_CPUTAPID, matched-id-$_OTHERCPUTAPID, and nomatch.This is precisely the control-inversion problem: lots of events and yet never enough flexiblity.My current thinking is now that we should allow the entire jtag valdiation to be written in tcl by the target configuration if something funky is needed.
So if a target configuration needs to do something completely strange, they can write a new "jtag_validate" TCL method and take over the entire validation procedure. That's fine, but it doesn't remove the use cases for having -expected-id and match events. They still provide control-inversion for the 99% case. Every example I've seen can be handled via -expected-id with 0 or 1 events based on the matched ID.
Normal case should be no more complicated than today.
That's because they shouldn't change. If the new "jtag_validate" TCL method isn't overridden, it should use -expected-id just like today. If you want to reimplement that in TCL, feel free, but I suspect it will be _much_ harder since -expected-id is fed into the C side of things. I'd suggest having the default jtag_validate call into the C jtag_validate which uses the -expected-id list and calls the correct events.
-- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
