> On 9 Jun 2017, at 21:18, Anders Montonen <[email protected]> wrote:
>
> ... IMO the right thing would be for device vendors to use a custom VID/PID
> when the FTDI chips are not used as plain serial ports, and supply the
> necessary inf files/kexts/udev rules to map the wanted functionality.
that's exactly my conclusion too :-(
the fact is that standard ftdi drivers, when encounter standard ftdi ids,
associate them with virtual serials. at least on macOS and windows.
on macOS the only 'legal' solution is to use devices that have vendor IDs, so
the association with the default virtual serial driver is no longer done.
to be noted that some ftdi devices have an eeprom and with an windows program
provided by ftdi, some settings can be changed.
for windows, instead of using Zadig, I discovered a less invazive method:
libusbK:
https://sourceforge.net/projects/libusbk/
it generates a WinUSB driver for a given vid/pid. this driver has a more or
less usual setup, that can be not only installed, but also uninstalled. :-)
unfortunately, for macOS there is no such trick...
regards,
Liviu
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
