Setcommstate ошибка 87

I’m working on some basic serial communication stuff and I’ve come across this issue that I can’t seem to work around. I’m trying to set my comm state to a certain baud rate, stop bit, parity bit and data size. As shown in my example code below, I’m getting the current COM state from getComState and modifying some values.

    DCB dcb = { 0 };
    // for set timeout for readfile function
    COMMTIMEOUTS timeouts = {   0,  // interval timeout. 0 = not used
                                0,  // read multiplier
                                500, // read constant (milliseconds)
                                0,  // Write multiplier
                                500 // Write Constant
                            };

    if (SetCommTimeouts(usb_device, &timeouts) == FALSE) {
        "ERROR: SetCommTimeouts failed with error %d.n", GetLastError();

        add_log_trace("ERROR: SetCommTimeouts failed with error %d.n", GetLastError());
    }

    BOOL fSuccess;
    //  Initialize the DCB structure.
    SecureZeroMemory(&dcb, sizeof(DCB));
    dcb.DCBlength = sizeof(DCB);

    //  Build on the current configuration by first retrieving all current
    //  settings.
    fSuccess = GetCommState(usb_device, &dcb);

    //  Fill in some DCB values and set the com state: 
    //  115,200 bps, 8 data bits, no parity, and 1 stop bit.
    dcb.BaudRate    =   CBR_115200;     //  baud rate
    dcb.ByteSize    =   8;             //  data size, xmit and rcv
    dcb.Parity      =   NOPARITY;      //  parity bit
    dcb.StopBits    =   ONESTOPBIT;    //  stop bit

    fSuccess = SetCommState(usb_device, &dcb);

However, this function tends to fail me no matter what I do. The error is pretty straight forward(error code 87) which signifies that there is an invalid parameter. After doing some research the solution seems pretty obvious. However, I’ve tried the solutions listed below including some sanity test and nothing seems to work.

• Setting the DCB struct to only initialize with the size
• Disabling handshake in the DCB struct
• Setting the DCB struct to no values
• Using an alternate way to set the DCB struct besides GetCommState
• Setting the CommState to the same state that I get from GetCommState
• Ensuring the COM port name is correct when opening the file

I’ve also taken into account the remarks that were left by MSDN developers in regards to using the SetComState function however, the function call continues to fail nevertheless.

I’ve attempted running similar code on a linux box and setting the com port works fine. I came across some articles where they’re stating that Windows has messed up their usbser.sys file which handled communication between the OS and the device.

• Accessing COM-port with Windows 10
• USB serial interface problems with Windows 10

I’m tempted to try replacing the usbser.sys file with an older one however I’d wanted a second opinion in regards to this issue. Is this a common issue? Is there a more straight forward solution? I’d appreciate if someone could point me in the right direction or correct me in some of my assumptions and methodology. Hopefully this post isn’t too board in terms of scope. I’m just trying to set my baud rate right using SetCommState. Lolz.

Thank you

I have some stupid code to access a Windows COM-port (just some pseudo-code of the most relevant functions):

// open device:
COMMTIMEOUTS timeouts;
DCB          ComSettings;

memset(&ComSettings,0,sizeof(ComSettings));
ComSettings.DCBlength=sizeof(DCB);
*fd=CreateFile(serialParams>port,GENERIC_READ|GENERIC_WRITE,0,0,OPEN_EXISTING,0,0);
GetCommState(*fd,&ComSettings);
ComSettings.BaudRate=9600;
ComSettings.ByteSize=8;
ComSettings.Parity=NOPARITY;
ComSettings.fParity=0;
ComSettings.StopBits=ONESTOPBIT;
ComSettings.fOutX=FALSE;
ComSettings.fInX=FALSE;
ComSettings.fBinary=TRUE;
ComSettings.fDtrControl=DTR_CONTROL_DISABLE;
ComSettings.fRtsControl=RTS_CONTROL_DISABLE;
ComSettings.fAbortOnError=FALSE;

SetCommState(*fd,&ComSettings);

timeouts.ReadIntervalTimeout        =MAXDWORD;
timeouts.ReadTotalTimeoutMultiplier =0;
timeouts.ReadTotalTimeoutConstant   =0;
timeouts.WriteTotalTimeoutMultiplier=0;
timeouts.WriteTotalTimeoutConstant  =250;

SetCommTimeouts(*fd, &timeouts);

Reading of data from serial port is done with

ReadFile()

and writing with

WriteFile()

In my particular case the device is a USB gadget which connects as serial interface and where speed-settings and other things do not really matter.

This code is working fine with all Windows variants including 8.1 but for Windows 10 some users report there is no communication possible with the device. Unfortunately I do not have the related Win10 version for testing.

So my question: are there some issues/important changes in Windows 10 which could cause such a behaviour or require some changes in serial port communications?

Thanks!

****** Update ******************************************************************

Just as update to this: function SetCommState() fails with an error 87 (ERROR_INVALID_PARAMETER). Here it does not matter if I set own parameters, if I use the data received from GetCommState() or if I completely initialise and configure the DCB-structure. So…is this a known bug in SetCommState() of Win 10?

Just to note: it fails only in 4 of 5 cases, so it is not a systematic error, but a random one!