QSerialPort open error code 10

addebito

@Christian-Ehrlicher you are right but there isn't a call ".utf16()" in QByteArray class so I've replaced with a mistake.

Now the CreateFile with L"COM5" works. I don't get any error.

Christian Ehrlicher

@addebito said in QSerialPort open error code 10:

QByteArray

Because it should be QString :)

Ok, then you have to debug by yourself, don't see what should go wrong within QSerialPort code nor can I test it locally.

addebito

@Christian-Ehrlicher said in QSerialPort open error code 10:

Ok, then you have to debug by yourself, don't see what should go wrong within QSerialPort code nor can I test it locally.

Yes but is not as easy as I thought.
I've run the maintenance QT software and I've check if the source was installed.

I've created a simple demo project and added this lines inside the .pro

include(C:/Qt/5.14.2/Src/qtserialport/src/serialport/serialport-lib.pri)

I have to add also these lines to resolve some issues

INCLUDEPATH += "C:/Qt/5.14.2/Src/qtbase/include/QtCore/5.14.2/QtCore"
INCLUDEPATH += "C:/Qt/5.14.2/Src/qtbase/include/QtCore/5.14.2"
INCLUDEPATH += "C:/Qt/5.14.2/msvc2017_64/include/QtCore/5.14.2"

But now, when I compile I get this error:

definition of dllimport static data member not allowed

I think there is something wrong in my approach...
How should i do to debug QSerialPort class?
thank you for your time and your patience.

Christian Ehrlicher

I don't understand why you try to compile QSerialPort by yourself. Install the debug symbols and sources, compile your app with debug informations, add a breakpoint on QSP::open() call and step into the call.

addebito

@Christian-Ehrlicher what you means with "Install the debug symbols and sources"?

I'm in debug with a breakpoint but if try to step into by F11...

KroMignon

@addebito said in QSerialPort open error code 10:

what you means with "Install the debug symbols and sources"?

With Maintenance Tool, select "Sources" and "Qt Debug Information Files" for the select Qt Version:

Then build your project in "Debug" and start debugging.

addebito

@KroMignon I've already installed but I don't see anything when I step into...
I see only the debugger on line 118 (qflags.h) and after F11 again the debugger return on my mainwindow.cpp.

J.Hilk

@addebito
did you add the sources inside QtCreator ? In the Debugger section

Christian Ehrlicher

@addebito said in QSerialPort open error code 10:

I see only the debugger on line 118 (qflags.h) and after F11 again the debugger return on my mainwindow.cpp.

That's correct since first the flags ctor is called, then hit F11 again to step into the function call.

addebito

@J-Hilk Thank you. Now I can step into.

Now I found the line when the class call "return false"

SetCommState return 87

J.Hilk

Well, if I'm not mistaken, then thats the error code for an invalid parameter 🤷‍♂️

What Windows version do you use ? Is it up to date ? The windows Api changes regularly

addebito

@J-Hilk

https://docs.microsoft.com/it-it/windows/win32/debug/system-error-codes--0-499-?redirectedfrom=MSDN

Yes, from msdn
87 The parameter is incorrect.

What kind of parameters ??
Ohh Windows...
I'm definitely being roasted.

Windows 10 home
Auto update activated
QT 5.14.2

Any other suggestions?

kuzulis

@addebito said in QSerialPort open error code 10:

Any other suggestions?

Build qtserialport from sources (just download the sources, open in QtCreator and re-build all targets, include examples). And then from the QtCreator run the terminal-example under the debugger, open your serial port and try to debug as usual.. Then, try to comments-out step-by-step the functions like qt_set_{common|baudrate...}, and then re-build qtserialport and try again.. And then you can look wich function brokes the work.

