Cannot connect to remote target via serial port

Cannot connect to remote target via serial port

[Hans Kester]

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."

This happens with Insight 5.2, 6.0 and 6.1. It also has something to do
with the version of Cygwin I am using. With the latest or a recent
version of Cygwin I get this error, with an older one (1.3.22) it still
works.

Anyone with the same problem? Any ideas what might be the cause of this?

Regards,

Hans Kester

RE: Cannot connect to remote target via serial port

[Jon Beniston]

> 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."
> 
> This happens with Insight 5.2, 6.0 and 6.1. It also has 
> something to do with the version of Cygwin I am using. With 
> the latest or a recent version of Cygwin I get this error, 
> with an older one (1.3.22) it still works.
> 

Can you connect with GDB in command line mode? i.e.

sh-elf-gdb prog.x
set remotebaud 115200
target remote /dev/ttyS0

Cheers,
Jon

Re: Cannot connect to remote target via serial port

[Keith Seitz]

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".

Could you please confirm this for me before I commit a patch?

Keith

RE: Cannot connect to remote target via serial port

[Dave Korn]

> -----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.

http://www.cygwin.com/cygwin-ug-net/using-specialnames.html

"Cygwin also has several Windows-specific devices: /dev/comX (the serial
ports, starting with COM1 which is the same as ttyS0)"


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

RE: Cannot connect to remote target via serial port

[Hans Kester]

Dave is right, /dev/comX works fine. And it is indeed not fixed in 6.1.

Hans


-----Original Message-----
From: Dave Korn [mailto:dk@artimi.com] 
Sent: Friday, November 19, 2004 6:10 PM
To: 'Keith Seitz'; Hans Kester
Cc: insight@sources.redhat.com; cygwin@cygwin.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.

http://www.cygwin.com/cygwin-ug-net/using-specialnames.html

"Cygwin also has several Windows-specific devices: /dev/comX (the serial
ports, starting with COM1 which is the same as ttyS0)"


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

RE: Cannot connect to remote target via serial port

[Hans Kester]

Yes! Thanks a lot for this prompt answer!

Hans

-----Original Message-----
From: Jon Beniston [mailto:jbeniston@compxs.com] 
Sent: Friday, November 19, 2004 2:26 PM
To: Hans Kester; insight@sources.redhat.com
Subject: RE: Cannot connect to remote target via serial port

> 
> Yes, that works. Conclusion?

Maybe its something to do with this:

http://sources.redhat.com/ml/insight/2004-q1/msg00025.html

Cheers,
Jon

RE: Cannot connect to remote target via serial port

[Jon Beniston]

> 
> Yes, that works. Conclusion?

Maybe its something to do with this:

http://sources.redhat.com/ml/insight/2004-q1/msg00025.html

Cheers,
Jon

RE: Cannot connect to remote target via serial port

[Hans Kester]

Yes, that works. Conclusion?

Hans


-----Original Message-----
From: Jon Beniston [mailto:jbeniston@compxs.com] 
Sent: Friday, November 19, 2004 2:14 PM
To: Hans Kester; insight@sources.redhat.com
Subject: RE: Cannot connect to remote target via serial port


> 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."
> 
> This happens with Insight 5.2, 6.0 and 6.1. It also has 
> something to do with the version of Cygwin I am using. With 
> the latest or a recent version of Cygwin I get this error, 
> with an older one (1.3.22) it still works.
> 

Can you connect with GDB in command line mode? i.e.

sh-elf-gdb prog.x
set remotebaud 115200
target remote /dev/ttyS0

Cheers,
Jon