On 2/29/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Feb 29 22:20, hce wrote: > > On 2/29/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote: > > > > /dev/ttyUSB0 works?!? It's no device name recognized by Cygwin, so > > > I assume you created a file on the disk called /dev/ttyUSB0 when > > > using it. > > > > It was copied from Linux. > > > Yeah, I assumed that much. As I said, that's not a device name > Cygwin can do anything useful with. > > > > > My knowledge about serial I/O is rather clumsy, but isn't there a > > > virtual COM port attached, or can't you attach a virtual COM port to > > > your USB I/O? AFAIK, you should find something like, say, COM9, which > > > would be available as /dev/com9 or /dev/ttyS8. > > > > My knowledge to Window machine is also limited. So, I should open > > /dev/com9 or /dev/ttyS8 regardless it is connected to a serial cable > > or a USB serial adaptor. I don't have the Window machine at home, I'll > > try next day. > > > I didn't say you should open /dev/ttyS8. This was just an example. You > first have to find out (or set?) the number of the virtual COM port. > For all I know it could be COM5 or COM12 or whatever. The important > part is that, after you *know* the number X, you can use /dev/comX or > /dev/tty[X-1] to access this serial port. Just don't access it using > the Windows name, COMx or \\.\COMx, because then you will not get any > POSIX serial I/O support from Cygwin.
Thanks Corinna, it works under /dev/comx. One more thing, if a serial port is not connected by a serial cable, it can still open a serila port without errors. That was very stange to everybody when a problem printed out "Open Serial Port /dev/com1 success", but actually there was no cable connected to that port. Is it a bug in Cygwin? Thank you. Kind Regards, Jim -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
