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

Author Topic: Issue while detecting and communicating with FT260  (Read 508 times)

Rr42

  • Newbie
  • *
  • Posts: 2
    • View Profile
Issue while detecting and communicating with FT260
« on: May 31, 2022, 12:18:29 PM »

Hi,
I'm trying to design a board with the FT260 and an ESP-WROOM-02.
I followed the instructions given in the Driver installation guide (though Windows 10 21H1 [OS build: 19043.1706] did auto detect the driver). Still, Windows sees it as a "USB Input device" under "Human Interface Devices" in Device Manager, however, the guide shows it being detected as a "USB Serial Converter" under "Universal Serial Bus controllers" in Device Manager.
In addition, Windows doesn't seem to be able to identify the manufacturer's name.

I have attached (Device-manager-snip_inked-2.jpg) the snip of the Device Manager dialogue and usbview window side by side.

I have also attached my schematic for the FT260 (U3 in the schematic): FT260-schematic-2.jpg

I also tried compiling and running one of the library samples (getting_started sample) but it also doesn't seem to be able to connect/detect the device:
Code: [Select]
Number of devices : 27

Open device index:0 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#converteddevice&col01#5&2204aa2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:1 OK
Device path:\\?\hid#converteddevice&col02#5&2204aa2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:2 OK
Device path:\\?\hid#converteddevice&col03#5&2204aa2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:3 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#dll0945&col01#5&102ea23&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:4 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#dll0945&col02#5&102ea23&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:5 OK
Device path:\\?\hid#dll0945&col03#5&102ea23&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:6 OK
Device path:\\?\hid#dll0945&col04#5&102ea23&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:7 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#elan2d26&col01#5&a39bd1e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:8 OK
Device path:\\?\hid#elan2d26&col02#5&a39bd1e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:9 OK
Device path:\\?\hid#elan2d26&col03#5&a39bd1e&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:10 OK
Device path:\\?\hid#elan2d26&col04#5&a39bd1e&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:11 OK
Device path:\\?\hid#elan2d26&col05#5&a39bd1e&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:12 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#int33d2&col01#6&94dea51&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:13 OK
Device path:\\?\hid#int33d2&col02#6&94dea51&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:14 OK
Device path:\\?\hid#int33d2&col03#6&94dea51&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:15 OK
Device path:\\?\hid#intc816#3&36043c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:16 OK
Device path:\\?\hid#vid_0403&pid_6030#6&1e06c270&8&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:17 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#vid_1b1c&pid_1b33&mi_00&col01#8&2489eb5b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:18 OK
Device path:\\?\hid#vid_1b1c&pid_1b33&mi_00&col02#8&2489eb5b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:19 OK
Device path:\\?\hid#vid_1b1c&pid_1b33&mi_00&col03#8&2489eb5b&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:20 OK
Device path:\\?\hid#vid_1b1c&pid_1b33&mi_00&col04#8&2489eb5b&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:21 OK
Device path:\\?\hid#vid_1b1c&pid_1b33&mi_01#8&37ba0799&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:22 OK
Device path:\\?\hid#vid_8087&pid_0ac2#6&1318d6e9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Open OK

Open device index:23 NG, status: FT260_DEVICE_OPEN_FAIL
Device path:\\?\hid#virtualdevice&10#2&90c581f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:24 NG, status: FT260_DEVICE_OPEN_FAIL
Get Device Path NG, status: FT260_BUFFER_SIZE_ERROR
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:25 NG, status: FT260_DEVICE_OPEN_FAIL
Get Device Path NG, status: FT260_BUFFER_SIZE_ERROR
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device index:26 OK
Get Device Path NG, status: FT260_BUFFER_SIZE_ERROR
Open NG, status: FT260_DEVICE_OPEN_FAIL
Not FT260 device

Open device by vid pid OK

Not FT260 device

Press any key to continue . . .

Am I doing something wrong? or have I missed something in my design?
Thanks in advance!
Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 749
    • View Profile
Re: Issue while detecting and communicating with FT260
« Reply #1 on: June 01, 2022, 04:32:43 PM »

Hi
FT260 is a HID class device and does not use the standard VCP/D2xx drivers. LibFT260 can be used (or raw HID class commands. See AN_394 and AN_395.
https://ftdichip.com/wp-content/uploads/2021/02/AN_394_User_Guide_for_FT260.pdf
https://ftdichip.com/wp-content/uploads/2020/07/AN_395_User_Guide_for_LibFT260.pdf

Regards
FTDI Community 
Logged

Rr42

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Issue while detecting and communicating with FT260
« Reply #2 on: June 01, 2022, 05:48:09 PM »

Hi,
Thanks for the reply, I understand that this cannot create a COM port that software IDEs like the Arduino IDE use.
But will it be ok to program the ESP8266 using the FT260_UART_Write function in LibFT260 from the .BIN file that the Arduino software generates?

I would like to build some firmware for the MCU while I modify my design to use the other ICs like the FT231 that do create a COM port.
Logged

ffred

  • Newbie
  • *
  • Posts: 15
    • View Profile
Re: Issue while detecting and communicating with FT260
« Reply #3 on: June 02, 2022, 07:23:55 AM »

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

Logged