The only reason I can think of for a specic numbering is that it might optimize the gate design in a hardware implementation of the tap state engine. But this is not a problem for us so thats OK. If we want to follow JTAG documentation standards (ARM ane IEEE) in our code then the state names should also change like:
TAP_DREXIT2 --> TAP_EXIT2_DR etc (this will have a greater impact ... ) and finally TAP_INVALID is used in the target code to mean "TAP DONT CARE" so calling it invalid is a bit misleading. Regards, Magnus Zach Welch wrote: > Hi all, > > This patch -- also derived from Jeff Williams' work -- reorders the enum > tap_state symbols to reflect the states used by most/all ARM parts. > > I verified that these states match the documentation that I have here, > and I tested that nothing appears immediately broken. If I am right in > say that OpenOCD does not care about their specific values (only that > they have unique values), then this is completely safe to apply. > > Cheers, > > Zach > > > ------------------------------------------------------------------------ > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
