[LinuxPPS] ntpd

[Folkert van Heusden]

> > But still ppstest doesn't emit anything at all.
> At this point you shouldn't use ppstest since you are using NTPD which
> does the same things. ppstest has been written for very basic tests.
> I suggest you to enable CONFIG_PPS_DEBUG kernel option and looking the
> kernel messages _while_ NTPD is running.
> If the PPS signal reach your DCD pin you should see something like
> this:
>    serial8250: PPS assert event at xxxxxx
> or
>    serial8250: PPS clear event at xxxxxx

[42996225.890000] drivers/pps/pps.c: New message from PID 16224 (flags 0)
[42996225.890000] drivers/pps/pps.c: PPS_FETCH: source 1
[42996225.910000] drivers/pps/kapi.c: capture clear seq #1812 for source 7
[42996225.910000] drivers/serial/8250.c: serial8250: PPS clear event at 4655295
[42996226.710000] drivers/pps/kapi.c: capture assert seq #1816 for source 7
[42996226.710000] drivers/serial/8250.c: serial8250: PPS assert event at 4655375
[42996226.890000] drivers/pps/pps.c: New message from PID 16224 (flags 0)
[42996226.890000] drivers/pps/pps.c: PPS_FETCH: source 1
[42996226.910000] drivers/pps/kapi.c: capture clear seq #1813 for source 7
[42996226.910000] drivers/serial/8250.c: serial8250: PPS clear event at 4655395

Ah ok, so it now works, right?

> otherwise you should use an oscilloscope to verify if the PPS signal
> is reaching the serial port.

I already verified that and it DOES reach the serial port. When I run
minicom on ttyS1 (on which the GPS is connected), I see the carrier
detect line toggle every second.


Folkert van Heusden

-- 
www.biglumber.com <- site where one can exchange PGP key signatures 
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com