Hi Fred,
On your initial point regarding the versioning of libFT260, it looks like you are using a link to an old version of our website (see the old2020 part of your URL) which is where you are finding the 1.1.3 file.
   
Version 1.1.5 is the current version on the website.... https://ftdichip.com/products/ft260q/    

The only way to edit the serial number or description is via FT Prog.  This is a HID class device.

See section 9 User Configuration of the FT260 Datasheet for programmable parameters. FT_PROG must be used to program these as it can't be done using the library. You must also use UMFTPD3A for programming.
https://ftdichip.com/products/umftpd3a/

There is an update to the libFT260 user guide which hasn't made it to the website yet.   If you can send us an email we can send you this version for now.   

Regards
FTDI Community 

Hi,

Yes, to enable MPSSE mode you need to set the bit mode to 0x02 using the FT_SetBitMode function. the MPSSE basics document i linked previously explains this. the set up the MPSSE. the LibMPSSE-SPI user guide explains the API and how it is built on the D2XX driver.

You can run the example code i linked on visual studio.

Best Regards

FTDI Community 

Hello,

from the wave forms it looks like the data is changing on the rising edge of the clock. you are using SPI mode 0, in this mode the data should be changing on the falling edge of the clock.

it looks like you have the set configuration mode correctly, so this shouldn't be happening. could you run your original code that you first posted and send the wave forms of that please? just so we can compare.

Best Regards
FTDI Community   

Hello,

have you made sure to initialize the states of the MPSSE pins? command 0x11 makes the clock start low and command 0x10 makes the clock start high.

section 3.3 of https://www.ftdichip.com/Support/Documents/AppNotes/AN_108_Command_Processor_for_MPSSE_and_MCU_Host_Bus_Emulation_Modes.pdf explains this further.

Best Regards

FTDI community

Hello Matt,

You can find the error codes in LibFT260.h which is included with LibFT260:

enum FT260_STATUS
{
                FT260_OK,
                FT260_INVALID_HANDLE,
                FT260_DEVICE_NOT_FOUND,
                FT260_DEVICE_NOT_OPENED,
                FT260_DEVICE_OPEN_FAIL,
                FT260_DEVICE_CLOSE_FAIL,
                FT260_INCORRECT_INTERFACE,
                FT260_INCORRECT_CHIP_MODE,
                FT260_DEVICE_MANAGER_ERROR,
                FT260_IO_ERROR,
                FT260_INVALID_PARAMETER,
                FT260_NULL_BUFFER_POINTER,
                FT260_BUFFER_SIZE_ERROR,
                FT260_UART_SET_FAIL,
                FT260_RX_NO_DATA,
                FT260_GPIO_WRONG_DIRECTION,
                FT260_INVALID_DEVICE,
                FT260_INVALID_OPEN_DRAIN_SET,
                FT260_INVALID_OPEN_DRAIN_RESET,
                FT260_I2C_READ_FAIL,
                FT260_OTHER_ERROR
};
If you are seeing FT260_INCORRECT_CHIP_MODE then check the hardware configuration.
See FT260 – Full speed HID Class USB to UART/I2C Datasheet section 5.1 Device Interface Configuration. DCNF0 and DCNF1 are configured on hardware.
Ensure you have I2C enabled and are opening the correct interface number.

IO_ERROR may also be a hardware issue. I would advise test, evaluation and reference using the UMFT260EV1A if you are already using custom hardware.

Also refer to the examples provided with LibFT260.

The other alternative is not to use LiBFT260 and access the device with raw HID commands. See AN_394 User Guide for FT260.

Best Regards,
FTDI Community

Hi
Since this is not one of our products, we are unable to support it.
Product Manufacturers are responsible for supporting end-users of their products.
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:

https://ftdichip.com/wp-content/uploads/2020/08/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf

You should contact Analog Devices with regard to their software

Regards
FTDI Community

Hello,

You are already in contact with us via email about this enquiry.

Please feel free to post any resolution here to help other community users.

Best Regards,
FTDI Community