-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to open /dev/pts
devices (used by socat and jpnevulator)
#60
Comments
Hello, I think I have the same problem (or atleast similar). I am using a SBC(Single board computer) to manage 4 devices (card reader, LED controller, touch screen etc...). However the SBC doesn't have enough ports, so I am using a board to combine all of the serial ports into one usb, then that usb is connected to the SBC and then an app 'splits' that usb connection into 4 virtual serial ports.
If I open some of the ports with minicom, everything is working fine But if I try to open it with libserialport I receive the following error:
|
The question may be can |
It's indeed a problem with the Sigrok serialport library and not the dart wrapper, @jpnurmi created a PR a few years ago that is still open: sigrokproject/libserialport#4 |
@AurelienBallier How I can use a patched libserial port in my case? |
You can:
And then build and install the lib on your system. |
I made a minimalistic example using your library:
And I used a serial port monitor to intercept any incomming and outcomming messages from and to a serial port:
But once I run
dart run
I get the error:Meaning that dart is unable to read and write towards
/dev/pts/3
device. Thoudh I am able to access the/dev/ttyACM0
directly if I replace the /dev/pts/3 with /dev/ttyACM0:Works fine as you can see:
The problem is that I am unable to read any data that dart code sends towards the device, but I can only read whatever device sends towards the application. That it hinders me on debugging my dart code. Is there a way for the library to open
/dev/pts
devices as well?The text was updated successfully, but these errors were encountered: