Re: simple serial loopback
On Thu, Jan 27, 2005 at 10:00:40AM +0100, Florian Hengstberger wrote: Hi list! I'm currently trying to setup my box for simple data transfer to a microcontroller via the serial interface. Therefore I've wired a nullmodem cable and as a first test I was trying to connect from cuaa0 to cuaa1 simply by Generally you shouldn't need a null modem for a microcontroller, just a regular cable. That's because it's expected to be a slave to a PC, I think the technical term is Data Set, which is just like a regular modem is a Data Set, where a PC is a master or Data Terminal. So PC to PC you need a null modem since it's Data Terminal to Data Terminal. For monitoring my tty I find minicom or cu -l /dev/cuaa0 to work just fine. xterm1: cat /dev/cuaa0 xterm2: echo Something /dev/cuaa1 Unfortunatly cat exits with 0 after the first echo although it displays the message correct, so I have to cat /dev/cuaa0 everytime I send something. Why is this? Is there a better way to keep track of the ascii-chars sent over a serial connection? Kermit and minicom seem to be some sort of monster for real serial connection (initialisation ...) which is a bit to much for me. In the end I just wan't to see the chars sent over the cabel and wan't to reply to them by typing on the keyboard, that's it! Thanks in advance Florian PS: Maybe a simple shell/perl script can help, should I focus on that? -- Linux/BSD: The daemons are not longer just in my head! -- Florian Hengstberger [EMAIL PROTECTED] http://stud3.tuwien.ac.at/~e0025265 -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
simple serial loopback
Hi list! I'm currently trying to setup my box for simple data transfer to a microcontroller via the serial interface. Therefore I've wired a nullmodem cable and as a first test I was trying to connect from cuaa0 to cuaa1 simply by xterm1: cat /dev/cuaa0 xterm2: echo Something /dev/cuaa1 Unfortunatly cat exits with 0 after the first echo although it displays the message correct, so I have to cat /dev/cuaa0 everytime I send something. Why is this? Is there a better way to keep track of the ascii-chars sent over a serial connection? Kermit and minicom seem to be some sort of monster for real serial connection (initialisation ...) which is a bit to much for me. In the end I just wan't to see the chars sent over the cabel and wan't to reply to them by typing on the keyboard, that's it! Thanks in advance Florian PS: Maybe a simple shell/perl script can help, should I focus on that? -- Linux/BSD: The daemons are not longer just in my head! -- Florian Hengstberger [EMAIL PROTECTED] http://stud3.tuwien.ac.at/~e0025265 -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: simple serial loopback
Florian Hengstberger skrev:
Hi list!
Hello.
I'm currently trying to setup my box for simple data transfer
to a microcontroller via the serial interface.
Therefore I've wired a nullmodem cable and as a first test
I was trying to connect from cuaa0 to cuaa1 simply by
xterm1: cat /dev/cuaa0
xterm2: echo Something /dev/cuaa1
Thanks in advance
Florian
PS: Maybe a simple shell/perl script can help, should I focus on that?
Try cu.
%cu --help
Taylor UUCP 1.06.1, copyright (C) 1991, 92, 93, 94, 1995 Ian Lance Taylor
Usage: cu [options] [system or phone-number]
-a,-p,--port port: Use named port
-l,--line line: Use named device (e.g. tty0)
-s,--speed,--baud speed, -#: Use given speed
-c,--phone phone: Phone number to call
-z,--system system: System to call
-e: Set even parity
-o: Set odd parity
--parity={odd,even}: Set parity
-E,--escape char: Set escape character
-h,--halfduplex: Echo locally
--nostop: Turn off XON/XOFF handling
-t,--mapcr: Map carriage return to carriage return/linefeed
-n,--prompt: Prompt for phone number
-d: Set maximum debugging level
-x,--debug debug: Set debugging type
-I,--config file: Set configuration file to use
-v,--version: Print version and exit
--help: Print help and exit
No idea if that's what you are looking for.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
