Is it possible to get the PL-2303 Driver to work on Apple Silicon Macs ?
Also to compile for macOS 11, 12 and 13 (Big Sur to Ventura)?
I have a Glucose Meter using PL-2303 I wish to get the data off via Python.

I have a question and was hoping you would be able to help me with this. I'm using the PL2303 driver on OS X 10.8 and I noticed that when I transmit a 0xFF byte it actually sends 2 0xFF bytes (I can see this on the TX pin using a CRO). I had a look at the source and noticed the code below, which I'm guessing is the cause.

if FIX_PARITY_PROCESSING

    if(*Buffer == 0xff)
        addBytetoQueue(Queue, 0xff);

endif

Is this correct behavior and if so is there a way around this? The device I'm talking to returns an error when I send a packet containing a FF byte.

Just FYI, I used the code below for testing below:

_fd = open([name UTF8String], O_RDWR | O_NOCTTY | O_NONBLOCK );

if (_fd != -1)
{
    struct termios newtio;

    bzero(&newtio, sizeof(newtio));
    cfmakeraw(&newtio);
    newtio.c_cflag = CS8 | CLOCAL | CREAD | PARENB;
    newtio.c_iflag = IGNPAR | IGNBRK;
    newtio.c_oflag = 0;
    newtio.c_lflag = 0;
    newtio.c_cc[VMIN]=0;
    newtio.c_cc[VTIME]=10;
    cfsetispeed (&newtio, B115200);
    cfsetospeed (&newtio, B115200);

    tcflush(_fd, TCIOFLUSH);
    tcsetattr(_fd,TCSANOW,&newtio);

    int flags = fcntl(_fd, F_GETFL);
    fcntl(_fd, F_SETFL, flags & ~O_NONBLOCK);
}


const uint8_t data[] = { 0xFF, 0x00, 0xFF, 0x00, 0xFF, 0x00, 0xFF, 0x00, 0xFF, 0x00 };
while (true)
{
    write (_fd, data, 1);
    usleep(100*1000);
}

Kind Regards,
Martin

In Driver_PL2303.cpp Line 1119:

    unsigned char       rname[10];

The array is not guaranteed to be null, nor is bzero() called. If the createSuffix() call at line 1150 uses the entire length of the buffer for the device serial number value then the strncpy() will leave a not-null terminated buffer. Below that call the value is used by setProperty() at line 1152:

fNub->setProperty( kIOTTYSuffixKey, suffix ) 

The incorrectly terminated string will result in a malformed property string, potentially a security issue, kernel panic, and makes the driver fail to generate /dev/tty.xxx entries.

Proposed fix

Add the following at line 1151:

bzero(rname,10)

closeQueue and flush do not reset InQueue.
They should both set Queue->InQueue = 0

Hi,

Just tried compiling using Xcode 7 Beta3 under ElCapitain and I get the following:

clang: error: no such file or directory: '/Users/courchea/Documents/mac-osx-pl2303/Driver PL2303/Driver PL2303-Prefix.pch'
clang: error: no input files

The checkin does not include a copy of the following files which are referenced in the xcode project, causing failure to compile without adding blank copies of these files:

• InfoPlist.strings
• Driver PL2303-Prefix.pch

Proposed fix:
Add these files to git checkin

There was no traffic through the serial port at that moment.

Problem report after reboot:
https://gist.github.com/kika/3668a04a03a43e4801f0

the /dev/tty.NoZAP-PL2303-XXXXX device name changes when I dock and undock my computer. So, I can have a config file for Minicom configured properly with /dev/tty.NoZAP-PL2303-XXXXX, undock, redock, and the device name will change to /dev/tty.NoZAP-PL2303-XXYYYY.

Why does this happen? Is there a way to fix the device name?

For OS 10.9 "Mavericks" Apple has included support for signed KEXTs, non-signed KEXTs will generate a warning dialog to the user.

Signing keys cannot be included in the git repository, however a README note should be included, and the "official" installer should use a signed copy of the KEXT. For more information see the Apple WWDC presentation "What's New in KEXTs"

Hi @bjarnoldus

I've just installed the "OS X 10.10-I64 (Yosemite, signed)" and i wanted to test it with Sanwa multimeret USB cable (found reference here: http://sourceforge.net/p/osx-pl2303/discussion/530718/thread/06e14f29/#fdcf/7901) but it appears as "/dev/tty.NoZAP-PL2303-00001083???" so for example CoolTerm can't connect to it. screen /dev/tty.NoZAP-PL2303-00001083??? 115200 also doesn't return anything.

The device name doesn't seem correct. Can I fix it somehow?