Hi,

You could try doing a check on lpdwBytesWritten in FT_Write. This shows the number of bytes written to the device. So you could use this to see if all the data has been sent, before starting the next transmission.

Best Regards

FTDI Community

Hello,

Yes this errata may affect your operation.

FT4222_I2CMaster_Write is not a synchronous function. It stores the i2c command and data into the USB buffer.
There is a firmware bug and it happens on i2c data transaction and querying status at the same time.
Even these two actions are executed at the same time. The error rate is very low.
That is why you can run the test case for a long time but finally fails.

See the following code modifications.
You can see the bold section:

FT4222_STATUS stat = FT4222_I2CMaster_Write(data_handle, slaveAddress_, data, size, &bytesWritten);
if (stat != FT4222_OK)
    throw std::runtime_error("Error writing data over FT4222");
uint8_t flags = 0;
do {
    for (uint32_t retries = 3; retries > 0; --retries) {
        // Wait for the i2c transmission done, the waiting time depend on the i2c transaction time
        // for example:
        // 100Kbps to transfer 10 bytes , wait 8(bit) * 10us (1bit time)* 10 (bytes) = 800 us
        // 1Mbps to transfer 10 bytes , wait 8(bit) * 1us (1bit time)* 10 (bytes) = 80 us

        Sleep(1);
        stat = FT4222_I2CMaster_GetStatus(data_handle, &flags);
        if (stat == FT4222_OK)
            break;

    }
    if (stat != FT4222_OK)
        throw std::runtime_error("Error reading status from FT4222");
    if (I2CM_DATA_NACK(flags) || I2CM_ADDRESS_NACK(flags))
        throw std::runtime_error("The peripheral did not acknowledge the message as expected");
} while (!I2CM_IDLE(flags));

Best Regards,
FTDI Community

Hi
Your company has already contacted us via email about this issue, please continue to work with us via email.   

Regards
FTDI Community

Hello,

If you call FT4222_ChipReset / FT4222_Close, you need to restart all chip configuration process from the beginning.

Best Regards

FTDI Community

Hello,

Try this link AN_430 FT60X PCB Layout Guidelines. if that doesn't work you can find it on our website under application notes.

Best Regards
FTDI Community 

Hi,

so it randomly disconnects and then once this happens it takes a few tries to get it to reconnect again? but using the device reset it appears again first time? am i understanding this correctly?

does the disconnect happen during any data transfer or can it happen even when the device is idle? you should have a look at the FT601 errata and see if any of the situations apply to you and let me know. TN_168 FT600/FT601 Errata Technical Note.

Best Regards
FTDI Community

An issue has been reported with building V2DPS with SP3 Patch:

Linking Release\V2DPS
2 errors, 0 warnings and 0 informational messages
(C:\ProgramData\FTDI\Vinculum II Toolchain\Firmware\drivers\lib\USBSlaveFT232.a) : (error) L0019 archive symbol is missing memset
(kernel.a) : (error) L0017 invalid archive file
VinBuild.exe failed with return code 5

The fix is to add string.a and string.h to the project and rebuild.

Best Regards,
FTDI Community

Hello,

Please note that the CP2105 is not from FTDI but from Silicon Labs.

Since this is not one of our products, although it utilises our device, I am unable to support it.
Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact the OEM.
FTDI cannot control how the USB ICs are used and often has no knowledge of the entire product.
Please see the following document for reference:

http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf

Best Regards,
FTDI Community