For this, you can temporary rename the qtserialportd.dll in your installed Qt path.. In this case will be used another dll compiled in qtserialport build directory (make sure that this directory is in `run environment' PATH of your project settings in QtCreator).

addebito

Thank you @kuzulis , I'll try.

I've done another test, same hardware and same computer but with Linux Ubuntu 20.04.1 LTS.
No problem, I can open the "ttyACM0" write and receive data.

Christian Ehrlicher

Since you can already call CreateFile() simply go further and call GetCommState/SetCommState and set the parameters one by one according to what Qt does and see which one fails. Maybe first try to call SetCommState without modifying the DCB structure at all.

addebito

@kuzulis I've try to recompile step by step and try with the qt_set_{...} commented-out but... nope I've commented all the 5 lines without good result.

BUT ....unbelievable...
I've try more than one time.
If I run the terminal example under Linux, everything works fine, after that if I restart the computer without power off the board and run Windows instead Linux.... The terminal example works !!!
If I switch OFF and after, switch ON again the board the terminal example under Windows going back to fail !!

So, follow step by step my tests

run my lapton on Linux partition and run the Terminal Example

Restart the computer, run the Windows partition and run the Terminal Example

Switch off/on the board, the Terminal example doesn't work.

If I run Hercules... it's still working

ollarch

Can you try to remove the USB device, plug it again and start your software?
If if fails, could you try to delete the COM controller from Windows devices and force Windows to search for new devices?

addebito

@ollarch thank you for your suggestion but doesn't work

Same error:
"Can't open COM5, error code 10" "Parametro non corretto."

I've unistall the COM driver in Windows device manager.
Unplug the COM in the same USB.
Windows reinstall the drivers.
Run my application but doesn't works.

I've tried the same procedure with another USB port.

Now I'm trying the last @Christian-Ehrlicher suggestion.

addebito

This is my last test for today....

I run the terminal example under Linux (it's works fine)
Restart the computer without unplug or switch off the board
Run hte new code to get the com state (GetCommState). Thanks @Christian-Ehrlicher
Print screen

Call SetCommState with these parameters... works under Windows.
Power off the board
Power on the board
Run again my demo and get the com state as before.
Apart the usual settings like 9600 8 N 1.... I see that Linux set the port with the RTS Control Enable, and now is not set !!
So, I add this line of code

dcb.fRtsControl = RTS_CONTROL_ENABLE;

Run again the demo without success....
setCommState error: 87 "Parameter is not correct."

This is the used code:

    DWORD desiredAccess = GENERIC_READ | GENERIC_WRITE;

    HANDLE handle = ::CreateFile(reinterpret_cast<const wchar_t *>(L"COM5"), desiredAccess, 0, nullptr, OPEN_EXISTING, FILE_FLAG_OVERLAPPED, nullptr);
    if (handle == INVALID_HANDLE_VALUE)
    {
        // OOPS
        const DWORD error = ::GetLastError();
        qDebug() << "ERROR:" << error;
    }

    DCB dcb;
    int systemErrorCode = 0;

    // --------------------------------------------------
    // bool QSerialPortPrivate::getDcb(DCB *dcb)
    ::ZeroMemory(&dcb, sizeof(DCB));
    dcb.DCBlength = sizeof(DCB);

    if (!::GetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "GetCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        return;
    }

    // --------------------------------------------------
    // static inline void qt_set_common_props(DCB *dcb)
    dcb.fBinary       = TRUE;
    dcb.fAbortOnError = FALSE;
    dcb.fNull         = FALSE;
    dcb.fErrorChar    = FALSE;

    if (dcb.fDtrControl == DTR_CONTROL_HANDSHAKE)
        dcb.fDtrControl = DTR_CONTROL_DISABLE;

    if (dcb.fRtsControl != RTS_CONTROL_HANDSHAKE)
        dcb.fRtsControl = RTS_CONTROL_DISABLE;

    // --------------------------------------------------
    // baud rate
    dcb.BaudRate = QSerialPort::Baud9600;
    /*
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "BaudRate: setCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        ::CloseHandle(handle);
        return;
    }
    */

    // --------------------------------------------------
    // byte size
    dcb.ByteSize = QSerialPort::Data8;
    /*
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "ByteSize: setCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        ::CloseHandle(handle);
        return;
    }
    */

    // --------------------------------------------------
    // parity
    dcb.Parity  = NOPARITY;
    dcb.fParity = FALSE;
    /*
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "Parity: setCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        ::CloseHandle(handle);
        return;
    }
    */

    // --------------------------------------------------
    // stopbit
    dcb.StopBits = ONESTOPBIT;
    /*
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "StopBit: setCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        ::CloseHandle(handle);
        return;
    }
    */

    // --------------------------------------------------
    // flow control
    dcb.fInX         = FALSE;
    dcb.fOutX        = FALSE;
    dcb.fOutxCtsFlow = FALSE;
    if (dcb.fRtsControl == RTS_CONTROL_HANDSHAKE)
        dcb.fRtsControl = RTS_CONTROL_DISABLE;
    //    switch (flowcontrol)
    //    {
    //        case QSerialPort::NoFlowControl:
    //            break;
    //        case QSerialPort::SoftwareControl:
    //            dcb.fInX  = TRUE;
    //            dcb.fOutX = TRUE;
    //            break;
    //        case QSerialPort::HardwareControl:
    //            dcb.fOutxCtsFlow = TRUE;
    //            dcb.fRtsControl  = RTS_CONTROL_HANDSHAKE;
    //            break;
    //        default:
    //            break;
    //    }

    dcb.fRtsControl = RTS_CONTROL_ENABLE;
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "setCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        ::CloseHandle(handle);
        return;
    }

kuzulis

If this does not work when you did:

...
    if (!::GetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "GetCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        return;
    }
...

and then immediatelly:

...
    if (!::SetCommState(handle, &dcb))
    {
        systemErrorCode = ::GetLastError();
        qDebug() << "SetCommState error:" << systemErrorCode << qt_error_string(systemErrorCode);
        return;
    }
...

then it is LOL.

Then you can install the serial port sniffer application and to sniff the device I/O control call for the SetCommStat. To see, which parameters are passed with this call e.g using the hercules application, and to compare with the qtserialport.

Most likelly, it is a bug in FW of your device (in USB CDC class implementation). Or, maybe it expect some specific DCB structure (some specific DCB flags).

Question: Do you have the specific serial port driver for your device, or do you use the 'standard' usbser.sys driver from Windows?

PS: On Linux there are different drivers implementation.