This is the mail archive of the
mailing list for the Insight project.
RE: Cannot connect to remote target via serial port
- From: "Hans Kester" <hans at ellips dot nl>
- To: "Dave Korn" <dk at artimi dot com>, "Keith Seitz" <keiths at redhat dot com>
- Cc: <insight at sources dot redhat dot com>, <cygwin at cygwin dot com>
- Date: Mon, 22 Nov 2004 09:16:10 +0100
- Subject: RE: Cannot connect to remote target via serial port
Dave is right, /dev/comX works fine. And it is indeed not fixed in 6.1.
From: Dave Korn [mailto:email@example.com]
Sent: Friday, November 19, 2004 6:10 PM
To: 'Keith Seitz'; Hans Kester
Cc: firstname.lastname@example.org; email@example.com
Subject: RE: Cannot connect to remote target via serial port
> -----Original Message-----
> From: insight-owner On Behalf Of Keith Seitz
> Sent: 19 November 2004 16:48
> To: Hans Kester
> On Fri, 2004-11-19 at 05:08, Hans Kester wrote:
> > When I try to connect to my remote target (sh-elf) with the
> serial port
> > (COM1) I get the following error message:
> > "com1: Inappropriate ioctl for device."
> Does this really still happen with 6.1? A patch was committed which I
> thought fixed the problem.
> So it appears the latest is that cygwin must now use "/dev/ttySX"
> (X=0,1,...) instead of "/dev/comX".
No, /dev/comX should be fine for cygwin (unless I've missed a recent
change and the docs haven't yet been updated, but I don't think that's
happened), and if it isn't, it's a cygwin bug.
"Cygwin also has several Windows-specific devices: /dev/comX (the serial
ports, starting with COM1 which is the same as ttyS0)"
Can't think of a witty .sigline today....