|
From: Anders M. <And...@ik...> - 2017-06-09 18:18:24
|
> On 8 Jun 2017, at 13:51, Liviu Ionescu <il...@li...> wrote: > > there are many other FTDI applications out there (I have and use some) which rely on this standard behaviour. what do you think will happen to all these devices if I unload the FTDI kext? If your other devices aren’t using specifically 2232H chips as serial ports, you can use a kext that matches only that VID/PID pair. > so, the natural question would be: is it possible to access the programming pins via the standard serial port? (in principle, not with existing OpenOCD support). Not that I’m aware of, but you could try asking on Apple’s USB developer mailing list or developer forums. 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. Regards, Anders |