From: <tim...@co...> - 2007-09-26 01:40:36
|
try /dev/ttyS1 -------------- Original message ---------------------- From: "Brown, Scott A CIV NAVAIR, 472500D" <sco...@na...> > Hi folks, > > On the console-hw, I read on the wiki that the inner 8 pin mini-DIN > female connector is the one that you connect to the host machine. > Testing proved that the host machine links up to the gumstix via Kermit > or minicom. When I connect to the outer serial connector and try to > communicate to the host machine, nothing happens. Why is this? If I > want to send information on the outer serial connector to another > device, what is the outer serial connectors name? > > Thanks, > > Scott Brown > |
From: Scott B. <sco...@na...> - 2007-09-26 18:23:23
|
<timcrawford <at> comcast.net> writes: > > try /dev/ttyS1 > -------------- Original message ---------------------- > From: "Brown, Scott A CIV NAVAIR, 472500D" <scott.a.brown4 <at> navy.mil> > > Hi folks, > > > > On the console-hw, I read on the wiki that the inner 8 pin mini-DIN > > female connector is the one that you connect to the host machine. > > Testing proved that the host machine links up to the gumstix via Kermit > > or minicom. When I connect to the outer serial connector and try to > > communicate to the host machine, nothing happens. Why is this? If I > > want to send information on the outer serial connector to another > > device, what is the outer serial connectors name? > > > > Thanks, > > > > Scott Brown Thanks for the feedback, but I have tried /dev/ttyS1. In the /dev file I can see the tty0, tty1, tty2, etc. listed. I have been searching for a way to check to see what serial ports are recognized by the kernel and which aren't, but with no luck. Gumstix doesn't seem to support the setserial command to see if it can locate what serial port is doing what. I have tried to connect to the outer serial connector on the console using minicom but it doesnt recognize any communication from the host machine. Is there a way to check to see what serial port is doing what? Does gumstix have any kind of Bios to set serial ports? What I have is a wifistix FCC + connex 400xm + console-hw connecting to a device to fly an RC airplane. In order to monitor how the device is responding to my software, I hooked up one of the serial connectors on the console-hw to a host machine and connected the other serial port to the avionics on the RC airplane. When I broadcast wirelessly to the gumstix, my groudstation recognizes the software that I installed onto the gumstix but doesn't recognize the avionics. Testing showed that the outer serial connector isn't sending or receiving data. The only way that I can communicate with the gumstix is by connecting to the inner serial connector. Anyone know how to test to see how to set the outer serial up to send or receive data? or possibly the outer connector is broken and I need a new console-hw? Thanks, Scott Brown |
From: Craig H. <cr...@gu...> - 2007-09-26 19:49:46
|
On Sep 26, 2007, at 11:23 AM, Scott Brown wrote: > I have been searching for a way to > check to see what serial ports are recognized by the kernel and > which aren't, > but with no luck. dmesg | grep UART C |
From: Dave H. <dhy...@gm...> - 2007-09-26 20:59:29
|
Hi Scott, > Thanks for the feedback, but I have tried /dev/ttyS1. In the /dev file I can > see the tty0, tty1, tty2, etc. listed. I have been searching for a way to > check to see what serial ports are recognized by the kernel and which aren't, > but with no luck. Gumstix doesn't seem to support the setserial command to see > if it can locate what serial port is doing what. I have tried to connect to > the outer serial connector on the console using minicom but it doesnt recognize > any communication from the host machine. Is there a way to check to see what > serial port is doing what? Does gumstix have any kind of Bios to set serial > ports? I use a little program I wrote called sertest on the gumstix and whatever terminal program you use for talking to the console to talk to the other port. By default, there is no software on the gumstix talking to the serial port, so I wouldn't expect to see anything show up by just connecting to it using minicom from the host. You can find sertest here: <http://docswiki.gumstix.com/Sample_code/C/Serial> Once you've compiled it, and copied it to the gumstix, from the console do: sertest -b 9600 -p /dev/ttyS1 The connect using minicom and set the baud rate to 9600. Also, check the GPIO settings as per: <http://docswiki.gumstix.com/Gumstix_UARTs> -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |