On Fri, Sep 09, 2022 at 08:45:19AM +0800, Hamilton Alex wrote:
> Hi, Richard:
> I am not quite understand. I am using Calnex master-->board slave, if the
> linuxptp print out is correct, that means local clock
> has the same frequency and phase as master clock, then the 1PPS out should
> near
Hi, Richard:
I am not quite understand. I am using Calnex master-->board slave, if the
linuxptp print out is correct, that means local clock
has the same frequency and phase as master clock, then the 1PPS out should
near the reference 1PPS.
why path asymmetry would affect the 1PPS out?
Thanks
On Thu, Sep 08, 2022 at 06:40:26AM -0700, Richard Cochran wrote:
> On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton Alex wrote:
>
> > however, the 1pps time error is around 40 NS, which means my board is
> > ahead of the reference for about 40NS, which doesn't match the result
> > dumped by
On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton Alex wrote:
> however, the 1pps time error is around 40 NS, which means my board is
> ahead of the reference for about 40NS, which doesn't match the result
> dumped by ptp4l.
>
> anyone has met similar issue before? how to debug such issue?
Hi:
I got an issue that linuxptp result doesn't match 1PPS measurement.
my board is acting as a slave, the calnex is acting as a master with
reference clock.
after ptp4l runs, result is below, looks pretty good:
ptp4l[130166.661]: rms1 max2 freq-50 +/- 4 delay 9059 +/- 0
