On Tue, Feb 14, 2012 at 9:56 AM, Vivien Giraud <[email protected]> wrote:
> In my case I don't need layout because I make my own, I'm working on own > devboard for my company. You definitely need to specify your layout (mapping between FTDI I/O and signals such as nSRST/nTRST and how the I/O need to be handled to control level shifters, blink LED or other circuitry), one way or the other. > FT4232H don't work with OpenOCD you have to change some code because FT4232 > PID is 0x6011 not 0x6010 and it's hard-coded. No, VID/PID is not hard coded in OpenOCD. They are configured from Tcl at runtime. > 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 ? No one knows, it's been like that forever. The ft2232 driver is fundamentally broken, that's why I rewrote it. Just ignore that value and look forward instead. > 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
