Hi,
Number 1 is just the general configuration of the device. Number 2 is to enable the GPIOs. Have a look at section 3.1 of AN_412 FT600/FT601 Bridge Chips Integration.
This goes over the configuration modes of FT600 with section 3.1.5 focusing on the GPIO configuration.
We have a FT60x configuration programmer that you can use. You can find it here along with the AN_370 FT60X Configuration Programmer User Guide.
Best Regards
FTDI Community
- April 20, 2024, 03:26:26 PM
- Welcome, Guest
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
21
on: March 14, 2024, 10:52:13 AM
|
||
Started by Arsen - Last Post by FTDI Community | ||
22
on: March 14, 2024, 10:14:56 AM
|
||
Started by Arsen - Last Post by Arsen | ||
Thank you very much for Your reply.
|
23
on: March 14, 2024, 09:41:41 AM
|
||
Started by Arsen - Last Post by FTDI Community | ||
Hi,
Have a look at section 3.2 of AN_412 FT600/FT601 Bridge Chips Integration, this goes over the abort recovery process. Any error or timeout requires this abort process before resuming the read/write. Best Regards FTDI Community |
24
on: March 14, 2024, 07:34:33 AM
|
||
Started by Arsen - Last Post by Arsen | ||
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 !!! |
25
on: March 13, 2024, 04:42:29 AM
|
||
Started by Arsen - Last Post by Arsen | ||
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. |
26
on: March 08, 2024, 10:58:42 AM
|
||
Started by kiran - Last Post by kiran | ||
We are using FT2232hpq module and We are using "MPSSE" mode(SPI) and is it possible to operate the GPIO0(56-pin),GPIO1(55-pin),GPIO2(54-pin) and GPIO3 (5-pin) pins in software.
|
27
on: March 01, 2024, 07:32:04 AM
|
||
Started by wberger - Last Post by ffred | ||
Hi,
just to report informations about some tests I did (after a long pause on my FT260 project..) on a small dev board. I put a UMFT260EV1A on it, with a MCP23008 I/O expander connected to 4 buttons and 4 Leds and I connected the MCP23008 INT pin to GPIO3 (INTRIN/WAKEUP) of the FT260. I had to activate the two HID ports, for I2C & UART, because with only the I2C it wasn't working.. (so the DLL is really using the UART to read the interrupt flag) so, from LibFT260, I used FT260_UART_Init, FT260_SetInterruptTriggerType, FT260_SetWakeUpInterrupt , then FT260_I2CMaster_Init. after that I send the config to the MCP23008 to activate the interrupt in open drain mode when I push a button. and then I could use F260_CleanInterruptFlag to see if an interrupt occured and set a Led ON. and it worked ! so the Interrupt flag can be used. |
28
on: February 29, 2024, 02:13:46 PM
|
||
Started by FTDI Community - Last Post by FTDI Community | ||
Hello All,
LibMPSSE 1.0.5 fixes all known issues and is available on our website: https://ftdichip.com/software-examples/mpsse-projects/ Best Regards, FTDI Community |
29
on: February 29, 2024, 02:06:05 PM
|
||
Started by fhsakaci - Last Post by FTDI Community | ||
Hi,
We don't have any references for doing SPI communication using Bit-Bang. I would recommend that you use the MPSSE for SPI communication instead. To use I2C/SPI as a master (no slave functionality), see AN_135 MPSSE Basics and our existing MPSSE Example projects: MPSSE Examples There are two options to use I2C/SPI modes with the MPSSE engine: a. Use LibMPSSE libraries. Example code is provided with the download. Source code is also provided. b. Use D2XX drivers direct. Example code is shown at I2C / SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information. Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library). Also please also note, SPI modes 1 and 3 are not supported with our MPSSE engine. So please check that your SPI device doesn’t work with these modes. You can find all the referenced documentation above, here |
30
on: February 29, 2024, 02:03:51 PM
|
||
Started by joseph - Last Post by FTDI Community | ||
Hi Joseph,
All of the formats supported by FT602 can be found on page 13 of the FT602_UVC_Chip_Configuration_Guide. There are no signals like VSYNC/HSYNC/PCLK on FT602. FT602 is connected via an FPGA. You can refernce the FT602 example code, which you can find here. The example code shoes YUV only, but you can use it for a reference for the other formats. |