Hi Jon,
I really think it is not related to OS kernel nor to kernel driver nor
Virtual Machine. But really coming from something in the OpenOCD code
itself.
Also, it should be related to *HOW* OpenOCD is closing the Amontec
JTAGkey (and or the JTAGkey-2 ), specially regarding TRST and SRST. If I
found time today, I will provide a patch to try.
Regards,
Laurent Gauch
http://www.amontec.com
http://www.amontec.com/jtagkey.shtml
In the course of my fooling around lately it seems I am able to wedge
something, libftdi or the JTAGKey-Tiny, I got it into a state where OpenOCD
would only produce this on startup, even after power cycling the target:
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Leaving the target powered I replugged the JTAGKey-Tiny and on next start of
OpenOCD it found things:
Info : RCLK (adaptive clock speed) not supported - fallback to 100 kHz
Info : JTAG tap: penta.tap tap/device found: 0x04040009 (mfg: 0x004, part:
0x4040, ver: 0x0)
Info : JTAG tap: dm355.jrc tap/device found: 0x0b73b02f (mfg: 0x017, part:
0xb73b, ver: 0x0)
Info : JTAG tap: dm355.etb enabled
Info : JTAG tap: dm355.arm enabled
Info : Embedded ICE version 6
Info : dm355.arm: hardware has 2 breakpoint/watchpoint units
Info : ETM v1.3
Note: I am running OpenOCD on Linux inside VirtualBox hosted on Windows, using
VirtualBox's USB capture features.
If this is of interest to anyone please let me know if there is something you'd
like me to try / information to capture next time.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
