FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: [1] 2 3 ... 10
 1 
 on: Today at 03:46:52 pm 
Started by TonySH - Last Post by FTDI Community
Hello,

Yes you can use FT4222_SetClock to set the system clock to 80MHz, then use FT4222_SPIMaster_Init and set clock_div to CLK_DIV_2 (1/2 System Clock) which should give 40MHz on SCK.

Please make sure you are using the latest version of LibFT4222:

https://ftdichip.com/software-examples/ft4222h-software-examples/

And reference AN_329 User Guide for LibFT4222.

Best Regards,
FTDI Community

 2 
 on: Today at 03:28:16 pm 
Started by sunlite - Last Post by FTDI Community
Hi,

Could you please contact your local support line at: cn.support@ftdichip.com. They will be able to help you.

Best Regards
FTDI Community

 3 
 on: Today at 12:04:02 pm 
Started by sunlite - Last Post by sunlite
Hello,

Have to ask technical experts a question. We use your prestigious company's FT232 for communication between master and slave computers through USB to RS232 serial port. We used the driver of FTDI, but we customized it our own driver by wrapping it outside of FTDI. Our drivers mainly include two inf files: FTDI Bus and FTDI Port. The matter is that the device manager is unable to recognize the COM port. Our Port cannot be displayed under the ports (COM and LPT) of device manager.
Currently, it can only be displayed on 2 sets of ASUS laptops ( Windows 11 Home Chinese version , Intel Core i3, X64) under the device manager ports (COM and LPT) . Tried other brands like Lenovo, Hua wei, Dell, Hassee, Haier,  even if other same model of ASUS laptops but all failed, it won't work. Including desktop computers. This problem has been troubling us and we stuck here for a long time and needs to be solved urgently. Otherwise, the Labview program that is nearly finished will be unable to deploy to the client's machine due to this driver issue!

Please help, the sooner, the better!  :)
Thank you very much!

sunlight

 4 
 on: Today at 06:10:42 am 
Started by TonySH - Last Post by TonySH
Hi experts,
    Thanks for your confirmation.

    About the library "LibFT4222" I used, I also need to double check with you, LibFT4222 supports the SCK performed with 40 MHz in SPI master mode, is that right?

Thanks
TonySH

 5 
 on: May 20, 2024, 04:39:52 pm 
Started by TonySH - Last Post by FTDI Community
Hello,

I can confirmed that the maximum SCK in SPI Master mode is 40MHz.

We will update the UMFT4222EV datasheet.

Best Regards,
FTDI Community

 6 
 on: May 17, 2024, 11:56:19 am 
Started by Arsen - Last Post by FTDI Community
Hi,

The source code for the FT60x Chip Configuration Programmer cannot be given out.

could you please email support1@ftdichip.com? we can then discuss your issue further.

Best Regards
FTDI Community

 7 
 on: May 17, 2024, 10:25:35 am 
Started by TonySH - Last Post by TonySH
Hi experts,
    I got a FTDI device module UMFT4222EV-D, my target are using a GPIO pin and a channel SPI with clock running as 40M Hz.
    So, I looked up the data sheet of the module UMFT4222EV and chipset FT4222, and found it supports different maximum clock frequency.

    In the "UMFT4222EV - USB2.0 to QuadSPI/I2C Bridge Development Module Datasheet Version 1.4" from the FTDI website.
   
Quote
3 FT4222H Features and Enhancement
...
The max SPI interface operating clock can be set up to 30MHz in master mode and 20MHz in slave mode.
...

    In the "FT4222H USB2.0 TO QUADSPI/I2C BRIDGE IC Datasheet Version 1.5" from the FTDI website.
   
Quote
4.1 Key Features
...
The maximum SPI interface operating clock can be set up to 40MHz in master mode and 20MHz in slave mode.
...

    There is 10MHz lost on UMFT4222EV-D device in master mode, what's going on the device? and for my target, which device I can use? Is there a suggestion?
   
Thanks
TonySH

 8 
 on: May 16, 2024, 02:52:49 pm 
Started by Arsen - Last Post by Arsen
According to the documentation, after FT_SetChipConfiguration the device should reboot. “The device will restart after the chip configuration is written to the device.” (AN_379 D3XX Programmers Guide, page 45, Remarks). But it does not reboot, so it doesn't open again.(FT_DEVICE_NOT_FOUND)
Where can I get the source code for the "FT60x Chip Configuration Programmer"
Thanks everyone.

 9 
 on: May 10, 2024, 09:57:44 am 
Started by Arsen - Last Post by Arsen
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

 10 
 on: April 22, 2024, 01:44:42 pm 
Started by AndreiBu - Last Post by FTDI Community
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

Pages: [1] 2 3 ... 10