From rgrover1 at gmail.com Tue Jul 1 10:01:45 2008 From: rgrover1 at gmail.com (Rohit Grover) Date: Tue Jul 1 10:01:48 2008 Subject: having trouble receiving serial data using my USB->serial adaptor In-Reply-To: <4869337C.6050105@vwsoft.com> References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> Message-ID: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> 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 > From rb at gid.co.uk Tue Jul 1 10:39:31 2008 From: rb at gid.co.uk (Bob Bishop) Date: Tue Jul 1 10:39:36 2008 Subject: having trouble receiving serial data using my USB->serial adaptor In-Reply-To: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> Message-ID: Hi, On 1 Jul 2008, at 11:01, Rohit Grover wrote: > 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. FTR, standards-compliant serial ports are pretty robust; it would be much more surprising if the devices hadn't survived. -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295 From v.werth at bally-wulff.de Tue Jul 1 11:40:34 2008 From: v.werth at bally-wulff.de (Werth, Volker) Date: Tue Jul 1 11:40:39 2008 Subject: having trouble receiving serial data using my USB->serial adaptor In-Reply-To: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> Message-ID: <200807011316.50422.v.werth@bally-wulff.de> Volker Werth schrieb am 01.07.2008 13:16 _____________________________________________________________________ Am Dienstag, 1. Juli 2008 12:01 schrieb Rohit Grover: > 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 Rohit, correct terminology is: Instead of the usual DTE (provided by built-in PC serial ports), your adapter is a DCE. Connecting that to a DTE (modem, serial terminal) does not require a null-modem (crossed Rx/Tx, handshake) cabling. Connecting DCE to DCE or DTE to DTE always requires a (crossed) null modem connection. DTE to DCE requires a straight 1:1 cabling. Against everybody's assumption, a PC's serial port is mostly always a DTE. I think this may go back to the time (some 20 or 30 years) while PCs were seen just as smart (dumb?) terminals connected to a mainframe. HTH Volker -- Volker Werth system engineering Bally Wulff Entertainment GmbH Maybachufer 48-51 12045 Berlin, Germany ph: +49(30)62002-109 Bally Wulff Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, Postanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: 030-620 02-200, Gesch?ftsf?hrer: Sascha Blodau, Wolfram J. Seiffert, Tim Wittenbecher, Amtsgericht Berlin-Charlottenburg, HRB 91532 B, UST-ID DE 234 517 998 _____________________________________________________________________ Dieses E-Mail ist nur f?r den Empf?nger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- ?u?erung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Entertainment GmbH dar. Sind Sie nicht der Empf?nger, so haben Sie diese E-Mail irrt?mlich erhalten und jegliche Verwendung, Ver?ffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Entertainment GmbH noch der Absender (Volker Werth) ?bernehmen die Haftung f?r Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren 0 Anh?nge auf Viren zu pr?fen. 0 Anh?nge: _____________________________________________________________________ Versand am 01.07.2008 13:16 von Werth Volker From imp at bsdimp.com Mon Jul 7 00:23:35 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Jul 7 00:23:52 2008 Subject: Minor reorg fyi Message-ID: <20080706.182254.-1585756927.imp@bsdimp.com> After talking with people in the FreeBSD mips community, I've moved some files around in subversion. For all the details, and some info about my plans in the near future, please see my blog http://bsdimp.blogspot.com/ If you have questions or concerns about things, please feel free to talk about them here... Warner From bugmaster at FreeBSD.org Mon Jul 7 11:06:57 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 7 11:07:45 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200807071106.m67B6twk061984@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total. From bugmaster at FreeBSD.org Mon Jul 14 11:06:56 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 14 11:07:24 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200807141106.m6EB6tBZ014369@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total. From bugmaster at FreeBSD.org Mon Jul 21 11:06:53 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 21 11:07:18 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200807211106.m6LB6qaw031823@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total. From bugmaster at FreeBSD.org Mon Jul 28 11:06:54 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 28 11:07:18 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200807281106.m6SB6rqp078861@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total.