> -----Original Message----- > From: Hutchinson, Brian <brian.hutchin...@l3harris.com> > Sent: Friday, December 06, 2019 2:04 PM > 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 4:57 PM > > To: Hutchinson, Brian (US) <brian.hutchin...@l3harris.com>; linuxptp- > > us...@lists.sourceforge.net > > Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns > > nothing > > > > > -----Original Message----- > > > From: Hutchinson, Brian <brian.hutchin...@l3harris.com> > > > Sent: Friday, December 06, 2019 1:49 PM > > > 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 > > > > > > > > > > > > > > Out of curiosity, what version of linuxptp are you using? it looks > > > > like the -f option is documented on master. > > > > > > > > Thanks, > > > > Jake > > > > > > > > > > I started out with whatever was in Yocto Sumo (2.5) release (I think > > > it was linuxptp 1.8) but quickly realized that it didn't support the > > > G.8275.2 profile I was trying to get to work with my Trimble GM so I > > > had to cherry pick the linuxptp 2.0 recipe from Yocto Warrior (2.7) > > > release. > > > > > > Regards, > > > > > > Brian > > > > > > > Yea. the manual pages were updated in the 1.9.2 release, so you likely just > > have manual pages that are out of date. > > > > At any rate, glad things are working for you! > > > > Best of luck. > > > > Regards, > > Jake > > Thanks! > > So now that I have phc2sys working command line ... I guess I need to have > systemd start that as a service too. I'm guessing that it should be kicked > off using > the -w flag so it hangs out waiting for ptp4l to do it's job syncing with GM. > > Regards, > > Brian >
Yea. If you have ptp4l running as a service, you can also configure the systemd service for phc2sys to avoid starting until after ptp4l is started, though I'm not sure that fully matters. It might even be possible to get ptp4l and phc2sys working with the systemd socket setup so that the sockets for the UDS are started by systemd initially and just used by the phc2sys and ptp4l application. Thanks, Jake _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
