Hi, an update here, So I found that when launching ptp4l it automatically assigns itself a /dev/ptp* device. One time it assigns /dev/ptp2, another time it assigns /dev/ptp4 etc very random. I have a total of 5 devices: /dev/ptp0, /dev/ptp1, /dev/ptp2, /dev/ptp3 and /dev/ptp4. Phc2sys is launched at the same time by using # phc2sys -c /dev/ptp0 -s CLOCK_REALTIME -m -q -w.
When specifying /dev/ptp0 in the ptp4l command (# ptp4l -i enp0s25 /dev/ptp0 -m -q -4 -H) it still automatically chooses another /dev/ptp* device. When not specifying enp0s25 but only the device (# ptp4l -i /dev/ptp0 -m -q -4 -H) it returns the following message: ioctl CIOCETHTOOL failed: No such device ptp device not specified and automatic determination is not supported. please specify ptp device. In this case, phc2sys will also not start: continuously returning the following messages: waiting for ptp4l … uds: sendto failed: No such file or directory When removing the -w option in the phc2sys command it returns the following: time offset must be specified using -w or -O When letting ptp4l choose a device by just running # ptp4l -i enp0s25 -m -q -4 -H and letting phc2sys synchronise the /dev/ptp0 device to the system clock by using # phc2sys -c /dev/ptp0 -s CLOCK_REALTIME -m -q -w, ptp4l does return the message that it assumed the grandmaster role and phc2sys starts synchronising /dev/ptp0 to the system clock (I also checked this with phc_ctl and this seems perfectly fine). When specifying any other device in the phc2sys command (such as /dev/ptp4 or /dev/ptp2 etc.) it does never reach servo 2 and always keeps returning the message “Clock check: clock jumped forward or running faster than expected!” This seems to me that /dev/ptp0 is the only device that is correctly able to synchronize to the system clock, however I can never get ptp4l to distribute the time of /dev/ptp0 over the network.. Jord > On 14 Jun 2018, at 16:56, Richard Cochran <richardcoch...@gmail.com> wrote: > > On Thu, Jun 14, 2018 at 11:49:44AM +0000, Jord Pool wrote: > >> What is the reason that I am unable to synchronise enp0s25 to the >> system clock? And what is the reason that /dev/ptp0 does synchronise >> to the system clock properly? And what is the reason that /dev/ptp0 >> is not linked to enp0s25? Can I link /dev/ptp0 manually to enp0s25 >> or? > > Please show us: > > ethtool -i enp0s25 > > ethtool -T enp0s25 > > Thanks, > Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
