So. . . *william@eee-pc:~$* ls -I "tty[0-9]*" /dev |grep tty tty ttyS0 ttyS1 ttyS2 ttyS3 ttyUSB0
william@eee-pc:~$ sudo screen /dev/ttyUSB0 115200 [sudo] password for william: Press enter if you need a prompt, but this is mostly only good for viewing serial debug output from the kernel. Press ctrl A + ctrl D to exit screen [detached from 14104.pts-0.eee-pc] cat is only about as useful as above. Except with screen you can actually interact with the serial interface. With cat, you only get a serial output "dump" Then minicom . . I've only used it a handful of times, and it's not much better in the way of screen formatting than either of the above cases. Anyway, /dev/ttyS3 is probably not the right interface for your serial device. Why don';t you run the first command I demonstrated above and then show us the output. On Thu, Feb 16, 2017 at 4:23 PM, mzimmers <[email protected]> wrote: > Hi, all - > > I'm running Jessie on my desktop (I can also boot Windows 7). I have > Ethernet connectivity to my BBB, and am trying to set it up so I can direct > BBB console output to a window on my desktop. > > Oddly enough, this works using PuTTY under Windows, but when I apply the > same settings to PuTTY under Debian, I get an error: > > Unable to open connection to /dev/ttyS3 > > Unable to configure serial port > > > Since I can get this to work on Windows, I can rule out the serial-to-USB > cable as a possible culprit, and I know that the connection is at least > valid from a hardware sense. Also, I'm guessing the problem isn't on the > BBB, so I'm figuring it's some kind of configuration issue on the desktop. > > I thought this might be a permissions issue, but I added "dialout" to my > user's groups, and I've tried it from root, with the same results, so > that's not looking promising. > > Any suggestions? I'm not married to using PuTTY. I started with it because > I thought it would be easy since I already had it working under Windows, > but I'm willing to use most anything. > > I'm still new to Linux and BBB, so I'd appreciate fairly explicit answers. > > Thanks! > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/aa13c912-3627-4cb7-bba8-625eeda6d660%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/aa13c912-3627-4cb7-bba8-625eeda6d660%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrp55BgrLxJt%3DedL7hxFXty6Pfw37u04nq__iEpRJKxRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
