Accessing serial port.

Accessing serial port.

[Hans - Dulimarta]

I am porting my C codes from DJGPP to Cygwin. One of the modules has
several lines which read and write to COM1. I rewrite the code using
open ("/dev/com1"), read (....), write (....), etc. However, the code
seems to hang. The exact same code works fine under Linux by replacing
"/dev/com1" to "/dev/ttyS0". 

Could somebody please help me out.
Thanks.


Hans Dulimarta, Ph.D.    [dulimart@egr.msu.edu, dulimart@computer.org]
Visiting Research Associate
Department of Electrical & Computer Engineering         (517) 432-7589
Michigan State University, East Lansing, Michigan 48824


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Accessing serial port.

[Suhaib M. Siddiqi]

>
>
> I am porting my C codes from DJGPP to Cygwin. One of the modules has
> several lines which read and write to COM1. I rewrite the code using
> open ("/dev/com1"), read (....), write (....), etc. However, the code
> seems to hang. The exact same code works fine under Linux by replacing
> "/dev/com1" to "/dev/ttyS0".
>

This requires accessing the hardware through a proper device driver on
Windows.
It is not that easy
to change /dev/xxx to someting.  Check http://www.microsoft.com/hwdrv/ddk
for info about devices.  If it would have been so easy I would have finished
Xfree86 port a long time ago ;-)



> Could somebody please help me out.
> Thanks.
>
>
> Hans Dulimarta, Ph.D.    [dulimart@egr.msu.edu, dulimart@computer.org]
> Visiting Research Associate
> Department of Electrical & Computer Engineering         (517) 432-7589
> Michigan State University, East Lansing, Michigan 48824
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[David Young]

> ... Check http://www.microsoft.com/hwdrv/ddk ...

That URL gives:
Sorry, there is no microsoft.com Web page matching your request.

Anyways, why don't you just use the MS Serial Port functions:

CreateFile()
SetupComm()
SetCommState()
ReadFile()
CloseHandle()

Thanks A Bunch! David Young; VVI-DCS
dyoung@vvi.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Emil Hallin]

David Young wrote:
> 
> > ... Check http://www.microsoft.com/hwdrv/ddk ...

correct URL is:
http://www.microsoft.com/hwdev/ddk
                            ^

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Chris Faylor]

On Thu, Aug 05, 1999 at 01:18:26PM -0400, Suhaib M. Siddiqi wrote:
>
>
>>
>>
>> I am porting my C codes from DJGPP to Cygwin. One of the modules has
>> several lines which read and write to COM1. I rewrite the code using
>> open ("/dev/com1"), read (....), write (....), etc. However, the code
>> seems to hang. The exact same code works fine under Linux by replacing
>> "/dev/com1" to "/dev/ttyS0".
>>
>
>This requires accessing the hardware through a proper device driver on
>Windows.  It is not that easy to change /dev/xxx to someting.  Check
> http://www.microsoft.com/hwdrv/ddk for info about devices.  If it would
>have been so easy I would have finished Xfree86 port a long time ago
>;-)

Um.  No.  I don't know why you think that this requires a device driver.
You should be able to access /dev/com1 using normal open/close/read/write
semantics.

However, there were serial problems in B20.1 that should be fixed in
current snapshots: http://sourceware.cygnus.com/cygwin/snapshots/

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Suhaib M. Siddiqi]

Chris Faylor wrote:
> 
> On Thu, Aug 05, 1999 at 01:18:26PM -0400, Suhaib M. Siddiqi wrote:
> >
> >
> >>
> >>
> >> I am porting my C codes from DJGPP to Cygwin. One of the modules has
> >> several lines which read and write to COM1. I rewrite the code using
> >> open ("/dev/com1"), read (....), write (....), etc. However, the code
> >> seems to hang. The exact same code works fine under Linux by replacing
> >> "/dev/com1" to "/dev/ttyS0".
> >>
> >
> >This requires accessing the hardware through a proper device driver on
> >Windows.  It is not that easy to change /dev/xxx to someting.  Check
> > http://www.microsoft.com/hwdrv/ddk for info about devices.  If it would
> >have been so easy I would have finished Xfree86 port a long time ago
> >;-)
> 
> Um.  No.  I don't know why you think that this requires a device driver.
> You should be able to access /dev/com1 using normal open/close/read/write
> semantics.
> 
> However, there were serial problems in B20.1 that should be fixed in
> current snapshots: http://sourceware.cygnus.com/cygwin/snapshots/
> 
> cgf

I think for serial only might be possible.  
In my case, I need more then /dev/com1.  
I did try /dev/com1 on Windows NT  and it was
crashing, at least my code, with 
privilaged_access_violation.


Suhaib

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Chris Faylor]

