On 02/14/2012 02:03 AM, Andreas Fritiofson wrote:
On Tue, Feb 14, 2012 at 12:54 AM, Peter Stuge<[email protected]> wrote:
Andreas Fritiofson wrote:
Andreas, Vivien is eager to do some work on cleaning up the ft2232
driver, but I recall that you had also begun on that. What's the
status?
The new driver is more or less ready and waiting to get pushed for
review.
Great news!
Great ! I'm excited to see it !
Main thing missing is the handling of different layouts. It's
not clear to me what's the best way to handle it. I really want the
layouts specified in Tcl instead of C, but I'm not really fluent in
that language or Jim's integration with OpenOCD. I'm about to ask for
help with that on the list. Maybe I'll push the driver first to get
some context to the question and widespread testing.
I think this is a good idea!
Oh, heck, I'll just Cc the list, if someone understands what I'm
after, feel free to share your thoughts, otherwise I'll post a more
specific request tomorrow when I'm not so tired.
In my case I don't need layout because I make my own, I'm working on own
devboard for my company.
Looking at Vivien's first mail it seems like the intention perhaps is
to auto-select the ft2232 layout based on the vid/pid of the connected
devices. In that case I have some, possibly conflicting, ideas about a
more general mechanism along that line.
If I understood correctly,/his, not her :)/ primary interest is to also make
FT4232H-based adapters work in OpenOCD.
Don't they work today? I don't have one so I don't know. I think it should work.
FT4232H don't work with OpenOCD you have to change some code because
FT4232 PID is 0x6011 not 0x6010 and it's hard-coded.
My automatisation work now, now I have to change some settings in
fonction of the PID found.
My second step is to find the IDCODE at the begin to charge settings of
the connected CPU (we have our own CPU).
I'm very eager to look at your driver. On a side note, hopefully
you're not using Mauro Gamba's code for libusb-1.0, because that
will get reverted. (It's incomplete and issues pointed out in review
have not been addressed.) I'll wait with that until I see your new
driver though.
I'm not quite sure what you mean so I'm pretty sure I'm not using it.
I have used the existing configure.ac stuff for detecting libusb-1.0,
though, and noticed there are flaws there.
/Andreas
Andreas, last question, do you understand why #define FT2232_BUFFER_SIZE
is at 13000 or something like that (I don't remember exactly the number
because I use 8192 to work with FT4232 even it's made a buffer overflow
and nothing is written in memory.
How FT2232_BUFFER_SIZE is calculated ?
Cheers
Vivien
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
