> Step 3 > > We create a new "event" - that does -invokes a TCL script. > > That TCL script does the following: > > (a) wiggle pins and configure the JRC tap. > (b) executes the "jtag order" command.
Could you clarify this a bit more? I'm wondering if we should reduce the # of events and encourage target scripts to implement the process reset proc... That was the original idea with the reset proc being in tcl... > You delete the index variable from the target and device structure, along > with the 'next' element, turn on every warning about "unknown and unused > variable" you can find.... We'd have to do the same thing for fn's that get a target given an 'num'... It does seem like we're homing in on a plan here... It's flexible, should work with Beagleboard(right?) and not too complicated. W.r.t. it not working correctly we're not really vulnerable to regressions, but rather that the new stuff won't work(i.e. that 'num' is not treated properly as an id)... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer Free eCos workshop in Oslo October 21! http://www.zylin.com/workshop.html _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
