Hello,

Yes that is correct when used in Input Mode, the input pins are pulled to VCCIO via internal 200kΩ resistors, so they will gently pull high unless driven by some external logic. These pins can be programmed to gently pull low during USB suspend (PWREN# = “1”) by setting an option in the internal EEPROM. But unfortunately you cannot disable the pull up entirely.

Best Regards,
FTDI Community

Hello,

The MaxPower Descriptor defines the maximum power that may be drawn by the peripheral from the USB host. The USB host will read this value during enumeration to determine if it can provide the desired current draw the device is requesting. If for example you change this setting to 500mA and the USB host cannot provide this much power to the device, then the device will not enumerate.

The MaxPower Descriptor relates to Bus Powered devices, when using a Self Powered design you can set this value to 0mA.

Best Regards,
FTDI Community

Hello,

Although the FT4222H uses a data byte of 8 bits, most SPI peripherals can still use this so long as you keep CS asserted as they still see this as one transfer.

It looks like this particular device has some kind of timeout if the clock sits low for more than 28ms but beyond that was there any other reason why it could not accept multiple bytes so long as CS is kept asserted?

MPSSE (for example the FT232H) would have been another option but can only do SPI modes 0 and 2 and it looks like this ADC may need mode 1.

Best Regards, FTDI Community

Hello,

The LibFT4222 API return code 1000 is FT4222_DEVICE_NOT_SUPPORTED.

Which revision of silicon are you using?

Which mode are you using the device in? Which hardware are you using?

Which version of the D2xx driver are you using and which version of LibFT4222?
Note the following versions for the 64bit dlls and libs:

.\CDM v2.12.28 WHQL Certified\amd64
.\LibFT4222-v1.4.4\imports\LibFT4222\dll\amd64

This issue has never been reported before.
Have you tried the 32bit and 64bit dlls with the standard examples provided with LibFT4222? This would take the python aspect out of the equation, if you say that it’s a problem with our dll:

.\LibFT4222-v1.4.4\samples

Unfortunately we have no support for Python, but you can check out the following information with respect to the D2xx driver (not specifically LibFT4222):

It is possible implement the D2XX driver in python scripts.

The following imports are required:

import os
import sys
import ctypes

And the library can be loaded in the following manner:

class D2XXTest(object):
    def __init__(self):
        #Load driver binaries
        if sys.platform.startswith('linux'):
            self.d2xx = ctypes.cdll.LoadLibrary("libftd2xx.so")
        elif sys.platform.startswith('darwin'):
            self.d2xx = ctypes.cdll.LoadLibrary("libftd2xx.1.1.0.dylib")
        else:
            self.d2xx = ctypes.windll.LoadLibrary("ftd2xx")
        print 'D2XX library loaded OK'
        print
        sys.stdout.flush()

Also see some other Third Party Implementations:

http://bleyer.org/pyusb/
https://pypi.org/project/pylibftdi/
https://pypi.org/project/pyftdi/
https://learn.adafruit.com/adafruit-ft232h-breakout/mpsse-setup
https://iosoft.blog/category/ftdi/ 
 
ctypes Wrapper for D2XX:
https://pypi.org/project/ftd2xx/

I found one for LibFT4222 also:
https://pypi.org/project/ft4222/

There also may be other FTDI Community users with Python knowledge and LibFT4222 who may be able to help you further.

Best Regards,
FTDI Community

Hello,

The following function should help:

USBH_device_get_descriptor(hDev, USB_DESCRIPTOR_TYPE_REPORT, index, offset, buffer)

USB_DESCRIPTOR_TYPE_REPORT comes from ft900_usb_hid.h.

Best Regards,
FTDI Community

Hello,

Can you please email your local support team and we can look into this issue further?

https://www.ftdichip.com/FTContact.htm

Then you can post any resolution here to help other community users.

Best Regards,
FTDI Community

Hello,

You have already emailed our support team on this issue.

Feel free to post any resolution here to help other FTDI Community users.

Best Regards,
FTDI Community

Hello,

Glad you have managed to resolve the issue.

Best Regards,
FTDI Community