Duane Ellis wrote:
> dirk> Why is irscan implemented as handle_irscan_command(), but drscan as
> dirk> Jim_Command_drscan()? What is the difference between
> dirk> handle_xx_command and Jim_command_xx?
> 
> Historically - OpenOCD did not have a script language other then a 
> simplistic series of commands, ie: No "IF" statements, no subroutines, 
> no nothing. "JIM-TCL was adopted as a replacement/enhancements, because 
> it was a very simplistic thing, and it could "mix well" with the 
> existing command structure. Many new commands have been added, updated, 
> modified, changed over time and are actually implemented via TCL.  Not 
> everything was changed, lots of this happened spring/summer 2008.
> 
> OLD:  handle_xx_command()
> NEW: Jim_Command_xxx()
> 
> The idea was: New commands should generally be implemented using TCL, so 
> that they are "script friendly".
> 
> ====
> 
> I'm sorry I've not been following much lately - been very very busy with 
> daytime activities.
> 
> Do you know what you needed to what command? Perhaps - I can answer some 
> "how to questions" for TCL

In [1] Rick proposed

"... that the C function for the irscan and drscan commands needs to 
look for another argument (namely the end state) and add a call to 
jtag_set_end_state.  This might also be handled already with a 
'end_state' command. "

and I looked into it and was slightly confused by the different 
implementations of irscan and drscan commands.

Best regards

Dirk

Btw.: If somebody has some time and likes to discuss about OMAP3 JTAG, 
would be nice to show up from time to time at #openjtag. Kees and I 
are sometimes there ;)

[1] 
https://lists.berlios.de/pipermail/openocd-development/2009-February/004778.html
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to