Come to think of it...
This is precisely what we addressed with target configuration scripts being able to implement the entire reset procedure. Similarly the target configuration script should be able to implement the entire JTAG validation procedure, not just a small part of it. In theory a target configuration script could be written to handle N completely different CPU's depending on what was detected. So from this point of view the JTAG examiniation sub events become much less important. Events is a inversion-control based approach, whereas the target script implementing the entire validation procedure is the other way around: the target config script stays completely in control. So: I'm according to this, I'm thinking that there should be a default tcl JTAG validation procedure(i.e. port todays procedure to tcl). -- Ø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
