<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I deleted the third-party (FTDI) drivers and rebooted. It works now.<div class=""><br class=""></div><div class="">Here’s the instructions I followed:</div><div class=""><a href="http://apple.stackexchange.com/questions/166906/how-can-i-uninstall-the-ftdiusbserialdriver" class="">http://apple.stackexchange.com/questions/166906/how-can-i-uninstall-the-ftdiusbserialdriver</a></div><div class=""><br class=""></div><div class="">command history:</div><div class=""><div style="margin: 0px; font-size: 10px; line-height: normal; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">2015<span class="Apple-tab-span" style="white-space:pre"> </span>sudo pkgutil --forget com.FTDI.driver.FTDIUSBSerialDriver</span></div><div style="margin: 0px; font-size: 10px; line-height: normal; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">2016<span class="Apple-tab-span" style="white-space:pre"> </span>sudo pkgutil --forget com.FTDI.ftdiusbserialdriverinstaller.FTDIUSBSerialDriver-2.pkg</span></div><div style="margin: 0px; font-size: 10px; line-height: normal; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">2017<span class="Apple-tab-span" style="white-space:pre"> </span>sudo pkgutil --forget com.FTDI.ftdiusbserialdriverinstaller.postflight.pkg</span></div><div style="margin: 0px; font-size: 10px; line-height: normal; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">2018<span class="Apple-tab-span" style="white-space:pre"> </span>sudo pkgutil --forget com.FTDI.ftdiusbserialdriverinstaller.preflight.pkg</span></div></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 13, 2016, at 5:45 PM, Rodney Radford <<a href="mailto:ncgadgetry@gmail.com" class="">ncgadgetry@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Yes... they did back out the change that bricked the hardware, but if the hardware was used with the old driver, it does not un-brick when used with a new driver. They actually changed the vendor ID in the chip so no driver can find it again (even under Linux). So once brick'ed it stays brick'ed unless you can reprogram the vender ID.<div class=""><br class=""></div><div class="">The latest Windows change is to send a garbage string from the driver back to the app, so not brick'ed, but also not usable. The advantage of this system is that switching drivers or OS's does restore the functionality again (ie: not permanent changes to the device).</div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Apr 13, 2016 at 5:35 PM, <span dir="ltr" class=""><<a href="mailto:jonjwolfe@anibit.com" target="_blank" class="">jonjwolfe@anibit.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FTDI quickly backpeddled on their counterfeit-bricking drivers from 2 years, but apparently there is a new FTDIgate v2 a couple months ago that I missed:<br class="">
<br class="">
<a href="http://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/" rel="noreferrer" target="_blank" class="">http://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/</a><br class="">
<br class="">
This one doesn't brick the hardware per se, but will make it potentially unusable with the latest drivers. It doesn't affect Linux because the drivers are open-source, I don't know about OSX.<span class=""><br class="">
<br class="">
<br class="">
<br class="">
On 2016-04-13 15:10, Rodney Radford via TriEmbed wrote:<br class="">
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Could you be a victim of FTDI-gate?<br class="">
<br class="">
If the answer to both of these questions is yes:<br class="">
* Have you ever used this FTDI adapter on a Windows box?<br class="">
* Is it possible you have an FTDI clone?<br class="">
<br class="">
<a href="http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/" rel="noreferrer" target="_blank" class="">http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/</a><br class=""></span>
[3]<div class=""><div class="h5"><br class="">
<br class="">
On Wed, Apr 13, 2016 at 2:53 PM, Alex Davis via TriEmbed<br class="">
<<a href="mailto:triembed@triembed.org" target="_blank" class="">triembed@triembed.org</a>> wrote:<br class="">
<br class="">
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="h5">
Anyone run OSX 10.11 and use an FTDI with an Arduino-type board? I<br class="">
had<br class="">
repaired some broken HT1632-based LED displays with a new driver<br class="">
chip<br class="">
and wanted to test them, and the nearest thing at hand was an AVR<br class="">
1284P<br class="">
"mighty mini" board, which needs an FTDI to program it.<br class="">
<br class="">
I hadn't used that since last year, and I've gone through a few<br class="">
Arduino<br class="">
verions since, so I had to go through the routine of updating my<br class="">
"hardware" directory with a version which works with 1.6.7.<br class="">
<br class="">
My issue is when I try to program via the FTDI, something goes<br class="">
wrong,<br class="">
which then causes OSX to dump the driver, which makes the entry in<br class="">
/dev/<br class="">
disappear. This is apparently due to a bug in the FTDI-supplied<br class="">
driver,<br class="">
and supposedly the solution is to use a utility to delete the kext<br class="">
for<br class="">
it.<br class="">
<br class="">
Anyone gone through this successfully? I'm not SOL at the moment,<br class="">
as I<br class="">
can use my AVRISP MKII to program it directly through the ICSP<br class="">
connector, but I do have other boards which lack that and need the<br class="">
FTDI.<br class="">
<br class="">
--<br class="">
"The theater of noise is proof of our potential."<br class="">
| | (¯ / |¯ |V| | ¯|¯ |¯) | / | | | |¯ (¯ /¯ / |V|<br class="">
|-||_ (_ / |_/ @| | |-| | | | / |^| | |_/ (_ . _ / | |<br class="">
<br class="">
You won't find me on Facebook.<br class="">
<br class="">
_______________________________________________<br class="">
Triangle, NC Embedded Computing mailing list<br class="">
<a href="mailto:TriEmbed@triembed.org" target="_blank" class="">TriEmbed@triembed.org</a><br class="">
</div></div><a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a> [1]<br class="">
TriEmbed web site: <a href="http://triembed.org/" rel="noreferrer" target="_blank" class="">http://TriEmbed.org</a> [2]<br class="">
</blockquote>
<br class="">
<br class="">
<br class="">
Links:<br class="">
------<br class="">
[1] <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br class="">
[2] <a href="http://triembed.org/" rel="noreferrer" target="_blank" class="">http://TriEmbed.org</a><br class="">
[3]<br class="">
<a href="http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/" rel="noreferrer" target="_blank" class="">http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/</a><span class=""><br class="">
<br class="">
_______________________________________________<br class="">
Triangle, NC Embedded Computing mailing list<br class="">
<a href="mailto:TriEmbed@triembed.org" target="_blank" class="">TriEmbed@triembed.org</a><br class="">
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br class="">
TriEmbed web site: <a href="http://triembed.org/" rel="noreferrer" target="_blank" class="">http://TriEmbed.org</a><br class="">
</span></blockquote>
<br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""><div class="">
<div class="">“The right of the people to be secure in their persons, houses, papers, and </div><div class=""> effects, against unreasonable searches and seizures, shall not be violated, </div><div class=""> and no Warrants shall issue, but upon probable cause, supported by Oath </div><div class=""> or affirmation, and particularly describing the place to be searched, </div><div class=""> and the persons or things to be seized.”</div><div class=""><br class=""></div><div class="">US Constitution 4th Amendment - It's The Law</div><div class=""><br class=""></div><div class="">|\ | (¯ \/ |¯\ |V| |\ ¯|¯ |¯) | \/ | | | |¯\ (¯ /¯ /\ |V|</div><div class="">|-||_ (_ /\ |_/ @| | |-| | | \ | /\ |^| | |_/ (_ . \_ \/ | |</div><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">
</div>
<br class=""></div></body></html>