I’m having some issues when running the phc2sys service:
Getting too big offsets (above 1000 ns, something even above 10000 ns).
Frequency doesn’t offset not stable (goes backward and forward between -1000 to +15000).
Delay seems too high (around 85000 ns) and also not stable.
My board is running as a PTP slave (running ptp4l), so I thought that maybe due to the PTP operations on the PHC, the PHC jumps too frequently (-/+500 ns), and that’s may cause the PHC offset (from the SYSTEM clock) to jumps even more frequently.
So I tried to disable the PTP on the slave side, so now I’m only trying to synchronize the SYSTEM clock to the PHC, but the PTP isn’t running - so the ptp4l isn’t touching the PHC (maybe some other app is touching it?), but I still getting huge numbers when running: phc2sys -s eth0 -c CLOCK_REALTIME -O 0 -m
The first thing I’m concerned about is that the calculated delay is too high. It doesn’t make any sense (to me…).
The second thing I’m concerned about is that maybe some other program is playing with the PHC - but how can I trace after such operations on the PHC ?
Any idea what could it be ?
Maybe some guidelines on what should I check and how ?
Platform:
My board is running with KSZ9477 switch (with HW timestamping support) on linux 4.19.
I’m having some issues when running the phc2sys service:
My board is running as a PTP slave (running ptp4l), so I thought that maybe due to the PTP operations on the PHC, the PHC jumps too frequently (-/+500 ns), and that’s may cause the PHC offset (from the SYSTEM clock) to jumps even more frequently.
So I tried to disable the PTP on the slave side, so now I’m only trying to synchronize the SYSTEM clock to the PHC, but the PTP isn’t running - so the ptp4l isn’t touching the PHC (maybe some other app is touching it?), but I still getting huge numbers when running:
phc2sys -s eth0 -c CLOCK_REALTIME -O 0 -m
Question:
The first thing I’m concerned about is that the calculated delay is too high. It doesn’t make any sense (to me…). The second thing I’m concerned about is that maybe some other program is playing with the PHC - but how can I trace after such operations on the PHC ? Any idea what could it be ? Maybe some guidelines on what should I check and how ?
Platform:
My board is running with KSZ9477 switch (with HW timestamping support) on linux 4.19.