Re: Remote Flashing w/ Window Client & OpenOCD

linnix wrote:
OK, increased bulk transfer of 64 bytes,
which caused 590 bytes write to the USB FTDI.
Tried 128 bytes and caused 1100 bytes USB write
and the FTDI choked on it.

I guess I have to break down the packet in GDB code
before sending it to FTDI.

Did you try the (not free, but gratis) FTD2XX driver from FTDI? I've run
into all kinds of problems with libftdi, and I always intented to work on
fixing it, but the low level details of the FT2232C aren't well documented.
Since the OpenMoko project is using the OpenOCD to debug the Neo1973 this
might change, as they're using libftdi instead of FTD2XX.

There's a fix for ft2232.c when using libftdi in the latest trunk release
(added because of a bug report from OpenMoko):
http://svn.berlios.de/wsvn/openocd/trunk/src/jtag/ft2232.c?op=diff&rev=0&sc=0

This fixes initialization problems (sometimes the OpenOCD couldn't talk to
the FT2232 when using libftdi, and required a restart) and at least on the
few tests I ran it also cured the choking on large packets, but maybe
that's just a coincidence and the problem is still there.

The fun never end.
No offend intended to you, Domicic.
but who said open source is free?
It's cheap, but not free.

Heh, I'm sure that's not what you want to hear, but the 'free' in 'free
software' is about being free for you to use any way you like, and I
suppose your case shows that it nicely plays that role.

The free as in beer/gratis is something that's usually disregarded among the
free software community.

But of course you are right, the OpenOCD needs more work for setup and
learning than a commercial offering.

Regards,

Dominic
.