On Feb 28, 2009, at 9:20 AM, Dirk Behme wrote:
Ah, yes. Understood. Looking at jtag.c and irscan/drscan implementations:Why is irscan implemented as handle_irscan_command(), but drscan as Jim_Command_drscan()? What is the difference between handle_xx_command and Jim_command_xx?
OpenOCD hasn't established naming conventions.
Additionally, short status update from me:As pointed out by Kees [1], the 'do always 7 clocks tap_get_tms_path()' might not be flexible enough for OMAP. So I played a little with Holger's jtag_move_to() [2] and used it to hack a new tap_get_tms_path() (see patch in attachment for recent status). Unfortunately, this doesn't work correctly yet:Adding some debugging output to original version of OpenOCD and the hacked one with 'new' tap_get_tms_path() I get the output below. Have to investigate why new version fails with 'Could not validate end ...'.And, I wonder why the new version needs ~6 initial TAP_RESET moves as marked with OMAP3_HACK in patch in attachment. Else, the ID code won't be detected correctly. I assume that this isn't related to new tap_get_tms_path(). I vote for a reset issue (?)
After TRST, the OMAP3 needs 10 TCK pulses before the JTAG hardware turns on. I'm assuming that the 7 TAP_RESET moves combined with 3 other pulses was just enough to get things turned on.
Best regards Dirk [1] https://lists.berlios.de/pipermail/openocd-development/2009-February/004773.html [2] https://lists.berlios.de/pipermail/openocd-development/2009-February/004736.html
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
