I've started a new thread on how jtag_init() should be handled
to give the target script much more control.
Your patch allows for a particular type of change, but I'd rather
make it much more general.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger a
The problem I have with this patch is the concept that the
interface is in a particular sate when OpenOCD is not
running where it is possible to "smoothly"
transition into the "OpenOCD state".
How about allowing scripts to override the "init"
of OpenOCD to e.g. add a sleep after the device is
init
I've changed my mind. It helps if I read through the patch. :-)
This patch makes it possible for a config script to skip
the reset on starting up OpenOCD. This makes a lot
of sense to me.
How and when to start communicating with the target after
launching OpenOCD *should* be under the target conf
Here is the patch on jtag_reset_on_init (again).
This fixes the problem with Olimex dongle (on power-on it drives srst
low) but will also fix libftd2xx.so library (asserts srst for > 250ms).
On Thu, 2009-10-01 at 07:32 +0200, Øyvind Harboe wrote:
> > 1. put reset_on_init patch that I submitted
> 1. put reset_on_init patch that I submitted earlier and make it
> dependent on hardware used to access JTAG.
Where is this patch?
> 2. put in udev rules a small program that will de-assert srst. I am not
> sure if would be committed to openocd tree?
>
> Comments or ideas?
Remove the initial sc
There is one more problem with reset handling during init. for ft2232
chips [at least on Olimex dongle].
When you first plug-in the Olimex dongle to USB port it drives srst
signal low. This cause failure (see output below) during initial openocd
JTAG scan. It only fails on the first try. All later
