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

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - Arsen

Pages: [1]
1
Discussion - Software / problem with FT_SetChipConfiguration
« on: May 10, 2024, 09:57:44 AM »
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

2
General Discussion / Re: Question
« on: March 14, 2024, 10:14:56 AM »
Thank you very much for Your reply.

3
General Discussion / Question
« on: March 14, 2024, 07:34:33 AM »
What the  difference between these two approaches for device configuring process:
1.
FT_60XCONFIGURATION oConfigurationData = {0};
FT_GetChipConfiguration(HandleFtdi, &oConfigurationData);
if (oConfigurationData.ChannelConfig != CONFIGURATION_CHANNEL_CONFIG_1 ) {
    oConfigurationData.ChannelConfig = CONFIGURATION_CHANNEL_CONFIG_1;
    FT_SetChipConfiguration(HandleFtdi, &oConfigurationData);
}

2.ftStatus = FT_EnableGPIO(ftHandle, 0x1, 0x1); //??
    ftStatus = FT_WriteGPIO(ftHandle, 0x1, 0x1);
Thank You !!!

4
General Discussion / Question
« on: March 13, 2024, 04:42:29 AM »


      while(1)
        for (int i = 0; i < configurationDescriptor.bNumInterfaces; i++) {
            FT_GetInterfaceDescriptor(HandleFtdi, i, pInterfaceDescriptor + i);
            for (int j = 0; j < pInterfaceDescriptor.bNumEndpoints; j++) {
                res = FT_GetPipeInformation(HandleFtdi,i,j, &pipeInformation);
                if (res != FT_OK) {
                    cout << "FT_GetPipeInformation Error!";
                } else {
                    if (!(pipeInformation.PipeId & 0x80)) {
                        res = FT_WritePipe(HandleFtdi, pipeInformation.PipeId, bufWr, pipeInformation.MaximumPacketSize, &ulBytesTransferred, NULL);
                        if (res != FT_OK) {
                            cout << "FT_WritePipe Error " ;
                        }
                    }
                    else {
                        res = FT_ReadPipe(HandleFtdi, pipeInformation.PipeId, bufRd, pipeInformation.MaximumPacketSize, &ulBytesTransferred, NULL); //second time this function does not return. Why? The first time it returns by timeout.
                        if (res != FT_OK) {
                            cout << "FT_ReadPipe Error " ;   
                        }
                   }
                }
            }
        }

Hi all. Please, say Me.
This part of the program works well, but on the second pass, when FT_ReadPipe is executed, the program freezes and does not return after timeout. The first time it returns by timeout (default 5 seconds).
In addition, I want to say that we made a USB device with FT600 and STM. But the STM is not running yet and is not writing to the FT600 buffer, so it's good that FT_ReadPipe is returning after a timeout. But why doesn’t it return the second time but freezes?
Thank everybody.

5
Discussion - Drivers / Re: How to use the FTDI device from kernel mode
« on: November 28, 2023, 01:26:05 PM »
Thank You very much

6
Discussion - Drivers / Re: How to use the FTDI device from kernel mode
« on: November 27, 2023, 08:33:28 AM »
And the second question, please. Can we implement a compound USB device using FTDI 600 and Dx200 or Dx300? One function will be regular file memory (like regular flash memory), and the second will be information conversion. We have implemented the second part. I'm interested in the first function. Can your device (ftdi) simulate regular flash memory. Thank you.

7
Discussion - Drivers / Re: How to use the FTDI device from kernel mode
« on: November 24, 2023, 08:06:01 AM »
Thank you, Mister. We will make a decision and I will write to you. Moreover, we are going to change FTDI 200 to FTDI 600. But this, I think, does not make the problem go away

8
Discussion - Drivers / How to use the FTDI device from kernel mode
« on: November 23, 2023, 05:32:01 AM »
Hello everybody. I'm new to the FTDI community.
We have a controller that communicates with the computer via FTDI. We use the D2XX interface functions from the user mode program to communicate with the FTDI driver (device). Now I want to use the FTDI device from kernel mode (Windows), but we don't have any documentation related to the FTDI driver. Please tell me where to find or buy it. Thank you.

Pages: [1]