On Thu, Jun 08, 2017 at 01:51:43PM +0300, Liviu Ionescu wrote: > this is suboptimal as approach, not as wording.
It has a link about registering a driverless kext and with that I guess you can make the driver ignore just one specific device, not all FTDI converters. > 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? They won't be working during the debug session, granted, but will start working after kext loading or OS restart. > and, if I remember right, exactly the same thing happens on Windows, > if I install the standard FTDI drivers, when I connect the same > HiFive1 board I also get two new serial ports. On windows you can install WinUSB specifically for a device, so it won't affect anything else. Another possible approach is to use UsbDk (see my other mail). > 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). if so, with an appropriate > implementation, using OpenOCD with FTDI probes on Windows and macOS > wouldn't be a no-go, as it is now. Serial port abstraction provided by an OS is certainly not adequate to be able to talk MPSSE to the chip I think, so that's not an option. Plenty of people are using FTDI debug adapters on windows and OS X already, as far as I know. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ 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