On Thu, Aug 05, 1999 at 03:32:30PM -0400, Suhaib M. Siddiqi wrote:
>I think for serial only might be possible.  In my case, I need more
>then /dev/com1.  I did try /dev/com1 on Windows NT and it was crashing,
>at least my code, with privilaged_access_violation.

That would be one of those cases where you run gdb to find out *why*
it's crashing.

Cygwin has code for supporting things like /dev/null, /dev/tty, /dev/com1,
and other things.  There is nothing magic about any of it.  It all gets
translated into normal Windows API calls eventually.

It's certainly possible that there is something wrong somewhere in
cygwin with the handling of /dev/com1 but since this functionality is heavily
used by our gdb customers it's unlikely that there is something trivially
wrong with the emulation.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Suhaib M. Siddiqi]

Chris Faylor wrote:
> 
> On Thu, Aug 05, 1999 at 03:32:30PM -0400, Suhaib M. Siddiqi wrote:
> >I think for serial only might be possible.  In my case, I need more
> >then /dev/com1.  I did try /dev/com1 on Windows NT and it was crashing,
> >at least my code, with privilaged_access_violation.
> 
> That would be one of those cases where you run gdb to find out *why*
> it's crashing.
> 
> Cygwin has code for supporting things like /dev/null, /dev/tty, /dev/com1,
> and other things.  There is nothing magic about any of it.  It all gets
> translated into normal Windows API calls eventually.
> 
> It's certainly possible that there is something wrong somewhere in
> cygwin with the handling of /dev/com1 but since this functionality is heavily
> used by our gdb customers it's unlikely that there is something trivially
> wrong with the emulation.
> 
> cgf


I also do not think /dev/com1 is the real problem.  The problem
is the X11 server code, which read/writes to /dev/mem and /dev/iopl
after accessing each device.  
until I get this part straighten out, it is difficult to trace
and fix other problems in x11 code.
Is there any possibility of adding /dev/mem to Cygwin?  I know, as
you mentioned in one of your message, it might slow the application.

Another note, unrealted to this issue:- which relates to Sergey's latest
AF_UNIX diff file.  Out of curiousity I applied his AF_UNIX.diff file to
the lastest Winsup snapshot.  Build goes OK, but  applications linked
against the cygwin1.dll  (with Sergey's AF_UNIX patch) does not
execute.  It gives error, "Application failed to initialized".

Sorry for two different subjects in one message... 

Suhaib

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Accessing serial port.

[Hans - Dulimarta]

I am porting my C codes from DJGPP to Cygwin. One of the modules has
several lines which read and write to COM1. I rewrite the code using
open ("/dev/com1"), read (....), write (....), etc. However, the code
seems to hang. The exact same code works fine under Linux by replacing
"/dev/com1" to "/dev/ttyS0". 

Could somebody please help me out.
Thanks.


Hans Dulimarta, Ph.D.    [dulimart@egr.msu.edu, dulimart@computer.org]
Visiting Research Associate
Department of Electrical & Computer Engineering         (517) 432-7589
Michigan State University, East Lansing, Michigan 48824


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Chris Faylor]

On Thu, Aug 05, 1999 at 03:32:30PM -0400, Suhaib M. Siddiqi wrote:
>I think for serial only might be possible.  In my case, I need more
>then /dev/com1.  I did try /dev/com1 on Windows NT and it was crashing,
>at least my code, with privilaged_access_violation.

That would be one of those cases where you run gdb to find out *why*
it's crashing.

Cygwin has code for supporting things like /dev/null, /dev/tty, /dev/com1,
and other things.  There is nothing magic about any of it.  It all gets
translated into normal Windows API calls eventually.

It's certainly possible that there is something wrong somewhere in
cygwin with the handling of /dev/com1 but since this functionality is heavily
used by our gdb customers it's unlikely that there is something trivially
wrong with the emulation.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[David Young]

> ... Check http://www.microsoft.com/hwdrv/ddk ...

That URL gives:
Sorry, there is no microsoft.com Web page matching your request.

Anyways, why don't you just use the MS Serial Port functions:

CreateFile()
SetupComm()
SetCommState()
ReadFile()
CloseHandle()

Thanks A Bunch! David Young; VVI-DCS
dyoung@vvi.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Suhaib M. Siddiqi]

