FT232H is not the best choice, if the slave is a microcontroller. The FT232H doesn't support clock stretching.
It's easy to find, breakout boards are all over the place if you don't want to make your own board, and most of all, it's supported by PyFtdi, which was one point I made, for people who want to use Python.
Another benefit is that you can also use it for SPI, GPIO or as an USB FIFO, so it's very versatile.
But you're right, it doesn't support I2C clock stretching. I personally try to avoid clock stretching as much as I can in practice, so I personally don't see it as a big issue, but if you absolutely need to handle it, then agreed, look elsewhere. Make sure you absolutely need clock stretching though. (And I'm not sure I see why the fact you'd need to communicate with a MCU as I2C slave would imply having to use clock stretching necessarily.)
(One reason I usually avoid clock stretching is that it just "grabs" the bus, waiting for the slave to complete something, making any other communication on the bus meanwhile impossible, which kinda defeats the purpose of I2C unless there's only one slave on the bus. A "typical" use of clock stretching is for ADCs that will clock stretch until a conversion cycle has completed for instance, but most I2C ADCs, even when they support this mode, can usually be configured to not use clock stretching and allow polling flags instead, or via a "data ready" GPIO, which I find much better in practice.)
Home
Help
Search
Login
Register
