Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Re “the problem is really in the screen program”: I suggest you ditch screen and try picocom. This is a small program (tiny compared to screen) for accessing devices that provide serial consoles. It does only one thing but does it well; it does not try to emulate or multiplex terminals. I do not know whether picocom defaults to the correct behavior, but it keeps you in control: see the options --noreset, --hangup, --lower-rts, --raise-rts, --lower-dtr and --raise-dtr. Commented Aug 24, 2023 at 7:24
  • @EdgarBonet can I somehow "type in" file to picocom? As if I open picocom /dev/ttyACM0 communicate with Arduino over its Serial.read and then "type-in file lorem.txt" and Arduino will get impression, that I am typing really fast really long texts. (the Serial.read will just receive lots of chars - the content of the file) Commented Aug 24, 2023 at 18:57
  • I am using Gentoo Linux and I also use serial communication with other 8-bit computers, where I need sometimes send few kilobytes of hexa code (Intel Hex) so it will be more convenient, then simply copy-paste text to terminal window Commented Aug 24, 2023 at 19:12
  • 1
    picocom -b 115200 -s cat /dev/ttyUSB0 works (-s cat) and then C-a C-s ./test_serial.002.0200.s.x.hex Commented Aug 24, 2023 at 19:28