> On 8 Jun 2017, at 10:56, Paul Fertser <[email protected]> wrote: > > We already have some related information in README.OSX. Can you please > review it and clarify if anything is missing there or the wording is > suboptimal?
you mean the explanation on unloading the FTDI kext? this is suboptimal as approach, not as wording. FTDI is basically a proprietary virtual USART over USB, and the standard drivers available in recent macOS do exactly this, for example if I connect the RISC-V HiFive1 board I get two serial ports: crw-rw-rw- 1 root wheel 19, 10 Jun 8 12:48 /dev/tty.usbserial-fd1223A crw-rw-rw- 1 root wheel 19, 12 Jun 8 12:48 /dev/tty.usbserial-fd1223B 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? 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. 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. any thoughts? 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
