On Sat, Jan 18, 2014 at 12:48 PM, Paul Fertser <[email protected]> wrote:
> On Sat, Jan 18, 2014 at 10:21:07AM +0400, Paul Fertser wrote:
> > There's one case that still bothers me: xds100v2.
>
> Probably it's not really surprising after all. I've checked all the
> bits against the old driver and the ftdi config matches it
> perfectly. Except that it doesn't pull PWR_RST low initially when it's
> initialising the device. Probably if ftdi_set_signal wasn't
> COMMAND_EXEC it could be used to reset the adapter the same way the
> old driver does, i.e. first bring PWR_RST low, then high. What do you
> think?
>
Before init we don't have a connection to the adapter setup so we can't
execute ftdi_set_signal.
We could always initialize it low and require the user to do
"ftdi_set_signal PWR_RST 1" after init. Ideally there would be a hook that
the xds100v2 config could setup to do that after initializing.
>
> Are there any other known cases of ftdi driver not working while
> ft2232 works?
Not that I'm aware of.
There is one ft2232 adapter that's not supported at all by the ftdi driver
though, but it's hardly a standard one. It uses the EEPROM connection in
weird ways, it doesn't work on libftdi and I haven't heard of anyone using
it.
/Andreas
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
