Hello,

Please note that our recommendations are not intended to contradict or replace the datasheet, and are intended as additional helpful advice only. The device datasheet still provides the most up to date device information and so you can still refer to the configurations shown there.

By powering your regulator from the same source as VCC, you can avoid the case mentioned whereby the IOs are at unknown states which is advantageous for many use cases.

Best Regards, FTDI Community

Hello,

The VCC and VCCIO supplies should power on and off together and so should be supplied from the same overall source (even if VCCIO is derived from a regulator, this regulator should have the same source as VCC).

For example, you could
- Power VCC, VCCIO, 3v3out from a 3v3 rail in your device (self powered config)
- Power VCC from USB 5V and power VCCIO from 3v3OUT on the FT230X (bus powered config)
- Power VCC from USB 5V and power VCCIO from a regulator sourced from USB 5V (bus powered config) giving 3v3 or 1v8 VCCIO.

If you use the first option, you can use the VBUS Sense CBUS line to sense USB Vbus through a voltage divider to put the device in a low power suspend state when no USB host is present.

The second and third options will use power from the USB port and so won't use as much battery power. You can feed USB Vbus through a divider into an input line on your MCU and your code can use this signal to tristate it's connections to the RxD and CTS lines of the FT230X (since these are both outputs from the MCU) so that you don't have leakage from the MCU to the FT230X in their idle high state.

Best Regards, FTDI Community

Hello,

As per the LibFT4222 User Guide, the Checksum is the summation of all data fields’ lower two bytes starting from the first byte, the sync word, to the latest data byte.

Is there any particular reason you wish to fool the checksum?

Best Regards,

FTDI Community

Hello,

The FT4232H can only be an I2C Master unfortunately but our FT200XD or FT201X would be a good solution. Please find details below. The devices both offer the same USB-I2C functionality but differ in the IC package size and number of CBUS lines.

http://www.ftdichip.com/Products/ICs/FT200XD.html
http://www.ftdichip.com/Products/ICs/FT201X.html

We also have development modules available which can be found at the bottom of these product pages above.

These devices are I2C peripherals and can be used via either VCP or D2xx applications on the PC side.  You would set the I2C address in the MTP memory in the chip using FT_Prog and can then have your Master perform I2C reads and writes to transfer the data.

Best Regards,
FTDI Community

Hello Stefano,

I believe one of our support engineers has replied to the email you sent to support1@ftdichip.com this morning.

Best Regards,

FTDI Community

Hello,

I believe your query is already being dealt with privately via email by our support team.

Best Regards,
FTDI Community

Hello,
Are you looking for an I2C master or slave?
Here are our USB to I2C solutions available which are all at least USB 2.0 and support I2C data transfers up to 3.4Mbps.

I2C slave only:
FT200XD
FT201X

I2C master only (using MPSSE engine. LibMPSSE could be used. See AN_177):
FT232H
FT2232H
FT4232H

I2C master only (using HID class driver. LibFT260 could be used.):
FT260

I2C master or slave:
FT4222H (using D2XX drivers and LibFT4222)
FT90x / FT93x (these are indeed MCUs and would require software development to bridge to the USB port. See AN_360 FT9xx Example Applications for more information).

We have Development Modules available for test and evaluation.

Best Regards,
FTDI Community

Hello,

Could it be that the compiler isn't running correctly on Windows 7?

Unfortunately we do not have extensive Delphi experience, the only examples we have available can be found at the following:
http://www.ftdichip.com/Support/SoftwareExamples/CodeExamples/Delphi.htm

Best Regards,

FTDI Community