[Avila] COM ports on GW2342

[Tim Harvey]

have you tried simply booting the default linux image the board ships with having a console attached to COM2 to make sure the hardware is good?  What board do you have?

I assume your connecting a DTE (terminal) to COM2 and not a DCE?  I have an application that connects to a DCE on a GW2347 (therefore I use a null-modem adapter) and I have found in that instance whatever the redboot bootloader is doing to the serial port, locks up my DCE (my DCE is a dallas 1-wire rs232 adapter).  In that case, I modified redboot and told it I only had 1 COM port so that it did not try to intialize COM2 and everything was fine.

Tim

----- Original Message ----
From: "Boal, Mihir D  (US SSA)" <mihir.boal at baesystems.com>
To: Avila <avila at lists.unixstudios.net>
Sent: Monday, August 21, 2006 4:32:35 PM
Subject: [Avila] COM ports on  GW2342
Subject: [Avila] Hi All,

  I have installed a serial device on COM2, however my application (serial port server- sercd) cannot read anything from this device although stty showed that it is configured correctly. I changed the kernel to use COM2 for terminal output and connected my serial device to COM1 and I still could not read from the device so this excercise seemed to imply  that COM1 and COM2 were working. Are both COM ports locked out by kernel or someone?

Everything works fine on X86 based machine running  fedora5 , i.e my app is able to read from device.

Does kernel take over both com port not allowing apps to read serial ports ? Any clues suggestion is will be very helpfull 

Thanks

Mihir

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net