Hi,
just to report informations about some tests I did (after a long pause on my FT260 project..) on a small dev board. I put a UMFT260EV1A on it, with a MCP23008 I/O expander connected to 4 buttons and 4 Leds and I connected the MCP23008 INT pin to GPIO3 (INTRIN/WAKEUP) of the FT260.

I had to activate the two HID ports, for I2C & UART, because with only the I2C it wasn't working.. (so the DLL is really using the UART to read the interrupt flag)

so, from LibFT260, I used FT260_UART_Init, FT260_SetInterruptTriggerType, FT260_SetWakeUpInterrupt , then FT260_I2CMaster_Init.
after that I send the config to the MCP23008 to activate the interrupt in open drain mode when I push a button.
and then I could use F260_CleanInterruptFlag to see if an interrupt occured and set a Led ON. and it worked ! 

so the Interrupt flag can be used.

hello,
it would be nice to also have replies on the forum here. it would allow to have a source of information for the missing points in the documentation...

I'm also looking for info about the interrupt possibility with the FT260 and the Windows DLL.
actually it's not clear what we can do with the interrupt and how to use it.
in AN395 there's two function in the "FT260 general functions": FT260_SetWakeupInterrupt & FT260_SetInterruptTriggerType.
but there's also two functions in the "UART functions": FT260_GetInterruptFlag & FT260_CleanInterruptFlag.
if I only activate the I2C interface but not the UART, can I still use the two functions get & clean interruptFlag, since those two don't have "UART" in their name unlike the other functions in the UART section ?
does the SetWakeupInterrupt & SetInterruptTriggerType functions are related to the functions GetInterruptFlag & CleanInterruptFlag ? is it the "same" interrupt ?
can I use those functions to receive interrupts from I2C ICs (like when an input change on a I/O expander) or are those functions dedicated to USB transactions ?

thanks..

Ok, thanks very much for watching.
(Had to do a little pause in my development, but hope to get back to it very soon..)

hello,

yes of course I did unplug / replug it between the two results I post. even did it several times and also see that I can recover the original result after erasing the eeprom with FTPROG.
and I got the same thing on Windows 8.1 and Windows 10 (didn't have time to test on Windows 11 right now).

and what I posted in code sections is an extract from the USBview I take on FTDI website (I put the link at the bottom of my original post..).

 was thinking that my questions here (and even more the replies) could benefit to everyone. but I could also ask to the mail support next time if that's the better way for that.
(and there will be more questions coming, because I already found a few more errors and unclear points in the different pdf docs for the FT260; I just don't have enough time to verify everything before asking right now..)

thanks.
ffred

to everyone interested, I got a reply by mail :

I have got confirmation:
FT260_GetInterruptFlag reads but leaves the flags set and FT260_CleanInterruptFlag reads but also clears the flags.

Hi,
the documentation is nearly the same for the two functions FT260_GetInterruptFlag & FT260_CleanInterruptFlag. they're defined the same way, with the same parameters.
the only difference is the "summary" : get interrupt flag for one and clean the interrupt flag for the other, but they both got the same pbFlag parameter.
could be nice to have more explanation about that.

it's clear that with FT260_GetInterruptFlag we can read the interrupt flag and probably it's not reset after that.
but can I imagine that FT260_CleanInterruptFlag also read the interrupt flag AND reset it..??
if not, what is the pbFlag for ?

you should add a few words to FT260_CleanInterruptFlag summary to make things clearer...

thanks.
ffred

Hi Rr42,

yes, FT260 is HID, and you got two HID devices on one FT260. so you will have to use the LibFT260 library (or another one for direct hid communication) and you won't be able to use it as a classic COM port..

the output you give don't seem to be the one from the "getting_started" example, but from the "open_device" example.

now there's something problematic with the output you show (and I got something similar here after running the same example), because the index 1, 2, 5, 6,... are reported to be opened ok, but I don't see any FT260 VID/PID in the device path associated.
in fact, you got one on index 16 !

the problem I think is that the example is not using the good method to select and open an FT260 device. of course the library shouldn't reply opened ok for an hid device that is not an FT260, but there's a way to work around that here : https://github.com/fs000x/ft260UI
if you look in "ft.py", it read the device_path for every index and try to open it only if this device_path contain the VID/PID corresponding to the FT260. will do it like that in my code too..

ffred

it's ok now (didn't change my code). 
I also installed Microsoft Visual C++ 2010 x64 Redistributable.
thanks.
ffred