I've got a petalinux platform acting as slave that fails to synch to a
master.  Another similar petalinux platform on the network (different
hardware, same version of petalinux, same apparent ptp settings), synchs
just fine.  I have a feeling that I need to do something in the
platform-specific linux portions (i.e device tree?), but I wonder if anyone
might be able to see any patterns in the below failures.  Does it look like
the timestamping code has something wrong with the value it's using for a
frequency?

This should be running with a 250MHz clock fed to a Cadence macb driver
through an entry in the device tree.  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
ptp4l[1863.879]: rms 7630435116841505792 max 7630435120363045888 freq
+64000000 +/-   0 delay 107581456 +/- 31296274
ptp4l[1872.076]: rms 7630435108731066368 max 7630435112264740864 freq
+64000000 +/-   0 delay 205130930 +/- 31485515
ptp4l[1880.273]: rms 7630435100770999296 max 7630435104247852032 freq
+64000000 +/-   0 delay 165287547 +/- 22174280
ptp4l[1888.470]: rms 7630435092716822528 max 7630435096218990592 freq
+64000000 +/-   0 delay 212781807 +/- 36917730
ptp4l[1896.667]: rms 7630435084654562304 max 7630435088127610880 freq
+64000000 +/-   0 delay 280105538 +/- 28070547
ptp4l[1904.864]: rms 7630435076681515008 max 7630435080188012544 freq
+64000000 +/-   0 delay 262132308 +/- 8259122
ptp4l[1913.061]: rms 7630435068652837888 max 7630435072070512640 freq
+64000000 +/-   0 delay 283602718 +/- 54465238

This was from earlier in the day (it's possible that I manually set time in
between the two events):
# ptp4l  -i eth0 -m -s -f ptp4l.conf
ptp4l[404.634]: selected /dev/ptp0 as PTP clock
ptp4l[404.635]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[404.635]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[404.636]: port 1: link up
ptp4l[405.111]: port 1: new foreign master 0200c0.fffe.a80328-1
ptp4l[409.209]: selected best master clock 0200c0.fffe.a80328
ptp4l[409.210]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[413.006]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[413.734]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[414.030]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[414.607]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[415.055]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[415.191]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[416.080]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[416.184]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[417.104]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[417.856]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[418.129]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[418.129]: rms 1637167828864901376 max 3279450674306890752 freq
+64000000 +/-   0 delay -4098622952691958 +/- 342569061489599
ptp4l[419.153]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[419.655]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[419.810]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[420.178]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[420.801]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[421.203]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[422.227]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[422.505]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[423.252]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[423.526]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[424.277]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[424.686]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[425.301]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[426.326]: clockcheck: clock jumped forward or running faster than
expected!
ptp4l[426.326]: rms 135597402853273248 max 177243599217711776 freq
+64000000 +/-   0 delay -2016234365286032 +/- 501084510336480

Any help would be greatly appreciated.
Aaron
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to