The FTDI drivers on some macOS versions may cause an error while trying to open the reader by some of the µFR SDK tools.
If you are about to use the macOS Catalina and later version(s), you may have some trouble using the ReaderOpen() or ReaderOpenEx() functions. In case you get the “READER_OPENING_ERROR (0x54)” status, please check the following:
- macOS Catalina and consequently Big Sur should rely on their own AppleUSBFTDI driver.
- To run our SDK properly, you should unload any other currently present driver.
- Check the loaded FTDI drivers with the following command: kextstat | grep -i ftd
- If the “com.FTDI.driver.FTDIUSBSerialDriver”, or a similar string without the “Apple” string in its name is listed in the terminal output, you need to unload it.
For example, for testing purposes, we’ve used the following command to unload a sufficient driver:
sudo kextunload /Library/StagedExtensions/Library/Extensions/FTDIUSBSerialDriver.kext
After this step, there was no trouble executing the ReaderOpen/ReaderOpenEx functions from our API.
We also copied the dylib file to /usr/local/lib:
sudo cp Desktop/D2XX/libftd2xx.1.4.22.dylib /usr/local/lib/libftd2xx.1.4.22.dylib
These two steps should solve all the FTDI driver communication issues between the reader and the host.
