Hi folks, I need to use a program that access a serial port. The link to the serial port in ~/.wine/dosdevices/ and permissions are correct but at the terminal appears the following message: fixme:comm:GetCommProperties (0x48 0x33edac ) and the program cannot access the serial port. How could it be fixed? -- Marco Aur?lio
>>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> writes:Marco> Hi folks, I need to use a program that access a serial port. The Marco> link to the serial port in ~/.wine/dosdevices/ and permissions Marco> are correct but at the terminal appears the following message: Marco> fixme:comm:GetCommProperties (0x48 0x33edac ) Marco> and the program cannot access the serial port. How could it be Marco> fixed? Try to digg deeper, perhaps by running with relay debugging. Does the program really abort to access the serial port after the failing call to GetCommProperties()? Bye -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Em Dom 13 Mai 2007, voc? escreveu:> >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> writes: > > Marco> Hi folks, I need to use a program that access a serial port. The > Marco> link to the serial port in ~/.wine/dosdevices/ and permissions > Marco> are correct but at the terminal appears the following message: > > Marco> fixme:comm:GetCommProperties (0x48 0x33edac ) > > Marco> and the program cannot access the serial port. How could it be > Marco> fixed? > > Try to digg deeper, perhaps by running with relay debugging. Does the > program really abort to access the serial port after the failing call to > GetCommProperties()? > > ByeThe program do not crash, but it does not write or read from the serial port. It presents an error message and continues but does not work. The program was compiled with Borland C builder (do not know the version). I have the sorce code but not the compiler. It was created by a friend many years ago to help me test a electronic board. I tried to use hyperterminal to test the serial port access, but I could not setup it properly or it does not work under wine. I also tried to install an old terminal program called PROCOMM but the SETUP program complains that a SHELL.DLL was not found and aborts. I am triyng to find a simple terminal that uses a serial port to test it. -- Marco Aur?lio
On Sun, 2007-05-13 at 16:32 -0300, Marco Aur?lio Carvalho wrote:> Em Dom 13 Mai 2007, voc? escreveu: > > >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> writes: > > > > Marco> Hi folks, I need to use a program that access a serial port. The> The program do not crash, but it does not write or read from the serial port. > It presents an error message and continues but does not work. The program was > compiled with Borland C builder (do not know the version). I have the sorce > code but not the compiler. It was created by a friend many years ago to help > me test a electronic board. > I tried to use hyperterminal to test the serial port access, but I could not > setup it properly or it does not work under wine. > I also tried to install an old terminal program called PROCOMM but the SETUP > program complains that a SHELL.DLL was not found and aborts. > I am triyng to find a simple terminal that uses a serial port to test it. >Am I correct in thinking that this port has to communicate with a cpu on your test board which is talking via i2c boosted to rs-232 levels? Your firmware will have the baud rate set, along with parity, and error bits. Do you know what these settings should be? And some of the older circuits for this are inadequate, not meeting RS232 specs. Probably it is smartest to try to talk or listen in linux first, to get past those errors. man setserial is your friend. -- Declan Moriarty <junk_mail@iol.ie>
El Lunes, 14 de Mayo de 2007 06:55, Declan Moriarty escribi?:> On Sun, 2007-05-13 at 16:32 -0300, Marco Aur?lio Carvalho wrote: > > Em Dom 13 Mai 2007, voc? escreveu: > > > >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> > > > >>>>> writes: > > > > > > Marco> Hi folks, I need to use a program that access a serial port. > > > The > > > > The program do not crash, but it does not write or read from the serial > > port. It presents an error message and continues but does not work. The > > program was compiled with Borland C builder (do not know the version). I > > have the sorce code but not the compiler. It was created by a friend many > > years ago to help me test a electronic board. > > I tried to use hyperterminal to test the serial port access, but I could > > not setup it properly or it does not work under wine. > > I also tried to install an old terminal program called PROCOMM but the > > SETUP program complains that a SHELL.DLL was not found and aborts. > > I am triyng to find a simple terminal that uses a serial port to test it. > > Am I correct in thinking that this port has to communicate with a cpu on > your test board which is talking via i2c boosted to rs-232 levels? Your > firmware will have the baud rate set, along with parity, and error bits. > Do you know what these settings should be? And some of the older > circuits for this are inadequate, not meeting RS232 specs. > > Probably it is smartest to try to talk or listen in linux first, to get > past those errors. > man setserial is your friend.Group and owner of /dev/ttyS0 are rigth? Try chmod youruser.yourgroup /dev/ttyS0 This can grant permission. Regards -- SCHlabs developers +54 11 4639-5945 Buenos Aires, Argentina be free, be linux.
Em Seg 14 Mai 2007, voc? escreveu:> >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> writes: > > Marco> The program do not crash, but it does not write or read from the > Marco> serial port. It presents an error message and continues but > does Marco> not work. The program was compiled with Borland C builder (do > not Marco> know the version). I have the sorce code but not the > Marco> compiler. It was created by a friend many years ago to help me > Marco> test a electronic board. I tried to use hyperterminal to test > Marco> the serial port access, but I could not setup it properly or it > Marco> does not work under wine. I also tried to install an old > Marco> terminal program called PROCOMM but the SETUP program complains > Marco> that a SHELL.DLL was not found and aborts. I am triyng to find > a Marco> simple terminal that uses a serial port to test it. > > What error message? Can you show the code?I will try to find more information on source program in the next weekend. The program was written many years ago and I need to find the source files. -- Marco Aur?lio
Em Seg 14 Mai 2007, Declan Moriarty escreveu:> On Sun, 2007-05-13 at 16:32 -0300, Marco Aur?lio Carvalho wrote: > > Em Dom 13 Mai 2007, voc? escreveu: > > > >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> > > > >>>>> writes: > > > > > > Marco> Hi folks, I need to use a program that access a serial port. > > > The > > > > The program do not crash, but it does not write or read from the serial > > port. It presents an error message and continues but does not work. The > > program was compiled with Borland C builder (do not know the version). I > > have the sorce code but not the compiler. It was created by a friend many > > years ago to help me test a electronic board. > > I tried to use hyperterminal to test the serial port access, but I could > > not setup it properly or it does not work under wine. > > I also tried to install an old terminal program called PROCOMM but the > > SETUP program complains that a SHELL.DLL was not found and aborts. > > I am triyng to find a simple terminal that uses a serial port to test it. > > Am I correct in thinking that this port has to communicate with a cpu on > your test board which is talking via i2c boosted to rs-232 levels? Your > firmware will have the baud rate set, along with parity, and error bits. > Do you know what these settings should be? And some of the older > circuits for this are inadequate, not meeting RS232 specs. > > Probably it is smartest to try to talk or listen in linux first, to get > past those errors. > man setserial is your friend.The problem is not with my board or the serial HW. The external circuits use correct RS232 levels with 8N1 and 57600 baud. I can use the program inside a XP that runs inside VMware of the same machine. I am trying to run the SW directly on Linux with wine. -- Marco Aur?lio
Em Seg 14 Mai 2007, Christian Schmitz escreveu:> El Lunes, 14 de Mayo de 2007 06:55, Declan Moriarty escribi?: > > On Sun, 2007-05-13 at 16:32 -0300, Marco Aur?lio Carvalho wrote: > > > Em Dom 13 Mai 2007, voc? escreveu: > > > > >>>>> "Marco" == Marco Aur?lio Carvalho <maurelioc@astrotec.com.br> > > > > >>>>> writes: > > > > > > > > Marco> Hi folks, I need to use a program that access a serial > > > > port. The > > > > > > The program do not crash, but it does not write or read from the serial > > > port. It presents an error message and continues but does not work. The > > > program was compiled with Borland C builder (do not know the version). > > > I have the sorce code but not the compiler. It was created by a friend > > > many years ago to help me test a electronic board. > > > I tried to use hyperterminal to test the serial port access, but I > > > could not setup it properly or it does not work under wine. > > > I also tried to install an old terminal program called PROCOMM but the > > > SETUP program complains that a SHELL.DLL was not found and aborts. > > > I am triyng to find a simple terminal that uses a serial port to test > > > it. > > > > Am I correct in thinking that this port has to communicate with a cpu on > > your test board which is talking via i2c boosted to rs-232 levels? Your > > firmware will have the baud rate set, along with parity, and error bits. > > Do you know what these settings should be? And some of the older > > circuits for this are inadequate, not meeting RS232 specs. > > > > Probably it is smartest to try to talk or listen in linux first, to get > > past those errors. > > man setserial is your friend. > > Group and owner of /dev/ttyS0 are rigth? Try > > chmod youruser.yourgroup /dev/ttyS0 > > This can grant permission. > > RegardsNo problem with permissions. I am already the owner of the serial port. That was the first thing I confirmed. I also have a script that runs on boot to set permissions to serial and parallel ports. I use chip programmers on parallel port and the serial port is used to talk to external boards. In my office I also use a 2 serial/1 parallel port expansion board. I have there 2 types of programmers there, one tied to a main parallel port and another tied to the expansion parallel port. -- Marco Aur?lio