Hello.
After the FT_SetChipConfiguration command, I cannot close and reopen the FT600 device connected via USB 2. What could be the reason? Thank you.

FT_CreateDeviceInfoList(&numDevs);
FT_Create(ptDest->SerialNumber, FT_OPEN_BY_SERIAL_NUMBER, &HandleFtdi)
FT_GetChipConfiguration(HandleFtdi, &oConfigurationData);
oConfigurationData.FIFOClock = CONFIGURATION_FIFO_CLK::CONFIGURATION_FIFO_CLK_66;
oConfigurationData.ChannelConfig = CONFIGURATION_CHANNEL_CONFIG_1;                 //CONFIGURATION_CHANNEL_CONFIG_1
oConfigurationData.FIFOMode = CONFIGURATION_FIFO_MODE_600;  //CONFIGURATION_FIFO_MODE_600
oConfigurationData.PowerAttributes &= 0xBF;   //0x40 is the flag of Self/Bus powered
res = FT_SetChipConfiguration(HandleFtdi, &oConfigurationData);
res = FT_Close(HandleFtdi);  //res = 0: good!
res = FT_Create(ptDest->SerialNumber, FT_OPEN_BY_SERIAL_NUMBER, &HandleFtdi);  //error :: FT_DEVICE_NOT_FOUND

Hello,

This issue has been root caused.

Device manager can show “FTDI CHIP” as the driver provider.
This means that, this driver can be installed by the installer provided in the package.
 
In most of the cases, the installer is not required and WinUSB driver gets installed automatically.

What we have observed is, the issue happens when the installer in the package is executed. The issue is due to GUID mismatch.
The installer package is using a different ID, and this was causing the issue.
 
We have updated the installer files to use the Microsoft default GUID so that the application can work independent of driver version.

The updated package has been uploaded to our SFTP server.
 
1.   Please uninstall the existing drivers from device manager.
2.   Use the drivers from updated package.
3.   Install the drivers either from device manager or by using the installer in the package.

Please contact us if you would like to receive a beta of this update.

Best Regards,
FTDI Community

I believe you can switch between UART and MPSSE (I2C/SPI/JTAG) modes in software using set_bit_mode USB control request but I don't know if it's exposed in FTDI drivers.

I worked with FT2232H directly through libusb, without FTDI drivers.

Here are notes from my code regarding latency timer:

Set receive buffer latency timer (vendor-specific command)
Latency Timer is used as a timeout to flush short packets of data back to the host
The default is 16 ms, but it can be altered between 0 ms and 255 ms
At 0 ms latency packet transfer is done on every high speed microframe (every 125 us)
For MPSSE it's recommended to set it to the default 16 ms and use "send_immediate" command to send bytes back to host when required
This approach seems to be working fine for FT2232H but with FT232H there seems to be a latency delay present on the first small packet transfer therefore latency is set to 1
This was observed while programming SPI flash and checking its status register value

I've been working with FT2232H a lot but I don't use FTDI drivers, instead I work directly through libusb.

1. Does FT2232H support 30MHz at JTAG-TCK?

IIRC, yes, I think I measured it at some point.

2. Is it required for platform to provide 60MHz clock to FTDI or 12MHz crystal is sufficient? Or any other hardware change required?

12 MHz crystal is sufficient, nothing else is needed in HW.

3. Any reference driver/test to enable FT2232H JTAG TCK operating at 30MHz?

These are notes from my code:

Master clock is 60 MHz after /5 clock divider is disabled
required_clock = master_clock / (2 * (divider + 1))
divider = master_clock / required_clock / 2 - 1

If you set it to 30 MHz but actually measure 6 MHz then the /5 clock divider is enabled.

Hi

I was trying to use FT2232H Channel A as JTAG and configured it. I have enabled JTAGHiSpeed API's from driver and disabled divide_by_5, to get 30MHz as TCK. But when I probe, I see 6MHz at TCK Pin.

1. Does FT2232H support 30MHz at JTAG-TCK?
2. Is it required for platform to provide 60MHz clock to FTDI or 12MHz crystal is sufficient? Or any other hardware change required?
3. Any reference driver/test to enable FT2232H JTAG TCK operating at 30MHz?

Hi,
  I got it, thank you.

Best Regards
Tony

Hi Tony,

Your only option would be to add some external pulldown on the GPIOH pins. Even if they have been set as low and input, if there is no connection they will be pulled high by the internal pullups.

Best Regards
FTDI Community

Hi,
  I do connect the GPIOH with the slave device, I use GPIO to listen pull-high signal from the slave when the slave have data to send to the master via SPI.
 
  It works on our windows application used 232H and slave device when they are both power on. but it is a little bit bothered that I need to add time stamp in the test log and find out the first successful transfered message.
 
  I expect that I run my windows application first, and power on the slave device in second action, then the first log message on the application is what I need. so far, I will get the redundant message because of the default state "TriSt-PU" when starting to run the application. On my current test SOP, the default state is the fake signal for my application. How do I bypass this default state?

8. TriSt-PU – Input pulled up, not used

  Is the definition of TriSt-PU as defined above? What is the definition of "used"? I use FT_writeGPIO() to initialize to zero, is it not defined as "used"?

Best Regards
Tony

Hi Tony,

The default for these GPIO pins is TriSt-PU. See table 5.1 in FTDI Device Input Output pin States.

what are you planning on connecting the GPIOH pins to? have you tried connecting the pins to a slave device and performing a GPIO read?

Best Regards
FTDI Community