Serial Port Communication from Linux Command Line: A Comprehensive Guide from Windows to Linux

Fundamentals of Serial Port Communication and Migration Challenges from Windows to Linux

Serial port communication, as a traditional method for data exchange between devices, remains widely used in embedded systems, industrial control, and hardware debugging. When migrating from Windows to Linux, developers often encounter differences in command syntax and behavior, leading to communication failures. Windows uses the mode command to configure serial port parameters and copy con to send data, while Linux relies on standard tools like stty and echo.

The stty Command: Core of Serial Port Parameter Configuration

In Linux, the stty command is used to set terminal parameters, including key attributes for serial port communication. Proper configuration is essential for successful communication. The basic syntax is as follows:

stty -F /dev/ttyS0 speed 9600 cs8 -cstopb -parenb

This command sets the /dev/ttyS0 device to 9600 baud, 8 data bits, 1 stop bit, and no parity. Parameter explanation: -F specifies the device file, speed sets the baud rate, cs8 indicates 8-bit character size, -cstopb enables 1 stop bit, and -parenb disables parity. Ensure the device path is correct; common serial devices include /dev/ttyS0 (COM1) and /dev/ttyUSB0 (USB-to-serial).

The echo Command: Pitfalls of Data Sending and Escaping

After configuration, data is often sent using the echo command. However, directly using hexadecimal escapes can cause issues. For example:

echo '\x12\x02' > /dev/ttyS0

This command does not send the hexadecimal values 0x12 and 0x02, but the literal string "\x12\x02", because echo does not interpret backslash escapes by default. The solution is to use the -e option to enable escape interpretation:

echo -en '\x12\x02' > /dev/ttyS0

Here, -e enables escaping, and -n suppresses the trailing newline to avoid sending extra data. A newline can interfere with device protocols, causing operations to fail.

Alternative Escaping Methods: The Ctrl+V Key Combination Technique

Besides the -e option, Linux supports using Ctrl+V to input control characters. For example, to send Ctrl+R (ASCII 18, 0x12) and Ctrl+B (ASCII 2, 0x02):

echo -n ^R^B > /dev/ttyS0

On the command line, input ^R via Ctrl+V Ctrl+R and ^B via Ctrl+V Ctrl+B. This method embeds control characters directly, avoiding escape parsing issues, and is suitable for interactive environments or script files.

Common Troubleshooting and Handling Interference Sources

Even with correct commands, communication may fail. Common reasons include:

• Device Permission Issues: Ensure the user has read and write permissions for /dev/ttyS0; use sudo or modify permissions as needed.
• Background Process Interference: Services like gpsd may automatically occupy serial port devices. Check and stop relevant processes: sudo systemctl stop gpsd.
• Virtual Machine Configuration: In virtual environments like VirtualBox, correctly configure serial port redirection to ensure host serial ports are mapped to the guest machine.

For debugging, use cat /dev/ttyS0 to monitor serial output or strace to trace system calls.

Complete Workflow Example

Below is a full example from configuration to sending, simulating Windows' mode and copy operations:

# Configure serial port parameters
stty -F /dev/ttyS0 9600 cs8 -cstopb -parenb

# Send hexadecimal data 0x12 0x02
echo -en '\x12\x02' > /dev/ttyS0

# Or use the Ctrl+V method
# In a script, write directly: echo -n ^R^B > /dev/ttyS0

This workflow ensures parameter matching and accurate data transmission, suitable for most serial port device communication scenarios.

Conclusion and Best Practices

For Linux serial port communication, remember to: always verify configuration with stty, prefer echo -en for hexadecimal escaping, or use Ctrl+V for control characters in scripts. Avoid background process interference and regularly check device status. By understanding these core concepts, developers can efficiently migrate Windows serial port applications to Linux environments, enhancing cross-platform development efficiency.