FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - bludin

Pages: [1]
1
Discussion - Software / Re: FT260 LibFT260 I2C Flags
« on: October 07, 2019, 05:27:25 PM »
AN_395 doesn't explain how to use the I2C flags for a read-from-register (=combined write/read operation) and the examples do not contain this either, as far as I can see.
I would expect to work the way I outlined it in my initial post, however, it is confusing that there is only an enumeration for FT260_I2C_START_STOP but not for FT260_I2C_REPEATED_START_STOP.

Thanks for your help,
Beat

2
Discussion - Software / FT260 LibFT260 unknown ftStatus 19
« on: October 07, 2019, 09:32:40 AM »
In my test setup, FT260_I2CMaster_Read returns no data and ftStatus = 19 in about 20% of the cases.
Appendix C of AN_395_User_Guide_for_LibFT260.pdf only explains ftStatus 0-18 (17 being FT260_I2C_READ_FAIL).
What does 19 indicate?

see https://www.ftdichip.com/Support/Documents/AppNotes/AN_395_User_Guide_for_LibFT260.pdf

PS: the failure rate seems to be largely independent of the baud rate (100KHz, 400KHz, 1MHz), so bus capacitance is most likely not the problem.

3
Discussion - Software / FT260 LibFT260 I2C Flags
« on: October 04, 2019, 05:38:57 PM »
Which flags should be used to make a standard combined read register operation with the write and read operations respectively?

Logically, I would presume:
  • ftI2CMaster_Write with FT260_I2C_START (0x02)
and
  • ftI2CMaster_Read with FT260_I2C_REPEATED_START + FT260_I2C_STOP (0x03 | 0x04 = 0x07).

Is this correct?

4
Discussion - Drivers / Re: LibFT260.dll 64-bit
« on: September 24, 2019, 06:52:48 AM »
Excellent. Works like a charm. Thanks.

5
Discussion - Drivers / LibFT260.dll 64-bit
« on: September 23, 2019, 02:46:30 PM »
I believe that the current LibFT260.dll is 32-bit (so it can't be called from 64-bit Python via cytpes). If my suspicion is correct, could you supply a 64-bit version please?

TIA, Beat

6
Our customer who will do the software uses C++ (while we're mostly using Python ourselves for testing purposes mostly).

Among the sensors, there's a number of proximity sensors. Ultimately, they only serve to detect whether a slot is occupied or not. Rather than polling each sensor, this could be read out more elegantly via the INT lines and GPIOs.
You only mention the GPIOs of the FT232H. The FT260 also has 14 DIOs, two of which will be used for the I2C bus, so there should be 12 left that could be used as GPIOs, right?

Thanks a lot for your help.

7
Hello -

For a project that involves configuring and reading out several I2C-sensors from a PC via USB, I'm trying to find the best solution for a USB-I2C(master) bridge. It would be great if the chip also offered >=11 GPIs to read out the INT lines of the sensors (and maybe one GPO to control their RESET lines). As far as I can see, both the FT232H and the FT260 would fit the bill. There seem to be more libraries/support available for the FT232H on the one hand but getting the right driver to install may be a bit cumbersome. On the other hand, the FT260 needs less external components and no low-level driver installation (as far as I understand) but I'm not sure whether an HID device is suitable at all (since I have little knowledge about this) and whether more than one I2C slave can be addressed. Basically, we want to make it as easy as possible for us to develop the hardware, as easy as possible for our customer to develop the software and as trouble-free as possible for the user to install the device. Knowing that this will be a highly specialized low-volume product, what would be your recommendation? 

Thanks a lot in advance,
beat

Pages: [1]