Hello,

We have a new libmpsse version that you can try (V1.0.4).

Please contact your local support team for this:

https://ftdichip.com/technical-support/

The alternative is not to use LibMPSSE library and use D2xx driver direct which will give you more control:

To use I2C/SPI as a master (no slave functionality), see AN_135 MPSSE Basics and our existing MPSSE Example projects:
 
https://ftdichip.com/software-examples/mpsse-projects/
 
There are two options to use I2C/SPI modes with the MPSSE engine:
 
a.   Use LibMPSSE libraries. Example code is provided with the download. Source code is also provided.
b.   Use D2XX drivers direct. Example code is shown at I2C / SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.
 
Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library).

Best Regards,
FTDI Community

As an update, the support people reviewed my schematic, and found an issue -- an EEPROM is actually required for the FT232H's self powered operation mode, because you have to configure the chip to self powered in the EEPROM.  Also, ACBUS7 should be set so that the pin is pulled up  to 3.3V when USB VBUS is active.

That said, this still doesn't explain why it wouldn't enumerate on my board after the reworks, and I think I may have to give up on this chip for now.

Hi Terry,

we see no issue with this.

if you are looking for more control, you can utilize the MPSSE engine using the D2XX drivers directly. This will mean you will not have to rely on LibMPSSE.

To use I2C/SPI as a master (no slave functionality), see AN_135 MPSSE Basics and our existing MPSSE Example projects:
 
https://ftdichip.com/software-examples/mpsse-projects/
 
There are two options to use I2C/SPI modes with the MPSSE engine:
 
a.   Use LibMPSSE libraries. Example code is provided with the download. Source code is also provided.
Note there is a known issue with this library with I2C. See LibMPSSE Beta 1.0.2 which shows the source code change to allow you to rebuild.
b.   Use D2XX drivers direct. Example code is shown at I2C / SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.
 
Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library).

Best Regards
FTDI Community

about SPI Interface Speed

Hello,

could you please email your schematic to support1@ftdichip.com? we can then review it for you to see if there is anything that could be causing your issue.

Best regards
FTDI Community

Hello all!  I am working on a PCB design (open source here, the FT232H is on page 3) which uses an FT232H to provide USB to SPI/I2C/UART conversion.  I've been testing the first board for some time, and have been unable to get any response out of the FT232H chip.  I see that it's outputting power on the VPHY and VPLL pins, but it has not been responsive over the USB interface -- both USB pins seem to be stuck floating.

The elephant in the room with my design is that I didn't provide an EEPROM for the FT232H, since the datasheet indicates it's not required (this board will only be used internally and I don't need to use a custom VID/PID or any permanent configuration).  However, I couldn't find any examples whatsoever of how to connect the EEPROM pins when there isn't an EEPROM on the board, so I wasn't entirely sure what to do.  Originally I tried pulling EEDATA low, and then I tried reworking the board to pull all three EEPROM pins high, but neither seemed to produce a response.

Things I have tried so far:

• Pulling pin 31 (ACBUS7/PWRSAV#) high in case the chip is in sleep mode (even though the datasheet indicates that this function is disabled without an EEPROM
• Replacing the chip on the board
• Pulling all the EEPROM pins high
• Cutting the traces from the internal USB hub and bodge soldering on a USB cable direct to my PC (so I can rule out the internal hub)
• Measuring voltages on every pin.  I don't remember the exact results but there was nothing that seemed abnormal (except that, when I had the pulldown on EEDATA, it was at like 0.4V
• Attaching a 1Ghz logic analyzer to the USB traces.  Did not observe any activity other than the host device trying fruitlessly to reset the FT232H

After all this, I'm about out of ideas.  Does anyone know if there's anything special I need to do to get the FT232H to work without an EEPROM attached?  Are there any other troubleshooting steps I can do to diagnose the issue?  I'm just about to give up and redesign with a competitor chip (CY7C65211), so any tips would be appreciated!

Thank You very much

Hello,

Our devices can't simulate regular flash memory.

Best Regards,
FTDI Community

And the second question, please. Can we implement a compound USB device using FTDI 600 and Dx200 or Dx300? One function will be regular file memory (like regular flash memory), and the second will be information conversion. We have implemented the second part. I'm interested in the first function. Can your device (ftdi) simulate regular flash memory. Thank you.

Thank you, Mister. We will make a decision and I will write to you. Moreover, we are going to change FTDI 200 to FTDI 600. But this, I think, does not make the problem go away