-
Notifications
You must be signed in to change notification settings - Fork 322
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
Add UART support for IIOD #560
Comments
When doing this - it would be nice to return a list of available serial ports in the main library. This would ensure that end applications didn't need to link to libserial directly, and would just use libiio... something like: and implementing that with something like:
|
and it looks like - trying to open a context on a non-connected serial port hangs forever - there should be a timeout/failure mechanism of some sort... |
This may be out of scope for this, but I'm interested in interfacing with a client running tinyiiod using UART over BLE. At first glance, my use case might be feasible if there was a way for me to give libiio a byte sink and byte source (similar to |
tinyiiod using UART over BLE should work out of the box, and any serial client should work with that - it's already byte oriented... (unless I'm missing something?) |
Yes that was my understanding as well. What's not quite clear to me (sorry if its in the docs somewhere!) is how to interface with a client running tinyiiod over a non-standard interface such as BLE. The only solution I can think of is to take the BLE UART code on my host, and somehow hook it up to an emulated serial port (maybe/hopefully from userspace?). Then I can get libiio to talk to the client (running tinyiiod) over BLE by using the fake serial port as a bridge. (or am I completely missing something?) |
I'm pretty sure IIOD can already be used over UART without any additional code. It should just be a matter of running |
Disable feedback on the standard input when in interactive mode. This means that the commands entered on IIOD's interactive shell won't be displayed, as if the shell was "eating the input", unless the debug mode (-d) is enabled. This makes it possible to run IIOD on UART. For instance, with Busybox, running IIOD on /dev/ttyS2 is as simple as adding this line to /etc/inittab: ttyS2::respawn:/usr/sbin/iiod -i Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum: iiod -s /dev/ttyS2,57600n8 Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum: iiod -s /dev/ttyS2,57600n8 Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum: iiod -s /dev/ttyS2,57600n8 Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits/stop bits/flow settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum, 1 stop bit and RTS/CTS flow control: iiod -s /dev/ttyS2,57600,8n1r Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits/stop bits/flow settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum, 1 stop bit and RTS/CTS flow control: iiod -s /dev/ttyS2,57600,8n1r Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits/stop bits/flow settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum, 1 stop bit and RTS/CTS flow control: iiod -s /dev/ttyS2,57600,8n1r Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits/stop bits/flow settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum, 1 stop bit and RTS/CTS flow control: iiod -s /dev/ttyS2,57600,8n1r Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Add a -s option to serve IIO over UART. This option requires the UART dev node and optionally the baud/parity/bits/stop bits/flow settings to be specified as the parameter. For instance, this will run IIOD on the /dev/ttyS2 UART, at 57600 bps, no parity, 8 bits per datum, 1 stop bit and RTS/CTS flow control: iiod -s /dev/ttyS2,57600,8n1r Fixes #560. Signed-off-by: Paul Cercueil <[email protected]>
Request: https://ez.analog.com/linux-software-drivers/f/q-a/167536/iio-oscilloscope-through-serial-uart-backend-on-custom-board
The text was updated successfully, but these errors were encountered: