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: June 11, 2019, 09:22:26 AM 
Started by vytautasb - Last Post by vytautasb
Hello,

OK, waiting for reply.

Thank you

 2 
 on: June 11, 2019, 09:19:40 AM 
Started by vytautasb - Last Post by FTDI Community
Hello,

I see that you have also contacted email support where we will deal with your issue and post an outcome here.

Regards,
FTDI Community

 3 
 on: June 11, 2019, 07:56:34 AM 
Started by vytautasb - Last Post by vytautasb
Hi,

i am having difficulties running FT601 with 66MHz FIFO clock setting in Multi-Channel FIFO mode. We are using our custom board and example design for Altera FPGA.

I am using timing constraints provided in example design and example runs fine with 100MHz FIFO clock, but when i change FIFO clock setting (in configuration utility) to 66MHz example design does not work. I have tried editing timing constraints file for FPGA and change clock period from 100Mhz to 66 MHz but this does not help. 

Is there anything else has to be changed to make example design work with 66Mhz FIFO clock?

 4 
 on: June 07, 2019, 10:33:58 AM 
Started by techtoys - Last Post by FTDI Community
Hello,

Thanks for pointing this out!
This issue has been fixed in ESD 4.6 due to be released shortly.

Best Regards,
FTDI Community

 5 
 on: June 07, 2019, 08:47:10 AM 
Started by Tycoon - Last Post by Tycoon
Hello,

I'm trying to use LibMPSSE-I2C to communicate between an FT2232H (in a FTDI Click board) and MCP23017 and MCP3426.

Almost everything runs fine, including opening the channels and writing, but I have some issue with the I2C_DeviceRead function : it doesn't seem to send ACK after every byte the device sends. It's not an issue with the MCP23017 as the device sends only one byte at a time, but with the MCP3426 it's more problematic : the device sends back 3 bytes, but because it doesn't receive an ACK from the FT2232H after the first byte, it just stops the transfer.

Here's what it looks like under the oscilloscope :



I numbered the bits. Every nine bits, I've written an 'X' where either the FT2232H or the device is supposed to ACK. The first 'X' is correctly ACKed by the device, but the second 'X' is not ACKed by the FT2232H, causing the MCP3426 to stop the transfer. In the end, I get the first byte (which I assume is correct), but the two remaining bytes ends up being 0xFF which is incorrect.

Here's the DeviceRead I tried:

Code: [Select]
int err = I2C_DeviceWrite(i2cChannel->handle, address, size, payload, byte_transfered, I2C_TRANSFER_OPTIONS_START_BIT | I2C_TRANSFER_OPTIONS_STOP_BIT | I2C_TRANSFER_OPTIONS_FAST_TRANSFER_BYTES);
Code: [Select]
int err = I2C_DeviceWrite(i2cChannel->handle, address, size, payload, byte_transfered, I2C_TRANSFER_OPTIONS_START_BIT | I2C_TRANSFER_OPTIONS_STOP_BIT);
Code: [Select]
int err = I2C_DeviceWrite(i2cChannel->handle, address, size, payload, byte_transfered, I2C_TRANSFER_OPTIONS_START_BIT | I2C_TRANSFER_OPTIONS_STOP_BIT | I2C_TRANSFER_OPTIONS_NACK_LAST_BYTE);
Neither of them makes the FT2232H ACK.

Any idea where the problem could be ? Is it even a software problem ? On the hardware level, both SDA and SCL are pulled-up to the 3.3V (actually more like 3V but eh) with 4.7K resistors.

Thanks a lot !

 6 
 on: June 06, 2019, 04:21:19 AM 
Started by techtoys - Last Post by techtoys
Studying how EVE Screen Designer 4.5 works and found a datatype mismatch in FT_Esd_Dl.c.

This file is stored at ./EVE Screen Designer/Libraries/FT_Esd_Framework/

Data type for FT_Esd_BitmapHandleUse[] declared as ft_bool_t.

However, browsing down the source code at line #251 an assignment to 2 is declared.

Code: [Select]
if ((handle < FT_ESD_BITMAPHANDLE_NB) && (handle != FT_ESD_SCRATCHHANDLE)) // When valid and not using scratch handle
{
Ft_Esd_BitmapHandleUse[handle] = 2; // In use
}

This leads to compile error for some other toolchain.

 7 
 on: June 05, 2019, 09:25:01 AM 
Started by k.patel - Last Post by FTDI Community
Hello,

I'm working with you via email on this.

Please post the solution here which will benefit other users.

Best Regards,

FTDI Community

 8 
 on: June 05, 2019, 08:46:09 AM 
Started by k.patel - Last Post by k.patel
Hello everyone,

This is my first post in FTDI Community. So please forgive me if my question is not properly explained, but I will try my best.

In my application, I need to read and write the external EEPROM 93LC46B which is connected to TI MCU via FTDI Driver 2232D. I program the EEPROM with MProg 3.5, for example values for UID/PID, fixed serial numbers and so on.

FT2232D consists of dual channel USB. I am using Channel A for debugging purposes. Channel B is connected to RX (BDBUS-0) and TX (BDBUS-1) pins for UART to TI MCU.
Please have a look at the circuit diagram attached with the file.

My question: Is it possible to read and write the external EEPROM from MCU through UART communication with FTDI, provided that MCU supports this mode of communication and respective GPIO pins are already configured for it.

MY AIM: To access the values of Product Description, Fixed Serial Number, etc., by TI MCU which are already preprogrammed into EEPROM

Thanks in advance!

With regards,
Karan Patel

 9 
 on: June 04, 2019, 03:12:10 PM 
Started by aferquez - Last Post by FTDI Community
Hello,

In that case, can you send me a SPI capture of when you are sending the host commands?

Best Regards,
FTDI Community

 10 
 on: June 04, 2019, 02:47:04 PM 
Started by aferquez - Last Post by aferquez
Hello,

I will need to double check with the development team if it is possible to send host commands to a Cleo board in such a manner, as the FT900 on the Cleo is programmed with a custom firmware which expects Cleo.xxx() commands.

Best Regards,
FTDI Community

Hi,

Sorry, I has a mistake. My device is ME810A-HV35R. Not CleO device. I use ME810A-HV35R board with a MM900EV-LITE board.

Thanks and regards.

Pages: [1] 2 3 ... 10