> -----Original Message-----
> From: Hutchinson, Brian <brian.hutchin...@l3harris.com>
> Sent: Friday, December 06, 2019 11:58 AM
> To: Keller, Jacob E <jacob.e.kel...@intel.com>; linuxptp-
> us...@lists.sourceforge.net
> Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns nothing
> 
> 
> 
> > -----Original Message-----
> > From: Keller, Jacob E <jacob.e.kel...@intel.com>
> > Sent: Friday, December 6, 2019 12:18 PM
> > To: Hutchinson, Brian (US) <brian.hutchin...@l3harris.com>
> > Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns 
> > nothing
> >
> > > -----Original Message-----
> > > From: Hutchinson, Brian via Linuxptp-users <linuxptp-
> > > us...@lists.sourceforge.net>
> > > Sent: Friday, December 06, 2019 8:32 AM
> > > To: linuxptp-users@lists.sourceforge.net
> > > Subject: [Linuxptp-users] phc2sys stuck ... "Waiting for ptp4l..." and
> > > pmc returns nothing
> > >
> > > Hi,
> > >
> > > So I think I have ptp4l running ok:
> > >
> >
> > <snip>
> >
> > > ... but when I try to run phc2sys with the -m option all I get is 
> > > "Waiting for
> > ptp4l..."
> > >
> > > I've tried phc2sys -a -r -m, phc2sys -s eth0 -c CLOCK_REALTIME -w -m
> > > and a bunch of other combinations with same result.
> > >
> > > So I'm not understanding something or doing something right.  I'm not
> > > even 100% if I even need to be running phc2sys.
> > >
> > > Also, I tried to make ptp4l start as a service with systemd.  When I
> > > do a 'ps' I see it's started at bootup but can't see if it's synced
> > > properly.  I'm basically using NXP's Yocto build for the IMX8 Mini and
> > > have busybox versions of syslog etc.  When I look at /var/log/messages
> > > I don't see any ptp4l related messages and when I try to run any of the 
> > > pmc
> > commands nothing comes back at all.
> > >
> > > I've tried:
> > >
> > > pmc -u -b 0 'GET TIME_STATUS_NP'
> > > pmc -u -b 0 'GET CURRENT_DATA_SET'
> > >
> > > ... and get nothing.
> > >
> > > Any ideas how I can tell if the ptp4l service is synced up properly???
> > >
> > > Regards,
> > >
> > > Brian
> > >
> >
> > Did you change the clock domainNumber in the configuration? the unix
> > socket will advertise messages over that domain number and phyc2ys's
> > default might not match the configuration you used with p4ptl. This could be
> > why the UDS doesn't connect properly. I'm not sure what other config
> > options might impact this, but you could try using the -f
> > /etc/linuxptp/ptp4l.conf to load the same config when running pmc or
> > phc2sys
> >
> > Thanks,
> > Jake
> 
> Yes, I'm using the G. 8275.2 telco profile and domain is 44.  I didn't even 
> think
> about using the .conf file ... totally glossed over the fact phc2sys and pmc 
> even
> had a -f switch!  In fact the pmc man page I was looking at on the web didn't 
> even
> show a -f option.
> 
> It all works now!  You are the man!!!
> 
> Regards,
> 
> Brian

Out of curiosity, what version of linuxptp are you using? it looks like the -f 
option is documented on master.

Thanks,
Jake
 



_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to