Date: Wed, 18 Oct 2000 20:46:13 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: Chris Aitken <chris@ideal.net.au> Cc: questions@freebsd.org Subject: Re: Commandline Access to a Serial Port Message-ID: <14830.21093.897235.687784@guru.mired.org> In-Reply-To: <5.0.0.25.0.20001019123412.023dfac8@mail.ideal.net.au> References: <3302859@toto.iv> <5.0.0.25.0.20001019123412.023dfac8@mail.ideal.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Aitken writes: > At 08:27 PM 18/10/2000, you wrote: > >Chris Aitken writes: > > > Does anyone have any suggestions as to a tool I can use on my FreeBSD 3.4 > > > Stable box that can allow me to communicate with my Serial Port ? > >Are you looking for tip and/or cu? If the man pages tell you that's > >wrong, provide more details about what you want to do. > I have been playing with cu, which seems to be a possibility, but after a > few misc commands, cu seems to have stopped working, and I cant seem to get > it back to how it was. > > I ran > cu -l /dev/cuaa0 -s 9600 > > which allowed me to connect to the serial port, issue it an AT command it > received an OK back. But when I tried the needed command, it came back as > error (which when issued through minicom still works perfectly). > > Then after a couple of playing around with ~| and other things, its all > screwed up, and now it wont respond after it connects to the port. Sounds like you found the right tool set. You might try tip instead, though there's no real reason to expect it to be better. You also need to make that parity, word length, and stop bits are all correct. That's a bit easier with tip than cu, as you can store tip configuration in /etc/remote. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14830.21093.897235.687784>