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