Search
Searches topics and replies. Every word has to appear in the post.
10 posts found.
| Post | Posted |
|---|---|
It does. Resolved, and the file is clean. | by kris !LryyDLF- |
--logfile FILE if your picocom is 3.x or newer. Debian stable has it. | by Anonymous |
Following up on the serial terminal thread. Is there a way to have picocom write everything to a file? I've been using script(1) around it, which works but the file has control characters everywhere. | by kris !LryyDLF- |
Different cable, plugged straight into the laptop. Been stable for two days. Resolving. | by kris !LryyDLF- |
minicom if you want menus, screen /dev/ttyUSB0 115200 if you don't. picocom is what I'd pick too. | by frobnitz |
Try without the USB hub if you have one. Mine was a power issue; changing terminal settings didn't help. | by Anonymous |
The adapter connects fine at 115200 but eventually stops receiving. Unplugging and plugging it back in fixes it for a while. dmesg says "usb disconnect" when it happens. Same result with two different terminal programs. Going to try another… | by Anonymous |
picocom is fine. For logging, --logfile session.txt exists in newer versions. Older ones don't have it, which is probably why people wrap it in script. | by Anonymous |
Have a spare ThinkPad with a cracked corner and a working screen. Thinking of leaving it on the workbench for serial consoles. Any reason to use something other than picocom? Mostly routers and an Arduino. Would like to save the session to … | by kris !LryyDLF- |
Tcl expect, driving a router console through /dev/ttyUSB0 with spawn -open. Same script through ssh is fine. Over serial it matches the login prompt, sends the username, and then the "assword:" pattern never fires though I can see it in the… | by frobnitz |