I've noticed strange behaviour in initialization with TI OMAP4430 and
Freescale iMX53 using Amontec JTAGKEY. Even typing keys on OpenOCD shell
was very very slow.
I didn't investigate too much the causes. Anyway this patch fix it.
Signed-off-by: Luca Ellero <lroluk at gmail.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>>
---
src/jtag/core.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/jtag/core.c b/src/jtag/core.c
index 4c5d37a..ad662ef 100644
--- a/src/jtag/core.c
+++ b/src/jtag/core.c
@@ -1369,12 +1369,12 @@ int adapter_init(struct command_context *cmd_ctx)
}
int retval;
+ jtag = jtag_interface;
retval = jtag_interface->init();
if (retval != ERROR_OK)
{
return retval;
}
- jtag = jtag_interface;
/* LEGACY SUPPORT ... adapter drivers must declare what
* transports they allow. Until they all do so, assume
--
1.6.4.4
We do not have any TI OMAP 4430 in our lab, but your note is interesting since
Amontec Team is working on making the the ft2232 interface more robust,
( see last message of Sebastien).
The main problem is ft2232.c using a jtag_get_speed fn at the init stage ...
I was with the opinion to set a default frequency when initializing any jtag
adapter (long discussion somewhere last months), instead to call a upper jtag
layer fn as with jtag_get_speed (the big spaghetti). For the story.
But in an other way, as you use TI OMAP 4430 supporting JTAG RTCK feature, you
should try with an Amontec JTAGkey-2 supporting JTAG RTCK feature.
The main advantage to use a JTAG RTCK for Cortex-Ax is to have the JTAGkey-2 synchronized with the TI OMAP X frequency -> you do not need to be worry about the JTAG frequency, since the OMAP will give the tempo via the RTCK :-)
If you already have a Amontec JTAGkey, evaluate the Amontec JTAGkey-2 OEM
(coming without the cable, but at low cost )
---
Your patch is OK for me !
Regards,
Laurent
http://www.amontec.com/
Amontec JTAGkey-2 : High speed USB JTAG interface
http://www.amontec.com/jtagkey.shtml
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
