TDA4VM: The problem I encountered while using the phc2sys software

Albert

Part Number: TDA4VM

Hi， TI experts

I am currently running the SDK version 8.6 software using the VM development board. Then the board loads the k3-j721e-quad-port-eth-exp.dtb file to make it work in native driver mode.

I used the phc2sys software to synchronize the hardware clock with the software clock, but found that the synchronization failed. The following is the log

root@j7200-evm:~/rqyang# phc2sys -s /dev/ptp2  -c CLOCK_REALTIME -O 0  -q --step__threshold=0.00002 -m
phc2sys[373.301]: CLOCK_REALTIME phc offset 3468205803 s0 freq  +11050 delay   1020
phc2sys[374.301]: failed to step clock: Invalid argument
phc2sys[374.301]: CLOCK_REALTIME phc offset 3468205782 s1 freq  +11029 delay   1075
phc2sys[375.301]: CLOCK_REALTIME phc offset 3468205799 s0 freq  +11029 delay   1035
phc2sys[376.302]: CLOCK_REALTIME phc offset 3468205824 s0 freq  +11029 delay   1040
^Cphc2sys[376.797]: failed to step clock: Invalid argument
phc2sys[376.797]: CLOCK_REALTIME phc offset 3468205826 s1 freq  +11033 delay   1015
root@j7200-evm:~/rqyang# vi qbv.sh
root@j7200-evm:~/rqyang# phc2sys -s /dev/ptp2  -c CLOCK_REALTIME -O 0  -q -m
phc2sys[393.157]: CLOCK_REALTIME phc offset 3468205955 s0 freq  +11033 delay   1025
phc2sys[394.157]: failed to step clock: Invalid argument
phc2sys[394.157]: CLOCK_REALTIME phc offset 3468205976 s1 freq  +11054 delay   1000
phc2sys[395.157]: CLOCK_REALTIME phc offset 3468205960 s2 freq +100000000 delay   1035
phc2sys[396.158]: CLOCK_REALTIME phc offset 3357088434 s2 freq +100000000 delay    963
^Cphc2sys[396.209]: CLOCK_REALTIME phc offset 3351313232 s2 freq +100000000 delay    918
root@j7200-evm:~/rqyang# phc2sys -s /dev/ptp2  -c CLOCK_REALTIME -O 0  -q -m
phc2sys[398.551]: CLOCK_REALTIME phc offset 3091183268 s0 freq +100000000 delay    950
phc2sys[399.551]: failed to step clock: Invalid argument
phc2sys[399.551]: CLOCK_REALTIME phc offset 2980060365 s1 freq  +11059 delay    923
phc2sys[400.551]: CLOCK_REALTIME phc offset 2980044831 s2 freq +100000000 delay   1050
phc2sys[401.552]: CLOCK_REALTIME phc offset 2868926212 s2 freq +100000000 delay    931
phc2sys[402.552]: CLOCK_REALTIME phc offset 2757808339 s2 freq +100000000 delay    918
^Cphc2sys[402.689]: CLOCK_REALTIME phc offset 2742613614 s2 freq +100000000 delay    950

May I ask how to locate and solve this problem？

Regards, Albert

over 2 years ago

0 Tanmay Patil over 2 years ago

TI__Mastermind 38990 points

Hi Albert,

Can you try running this with "/dev/ptp1" instead of "/dev/ptp2".

I checked it on mysetup and the command is working. can you also check the output of "ethtool -T $IF_NAME", where IF_NAME is the interface name of any of the CPSSW9G interfaces and check what is "PTP Hardware Clock" value in the output.

Regards,
Tanmay

0 Albert over 2 years ago in reply to Tanmay Patil

Prodigy 210 points

Hi,

I have tried everything from ptp0 to ptp2. When synchronizing hardware time to Linux software time, the first attempt always fails, and then the second and later attempts can be successful. I don't know how to locate and solve it.

Regards,

Albert

0 Tanmay Patil over 2 years ago in reply to Albert

TI__Mastermind 38990 points

Hi Albert,

Albert said:
the first attempt always fails, and then the second and later attempts can be successful

This is an interesting observation. I was able to recreate this on my setup.

