Øyvind Harboe wrote: > - RESET is an illegal end state. It's split out as a separate thing for lots > of > reasons, including that this triggers events that listeners are listening > for, etc. > > - irscan should use the drscan code implementation. They are almost identical. > > - DRPAUSE makes no sense for IRSCAN as an endstate according to your > new and improved rules... Ditto for DRSCAN > > > If I were a user who wanted to work/play with direct jtag commands from the command line or in a script, I would REALLY hate it if I were told that the official stable states of the JTAG state machine were not available as end states for the scan commands. I could point to the STAPL documentation "The DRSTOP statement specifies the IEEE 1149.1 end state for data register scan operations. This end state must be one of the IEEE 1149.1 states: RESET, IDLE, IRPAUSE, or DRPAUSE.".
Well ... I am not playing with this at the moment and I can, and do, rewrite the code to work without unneccesary limits, but the strong selling points are lost on me. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
