On Thu, Jul 25, 2019 at 11:21:02AM +0530, gourav jain wrote:
> Master side:
>
> 1) setting date:
> root@CDOT-BBWT:/# date
> Thu Jul 25 11:03:00 IST 2019
>
> 3) running ptp4l
>
> root@CDOT-BBWT:/# ./ptp4l -i eth1 -m &
> root@CDOT-BBWT:/# ptp4l main
> ptp4l[4166.518]: selected /dev/ptp0 as PTP clock
> ptp4l[4166.523]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
> ptp4l[4166.524]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
> ptp4l[4174.288]: port 1: LISTENING to MASTER on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> ptp4l[4174.288]: selected local clock 00e00c.fffe.004202 as best master
> ptp4l[4174.289]: assuming the grand master role
>
> 5) running phc2sys
>
> root@CDOT-BBWT:/# ./phc2sys -a -a -r -m&
Oh, sorry, I gave you the wrong command line. It is the -r flag that
needs repeating.
./phc2sys -a -r -r -m
FYI, the phc2sys man page says:
OPTIONS
-a Read the clocks to synchronize from running ptp4l and follow
changes in the port states, adjusting the synchronization direc‐
tion automatically. The system clock (CLOCK_REALTIME) is not
synchronized, unless the -r option is also specified.
-r Only valid together with the -a option. Instructs phc2sys to
also synchronize the system clock (CLOCK_REALTIME). By default,
the system clock is not considered as a possible time source. If
you want the system clock to be eligible to become a time
source, specify the -r option twice.
> root@CDOT-BBWT:/# GJ: autocfg enabled
> GJ: autocfg enabled
> GJ: selected r
> GJ: autocfg mode
> phc2sys[4325.449]: reconfiguring after port state change
> phc2sys[4325.450]: selecting eth1 for synchronization
> phc2sys[4325.451]: nothing to synchronize
Did you see that? .. ^^^^^^^^^^^^^^^^^^^^^^
HTH,
Richard
_______________________________________________
Linuxptp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
