Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
1
answers
815
views
Minicom - How do I store the newline delay setting?
In Minicom, I prefer to change my `Newline tx delay (ms)` setting via `CTRL-A T` to incorporate some delay between newlines, usually 100ms. That way there is a delay when I am pasting something into a serial console. How can I store this setting? Currently I need to set it every time I open a minico...
In Minicom, I prefer to change my
Newline tx delay (ms)
setting via CTRL-A T
to incorporate some delay between newlines, usually 100ms. That way there is a delay when I am pasting something into a serial console. How can I store this setting?
Currently I need to set it every time I open a minicom instance. I would have thought that this setting would be located inside the minicom configuration, but it seems to be more of a runtime setting.
joeshmo
(15 rep)
Feb 19, 2021, 07:38 PM
• Last activity: Jun 17, 2025, 07:58 AM
2
votes
2
answers
4043
views
minicom on /dev/tty# - Ctl-A Z doesn't appear to work?
I have an old laptop (Dell Latitude D610) that I want to use as a serial terminal for some systems that require that, since this machine has a built-in RS-232 port. I have installed Debian 12 and minicom, but without graphical environment, so I login on the text console. However when I start minicom...
I have an old laptop (Dell Latitude D610) that I want to use as a serial terminal for some systems that require that, since this machine has a built-in RS-232 port. I have installed Debian 12 and minicom, but without graphical environment, so I login on the text console. However when I start minicom,
Ctl-A Z
doesn't open the help menu - instead I just see z
echoed and the cursor doesn't move. In fact I have observed the same in screen, so this isn't limited to minicom.
On my new laptop, I see the same phenomenon, but it works without problems in a GUI terminal on the same system, so it seems to be specific to the text mode consoles. Is there a setting somewhere that I can change to fix this issue?
j4nd3r53n
(779 rep)
Sep 8, 2023, 02:11 PM
• Last activity: May 27, 2025, 12:03 AM
3
votes
2
answers
6623
views
Minicom: transfer CRLF when hit enter?
I have a custom HW which *can* understand commands received over UART. For this purpose I'm using `minicom` on Linux. However the HW needs to get `CRLF` after the command to properly recognize it. How can I ask minicom to **send** CRLF after I hit enter? (I know I can ask it to add CRLF to incoming...
I have a custom HW which *can* understand commands received over UART.
For this purpose I'm using
minicom
on Linux.
However the HW needs to get CRLF
after the command to properly recognize it.
How can I ask minicom to **send** CRLF after I hit enter?
(I know I can ask it to add CRLF to incoming lines, but I need the other way here)
Daniel
(358 rep)
Aug 24, 2021, 07:17 AM
• Last activity: Dec 27, 2024, 09:09 AM
0
votes
2
answers
4022
views
Sending serial data to a USB port from the terminal?
I have an Arduino connected to my USB port (on my Linux based OS) at `/dev/ttyACM0` which is listening for serial data to be read and processes them when received. All I need to do is send data to this port. I have used the program `minicom` with the following command: ``` minicom --device=/dev/ttyA...
I have an Arduino connected to my USB port (on my Linux based OS) at
/dev/ttyACM0
which is listening for serial data to be read and processes them when received. All I need to do is send data to this port. I have used the program minicom
with the following command:
minicom --device=/dev/ttyACM0 --baudrate=9600
and it works perfectly. The problem is that minicom
runs in an interactive environment and I wish to write a shell script which sends information non interactively, something like
minicom --device=/dev/ttyACM0 --baudrate=9600 "message"
From what I understand, everything in Unix is a file - even USB ports - so I was wondering if it would be possible to simply echo
the bytes directly to the device file:
echo "message" >/dev/ttyACM0
But this **did not work**. I realized this might have something to do with mismatch in Baud rates. I ran the following command
$ stty -F /dev/ttyACM0
speed 9600 baud; line = 0;
min = 0; time = 0;
-brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke
But the baud rate is at 9600. Is there any way I can get this to work with the above command?
First User
(345 rep)
Jul 17, 2022, 07:39 PM
• Last activity: Dec 11, 2024, 02:51 PM
0
votes
1
answers
123
views
How to monitor the boot process for headless Jetson Orin via USB?
I've connected my Ubuntu 22 host to [nru-220s-nvidia-jetson-orin](https://www.neousys-tech.com/en/product/product-lines/edge-ai-gpu-computing/nvidia-jetson/nru-220s-nvidia-jetson-orin-fanless-pc) via a USB-A to USB-C cable. I used [Minicom](https://help.ubuntu.com/community/Minicom) to connect to `/...
I've connected my Ubuntu 22 host to [nru-220s-nvidia-jetson-orin](https://www.neousys-tech.com/en/product/product-lines/edge-ai-gpu-computing/nvidia-jetson/nru-220s-nvidia-jetson-orin-fanless-pc) via a USB-A to USB-C cable. I used [Minicom](https://help.ubuntu.com/community/Minicom) to connect to
/dev/ttyACM0
, and that works OK.
I can also connect via SSH, so this USB connection does not bring anything new.
I'd like to use Minicom (or other tool?) also to **monitor the Jetson boot process** - is this possible at all? While booting, there is no /dev/ttyACM0
yet, until the boot is finished, so nothing to connect to.
Danijel
(186 rep)
Oct 29, 2024, 12:23 PM
• Last activity: Oct 29, 2024, 03:02 PM
3
votes
2
answers
12937
views
Intercept communications on physical serial port using socat
I'm no Linux expert so please go easy ;). Ok, the situation is that I have a single board computer running Debian Wheezy. I know its old/risky etc etc but its not actually "my" equipment and therefore I have no control over this. There is some software running on it, written in c# and ran through mo...
I'm no Linux expert so please go easy ;).
Ok, the situation is that I have a single board computer running Debian Wheezy. I know its old/risky etc etc but its not actually "my" equipment and therefore I have no control over this.
There is some software running on it, written in c# and ran through mono. Again, this is not my software and I have zero control over it or the ability to alter the code.
The software sends AT commands down a physical serial port (
/dev/ttyS1
) to a modem which returns the appropriate responses to the commands.
The modems are no longer available and therefore I need to develop some alternative. Therefore I thought I could run a simple python script on the SBC that would "intercept" the AT commands, send back the appropriate responses to the c# software and then I can use the python script to talk to another device however I need to.
Having had a good "google", socat
seemed to be the best option for doing this. However, I have tried I dont know how many combinations and cannot get it to work the way I need it to.
The physical setup is that I currently have the serial port plugged into my laptop so I can see the AT commands coming up the pipe (on ttyS1) I then ssh into the SBC and fire up minicom to view the new "virtual ports" created by socat
.
Existing Setup
**C# ttyS1 Old Modem**
Desired Setup
**C# socat python -> New Modem**
Below is just two of the variations I've tried:
socat -x /dev/ttyS1,raw,echo=0,crnl PTY,link=/dev/ttyV1,raw,echo=0,crnl
... also tried the other way around in case I misunderstood ...
socat -x PTY,link=/dev/ttyV1,raw,echo=0,crnl /dev/ttyS1,raw,echo=0,crnl
I've also tried **many** different variations, pushing to files, "teeing" off to files, different command switches, configuring the ports using stty etc etc
Every time I have the same issue that I cannot actually see the AT commands being sent **from** the c# software?!
I can type into minicom on the SBC and see the output turning up on the serial port reader on my laptop, likewise I can type into the serial port reader on my laptop and see the input in minicom on the SBC, however what I cannot seem to intercept is the actual AT commands being sent from the c# software even though the software is configured to use ttyS1.
The one bit of control I do have over the software is which port it uses to talk to the modem on. Therefore I have also tried changing this to a virtual port e.g. /dev/ttyV1
and running socat
to create the virtual port during startup and before the c# program starts so that the virtual port is actually available. Again I have exactly the same issue where I still cannot see the AT commands being sent by c# software.
Hope someone can help as I've been at this two full days now and cannot get it to work. I'm pretty sure socat is the tool to use and hopefully I've just fundamentally misunderstood how it works.
RobF
(31 rep)
Jul 29, 2022, 09:44 AM
• Last activity: Jul 24, 2024, 03:04 AM
0
votes
1
answers
447
views
ttyUSB ordering
I am working on a project involving the development of a device that interfaces with multiple ttyUSB ports, specifically 16 of them. It's important to note that Linux handles ttyUSB ports differently from Windows. In Linux, ttyUSB ports are typically labeled in the order they are connected, which co...
I am working on a project involving the development of a device that interfaces with multiple ttyUSB ports, specifically 16 of them.
It's important to note that Linux handles ttyUSB ports differently from Windows. In Linux, ttyUSB ports are typically labeled in the order they are connected, which contrasts with Windows where each USB device consistently receives a specific and unchanging COM port number (e.g., COM7 always corresponds to the same USB device, regardless of reconnections or machine reboots).
My primary objective is to ensure that the ttyUSB port numbering in Linux remains consistent even after a device reboot. However, my experiments have shown that Linux does not assign ttyUSB ports in a specific order based on USB connections.
As an illustration, when examining the output of
dmesg | grep tty
, you can observe that usb 1-2 corresponds to ttyUSB0, and usb 1-1 starts from ttyUSB1. It's worth mentioning that usb 1-1 and usb 1-3 represents a USB-to-serial adapter with multiple serial ports.
If you have any insights or suggestions on how to achieve consistent ttyUSB port numbering in Linux, I would greatly appreciate your input.
dmesg | grep tty
- [ 0.241124] printk: console [tty0] enabled
- [ 98.575723] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
- [ 107.645192] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0
- [ 107.647738] usb 1-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB1
- [ 107.703274] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB5
- [ 107.718566] usb 1-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB2
- [ 107.734340] usb 1-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB3
- [ 107.736637] usb 1-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB4
- [ 107.778240] usb 1-3: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB6
- [ 107.831044] usb 1-3: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB7
- [ 107.832354] usb 1-3: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB8
- [ 107.850976] usb 1-3: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB9
Saman.K
(1 rep)
Sep 4, 2023, 04:14 PM
• Last activity: Sep 13, 2023, 09:21 AM
1
votes
2
answers
673
views
Serial port's modem lights up, but can't communicate
My MB has builtin UARTs (Supermicro X10SAE). I've got an external modem hooked up to /dev/ttyS0. I'm running CentOS7. - Without minicom running on /dev/ttyS0: - The modem has CTS on. - With minicom running on /dev/ttyS0: - The modem lights up RTS and DTR along with CTS. - Typing text into minicom do...
My MB has builtin UARTs (Supermicro X10SAE). I've got an external modem hooked up to /dev/ttyS0. I'm running CentOS7.
- Without minicom running on /dev/ttyS0:
- The modem has CTS on.
- With minicom running on /dev/ttyS0:
- The modem lights up RTS and DTR along with CTS.
- Typing text into minicom does NOT light up the TX/RX lights
- AT does nothing
- +++ does nothing
- ATDT does nothing
If I move the modem (on the same box!) to a usb/serial convertor, and connect minicom to /dev/ttyUSB0, the modem responds.
[root ~]# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
[root ~]# setserial -a /dev/ttyUSB0
/dev/ttyUSB0, Line 0, UART: 16654, Port: 0x0000, IRQ: 0
Baud_base: 460800, close_delay: 0, divisor: 0
closing_wait: infinte
Flags: spd_normal
I called the modem while on /dev/ttyS0 and saw a blip on TX for the RING, but it did not show on the screen.
I assume I have the right port -- I even moved it to ttyS1 for comparison. No difference.
I'm stumped! Ideas? I'm beginning to wonder if the MB header to serial jack ribbon cable -- both!? -- are defective somehow.
rrauenza
(852 rep)
Sep 1, 2014, 11:37 PM
• Last activity: Sep 10, 2023, 12:34 AM
0
votes
0
answers
86
views
Why is the serial communication with this device failing?
I have two serial to USB adapters connected to my computer, each one is connected to a microcontroller. What I want to do is send commands to each microcontroller through UART (I'm using minicom), but only one is succeeding. Both send data to the computer, but only one is capable of receiving it. Th...
I have two serial to USB adapters connected to my computer, each one is connected to a microcontroller.
What I want to do is send commands to each microcontroller through UART (I'm using minicom), but only one is succeeding. Both send data to the computer, but only one is capable of receiving it.
This is the result after sending a command to one device.
This is what happens with the other device.
It's not that the connection is wrong, because I switched to Windows and both of them worked. Also, I have to add that the adapter started to fail when I attempted to transmit information to both devices at the same time (as *ttyUSB0* and *ttyUSB1*). It was working fine before that attempt. After that, it doesn't matter if only one is connected, one always works and the other doesn't. It is recognized by the computer as *ttyUSB0* but it never receives the information.
As more evidence that it's the software that is wrong and not the hardware: the LED of the failing adapter never turns on when it's supposed to be receiving data.
Edit: information about the two adapters and the microcontrollers.
**Device CH341**
[11208.020500] usb 3-2.3: new full-speed USB device number 23 using xhci_hcd
[11208.222337] usb 3-2.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[11208.222345] usb 3-2.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[11208.222348] usb 3-2.3: Product: USB Serial
[11208.232359] usb 3-2.3: ch341-uart converter now attached to ttyUSB0
**Device FT232** (the one that doesn't receive data)
[11208.400547] usb 3-2.1.4: new full-speed USB device number 24 using xhci_hcd
[11208.613046] usb 3-2.1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[11208.613056] usb 3-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11208.613060] usb 3-2.1.4: Product: FT232R USB UART
[11208.613062] usb 3-2.1.4: Manufacturer: FTDI
[11208.613065] usb 3-2.1.4: SerialNumber: A9EYI2C0
[11208.621661] usb 3-2.1.4: Detected FT232RL
[11208.623137] usb 3-2.1.4: FTDI USB Serial Device converter now attached to ttyUSB1
The microcontrollers are both Black Pill boards (STM32F401)


EmTor
(1 rep)
Aug 8, 2023, 02:42 AM
• Last activity: Aug 8, 2023, 07:53 PM
1
votes
2
answers
2413
views
serial port via minicom: can minicom use line-editing (i.e. readline functionality)?
I am successfully talking to a board connected over a serial port interface to my PC. I can both send and receive bytes - but for interactive applications executing on the board, that try to read inputs from their stdin, minicom doesn't seem to offer any kind of *readline*-like editing functionality...
I am successfully talking to a board connected over a serial port interface to my PC. I can both send and receive bytes - but for interactive applications executing on the board, that try to read inputs from their stdin, minicom doesn't seem to offer any kind of *readline*-like editing functionality:
// code running on the embedded board
printf("Reading a number: ")
scanf("%d", &i);
In minicom:
$ minicom -D /dev/ttyS0 -b 38400
...
Reading a number: 1a^H
Once I enter an 'a', I can't backspace over it.
Note there's no shell or anything in between here - this is plain minicom over a serial line, nothing more.
screen /dev/ttyS0 38400
seems to work fine - allowing me to edit the line and only sending it to the serial when I press ENTER.
Can minicom be configured to do the same?
ttsiodras
(2446 rep)
Sep 23, 2016, 12:39 PM
• Last activity: May 14, 2023, 04:32 PM
0
votes
1
answers
846
views
Running minicom from a bash script for X amount of time (and getting the output)
I'm trying to write a script that involves repeatedly calling minicom, letting it run for 60 seconds, getting the output, then killing the job nad moving on to the next directory it runs minicom. So to do that I'm using the line `timeout 120s minicom` in a script. However, this doesn't print any of...
I'm trying to write a script that involves repeatedly calling minicom, letting it run for 60 seconds, getting the output, then killing the job nad moving on to the next directory it runs minicom.
So to do that I'm using the line
timeout 120s minicom
in a script.
However, this doesn't print any of the minicom output to the terminal and when it finishes it kills the script entirely.
Is there a way around this?
Ahmed
(1 rep)
Sep 23, 2022, 09:12 PM
• Last activity: Sep 23, 2022, 09:37 PM
1
votes
2
answers
3326
views
Why I can open serial via screen but cannot open via minicom?
I have an arduino communication via Serial port at `/dev/ttyACM0` and I can open it via screen: ``` $ screen /dev/ttyACM0 115200 ``` But for some reason I have no privileges to open it via minicom: ``` $ minicom /dev/ttyACM0 -b 115200 minicom: cannot open /dev/tty8: Άρνηση πρόσβασης ``` My user is i...
I have an arduino communication via Serial port at
/dev/ttyACM0
and I can open it via screen:
$ screen /dev/ttyACM0 115200
But for some reason I have no privileges to open it via minicom:
$ minicom /dev/ttyACM0 -b 115200
minicom: cannot open /dev/tty8: Άρνηση πρόσβασης
My user is in dialout
group:
$ groups
pcmagas adm dialout cdrom sudo dip plugdev lpadmin sambashare wireshark kvm docker
$ whoami
pcmagas
Any ideas why? AFAIK arduino uses an FTDI chip and the module used by kernel is cdc_acm
one:
$ udevadm info --query=all --name=/dev/ttyACM0
P: /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/tty/ttyACM0
N: ttyACM0
S: android0
S: serial/by-id/usb-Arduino__www.arduino.cc__0043_7533131313335170A061-if00
S: serial/by-path/pci-0000:00:14.0-usb-0:3:1.0
E: DEVLINKS=/dev/serial/by-id/usb-Arduino__www.arduino.cc__0043_7533131313335170A061-if00 /dev/android0 /dev/serial/by-path/pci-0000:00:14.0-usb-0:3:1.0
E: DEVNAME=/dev/ttyACM0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/tty/ttyACM0
E: ID_BUS=usb
E: ID_MM_CANDIDATE=1
E: ID_MODEL=0043
E: ID_MODEL_ENC=0043
E: ID_MODEL_FROM_DATABASE=Uno R3 (CDC ACM)
E: ID_MODEL_ID=0043
E: ID_PATH=pci-0000:00:14.0-usb-0:3:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_3_1_0
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_INTERFACE_FROM_DATABASE=XHCI
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_REVISION=0001
E: ID_SERIAL=Arduino__www.arduino.cc__0043_7533131313335170A061
E: ID_SERIAL_SHORT=7533131313335170A061
E: ID_TYPE=generic
E: ID_USB_CLASS_FROM_DATABASE=Communications
E: ID_USB_DRIVER=cdc_acm
E: ID_USB_INTERFACES=:020201:0a0000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Arduino__www.arduino.cc_
E: ID_VENDOR_ENC=Arduino\x20\x28www.arduino.cc\x29
E: ID_VENDOR_FROM_DATABASE=Arduino SA
E: ID_VENDOR_ID=2341
E: MAJOR=166
E: MINOR=0
E: SUBSYSTEM=tty
E: TAGS=:systemd:
E: USEC_INITIALIZED=9517655754
Though by passing the -D
parameter into minicom does open:
minicom -D /dev/ttyACM0 -b 115200
But I do not understand the reason why -D
parameter is required. Is that because for the device plugdev
group is used?
ll /dev/ttyACM0
crw-rw---- 1 root plugdev 166, 0 Αυγ 11 13:05 /dev/ttyACM0
Dimitrios Desyllas
(1301 rep)
Aug 11, 2022, 10:18 AM
• Last activity: Aug 11, 2022, 10:55 AM
0
votes
0
answers
1382
views
Minicom: send string when newline is detected
I have 3 different USB-to-UART FTDI cables and use minicom to debug some device. My problem is only one of these cables can buffer characters until I send a newline. Eg when I type the string "help", the device on the other side will not output the help string until I press Enter. The two other cabl...
I have 3 different USB-to-UART FTDI cables and use minicom to debug some device.
My problem is only one of these cables can buffer characters until I send a newline. Eg when I type the string "help", the device on the other side will not output the help string until I press Enter. The two other cables don't seem to wait for a newline when sending, typing the same string "help", I am seeing no output and newline will just add new lines to whatever I have typed.
I have enabled the following settings each time I start the minicom session:
- echo on
- linefeed on
- carriage return on
The cables I am using are:
- TTL-232R-3V3 (this one works)
- TTL-232R-3V3
- TTL-234X-3V3
Initially, I thought this was an issue with the cable but because another TTL-232R-3V3 has not worked, I think this may be a minicom configuration. But I can't find any configuration that would control this behaviour for my minicom session.
user1397215
(101 rep)
May 23, 2022, 09:20 PM
2
votes
2
answers
3485
views
How to set no stop bits in minicom?
How to set no stop bits in minicom? Apparently, there is no such setting: [![enter image description here][1]][1] Would it be senseless? I am trying to set this way since apparently (not sure) this is correct way to communicate via USB with arduino. [1]: https://i.sstatic.net/5jiOv.png
How to set no stop bits in minicom?
Apparently, there is no such setting:
Would it be senseless?
I am trying to set this way since apparently (not sure) this is correct way to communicate via USB with arduino.

Dims
(3425 rep)
Oct 12, 2015, 11:24 AM
• Last activity: Feb 27, 2022, 05:56 AM
4
votes
1
answers
4972
views
Can't open serial port via minicom, but fine via Python and shell
I have been having issues with connecting to serial ports via `minicom` the last two weeks. For some reason, `/dev/ttyACM0` maps to `tty8` when I try to connect to it. My user is member of the dialout group, and the permissions on `/dev/ttyACM0` seem to be set correctly. $ minicom -d /dev/ttyACM0 -b...
I have been having issues with connecting to serial ports via
minicom
the last two weeks. For some reason, /dev/ttyACM0
maps to tty8
when I try to connect to it. My user is member of the dialout group, and the permissions on /dev/ttyACM0
seem to be set correctly.
$ minicom -d /dev/ttyACM0 -b 115200
minicom: cannot open /dev/tty8: Permission denied
$ ll /dev/ttyACM0
crw-rw-rw- 1 root dialoot 166, 0 Aug 16 12:02 /dev/ttyACM0
I also tried to setup a connection with pyserial
, and this behaves as I expect..
>>> ser = serial.Serial('/dev/ttyACM0', 115200)
>>> ser.write(b"Hello\n")
10
>>> ser.readline()
b'Hello\r\n"
>>> ser.readline()
b'Hello: command not found\r\n'
>>> ser.close()
I tried installing the latest system updates (I run Zorin OS
, based on Ubuntu 20.04 LTS
) and rebooting several times. I also tried different USB ports, without results. Does anyone have an idea what could be wrong with my setup here?
Edit: I just got the idea to communicate directly via my shell, and this seems to be working. I therefore think it is a minicom issue. Still very strange, since I can't find other people with the same problem.
$ cat /dev/ttyACM0
$ echo "Hello\n" > /dev/ttyACM0
$ cat /dev/ttyACM0
Hello
Hello: command not found
Erik
(43 rep)
Aug 16, 2021, 10:14 AM
• Last activity: Aug 18, 2021, 12:13 PM
2
votes
1
answers
3943
views
Garbage characters when using serial connection over SSH connection with minicom/screen
I have a serial connection made with /dev/ttyUSB0 locally from my laptop to a cisco lab router and using minicom/putty/screen all work fine locally (hardware control: on, software control: off, 9600 8N1). When I'm at work I SSH into my laptop at home, which works fine, but when I use minicom/screen...
I have a serial connection made with /dev/ttyUSB0 locally from my laptop to a cisco lab router and using minicom/putty/screen all work fine locally (hardware control: on, software control: off, 9600 8N1).
When I'm at work I SSH into my laptop at home, which works fine, but when I use minicom/screen to use the lab router I get garbage characters. I tried SSHing at home from another machine and it worked fine initially, but then later it started having garbage characters.
Since this is only happening over an SSH connection, what could be causing this? Any setting changes that could fix this?
Nate
(29 rep)
Jun 28, 2016, 05:43 PM
• Last activity: Aug 5, 2021, 09:05 PM
3
votes
1
answers
2057
views
Some characters get lost when pasting large amounts of text into serial console
When pasting large amounts of text into a serial console like `screen` or `minicom`, some characters get lost and are not being transmitted.
When pasting large amounts of text into a serial console like
screen
or minicom
, some characters get lost and are not being transmitted.
finefoot
(3554 rep)
Jul 3, 2021, 06:23 PM
• Last activity: Jul 3, 2021, 06:23 PM
0
votes
2
answers
1642
views
How to set "character tx delay" in GNU screen? (Like in minicom)
Minicom has this useful setting called "character tx delay": [![minicom screenshot][1]][1] Is there a setting like this for GNU screen, too? [1]: https://i.sstatic.net/wvvoZ.png
Minicom has this useful setting called "character tx delay":
Is there a setting like this for GNU screen, too?

finefoot
(3554 rep)
Jul 1, 2021, 09:46 AM
• Last activity: Jul 3, 2021, 05:34 PM
4
votes
3
answers
11676
views
How do you use minicom with stdin and stdout?
I need to communicate with Python over a USB to RS-232 converter, to a device. The application `minicom` connects seamlessly, so if I could run that in non-interactive mode, everything would would be great. Reading the documentation there are some interesting options, but I'm not fully understanding...
I need to communicate with Python over a USB to RS-232 converter, to a device. The application
minicom
connects seamlessly, so if I could run that in non-interactive mode, everything would would be great.
Reading the documentation there are some interesting options, but I'm not fully understanding any one of them:
-t Terminal type. With this flag, you can override the environment
TERM variable.
-S script. Run the named script at startup.
How do I pipe data between my application and minicom
? Should I use something else?
Vorac
(3197 rep)
Sep 2, 2013, 08:24 PM
• Last activity: Apr 8, 2021, 11:39 AM
1
votes
1
answers
1432
views
How do I host a shell for a serial terminal?
I am building a dumb terminal with an arduino and I can now see the output of serial connections. How do I get a login/shell? I have tried `screen /dev/ttyACM0` and that lets me type on the host computer and see the results on the terminal screen, but no shell. Using screen's `:exec /bin/sh` command...
I am building a dumb terminal with an arduino and I can now see the output of serial connections. How do I get a login/shell?
I have tried
screen /dev/ttyACM0
and that lets me type on the host computer and see the results on the terminal screen, but no shell. Using screen's :exec /bin/sh
command starts a shell on that controlling xterm window but no longer outputs to the serial line. various attempts with agetty -L /dev/ttyACM0 9600
just sit and hang for a minute then exits without ever having put anything on the screen. I have tried cu -l /dev/ttyACM0 -s 9600
and again it hangs with no screen interaction. I have connected minicom to echo keys onto the arduino similar to screen but could not figure out how to get a shell. To be clear I am trying to access my main computer via the arduino based terminal, and I can not find a way to make my main computer offer a shell session to the arduino over a USB serial connection.
Gregory
(53 rep)
Feb 10, 2021, 03:00 AM
• Last activity: Feb 10, 2021, 01:52 PM
Showing page 1 of 20 total questions