Author Topic: Pb with GPS on ttyS0  (Read 3298 times)

DReymann

  • Newbie
  • *
  • Posts: 34
    • View Profile
Pb with GPS on ttyS0
« on: January 30, 2004, 09:28:10 am »
Hi,

I have a strange problem when I try to use my Garmin GPS on the serial port of my C760.

I have a cable which connects the Sharp I/O-port with a 9-pin serial cable. The cable is working as a test with a modem shows (echo ATZ ] /dev&ttyS0 leads to flickering modem leds).

I want to use my Garmin GPS 12 XL. It is setup for NMEA output with 4800 baud. The GPS is working with my Laptop and with my desktop-PC!

Everytime I connect the running GPS to the serial port or when I start the connected GPS I get a connection to my zaurus for a second or so (all gps-programs show, that they received some data) but then the program for the PC-Link (internally it\'s qtsamba) pops up and seems to block the serial port.

I tried the following (I found some posts in the net to do so):

- uncommented the line \"pd:3:respawn:/etc/sync/serialctl\" in /etc/inittab and restartet inet (init q).
- installed module serial_cs (modprobe serial_cs)
- aktivated/deactivated samba
- deactivating pppd (/etc/ppp/ppp-off or /etc/ppp/ppp stop)

I even reflashed the zaurus to the original Sharp-Rom with no other programs installed (I currently use the Cacko-QTopia-Rom).

No change in the behaviour. Something seems to \"listen\" on the serial port and starts qtsamba when incoming data is detected.


Any idea?

Detlev

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
Pb with GPS on ttyS0
« Reply #1 on: January 30, 2004, 11:22:01 am »
I\'ve had gpsd running without troubles on a Sharp 3.08 ROM. I presume you are using a null modem cable between your serial cable and the GPS?

Si
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

DReymann

  • Newbie
  • *
  • Posts: 34
    • View Profile
Pb with GPS on ttyS0
« Reply #2 on: January 30, 2004, 11:51:25 am »
Hi,

Quote
I\'ve had gpsd running without troubles on a Sharp 3.08 ROM. I presume you are using a null modem cable between your serial cable and the GPS?

Si

no, a \"regular\" serial cable. I own a null modem cable too, but there is no connection to the GPS with a null modem cable.

The ability to send commands to a modem shows, that it is the correct cable type.

In addition I meanwhile tested a little bit more and if I rename qtsamba to something else, there is a hourglas in the status line after connecting to the gps-device but the gps-programs work correctly. So the cable is correct.
But I don\'t find the process, which listens to the serial port and which tries to start qtsamba. :?:

Detlev

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
Pb with GPS on ttyS0
« Reply #3 on: January 30, 2004, 12:11:04 pm »
Fair enough. I\'m afraid I can\'t help you then. My assumption was that the sync software/system is basically the same for the C760 and the 5500 with the newer Sharp ROMs. I may well be wrong.

One thing which it might be worth checking is whether the PC Link applet is set to use serial rather than USB/IO which should eliminate the problem (though this applet might not even exist on your machine). I can\'t remember off the top of my head how pppd waited for the serial port on the old Sharp ROMs and unfortunately the devnet\'s down at the moment so I can\'t find out either.

Good luck,


Si
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

DReymann

  • Newbie
  • *
  • Posts: 34
    • View Profile
Pb with GPS on ttyS0
« Reply #4 on: January 30, 2004, 01:08:39 pm »
Hi,

no, the problem is independent of the settings of the PC Link applet. There is no serial option on the zaurus anyway.
I thought I have some knowledge on linux-systems (startet with Xenix for 286 systems some years ago 8-) ) but I really have no idea how to find the process which is listening to /dev/ttyS0.

grrr...  a little bit frustated ...

Detlev