On Mon, Jun 22, 2020 at 06:08:53PM -0400, Aaron Biver wrote: > This should be running with a 250MHz clock fed to a Cadence macb driver > through an entry in the device tree.
What platform, kernel, and driver are you using? > The macb driver is doing the > timestamping, supposedly. PHY timestamping is turned off in the kernel, in > the below examples, I believe phc2sys was not running, or if it was, it was > most certainly waiting for calibration. > > Mostly, on the failing slave, I get: > > # ptp4l -i eth0 -m -s -f ptp4l.conf > ptp4l[1848.892]: selected /dev/ptp0 as PTP clock > ptp4l[1848.893]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[1848.893]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[1848.893]: port 1: link up > ptp4l[1849.809]: port 1: new foreign master 0200c0.fffe.a80328-1 > ptp4l[1853.908]: selected best master clock 0200c0.fffe.a80328 > ptp4l[1853.908]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE It looks like the port is staying in the UNCALIBRATED state. It will not progress until the port performs a path/peer delay measurement. I would look to see why this failure to complete. Thanks, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
