On Tue, Feb 23, 2010 at 03:31:45PM +0100, Laurent Gauch wrote: > I think you are confusing the notion of Interface, Layout and Channel. > > The Layout defines how a Channel is used. > > The FT2232 C D and FT2232 H provides two Channels, each Channel can be > opened separately and can receive their own handle (ID). > > The selection of the Channel A or Channel B MUST not be defined in the > layout structure-> you could use the same layout on channel A and B. > Amontec is working on an new Amontec JTAG key using two JTAG interfaces, > one JTAG interface on Channel A and one JTAG interface on Channel B for > an internal FPGA configuration! > > For the selection of Channel A or Channel B, you have to modify your > specific Open /. Init functions and NOT the layout definition ;-) > Modifying the Layout definition for Channel selection will make a lot of > confusions !
Right now it's hardcoded to use INTERFACE_A. (that's the term the libftdi uses --- I was using their notation but I see that OpenOCD is using 'interface' also. I didn't realize that. So what libftdi calls "interface" OpenOCD calls "channel", yes?) How does a config file option like "ft2232_channel B" that defaults to A sound? As an example, my config would be: source [find target/mc13224v.cfg] interface ft2232 ft2232_layout foo ft2232_vid_pid 0x0403 0x6010 ft2232_channel B Would something like that have a good chance of getting pulled? -Mar. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