Chris Faylor wrote:
> 
> On Thu, Aug 05, 1999 at 01:18:26PM -0400, Suhaib M. Siddiqi wrote:
> >
> >
> >>
> >>
> >> I am porting my C codes from DJGPP to Cygwin. One of the modules has
> >> several lines which read and write to COM1. I rewrite the code using
> >> open ("/dev/com1"), read (....), write (....), etc. However, the code
> >> seems to hang. The exact same code works fine under Linux by replacing
> >> "/dev/com1" to "/dev/ttyS0".
> >>
> >
> >This requires accessing the hardware through a proper device driver on
> >Windows.  It is not that easy to change /dev/xxx to someting.  Check
> > http://www.microsoft.com/hwdrv/ddk for info about devices.  If it would
> >have been so easy I would have finished Xfree86 port a long time ago
> >;-)
> 
> Um.  No.  I don't know why you think that this requires a device driver.
> You should be able to access /dev/com1 using normal open/close/read/write
> semantics.
> 
> However, there were serial problems in B20.1 that should be fixed in
> current snapshots: http://sourceware.cygnus.com/cygwin/snapshots/
> 
> cgf

I think for serial only might be possible.  
In my case, I need more then /dev/com1.  
I did try /dev/com1 on Windows NT  and it was
crashing, at least my code, with 
privilaged_access_violation.


Suhaib

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Accessing serial port.

[Suhaib M. Siddiqi]

>
>
> I am porting my C codes from DJGPP to Cygwin. One of the modules has
> several lines which read and write to COM1. I rewrite the code using
> open ("/dev/com1"), read (....), write (....), etc. However, the code
> seems to hang. The exact same code works fine under Linux by replacing
> "/dev/com1" to "/dev/ttyS0".
>

This requires accessing the hardware through a proper device driver on
Windows.
It is not that easy
to change /dev/xxx to someting.  Check http://www.microsoft.com/hwdrv/ddk
for info about devices.  If it would have been so easy I would have finished
Xfree86 port a long time ago ;-)



> Could somebody please help me out.
> Thanks.
>
>
> Hans Dulimarta, Ph.D.    [dulimart@egr.msu.edu, dulimart@computer.org]
> Visiting Research Associate
> Department of Electrical & Computer Engineering         (517) 432-7589
> Michigan State University, East Lansing, Michigan 48824
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Suhaib M. Siddiqi]

Chris Faylor wrote:
> 
> On Thu, Aug 05, 1999 at 03:32:30PM -0400, Suhaib M. Siddiqi wrote:
> >I think for serial only might be possible.  In my case, I need more
> >then /dev/com1.  I did try /dev/com1 on Windows NT and it was crashing,
> >at least my code, with privilaged_access_violation.
> 
> That would be one of those cases where you run gdb to find out *why*
> it's crashing.
> 
> Cygwin has code for supporting things like /dev/null, /dev/tty, /dev/com1,
> and other things.  There is nothing magic about any of it.  It all gets
> translated into normal Windows API calls eventually.
> 
> It's certainly possible that there is something wrong somewhere in
> cygwin with the handling of /dev/com1 but since this functionality is heavily
> used by our gdb customers it's unlikely that there is something trivially
> wrong with the emulation.
> 
> cgf


I also do not think /dev/com1 is the real problem.  The problem
is the X11 server code, which read/writes to /dev/mem and /dev/iopl
after accessing each device.  
until I get this part straighten out, it is difficult to trace
and fix other problems in x11 code.
Is there any possibility of adding /dev/mem to Cygwin?  I know, as
you mentioned in one of your message, it might slow the application.

Another note, unrealted to this issue:- which relates to Sergey's latest
AF_UNIX diff file.  Out of curiousity I applied his AF_UNIX.diff file to
the lastest Winsup snapshot.  Build goes OK, but  applications linked
against the cygwin1.dll  (with Sergey's AF_UNIX patch) does not
execute.  It gives error, "Application failed to initialized".

Sorry for two different subjects in one message... 

Suhaib

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Emil Hallin]

David Young wrote:
> 
> > ... Check http://www.microsoft.com/hwdrv/ddk ...

correct URL is:
http://www.microsoft.com/hwdev/ddk
                            ^

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Accessing serial port.

[Chris Faylor]

On Thu, Aug 05, 1999 at 01:18:26PM -0400, Suhaib M. Siddiqi wrote:
>
>
>>
>>
>> I am porting my C codes from DJGPP to Cygwin. One of the modules has
>> several lines which read and write to COM1. I rewrite the code using
>> open ("/dev/com1"), read (....), write (....), etc. However, the code
>> seems to hang. The exact same code works fine under Linux by replacing
>> "/dev/com1" to "/dev/ttyS0".
>>
>
>This requires accessing the hardware through a proper device driver on
>Windows.  It is not that easy to change /dev/xxx to someting.  Check
> http://www.microsoft.com/hwdrv/ddk for info about devices.  If it would
>have been so easy I would have finished Xfree86 port a long time ago
>;-)

Um.  No.  I don't know why you think that this requires a device driver.
You should be able to access /dev/com1 using normal open/close/read/write
semantics.

However, there were serial problems in B20.1 that should be fixed in
current snapshots: http://sourceware.cygnus.com/cygwin/snapshots/

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com