From owner-freebsd-embedded@FreeBSD.ORG Tue Jul 1 10:01:45 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C568106566C for ; Tue, 1 Jul 2008 10:01:45 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id E2AF28FC13 for ; Tue, 1 Jul 2008 10:01:44 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2078755rvf.43 for ; Tue, 01 Jul 2008 03:01:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=67eG1jTEYbiBhWGJ02zbyBVlXIs58ttGJS7YCLbJe2E=; b=GKEup5WRt/6AYu2qSnUJq2q4DYWiWt7vV77/WTqHWpvCgx0/j37FtSrrhfhyRqaXO4 YgK0whN+kLQq+0vMkCTKbkqyiNKqNhDaVaBaaqiE8RYIRdw9P/xWfCSetKfMovHVmrSe GFo1zlJriCrWNdrN1iCrKk0Z87M5auprsuZF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=Szf89gl7PQctNH2MgfROtXkCkGYAQNM6icxjcNLZlrUlQum4ZEcKdhsFBDTzfZSifn C+qrgHMgg0XJzolPxFn69YL+7JFF1KUFklTjAXFtZ0/z9x9kq8JCVCygJdxDS/Tlt5Pi kuVvtRzn7Bg+0nB4CyC7OUrmBWOjhGe4gacPc= Received: by 10.141.71.8 with SMTP id y8mr3363972rvk.63.1214906504646; Tue, 01 Jul 2008 03:01:44 -0700 (PDT) Received: by 10.141.66.20 with HTTP; Tue, 1 Jul 2008 03:01:44 -0700 (PDT) Message-ID: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> Date: Tue, 1 Jul 2008 22:01:44 +1200 From: "Rohit Grover" To: Volker In-Reply-To: <4869337C.6050105@vwsoft.com> MIME-Version: 1.0 References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-embedded@freebsd.org Subject: Re: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 10:01:45 -0000 Hi, Thanks for the response. I stumbled upon the solution quite by chance. My USB->serial adaptor has a NULL modem built into it, so attaching an external NULL modem was un-necessary and incorrect. It is a wonder that the devices survived this treatment. thanks again. regards, > > > I am having trouble getting my BAFO 810 USB->serial adaptor to > > work. I have built the uplcom and ucom drivers into the kernel, > > and my USB->serial adaptor is recognized at boot, as can be > > inferred from the following lines from /var/run/dmesg.boot: > > > > ucom0: > 0/0, rev 1.10/3.\ 00, addr 2> on uhub3 > > > > I am using minicom to drive /dev/cuaU0 at 115200 8N1. > > > > If I connect the Tx and Rx lines (pins 2 and 3) of the DB9 > > connector, I can get echoes of my keystrokes on the minicom > > terminal. > > > > Unfortunately, I am unable to connect to an embedded device which > > supports serial connections at 115200 8N1. When I plug the serial > > output connector of my adaptor to a NULL modem and then to the > > target embedded system, I don't see any serial output from the > > device on my minicom terminal. This same device communicates > > correctly with the serial port of my linux desktop with minicom > > and 115200 8N1. > > > > As a further experiment, I manually connected pins 2,3, and 5 of > > the serial end of my adaptor to pins 3,2, and 5 respectively of > > the embedded device, but still no luck. > > > > What am I missing? > > > > regards, > > > > > Rohit, > > hard to tell on the distance but if you're able to receive (using a > loopback adapter), it sounds like either side is most likely requiring > hardware handshake (DSR/DTR, RTS/CTS). > > Sometimes it helps to short cut the DCD line (to RTS/DSR), as some > device refuse to send if DCD is not set. If you're owning a break out > box, it should be snap to figure that out. At least you should check > using a serial line tester (those little tools signaling line status > using LEDs or use a Voltmeter to check for correct line status). > > Volker >