> -----Original Message----- > From: David Brownell [mailto:davi...@pacbell.net] > Sent: Wednesday, December 30, 2009 3:17 PM > To: Laurent Gauch > Cc: openocd-development@lists.berlios.de; Austin, Alex > Subject: Re: [Openocd-development] [patch/rfc] Add support for > multiple-ports on FT4232H > > ... > > > The best to do: > > 2. Split the actual ft2232.c to two file ft2232_new.c and mpsse.c . > Then > > Austin could call funtions from mppse.c. When all is working we will > > rename ft2232_new.c to ft2232.c. Finally we will have : > > ft2232.c > > ft4232.c > > mpsse.c > > And, preferably, jtagkey2.c and friends ... there are *two* sets > of headaches with the current approach. One is how the core code > is factored. Another is how all the wiring variants are handled. >
Would it hurt too much to start out creating a library that wraps either libftd2xx or libftdi depending on configuration and exposes the same interface either way? Maybe libftdi could be extended to use libftd2xx if available and libusb if not? Re: supporting multiple interfaces for our device: After considering our needs, I've managed to move the reset lines to ADBUS5 and ADBUS6, since anyone who doesn't put a pull-up on the reset lines of a possible target will be answering to our senior systems engineer. That leaves BDBUS completely free for other uses TBD, and makes multiple-port support not quite so necessary. (Now I just need to see if I can solder the 4232HQ back onto the board...) _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
