From owner-freebsd-questions@FreeBSD.ORG Tue Mar 23 00:33:43 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D329516A4CE for ; Tue, 23 Mar 2004 00:33:43 -0800 (PST) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B221743D54 for ; Tue, 23 Mar 2004 00:33:42 -0800 (PST) (envelope-from richard.williamson@u4eatech.com) Received: (from filter@localhost) by mail.u4eatech.com (8.11.6/8.11.6) id i2N8XfZ05270; Tue, 23 Mar 2004 08:33:41 GMT X-Authentication-Warning: mail.u4eatech.com: filter set sender to richard.williamson@u4eatech.com using -f Received: from apus.u4eatech.com (unknown [172.30.20.100]) by mail.u4eatech.com (Postfix) with ESMTP id 6BEA51577D4; Tue, 23 Mar 2004 08:33:37 +0000 (GMT) Message-Id: <6.0.3.0.2.20040323082308.02513710@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Tue, 23 Mar 2004 08:31:23 +0000 To: freebsd-questions@freebsd.org, Nathan Kinkade From: "Richard P. Williamson" In-Reply-To: <20040322174108.GJ36839@nkinkade.bmp.ub> References: <6.0.3.0.2.20040322152842.024b8900@cygnus> <20040322174108.GJ36839@nkinkade.bmp.ub> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, hits=-6.7 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: Serial port (com1) baud rate oddity X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 08:33:44 -0000 At 17:41 22/03/2004, Nathan Kinkade wrote: >On Mon, Mar 22, 2004 at 04:14:56PM +0000, Richard P. Williamson wrote: >> Hello, >> >> I'm using 4.8 Release on an embedded pentium class device, >> and I'm having trouble with the serial (console) port. >> >> From a development machine, I can 'tip com1' and get contact, >> but the data is coming out as >> @@@ @ @@@ @@@ @@@ @@@@@@@@@@@ @@@ @@@@@@ @@@@@ @ @ @@@ >> @ @@ @@@ @ @ @@@@@ @ @@@@ @@@@@@ @ @@@ @@ @ @@@@ @@@@@ @ >> @ @@ @ @ @ @@@@ @ @@@@ @@@@@ @@@ @@ @ @@@@ @@@ @@ >> etc > >> Also minor problem, is this the reason why I can't talk out com3: >> "sio2: configured irq 5 not in bitmap of probed irqs 0" > > >tip gets it configurations from /etc/remote. Make sure that "com1" in >/etc/remote is set with appropriate values. The default is: > >sio0|com1:dv=/dev/cuaa0:br#9600:pa=none: That's what I have. And it was working up to the beginning of last week. Strangely, my son was born on Friday the 12th, and since then my console port no longer works. I'm sure they aren't directly related. However I may have changed something while distracted by my wife screaming she was going to kill me. >The output above looks to me like the problem is simply with the bit >rate. Try some other values. You can specify them manually on the tip >command line with the -s option. I have tried resetting the baud rate using stty, since I'm trying to change the source machine back to 9600. I'll see if using tip -s 1355 works on the sink machine this morning. One thing I tried returned 'TCSGETATTR: incorrect attribute' or something when trying to set the sink to 1355, however. >Regarding your problem with sio2, possibly your kernel is configured >specifying an extra serial port that doesn't actually exist on the >hardware? How many physical serial ports does your device actually >have? 4. com1 and com3 out through DB9s (male). com2 is attached to a densitron 2x16 LCD screen. com4 is unused (but the connector on the motherboard is there). Thanks for your time! rip