From: Jonathan Bredin <jbredin@co...> - 2005-04-05 21:35:32
I am trying to connect a Gumstix to a Brainstem through the serial
connection at /dev/ttyS0 and am having some difficulties. I have a
program that connects from a Linux i686 desktop to the Brainstem, but
when I cross-compile to the Gumstix problems arrise.
The program uses the Acroname libraries to establish a connection and
reports success on the Gumstix, but times out when trying to read values
from the Brainstem. Writing values reports success, though I see no
sign of it on the Brainstem side. After a couple of attempts, the
program drops the serial connection to the Brainstem.
I've been logging in over bluetooth to a gumstix connected with a serial
cable (not a null modem) on the leftmost (ttyS0) socket connected to the
Does anyone have any ideas? Are there certain baud rates that work?
Strange fcntrl options I need to set?
From: Dave Hylands <dhylands@gm...> - 2005-04-05 22:14:11
> I've been logging in over bluetooth to a gumstix connected with a serial
> cable (not a null modem) on the leftmost (ttyS0) socket connected to the
How are you initializing the serial port on the gumstix side of things?
I have some code that *should* work (it works fine under cygwin).
This page has lots of good info:
Make sure that you choose the right mode (canonical - or cooked mode
is typically used for processing line based input and control
characters have special meaning, non-canonical or raw mode is for
binary style input and a control character is just 8 more bits of
Remember that ttyS0 is normally the console port (where all the output
goes from the kernel during bootup).
Vancouver, BC, Canada
On Apr 5, 2005, at 3:14 PM, Dave Hylands wrote:
> Remember that ttyS0 is normally the console port (where all the output
> goes from the kernel during bootup).
Not just bootup -- even after all the boot messages, if you're booting
with console=ttyS0 then any other console messages after bootup (like
application error messages and such) might also go to that device. Any
reason you wouldn't use the other serial port in this case? Or are you
already doing that for some other device?