| Summary: | ftdi not detected | ||
|---|---|---|---|
| Product: | libsigrok | Reporter: | selevo <selevo> |
| Component: | Driver: ftdi-la | Assignee: | Nobody <nobody> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Gerhard.Sittig, soeren, uwe |
| Priority: | Normal | ||
| Version: | 0.4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Windows | ||
| Attachments: | gif animation of screen | ||
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? https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/ftdi-la/api.c;h=432f566f84ed71a00f38b077e065a0c28b926de7;hb=HEAD#l48 ide device:VID_0403&PID_6001 it match the VID:PID database 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: https://sigrok.org/wiki/Windows#Drivers 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. Thank's. After replacing the driver, other programs will not work with this USB-COM adapter? Every time you need to return the factory driver? Yes, but it's just a few clicks in Zadig to switch drivers (no reboot required either). |
Created attachment 531 [details] gif animation of screen see gif animation