ptp4l issue on LS1028ARDB

cancel
Showing results for 
Search instead for 
Did you mean: 

ptp4l issue on LS1028ARDB

Jump to solution
664 Views
ceroone
Contributor II

Hello,

I am trying to synchronize some NXP equipment using ptp4l. It works fine for all the other boards, but I am facing a problem with the LS1028ARDB.

I run the following command :

# ptp4l -i swp0 -i swp1 -f /etc/ptp4l_cfg/gPTP.cfg

But it returns this error (besides the fact that the offsets remain very high):

ptp4l[xxxx.xxx]: clockcheck: clock jumped backward or running slower than expected!

Can you help me to identify what is the problem there?

Thank you.

cerrone

You will find the gPTP .cfg file attached below.

Labels (1)
Tags (3)
0 Kudos
1 Solution
624 Views
andrei_skok
NXP TechSupport
NXP TechSupport

Could you try adding 'step_threshold 0.00002' setting to the gPTP.cfg file pls and let us know whether the situation is improved ?
(for more info ref: https://github.com/openil/linuxptp/issues/10)

> So could this phc_ctl command be the cause of the problem ?
It seems that a large change in PHC is difficult to tune for, so these gPTP.cfg tunings should help.

View solution in original post

0 Kudos
4 Replies
641 Views
ceroone
Contributor II

In fact it was allready commented, I forgot to indicate it in my previous message.

Another thing that I forgot to say: before lauching ptp4l on each board, I also reset the PTP Hardware Clock. On the LS1028ARDB, the exact command that I run is:

# phc_ctl /dev/ptp1 set 0; ptp4l -i swp0 -i swp1 -f /etc/ptp4l_cfg/gPTP.cfg -m

(I reset the PHC on every board, but the LS1028ARDB is the only one on which I get the error message...)

So could this phc_ctl command be the cause of the problem?

ceroone

0 Kudos
625 Views
andrei_skok
NXP TechSupport
NXP TechSupport

Could you try adding 'step_threshold 0.00002' setting to the gPTP.cfg file pls and let us know whether the situation is improved ?
(for more info ref: https://github.com/openil/linuxptp/issues/10)

> So could this phc_ctl command be the cause of the problem ?
It seems that a large change in PHC is difficult to tune for, so these gPTP.cfg tunings should help.

0 Kudos
597 Views
ceroone
Contributor II

Adding "step_threshold 0.00002" seems to solve the problem indeed.

Thank you !

0 Kudos
651 Views
andrei_skok
NXP TechSupport
NXP TechSupport

In gPTP.cfg, please comment out the neighborPropDelayThresh line
# neighborPropDelayThresh       800

and let us know how you get on.

0 Kudos