Hello Vladimir,

Sorry for the wrong debug log.
I processed this log in excel and saved it, that is why it lost the nano
second information.

Please refer this debug log :
https://drive.google.com/file/d/1bS6_9AOZlcOQVI2_7nY-zqJClZ8IX1Qr/view?usp=sharing
at 1597801630 timestamp.

I am using a 4.14.78 kernel with ublox gps receiver, I don't have access to
NMEA currently.

Thanks & Regards,

*JAIRAJ SOLANKI*


On Mon, Sep 7, 2020 at 2:40 AM Vladimir Oltean <olte...@gmail.com> wrote:

> Hi,
>
> The debug log you've shown:
>
> ts2phc[65078.518]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905801      diff    3
> ts2phc[65078.518]:      /dev/ptp1       master  offset  3       s2
> freq    3063
> ts2phc[65078.758]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    232250871
> ts2phc[65078.758]:      /dev/ptp1       master  offset  232250871
>  s2      freq    32767999
> ts2phc[65078.768]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    247064811
> ts2phc[65078.768]:      /dev/ptp1       master  offset  247064811
>  s2      freq    32767999
> ts2phc[65078.778]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    259363981
> ts2phc[65078.778]:      /dev/ptp1       master  offset  259363981
>  s2      freq    32767999
> ts2phc[65078.791]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    266250998
> ts2phc[65078.791]:      /dev/ptp1       master  offset  266250998
>  s2      freq    32767999
> ts2phc[65078.791]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    269792584
> ts2phc[65078.791]:      /dev/ptp1       master  offset  269792584
>  s2      freq    32767999
> ts2phc[65078.816]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    275713427
> ts2phc[65078.816]:      /dev/ptp1       master  offset  275713427
>  s2      freq    32767999
> ts2phc[65078.825]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    305627546
> ts2phc[65078.825]:      /dev/ptp1       master  offset  305627546
>  s2      freq    32767999
> ts2phc[65078.854]:      /dev/ptp1       extts   index   0       at
> 1597905800      corr    0       src     1597905800      diff    316218230
>
> does not match the code:
>
>         pr_debug("%s extts index %u at %lld.%09u corr %d src %" PRIi64
>                  ".%ld diff %" PRId64,
>                  slave->name, event.index, event.t.sec, event.t.nsec,
>                  slave->correction,
>                  (int64_t) source_ts.tv_sec, source_ts.tv_nsec, *offset);
>
> Specifically, the nanosecond portion of event.t and of source_ts is
> missing from your log.
>
> What other changes have you made to the code?
>
> I don't think one can say much from this log alone. Without seeing the
> nanoseconds portion of the timestamps, you can't get a good impression
> of what is going on. The source timestamps might be running slow, or the
> extts might be running fast, or there might simply be noise on the line
> causing spurious PPS events.
>
> What hardware driver are you using for collecting the extts timestamps?
> What kernel? What GPS module? Can you use the NMEA protocol parser for
> it?
>
> Thanks,
> -Vladimir
>

-- 


 YouTube: *https://youtu.be/Sn2-cZ_Ln9E <https://youtu.be/Sn2-cZ_Ln9E>*
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to