Hi,
i have the following problem:
Everytime when I try to get access to the Serial Ports I get the feedback that
the permission is denied:
$ /opt/owfs/bin/owhttpd -d /dev/ttyS0 -p 2010 --foreground
DEFAULT: ow_serial_open.c:(38) [Permission denied] Cannot open port: /dev/ttyS0
Permissions problem
On Jun 14 00:59, Yaakov S wrote:
I came across this while working on getting my Palm to hook up to
gnome-pilot over Bluetooth. COM3 is an incoming COM Port created within
Bluetooth Settings, although the STC has the same results on COM1 (a
standard serial port).
Unlike pilot-link's tools
I came across this while working on getting my Palm to hook up to
gnome-pilot over Bluetooth. COM3 is an incoming COM Port created within
Bluetooth Settings, although the STC has the same results on COM1 (a
standard serial port).
Unlike pilot-link's tools and jpilot (all three use pilot-link's
* On Thu, Jan 22, 2009 at 10:55:22AM -0500 Christopher Faylor wrote:
On Thu, Jan 22, 2009 at 10:25:32AM -0500, Paul Ingemi wrote:
[...]
It is a simple enough hack that I don't mind adding it, if it fixes your
problem but I am not convinced that your driver is operating correctly.
As I had
On Sat, Jan 24, 2009 at 03:30:34PM -0500, Paul Ingemi wrote:
* On Thu, Jan 22, 2009 at 10:55:22AM -0500 Christopher Faylor wrote:
On Thu, Jan 22, 2009 at 10:25:32AM -0500, Paul Ingemi wrote:
[...]
It is a simple enough hack that I don't mind adding it, if it fixes your
problem but I am not
On Sat, 24 Jan 2009 16:26:39 -0500 Christopher Faylor wrote:
On Sat, Jan 24, 2009 at 03:30:34PM -0500, Paul Ingemi wrote:
* On Fri, 23 Jan 2009 11:17:57 +0100 Spiro Trikaliotis wrote:
* On Thu, Jan 22, 2009 at 10:55:22AM -0500 Christopher Faylor wrote:
On Thu, Jan 22, 2009 at 10:25:32AM -0500,
Hello,
* On Thu, Jan 22, 2009 at 10:55:22AM -0500 Christopher Faylor wrote:
On Thu, Jan 22, 2009 at 10:25:32AM -0500, Paul Ingemi wrote:
[...]
It is a simple enough hack that I don't mind adding it, if it fixes your
problem but I am not convinced that your driver is operating correctly.
As I
is a test program which exhibits the symptoms when used
with com0com virtual serial ports.
I worked around the problem by performing a second select()
immediately after the first one returns with ready file descriptors.
That second select determines which of these really are ready.
Using strace
in. This does not happen with a real serial
port.
Attached below is a test program which exhibits the symptoms when used
with com0com virtual serial ports.
I worked around the problem by performing a second select()
immediately after the first one returns with ready file descriptors.
That second select
entries for USB serial ports there.
Once you have done that, you should then be able to reuse the previously
occupied COM port numbers.
AndyM
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation
subtree if you find any entries for USB serial ports there.
Once you have done that, you should then be able to reuse the previously
occupied COM port numbers.
AndyM
Don't forget the obvious: MS makes it easy for you to go mad!
It seems there are hidden hidden devices. Have
I've been successfully using the original two serial ports on my
Windows PC, COM1 and COM2, referring to them to Cygwin tools as
/dev/ttyS0 and /dev/ttyS1, respectively. I needed two more serial
ports, so I used a device that plugs into a USB port on a PC and
provides two serial ports
On 2008-08-05, Gary Johnson wrote:
I've been successfully using the original two serial ports on my
Windows PC, COM1 and COM2, referring to them to Cygwin tools as
/dev/ttyS0 and /dev/ttyS1, respectively. I needed two more serial
ports, so I used a device that plugs into a USB port on a PC
Thanks Christopher, thanks Dave,
the last snapshot (cygwin1-20080529.dll.bz2) works perfectly both with
/dev/ttyS5 and /dev/com6
Cheers,
Giovanni
On Thu, May 29, 2008 at 7:12 PM, Christopher Faylor
[EMAIL PROTECTED] wrote:
On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
On Fri, May 30, 2008 at 09:47:59AM +0200, Giovanni Maruzzelli wrote:
Thanks Christopher, thanks Dave,
the last snapshot (cygwin1-20080529.dll.bz2) works perfectly both with
/dev/ttyS5 and /dev/com6
Interesting. Thanks for the verification.
cgf
--
Unsubscribe info:
Hi all,
I am using the 1.7 cygwin on Vista (SP1, updated), installed yesterday
from scratch with setup-2.592-1.7special.exe.
Result of uname -a is:
CYGWIN_NT-6.0 vista-maruzz 1.7.0(0.185/5/2) 2008-05-25 20:10 i686 Cygwin
I cannot see the serial ports (/dev/ttyS*), it seems that they do
wrote on 29 May 2008 13:59:
I cannot see the serial ports (/dev/ttyS*), it seems that they do not
exist under Vista (tried both as a user with admin rights and as
Administrator, and tried also with AUC disabled).
Is this a known bug?
What, not checking errno?
int main (int argc, char* argv
Giovanni Maruzzelli wrote on 29 May 2008 13:59:
I cannot see the serial ports (/dev/ttyS*), it seems that they do not
exist under Vista (tried both as a user with admin rights and as
Administrator, and tried also with AUC disabled).
Is this a known bug?
What, not checking errno?
int
Giovanni Maruzzelli wrote on 29 May 2008 15:27:
Hi Dave,
thank you for the answer.
You mean that this is a bug into 1.7?
My answer was slightly tongue in cheek! :) But yes, it's very likely
you've uncovered a bug in 1.7 - it is work-in-progress after all. There
might be an issue in
in 1.7)
with 1.7 serial ports are missing (but present in 1.5.25)
Any help very appreciated
On Thu, May 29, 2008 at 5:00 PM, Dave Korn [EMAIL PROTECTED] wrote:
Giovanni Maruzzelli wrote on 29 May 2008 15:27:
Hi Dave,
thank you for the answer.
You mean that this is a bug into 1.7?
My answer
(but it works in 1.7)
with 1.7 serial ports are missing (but present in 1.5.25)
Any help very appreciated
Until one of the main developers can attend to it and then upload an
updated snapshot, you might be able to get some useful information for them
by running your test under 'strace'; you'll
waveinopen crashes (but it works in 1.7)
with 1.7 serial ports are missing (but present in 1.5.25)
Any help very appreciated
Until one of the main developers can attend to it and then upload an
updated snapshot, you might be able to get some useful information for them
by running your test
Giovanni Maruzzelli wrote on 29 May 2008 16:41:
Thanks a lot Dave!
Seems that it is looking for a \Device\Serial5
Ouch. That's a problem. Not all serial devices use the same name format.
Although it's not strictly supported, you might be able to work around it
by using .\\com6
.\\com6 gives me Device or resource busy, while all other com*
give me not existing.
So, it is definitely better. But do not yet works. Opening and
read/writing to it with native win32 API works (readfile etc)
following is the relevant strace:
67 36177 [main] ciapa 756 open: open
On Thu, May 29, 2008 at 05:15:00PM +0100, Dave Korn wrote:
Giovanni Maruzzelli wrote on 29 May 2008 16:41:
Thanks a lot Dave!
Seems that it is looking for a \Device\Serial5
Ouch. That's a problem. Not all serial devices use the same name format.
So what format do they use?
Although
Correction, my last post was ambiguous:
.\\com6 gives me Device or resource busy, while all other com*
give me not existing.
So, it is definitely better, it finds something! But do not yet works.
Opening and read/writing to COM6 with native win32 API (readfile
etc) works well, both
On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
Correction, my last post was ambiguous:
.\\com6 gives me Device or resource busy, while all other com*
give me not existing.
So, it is definitely better, it finds something! But do not yet works.
This is a red herring. It
Christopher Faylor wrote on 29 May 2008 17:52:
On Thu, May 29, 2008 at 05:15:00PM +0100, Dave Korn wrote:
Giovanni Maruzzelli wrote on 29 May 2008 16:41:
Thanks a lot Dave!
Seems that it is looking for a \Device\Serial5
Ouch. That's a problem. Not all serial devices use the same
Thank you Christopher!!
I'll try the snapshot tomorrow as soon as I'll be back in office and
then I'll report back.
On Thu, May 29, 2008 at 7:12 PM, Christopher Faylor
[EMAIL PROTECTED] wrote:
On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
Correction, my last post was
On May 2 20:27, Nefastor wrote:
Your trick worked as advertised, and on the first try, thank you very much
:handshake:
Anyone know where this problem with tcsetattr() comes from ? Is it
documented or specific to Cygwin ? (or both ?)
The reason is probably: Nobody ever implemented it.
On Wed, May 07, 2008 at 12:03:19PM +0200, Corinna Vinschen wrote:
On May 2 20:27, Nefastor wrote:
Your trick worked as advertised, and on the first try, thank you very much
:handshake:
Anyone know where this problem with tcsetattr() comes from ? Is it
documented or specific to Cygwin ?
-documentation-on-Cygwin-and-Serial-Ports-tp16827997p17031175.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ
I've got a few apps that still use serial ports, and now
that I'm using Bluetooth devices under XP, the serial
port numbers are getting really big - like COM40.
Yes, I've read about how to change the port number, and
for the Toshiba Bluetooth stack on my Dell D610, it's
not an option.
Yes, I've
Ralph Hempel wrote on 01 May 2008 16:37:
So now the question is, where do we poke around in the
source to increase the limit of serial ports under
Cygwin?
Look at winsup/cygwin/devices.in, which is a template that is used to
auto-generate the code in winsup/cygwin/devices.cc, using
Dave Korn wrote:
Ralph Hempel wrote on 01 May 2008 16:37:
So now the question is, where do we poke around in the
source to increase the limit of serial ports under
Cygwin?
Look at winsup/cygwin/devices.in, which is a template that is used to
auto-generate the code in winsup/cygwin
Ralph Hempel wrote on 01 May 2008 20:04:
Dave Korn wrote:
Ralph Hempel wrote on 01 May 2008 16:37:
So now the question is, where do we poke around in the
source to increase the limit of serial ports under
Cygwin?
Look at winsup/cygwin/devices.in, which is a template that is used
,params);
write (tty,Hello World,11);
close (tty);
return 0;
}
--
View this message in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16995311.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe
On 2008-05-01, Nefastor wrote:
Nefastor wrote:
Thanks for all the info, everyone :-D. I'm gonna try a few things and get
back to you.
So I've tried a few things, and obviously all hell broke loose, sort of.
I've written a very simple Hello World program, which I'll paste at the
end
Nefastor wrote on 24 April 2008 23:08:
case : My machine has two serial port, one on the MoBo and a USB-serial
adapter, yet Windows calls them COM1 and COM3.
Or /dev/ttyS0 and /dev/ttyS2, as they'll be known to cygwin.
Speaking of Windows' DM, it's rather quirky on the serial
ports : I
in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16896990.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16897467.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http
Nefastor wrote on 25 April 2008 17:26:
Thanks Dave, I kinda suspected the FTDI drivers for the COM3 issue
One tip I've learned is never, ever, ever, unplug them while you're still
running your terminal software (or whatever) and it's got the port open.
Disconnect, or exit the application, or
Dave Korn wrote:
RGH[*]! FTDIchip are the bane of my life at the moment. Buggy drivers.
I hate them so much spit.
[*] - I just got back from rebooting a testrig that locked up due to buggy
ftdichip drivers at about the twentytwo-hour point into a twentyseven-hour
testrun. I am not
on the MoBo and a USB-serial
adapter, yet Windows calls them COM1 and COM3. I've searched the whole
Device Manager but couldn't find any device that would be COM2. And I can
rename COM1 to COM2.
Speaking of Windows' DM, it's rather quirky on the serial ports : I noticed
that if I unplug my USB
quirky on the serial ports : I noticed
that if I unplug my USB cable (COM3) and try to change the name of COM1, in
the drop down box COM3 is listed as in use :confused: %-|.
So, I have a machine with two serial ports but no COM2, AND I can change the
COM port number to whatever I want, plus Windows
Nefastor wrote:
I want to write simple programs which use the serial port (for example, a
program that will trap and log activity on a serial port, nothing fancy). I
know how to do that under Linux, and under DOS as well. The problem is I
don't know which of Cygwin's /dev/tty device
in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16827997.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
On Oct 6 14:22, ahnkle wrote:
Hi,
I have more that 9 serial ports on my machine, some real, some virtual.
When I recently tried to open /dev/ttyS21 it failed. Is this :
some inbuilt limit?
Yes, Cygwin only allows /dev/ttyS0 up to /dev/ttyS15 so far. I raised
the limit to 63 in CVS
Hi,
I have more that 9 serial ports on my machine, some real, some virtual.
When I recently tried to open /dev/ttyS21 it failed. Is this :
some inbuilt limit?
some problem with cygwin not seeing some serial ports?
some action required by me to add more ports?
In Windows, doing 'mode
On Aug 14 14:16, [EMAIL PROTECTED] wrote:
Hello everyone,
I have what I suspect is a bug in cygwin's serial port handling which only
seems to manifest itself when using select, then read.
[...]
Thanks for the testcase, it was very helpful. It took me a long time to
come up with a working
ports in my applicaton) is to have one thread
waiting for incoming data on any number of serial ports (in the test code 2).
This reader thread will then send data to a registered user (in the application
a C++ object, in the test code the data is just printed out). Data will only be
sent
On 23 April 2006 05:44, David Christensen wrote:
Dave Korn wrote:
Well then, that's a really good argument for just using the builtin
access that cygwin provides through /dev/ttySx instead, isn't it?
The way Oliver's original post reads suggests that he was just thrown
off by not seeing any
And what is the final answer? Is there a
/dev/ttySx
in Cygwin which can be used in Perl or C, even if I can not see it with ls?
Alex
Dave Korn wrote:
On 23 April 2006 05:44, David Christensen wrote:
Dave Korn wrote:
Well then, that's a really good argument for just using the
is a bit funny because it's virtual, but you can see
it by entering ls -la /dev/ttyS0 explicitly; the mapping is that windows COM
port N is dev/ttyS N minus one; and although ls -la /dev/ttyS.. will work
for more serial ports than there actually are, you'll get ENOENT if you try
and use one that doesn't
Dave Korn schrieb:
Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use CPAN
modules, that is of course a good idea; but if the *nix one doesn't work under
cygwin, fixing it or rolling your own or even just using the bog-standard file
i/o features in perl is definitely far
On 23 April 2006 15:45, Oliver Vecernik wrote:
Dave Korn schrieb:
Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use
CPAN modules, that is of course a good idea; but if the *nix one doesn't
work under cygwin, fixing it or rolling your own or even just using the
On Sun, Apr 23, 2006 at 04:44:46PM +0200, Oliver Vecernik wrote:
Dave Korn schrieb:
Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use
CPAN modules, that is of course a good idea; but if the *nix one
doesn't work under cygwin, fixing it or rolling your own or even just
using the
Christopher Faylor schrieb:
Actually, ls /dev/ttyS3 *does* display proper information. It is ls /dev
which does not show all virtual devices.
You're absolutely right:
$ ls /dev
log=
But I can even list ports that definitely do not exist:
$ ls /dev/ttyS1
/dev/ttyS1
...
$ ls /dev/ttyS15
On Sun, Apr 23, 2006 at 08:26:02PM +0200, Oliver Vecernik wrote:
But I can even list ports that definitely do not exist:
$ ls /dev/ttyS1
/dev/ttyS1
...
$ ls /dev/ttyS15
/dev/ttyS15
The only physical ports that really exists are `/dev/ttyS0' and
`/dev/ttyS3'. Is this the expected behaviour?
On 22 April 2006 06:26, David Christensen wrote:
Oliver Vecernik wrote
I'd like to use the serial port from perl on my notebook.
Try the Win32::SerialPort Perl module:
http://members.aol.com/Bbirthisel/SerialPort.html
I used it in the past and it worked great, but I had to use
Dave Korn wrote:
Well then, that's a really good argument for just using the builtin
access that cygwin provides through /dev/ttySx instead, isn't it?
The way Oliver's original post reads suggests that he was just thrown
off by not seeing any devices under the virtual /dev dir, but that
Oliver Vecernik wrote
I'd like to use the serial port from perl on my notebook.
Try the Win32::SerialPort Perl module:
http://members.aol.com/Bbirthisel/SerialPort.html
I used it in the past and it worked great, but I had to use ActiveState Perl
rather than Cygwin Perl.
HTH,
David
--
Hi,
I'd like to use the serial port from perl on my notebook. This port is
connected via an usb-adapter and referred as COM4: on Windows. I
couldn't find any /dev/ttySx and I'm not sure if this is even supported.
Is this possible under Cygwin?
--
Oliver
Cygwin Configuration Diagnostics
On Fri, 21 Apr 2006, Oliver Vecernik wrote:
Hi,
I'd like to use the serial port from perl on my notebook. This port is
connected via an usb-adapter and referred as COM4: on Windows. I
couldn't find any /dev/ttySx and I'm not sure if this is even supported.
Is this possible under Cygwin?
Matthew,
http://cygwin.com/acronyms/#PPIOSPE. I'm redirecting this to the proper
list, and setting Reply-To: accordingly -- please make sure your mailer
respects it.
On Wed, 19 Apr 2006, Matthew Karas wrote:
Hello,
I've been trying to get awk to write to the serial port under cygwin.
On Wed, 19 Apr 2006, Igor Peshansky wrote:
On Wed, 19 Apr 2006, Matthew Karas wrote:
Hello,
I've been trying to get awk to write to the serial port under cygwin.
#script
BEGIN{
PRINT hello world /dev/com1;
}
#end script
this doesn't work in awk but
[snip]
enabled (RTS/CTS), and it is
unblocked as soon as CTS moves to the correct state.
Is this a problem with how I've configured serial ports? I've spent a lot of
time on the 'Net today and don't find anything related to this specific
problem, tested it on Linux FC4 and I have the behaviour I would
This is just a bit of an update.
I have got Win32::SerialPort working, at least a limited capacity.
After taking a look at the source for it, I discovered that this module
is actually just straight Perl, and it relies on Win32::API. I have
already been using /Reini's cut down version of this
On Tue, 31 May 2005, Jason Pearce wrote:
ps. I was never able to get the /dev/com1 or /dev/ttyS1 devices working.
I expected that I would be able to echo commands into /dev/com1 and cat
replies from it.
Just FYI: /dev/ttyS* devices are numbered from 0, so /dev/com1 corresponds
to
Igor Pechtchanski wrote:
Just FYI: /dev/ttyS* devices are numbered from 0, so /dev/com1 corresponds
to /dev/ttyS0... Also, if you have a sequence of shell commands that
should work but don't (e.g., stty followed by echo followed by read/cat),
could you please post them, along with an
Jason Pearce schrieb:
There was some recent discussion about serial ports and Perl.
http://sourceware.org/ml/cygwin/2005-05/msg00013.html
But I did not see any resolution.
Did anyone end up porting either Win32::SerialPort or Win32API::CommPort
as Reini suggested?
I need to talk
On May 20 19:25, Jason Pearce wrote:
There was some recent discussion about serial ports and Perl.
http://sourceware.org/ml/cygwin/2005-05/msg00013.html
But I did not see any resolution.
Did anyone end up porting either Win32::SerialPort or Win32API::CommPort
as Reini suggested?
I
There was some recent discussion about serial ports and Perl.
http://sourceware.org/ml/cygwin/2005-05/msg00013.html
But I did not see any resolution.
Did anyone end up porting either Win32::SerialPort or Win32API::CommPort
as Reini suggested?
I need to talk to a thermometer via a serial link
On May 20 19:25, Jason Pearce wrote:
There was some recent discussion about serial ports and Perl.
http://sourceware.org/ml/cygwin/2005-05/msg00013.html
But I did not see any resolution.
Did anyone end up porting either Win32::SerialPort or Win32API::CommPort
as Reini suggested?
I
Jason Pearce wrote:
... serial ports and Perl. ...
It's been a while, but I was only able to get Win32::SerialPort working under
ActiveState Perl. The same goes for Tk.
David
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Igor Pechtchanski on 4/28/2005 2:59 PM:
/dev is currently a virtual directory in Cygwin. Try ls -l /dev/ttyS1
-- you should get a listing. If you want Tab-completion, or if you want
find / to look at the devices in /dev, you can
On Apr 29 07:26, Eric Blake wrote:
crw--w--w- 1 eblake None 1, 7 Apr 29 06:45 full
srw-rw-rw- 1 SYSTEM root 53 Apr 28 06:08 log=
crw-rw-rw- 1 eblake None 1, 3 Apr 29 06:45 null
It looks like the relatively new syslogd is responsible for /dev/log.
Yes, it creates and destroys this UNIX
On Fri, 29 Apr 2005, Eric Blake wrote:
According to Igor Pechtchanski on 4/28/2005 2:59 PM:
/dev is currently a virtual directory in Cygwin. Try ls -l /dev/ttyS1
-- you should get a listing. If you want Tab-completion, or if you want
find / to look at the devices in /dev, you can create
Hi,
I just recently installed cygwin on my WinXP box here at work. I am trying to
migrate my Perl scripts over to the cygwin environment.
But now I can not access my Serial Ports thru cygwin. for instance, when I
tried installing a serial port device module for perl, the make file died
On Thu, 28 Apr 2005, rwj wrote:
Hi,
I just recently installed cygwin on my WinXP box here at work. I am
trying to migrate my Perl scripts over to the cygwin environment.
But now I can not access my Serial Ports thru cygwin. for instance,
when I tried installing a serial port device
want COM1, you need /dev/ttyS0.
jeez. yep, i forgot about that, and it just so happens that I have COM1,3,4,5
but not COM2. so of course /dev/ttyS1 failed (which was the test's default).
That solved the most glaring problem. thank you very much.
All of these means serial ports, I presume
81 matches
Mail list logo
