Part Number: XEVMK2LX
Other Parts Discussed in Thread: 66AK2L06
We are running the latest version of Linux on the ARM core of the K2L (from SDK software-dl.ti.com/.../index_FDS.html) and with the below options for ptp4l and phc2sys.
We are seeing ptp4l reporting "clock jumped forward" from multiple boards connected to the same master, but at different times.
root@k2l-evm:~# cat /etc/ptp4l.conf | grep -v "#"
[global]
slaveOnly 1
logAnnounceInterval 2
logSyncInterval 0
logMinDelayReqInterval 1
logMinPdelayReqInterval 1
announceReceiptTimeout 3
syncReceiptTimeout 0
fault_reset_interval ASAP
assume_two_step 0
logging_level 7
tx_timestamp_timeout 500
step_threshold 0.0000001
first_step_threshold 0.0000001
clock_servo nullf
network_transport L2
delay_mechanism E2E
time_stamping hardware
priority1 255
root@k2l-evm:~# cat /etc/default/phc2sys
# Add command line options for phc2sys
PHC2SYS_OPTS=-s /dev/ptp0 -w -S 0.00002 -F 0.00002 -l 7
<14>1 2023-05-18T06:58:03+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11848.820] master offset -2 s0 freq +0 path delay 2054
<14>1 2023-05-18T06:58:04+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11849.392] CLOCK_REALTIME phc offset -8 s2 freq -7 delay 1471
<14>1 2023-05-18T06:58:04+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11849.820] master offset -4 s0 freq +0 path delay 2056
<14>1 2023-05-18T06:58:05+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11850.393] CLOCK_REALTIME phc offset 0 s2 freq -1 delay 1465
<14>1 2023-05-18T06:58:05+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11850.820] master offset -4 s0 freq +0 path delay 2056
<14>1 2023-05-18T06:58:06+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11851.393] CLOCK_REALTIME phc offset 3 s2 freq +2 delay 1458
<14>1 2023-05-18T06:58:06+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11851.820] master offset 4 s0 freq +0 path delay 2056
<14>1 2023-05-18T06:58:07+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11852.393] CLOCK_REALTIME phc offset 6 s2 freq +6 delay 1452
<14>1 2023-05-18T06:58:07+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11852.820] master offset -4 s0 freq +0 path delay 2056
<14>1 2023-05-18T06:58:08+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11853.393] CLOCK_REALTIME phc offset -7 s2 freq -5 delay 1452
<14>1 2023-05-18T06:58:08+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11853.825] master offset -12 s0 freq +0 path delay 2056
<12>1 2023-05-18T06:58:09+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11854.165] clockcheck: clock jumped forward or running faster than expected!
<14>1 2023-05-18T06:58:09+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11854.394] CLOCK_REALTIME phc offset -34359738362 s0 freq -5 delay 1489
<14>1 2023-05-18T06:58:09+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11854.820] master offset 34359738372 s1 freq +0 path delay 2056
<14>1 2023-05-18T06:58:10+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11855.394] CLOCK_REALTIME phc offset 13 s0 freq -5 delay 1501
<14>1 2023-05-18T06:58:10+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11855.820] master offset 0 s2 freq +0 path delay 2056
<13>1 2023-05-18T06:58:10+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11855.820] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<14>1 2023-05-18T06:58:11+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11856.394] CLOCK_REALTIME phc offset 16 s2 freq +3 delay 1453
<14>1 2023-05-18T06:59:34+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14361.516] CLOCK_REALTIME phc offset -2 s2 freq -3 delay 1502
<14>1 2023-05-18T06:59:34+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14362.078] master offset -18 s0 freq +0 path delay 2193
<14>1 2023-05-18T06:59:35+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14362.516] CLOCK_REALTIME phc offset 12 s2 freq +11 delay 1489
<14>1 2023-05-18T06:59:35+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14363.078] master offset -10 s0 freq +0 path delay 2193
<14>1 2023-05-18T06:59:36+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14363.516] CLOCK_REALTIME phc offset -12 s2 freq -10 delay 1453
<14>1 2023-05-18T06:59:36+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14364.078] master offset -26 s0 freq +0 path delay 2193
<14>1 2023-05-18T06:59:37+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14364.517] CLOCK_REALTIME phc offset 3 s2 freq +2 delay 1459
<14>1 2023-05-18T06:59:37+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14365.078] master offset -8 s0 freq +0 path delay 2191
<14>1 2023-05-18T06:59:38+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14365.517] CLOCK_REALTIME phc offset -12 s2 freq -13 delay 1471
<14>1 2023-05-18T06:59:38+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14366.078] master offset 0 s2 freq +0 path delay 2191
<13>1 2023-05-18T06:59:38+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14366.084] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<12>1 2023-05-18T06:59:39+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14366.298] clockcheck: clock jumped forward or running faster than expected!
<14>1 2023-05-18T06:59:39+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14366.517] CLOCK_REALTIME phc offset -34359738370 s0 freq -13 delay 1501
<14>1 2023-05-18T06:59:39+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14367.078] master offset 34359738352 s1 freq +0 path delay 2191
<13>1 2023-05-18T06:59:39+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14367.080] port 1 (eth0): SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
<14>1 2023-05-18T06:59:40+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14367.517] CLOCK_REALTIME phc offset 8 s0 freq -13 delay 1502
<14>1 2023-05-18T06:59:40+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14368.078] master offset 0 s2 freq +0 path delay 2191
<13>1 2023-05-18T06:59:40+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14368.080] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<14>1 2023-05-18T06:59:41+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [14368.518] CLOCK_REALTIME phc offset 34 s2 freq +22 delay 1477
<14>1 2023-05-18T06:59:41+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [14369.078] master offset 8 s0 freq +0 path delay 2191
<14>1 2023-05-18T08:05:28+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18315.490] CLOCK_REALTIME phc offset -2 s2 freq -1 delay 1508
<14>1 2023-05-18T08:05:28+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18316.082] master offset -8 s0 freq +0 path delay 2183
<14>1 2023-05-18T08:05:29+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18316.490] CLOCK_REALTIME phc offset -8 s2 freq -7 delay 1471
<14>1 2023-05-18T08:05:29+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18317.082] master offset -16 s0 freq +0 path delay 2183
<14>1 2023-05-18T08:05:30+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18317.490] CLOCK_REALTIME phc offset 2 s2 freq +0 delay 1459
<14>1 2023-05-18T08:05:30+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18318.082] master offset -18 s0 freq +0 path delay 2185
<14>1 2023-05-18T08:05:31+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18318.491] CLOCK_REALTIME phc offset 8 s2 freq +7 delay 1489
<14>1 2023-05-18T08:05:31+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18319.082] master offset -18 s0 freq +0 path delay 2185
<14>1 2023-05-18T08:05:32+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18319.491] CLOCK_REALTIME phc offset -5 s2 freq -4 delay 1501
<14>1 2023-05-18T08:05:32+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18320.082] master offset -16 s0 freq +0 path delay 2183
<14>1 2023-05-18T08:05:33+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18320.491] CLOCK_REALTIME phc offset -33 s2 freq -33 delay 1630
<14>1 2023-05-18T08:05:33+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18321.082] master offset -16 s0 freq +0 path delay 2183
<14>1 2023-05-18T08:05:34+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18321.491] CLOCK_REALTIME phc offset -39 s2 freq -49 delay 1612
<14>1 2023-05-18T08:05:34+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18322.082] master offset 0 s2 freq +0 path delay 2183
<13>1 2023-05-18T08:05:34+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18322.088] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<12>1 2023-05-18T08:05:35+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18322.359] clockcheck: clock jumped forward or running faster than expected!
<14>1 2023-05-18T08:05:35+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18322.491] CLOCK_REALTIME phc offset -34359738287 s0 freq -49 delay 1507
<14>1 2023-05-18T08:05:35+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18323.082] master offset 34359738352 s1 freq +0 path delay 2183
<13>1 2023-05-18T08:05:35+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18323.083] port 1 (eth0): SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
<14>1 2023-05-18T08:05:36+00:00 192.168.192.51 k2l-evm - - - phc2sys[206]: [18323.492] CLOCK_REALTIME phc offset 107 s0 freq -49 delay 1471
<14>1 2023-05-18T08:05:36+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18324.082] master offset 0 s2 freq +0 path delay 2183
<13>1 2023-05-18T08:05:36+00:00 192.168.192.51 k2l-evm - - - ptp4l[205]: [18324.083] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<14>1 2023-05-18T07:00:28+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11993.820] master offset -24 s0 freq +0 path delay 2056
<14>1 2023-05-18T07:00:29+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11994.428] CLOCK_REALTIME phc offset -7 s2 freq -6 delay 1471
<14>1 2023-05-18T07:00:29+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11994.820] master offset -16 s0 freq +0 path delay 2056
<14>1 2023-05-18T07:00:30+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11995.428] CLOCK_REALTIME phc offset -1 s2 freq -2 delay 1501
<14>1 2023-05-18T07:00:30+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11995.820] master offset -8 s0 freq +0 path delay 2056
<14>1 2023-05-18T07:00:31+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11996.429] CLOCK_REALTIME phc offset 4 s2 freq +3 delay 1501
<14>1 2023-05-18T07:00:31+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11996.820] master offset -16 s0 freq +0 path delay 2056
<14>1 2023-05-18T07:00:32+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11997.429] CLOCK_REALTIME phc offset 3 s2 freq +3 delay 1459
<14>1 2023-05-18T07:00:32+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11997.820] master offset -24 s0 freq +0 path delay 2056
<14>1 2023-05-18T07:00:33+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11998.429] CLOCK_REALTIME phc offset 1 s2 freq +2 delay 1501
<14>1 2023-05-18T07:00:33+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11998.820] master offset -14 s0 freq +0 path delay 2054
<14>1 2023-05-18T07:00:34+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [11999.429] CLOCK_REALTIME phc offset 7 s2 freq +8 delay 1495
<14>1 2023-05-18T07:00:34+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [11999.820] master offset -12 s0 freq +0 path delay 2052
<14>1 2023-05-18T07:00:35+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [12000.430] CLOCK_REALTIME phc offset 4 s2 freq +7 delay 1508
<14>1 2023-05-18T07:00:35+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [12000.825] master offset 34359738340 s1 freq +0 path delay 2052
<12>1 2023-05-18T07:00:35+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [12000.925] clockcheck: clock jumped forward or running faster than expected!
<14>1 2023-05-18T07:00:36+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [12001.430] CLOCK_REALTIME phc offset -49 s2 freq -45 delay 1465
<14>1 2023-05-18T07:00:36+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [12001.820] master offset 16 s0 freq +0 path delay 2052
<14>1 2023-05-18T07:00:37+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [12002.430] CLOCK_REALTIME phc offset -2 s2 freq -12 delay 1446
<14>1 2023-05-18T07:00:37+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [12002.820] master offset 16 s0 freq +0 path delay 2052
<14>1 2023-05-18T07:00:38+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [12003.430] CLOCK_REALTIME phc offset 11 s2 freq +0 delay 1447
<14>1 2023-05-18T07:00:38+00:00 192.168.192.52 k2l-evm - - - ptp4l[208]: [12003.820] master offset 8 s0 freq +0 path delay 2052
<14>1 2023-05-18T07:00:39+00:00 192.168.192.52 k2l-evm - - - phc2sys[209]: [12004.431] CLOCK_REALTIME phc offset 6 s2 freq -2 delay 1447
<14>1 2023-05-18T15:47:47+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30000.190] master offset -46 s0 freq +0 path delay 2054
<14>1 2023-05-18T15:47:47+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30000.248] CLOCK_REALTIME phc offset 10 s2 freq +7 delay 1495
<14>1 2023-05-18T15:47:48+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30001.190] master offset -46 s0 freq +0 path delay 2054
<14>1 2023-05-18T15:47:48+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30001.249] CLOCK_REALTIME phc offset 12 s2 freq +12 delay 1452
<14>1 2023-05-18T15:47:49+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30002.190] master offset -38 s0 freq +0 path delay 2054
<14>1 2023-05-18T15:47:49+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30002.249] CLOCK_REALTIME phc offset 5 s2 freq +9 delay 1489
<14>1 2023-05-18T15:47:50+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30003.190] master offset -46 s0 freq +0 path delay 2054
<14>1 2023-05-18T15:47:50+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30003.249] CLOCK_REALTIME phc offset -8 s2 freq -3 delay 1502
<14>1 2023-05-18T15:47:51+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30004.190] master offset -44 s0 freq +0 path delay 2052
<14>1 2023-05-18T15:47:51+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30004.249] CLOCK_REALTIME phc offset -17 s2 freq -14 delay 1465
<14>1 2023-05-18T15:47:52+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30005.190] master offset -44 s0 freq +0 path delay 2052
<14>1 2023-05-18T15:47:52+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30005.250] CLOCK_REALTIME phc offset 5 s2 freq +3 delay 1532
<14>1 2023-05-18T15:47:53+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30006.190] master offset -36 s0 freq +0 path delay 2052
<14>1 2023-05-18T15:47:53+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30006.250] CLOCK_REALTIME phc offset -10 s2 freq -11 delay 1471
<14>1 2023-05-18T15:47:54+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30007.195] master offset -44 s0 freq +0 path delay 2052
<14>1 2023-05-18T15:47:54+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30007.250] CLOCK_REALTIME phc offset -34359738350 s0 freq -11 delay 1495
<12>1 2023-05-18T15:47:54+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30007.355] clockcheck: clock jumped forward or running faster than expected!
<14>1 2023-05-18T15:47:55+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30008.190] master offset 34359738332 s1 freq +0 path delay 2052
<14>1 2023-05-18T15:47:55+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30008.250] CLOCK_REALTIME phc offset -18 s0 freq -11 delay 1471
<14>1 2023-05-18T15:47:56+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30009.190] master offset 0 s2 freq +0 path delay 2052
<13>1 2023-05-18T15:47:56+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30009.190] port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
<14>1 2023-05-18T15:47:56+00:00 192.168.192.52 k2l-evm - - - phc2sys[200]: [30009.250] CLOCK_REALTIME phc offset 9 s2 freq +23 delay 1490
<14>1 2023-05-18T15:47:57+00:00 192.168.192.52 k2l-evm - - - ptp4l[199]: [30010.190] master offset -8 s0 freq +0 path delay 2052
1. Is there some known issue with PTP not working properly on this EVM?
2. Could you please check if this could be related to similar issue reported in https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1037027/tmdx654idkevm-clock-jump-of-ptp-device-for-icssg? It is a different board and we are not using the same drivers, but wanted to highlight that it is a similar issue.
3. Every time we see this issue the offset reported by phc2sys and ptp4l is 34359738 micro seconds (only the nano part seconds varies). Highlighting this because there might be a pattern that I am not seeing obviously.