I have filed an internal ticket for this issue with the development team. I will keep you updated of the progress here.

Regards,
Tanmay

0 Albert over 2 years ago in reply to Tanmay Patil

Prodigy 210 points

Hi Tanmay,

May I ask if there is any progress on this issue on your end? I still can't find a solution to the problem here.

Regards,

Albert

0 Tanmay Patil over 2 years ago in reply to Albert

TI__Mastermind 38990 points

Hi Albert,

The issue is under further investigation. Unfortunately, I am not able to give you a tentative time for a fix for this issue currently.

I will get back to you once I have an update on this issue.

Regards,
Tanmay

0 Siddharth Vadapalli over 2 years ago in reply to Albert

TI__Expert 3575 points

Albert said:
I have tried everything from ptp0 to ptp2. When synchronizing hardware time to Linux software time, the first attempt always fails, and then the second and later attempts can be successful. I don't know how to locate and solve it.

Hello Albert,

Could you please use the -S option and retest?
You could set it to 1000 for example. With that, it should immediately start synchronizing.
Please test the following command. It works in my setup:

phc2sys -s /dev/ptp1 -c CLOCK_REALTIME -O 0 -q -m -S 1000

Regards,
Siddharth.

0 Albert over 2 years ago in reply to Siddharth Vadapalli

Prodigy 210 points

Hi，

I tried this command, but it still had the problem of the first synchronization failure.

Regards,
Albert.

0 Siddharth Vadapalli over 2 years ago in reply to Albert

TI__Expert 3575 points

Hello Albert,

I am attaching the phc2sys binary which worked for me.
Can you please test with it and check if it works for you?
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/phc2sys

Regards,
Siddharth.

0 Albert over 2 years ago in reply to Siddharth Vadapalli

Prodigy 210 points

Hi，

Regards,
Albert.

0 Siddharth Vadapalli over 2 years ago in reply to Albert

TI__Expert 3575 points

Albert,

libc.so.6 should be packaged with the SDK. I am attaching the file here. Please copy it to the /lib directory.
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/libc.so.6

Regards,
Siddharth.

0 Albert over 2 years ago in reply to Siddharth Vadapalli

Prodigy 210 points

After I replaced the libc. so. 6 you gave me, the system couldn't start properly

Regards,
Siddharth.

0 Siddharth Vadapalli over 2 years ago in reply to Albert

TI__Expert 3575 points

Albert,

It appears to be an issue due to different versions of the rest of the components in your system
and the libc.so.6 library I shared. If it is possible to do so, I suggest updating to the latest phc2sys
binary which is compatible with the libc.so.6 library version on your system.

Regards,
Siddharth.

0 Albert over 2 years ago in reply to Siddharth Vadapalli

Prodigy 210 points

Hi,

Currently, I am using version 3.1.1 of phc2sys, but there may still be issues with synchronizing time to CLOCK_ The situation in REALTIME. In addition, I have found that when I use ptp4l to synchronize the time, there is also a situation where phc2sys cannot synchronize the time, even if phc2sys has already successfully synchronized at the beginning.

I don't know if it's a driver issue, or if there's something that's causing phc2sys to fail?

Regards,

Albert

0 Albert over 2 years ago in reply to Albert

Prodigy 210 points

Hi,

I found that when using clock_settime() to set CLOCK_REALTIME, it can be successfully set as soon as it is powered on. After running ptp4l for time synchronization and then setting CLOCK_REALTIME, there will be failures. Will the local time setting be affected by ptp4l, and whether there are any abnormalities in the driver of the local time setting.

Regards,

Albert

0 Tanmay Patil over 1 year ago in reply to Albert

TI__Mastermind 38990 points

Hi Albert,

Albert said:
After running ptp4l for time synchronization and then setting CLOCK_REALTIME, there will be failures

Are you running the clock_settime() mannually after ptp4l?

According to my understanding, ptp4l will not synchronize the CLOCK_REALTIME. It will only synchronize the hardware ptp clock. We have to use phc2sys post that to sync the ptp hardware clock to CLOCK_REALTIME.

Regards,
Tanmay

Processors

Processors forum

TDA4VM: The problem I encountered while using the phc2sys software