On Dec 10, 2008, at 4:41 AM, Øyvind Harboe wrote:
Hm.... I think perhaps the "jtag -expected-id" needs rethinking. The ID check should be in the target configuration script and not in C.
The actual check is fine being in C. There is no need to force the retrieval of the ID and comparison into a script.
The target script can accept multiple target id's and also output sensible target specific error messages or do whatever else is approperiate.
We could just as easily allow multiple -expected-id options and compare against the list. Target specific error messages don't necessarily seem appropriate, but could be implemented as a jtag tcl event when a jtag tap does not match any expected ids.
at91rm9200.cfg seems to be another case of where the standard expected-id breaks down.
Can you provide more details on how it fails to work in that case?
Thoughts? How about adding a jtag tcl event to handle a discovered id?
I see no harm in having such an event. We should also have a corresponding "id did not match any expected values" event. They can be used for target-specific error messages or for special circumstances (e.g. if id is X, we need to do Y for it to function).
-expected-id could create such a tcl event... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
-- 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
