Date: Thu, 02 Feb 2006 17:24:50 +0900
From: Gowri Satish Adimulam < gowri@xxxxxxxxxxx>
Subject: Re: needed help on MINICOM
To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
Message-ID: < 1138868690.3297.2.camel@xxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi ,
iam attaching minicom related files on my system /etc dir .
These may give some clue about my setting.
Thanks in advance
Gowri
On Thu, 2006-02-02 at 00:20 -0600, Mike McCarty wrote:
> Gowri Satish Adimulam wrote:
> > Hi ,
> > Iam try to use minicom as simple com-port, it is connected to embedded
> > system board via RS 232 cable.
>
> Try looking in your MINICOM environment variable.
> Try
>
> $ minicom -h
>
> and see what the compiled in path is. Then look in, for example,
> /etc/minicom.users or /var/lib/minicom.users or whatever it's
> compiled for.
>
> Are you using a "null modem" cable? You may need it.
>
> Mike
> --
> p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> This message made from 100% recycled bits.
> You have found the bank of Larn.
> I can explain it for you, but I can't understand it for you.
> I speak only for myself, and I am unanimous in that!
>
-------------- next part --------------
# $Id: minicom.users,v 1.1.1.1 1999/12/18 11:18:51 misiek Exp $
# Minicom.users Access file for the minicom program.
#
# Format: Either just one username per line, or
# a username followed by one or more
# configuration-names. The name of the
# default configuration is "dfl". The maximum
# significant line length is 70 characters.
#
# Location: The minicom library directory, probably
# /etc or /var/lib/minicom or whatever.
#
# Notes: If you don't install this file in the
# specified location, everybody will have
# access to minicom.
#
# This doesn't matter if minicom isn't installed
# setuid root since access will then be based
# on the permissions set on the serial port.
#
#
# Who may use minicom?
#
User gowri
# Everyone has access to all configurations.
ALL
## The rest are examples.
## # Erik only has access to the default configuration
gowri dfl
##
## # minicom has access to the default configuration, and configuration 'tty5'.
minicom dfl tty3
-------------- next part --------------
# Machine-generated file - use "minicom -s" to change parameters.
pr port /dev/ttyS3
pu baudrate 115200
pu bits 8
pu parity N
pu stopbits 1
pu minit
pu mreset
pu mdialpre
pu mdialsuf
pu mdialpre2
pu mdialsuf2
pu mdialpre3
pu mdialsuf3
pu mhangup
pu mdialcan
pu backspace BS
pu rtscts No
pu xonxoff Yes
-------------- next part --------------
# Machine-generated file - use "minicom -s" to change parameters.
pr port /dev/ttyS0
pu baudrate 57600
pu bits 8
pu parity N
pu stopbits 1
pu scriptdir /etc/
Hi Again Gowri!
In a previous e-mail you mentioned:
> > > ttyS3,
> > > baud rate 57600 8n1 which in acordance with embedded system.
But ttyS3 in your machine generated minicom setup file shows:
pr port /dev/ttyS3
pu baudrate 115200
pu baudrate 115200
And I note that you have a ttyS0 set up for 57600. Are you plugged into and talking with the right com port?
I also note that hardware/software flow control in the ttyS3 port is:
pu rtscts No
pu xonxoff Yes
pu xonxoff Yes
The "rtscts" is the hardware flow control (Request To Send - Clear To Send) and "xonxoff" is the software flow control. If it were me I would try actively setting and resetting each of these elements in an active session with the machine connected. You can do that from within the minicom program as previously mentioned.
If you have an old serial modem sitting arround they are good to use to tell you if you are talking with a given serial port. You could even use another computer in terminal mode.
If you are into voltmeters, the active (transmit) lines will rest at between -5 and -12 volts (it may be + - the RS232 standard has low a minus voltage and high a plus voltage but I may have that reversed). The RTS and DTE lines you should see change when you toggle the hardware flow control. The transmit line you should see "jump" as you transmit characters.
Good Hunting!
Tod
