Hello LabVIEW Community,
I'm working on code to perform I2C writes via the FT260 USB HID-to-I2C bridge device. I'm using the LibFT260.dll provided by FT. My hardware for initial development is the UMFT260EV1A eval board.
When I attempt to execute an I2C write I see no traffic on the I2C bus, which I'm probing with an o'scope.
I'm following the sequence outlined by example code from FT to initialize the I2C interface and attempt a write:
1. Discover and open HID interfaces using FT260_OpenByVidPid function.
2. Reset the I2C Master using FT260_I2CMaster_Reset function.
3. Initialize the I2C Master with 100kHz clock using FT260_I2CMaster_Init function.
4. Write to slave address 56 using FT260_I2CMaster_Write function.
5. Close the HID interfaces.
Things I have verified:
- I successfully see I2C traffic when I use a coworker's utility that was developed for Linux using raw HID packets and does NOT use the LibFT260.dll. I know my hardware is good.
- Using other functions in the LibFT260.dll to do other things works. For example, I can toggle GPIO and get status data from the FT260. I know I can communicate to the FT260.
- All I2C function calls to the DLL respond with OK status. The functions seem happy with my arguments.
The facts above lead me to believe something about my usage of the DLL, specifically the I2C functions, is not quite correct. I just cant figure out what it is.
I have attached my code, along with the DLL. Drill down in I2C 64bit Troubleshooter.vi for the sequence outlined above. Can you see any errors in what I have so far? Where could I be going wrong?
Thank you,
Aaron
