Hello,

Please refer to the FT220X Product Page:

https://www.ftdichip.com/Products/ICs/FT220X.html

Please note that this is not an SPI master.

FT220X implements FT1248 which is a proprietary FTDI interface that allows for a synchronous parallel/ serial interface where the data bus may be 1, 2, 4 or 8 bit wide.
This is not a standard SPI slave.

Data transfer rates up to 1MByte/s.

These app notes should help you:

AN_206 FT1248-1 Bit SPI
AN_167 FT1248 Dynamic Parallel/Serial Interface Basics
AN_173 Establishing FT1248 Communications using a Morph-IC-II

Have you considered our latest SPI slave product the FT4222H?
Do you require an SPI master or slave?

Best Regards,
FTDI Community

Hello,

Yes that is correct. Please refer to the D2XX Programmer's Guide:

FT_DEVICE (DWORD)
FT_DEVICE_232BM = 0
FT_DEVICE_232AM = 1
FT_DEVICE_100AX = 2
FT_DEVICE_UNKNOWN = 3
FT_DEVICE_2232C = 4
FT_DEVICE_232R = 5 (also includes FT245R)
FT_DEVICE_2232H = 6
FT_DEVICE_4232H = 7
FT_DEVICE_232H = 8
FT_DEVICE_X_SERIES = 9

Best Regards,
FTDI Community

Hello,

Yes that is correct, Apple develop their VCP driver independently from our VCP driver.

Best Regards,
FTDI Community

Hello,

The D2XX driver is a dynamic library file on macOS and is not related to the kernel/driver extension migration currently happening with the VCP driver.

What issues are you seeing with the D2XX driver?

Hi,
we are in a similar situation here, we currently use libftd2xx.dylib with our VID/PID. Do you plan to release a libftd2xx.dext?

Best Regards,
Daniele

Best Regards,
FTDI Community

Hello,

You need something connected to the UART with CTS / RTS flow control signals.
Or set it to UART_FLOW_NONE.
At some point it writes enough to the UART to be waiting for a flow control event.

// set flow control
uart_iocb.ioctl_code = VOS_IOCTL_UART_SET_FLOW_CONTROL;
uart_iocb.set.param = UART_FLOW_RTS_CTS;
vos_dev_ioctl(hUART, &uart_iocb);

Best Regards,
FTDI Community

Hello

It is now 5 months since the first developer beta of Big Sur, why is there still no updated driver? Can there be at least an update on how far along it is, 10%? 90%?

Are you using a device with a non default VID/PID combination?

As far as I am aware our developers are still waiting on Apple clarifying some questions on .dext development. Unfortunately I do not have an updated schedule for release at this point. But this is a top priority for us and I will update when I have any new information.

Best Regards,
FTDI Community

Hello,

FT_IO_ERROR usually points to a hardware issue.

Please test with our known good hardware:

https://www.ftdichip.com/Products/Modules/SuperSpeedModules.htm

Also reference our known good software:

https://www.ftdichip.com/Support/SoftwareExamples/FT60X.htm

The post creator 'randomEngineer' may also be able to provide you with information from his original issue.

Best Regards,
FTDI Community

Hello,

What hardware are you using exactly?

What software are you using and what is the error message?

We have no knowledge of ECMSpy.

If it's 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.
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

If the product uses our standard driver (note that it may use custom drivers), usually windows will automatically find and install the driver if you are connected to the internet. Simply plug the device into the PC.
However, you can use the setup executable found on our website.
Note: you may need to save to PC, right-click and select run as administrator.
This will install the drivers on your PC with licensing information, so next time you plug in the device the device should be enumerated with those drivers.

Also, we cannot support any virtual type OS. There can be all sorts of problems that are out of our control.
You can find our supported drivers here:

http://www.ftdichip.com/FTDrivers.htm

If your target OS is Windows or Linux, please use it directly on that OS without any virtual machine.

Best Regards,
FTDI Community