On Sunday 07 June 2009 04:05:53 Duane Ellis wrote:
> I think you are *buried* in the details.
That is obviously true.. but you really helped to make things more clear.
> This is handled *automagically* by the FT2232H
> chip, you only need to enable it.
>
> The ftdi-2232-H monitors the RTCK signal
On Sunday 07 June 2009 01:51:21 Duane Ellis wrote:
> In the ARM diagram, Look at the TCK synchronizer and the RTCK signal to
> the TAP in the block diagram on the ARM site.
So the JTAG-debugger needs an input pin attached to RTCK. OpenOCD has to
monitor the state of this pin an wait for a falling
On Sunday 07 June 2009 01:51:21 Duane Ellis wrote:
> Patrick Wieland wrote:
> >> (I added some ultra high speed level shifters
>
> FYI - the XVERVE -signalyzer has this "built in", as does many of the
> SEGGER dongles, do check, you can screw up a target bo
Thank you Duane for your super fast reply!
My dongle is pin compatible to openocd by now (I just added high speed level
shifters to support targets from 1.2V to 3.3V with TCK speed greater than
30MHz). You said I'd have to set jtag clock speed to zero to enable adaptive
clocking, ok, but as I am
On Sunday 07 June 2009 01:07:29 Duane Ellis wrote:
> Patrick Wieland wrote:
> > I am working on a OpenOCD dongle based on the FT2232H. I want to support
>
> The "FT2232H" is already supported :-)
>
> See the configure option:
> --enable-ftd2xx-highspeed
This is my first posting to this mailing list, so I friendly say 'hello' to
everyone :-)
I am working on a OpenOCD dongle based on the FT2232H. I want to support
adaptive clocking, but I don't know how to accomplish this task. AFAIK there
are no FT2232 based designs with this feature available.
