This all went swimmingly but did not help even after a reboot, and not obvious clue as to why. No clue that there is a problem with drivers. Importantly there was no pop-up or prompt or error of any sort when connecting the lead, it simply appears in /dev/ as you would expect. It is recognised and the /dev/ created as you would expect, but shows the resource busy error.
It looks like FTDI USB serial should work on a Mac without needing custom drivers, but it does not work. Someone even suggested it was not a genuine FTDI chip, so I ordered a cable from RS, and the same issue persisted.Īfter a lot of googling, it seems to me that there must be some sort of bug in Catalina.
Some pages even suggested update to python, but I confirmed that even a simple cat of /dev/cu.usbserial-A. said the same, so not python. Using lsof I confirmed it was not open by something else. The problem is that googling this gets a lot of people saying they have this issue and a lot of answers which didn't help me - it seems many people do this to themselves by having the device open from some other app. New MacBook Pro, using an FTDI USB serial cable (used to program ESP32 chips). In an effort not to be DenverCoder9, here is what I found.
