Bug 1392 - ftdi not detected
Summary: ftdi not detected
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: ftdi-la (show other bugs)
Version: 0.4.1
Hardware: x86 Windows
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2019-06-19 16:58 CEST by selevo
Modified: 2019-06-21 09:55 CEST (History)
3 users (show)

gif animation of screen (331.02 KB, image/gif)
2019-06-19 16:58 CEST, selevo

Note You need to log in before you can comment on or make changes to this bug.
Description selevo 2019-06-19 16:58:09 CEST
Created attachment 531 [details]
gif animation of screen

see gif animation
Comment 1 Gerhard Sittig 2019-06-19 17:06:35 CEST
Could you tell the VID and PID of that specific device? The information 
that is available so far only claims it's "something FTDI".  Is it one of 
the supported chip types, does it match the VID:PID database that's encoded 
in the driver source?

Comment 2 selevo 2019-06-19 18:34:12 CEST
ide device:VID_0403&PID_6001
it match the VID:PID database
Comment 3 Uwe Hermann 2019-06-20 14:52:10 CEST
I've reproduced this, the reason why it (seemingly) didn't work is that you have to use Zadig to assign the "WinUSB" driver for the FTDI device if you want to use it with the ftdi-la driver:


This is *not* necessary if you want to use it with drivers that just need a "COM port", but ftdi-la doesn't use it as a COM port, thus needs the Zadig steps mentioned in the wiki.

I've updated the wiki pages to explicitly mention this.
Comment 4 selevo 2019-06-21 07:12:32 CEST
After replacing the driver, other programs will not work with this USB-COM adapter?
Every time you need to return the factory driver?
Comment 5 Uwe Hermann 2019-06-21 09:55:00 CEST
Yes, but it's just a few clicks in Zadig to switch drivers (no reboot required either).