• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 843 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5708: PTP peer delay issue

Jose Carlos Billalabeitia
Expert 2490 points

Part Number: AM5708

Hi

I have a custom AM5708 based board.I am running "ptp4l" acting as a slave only device. The issue is as follows:

If the master does not provide p2p delay response, the board  does not synchronize.

I was trying to find any parameter or configuration value that could deal with this issue and also tried

to find a response in the web but found nothing.

Do you know if ptp4l stack needs p2p mechanism to synchronize the bridge clock? I think that

the fact that the master does not provide p2p response should not keep the slave from synchronizing.

 

Regards

Billa

  • 0
    TI__Guru**** 393215 points

    Please post which SDK you are using - Linux or RTOS? Which version?

  • 0 in reply to Biser Gatchev-XID
    Expert 2490 points

    ti-processor-sdk-linux-rt-1m57xx-evm-05.02.00.10

    Linux RT

    SDK 5.02

    Regards

    Billa

  • 0 in reply to Jose Carlos Billalabeitia
    TI__Mastermind 40730 points

    Hi,

    I wanted to let you know that we are looking at this and will get back to you later this week or early next week. 

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    TI__Guru** 106850 points

    Hello Billa,

    Are you using the CPSW ethernet port, or the ICSS ethernet port?

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Expert 2490 points

    Hello Nick:

        I am using CPSW.

    Regards

    Billa

  • 0 in reply to Jose Carlos Billalabeitia
    TI__Mastermind 40730 points

    Hi,

    Could you please attach the ptp4l configuration and console log files for us to analyze?

    Thank you.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Expert 2490 points

    Hi:

       Here they are.

    ptp4l -2 -P -foc.cfg -s -m

    Regards

    Billaoc.cfg

    Fullscreen ptp_console_log_file.txt Download 
    PTP_GMAC[158.113]: selected best master clock 0050c2.fffe.b72df2
PTP_GMAC[158.116]: foreign master not using PTP timescale
PTP_GMAC[158.116]: running in a temporal vortex
PTP_GMAC[158.117]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
PTP_GMAC[159.122]: master offset 7351347737001 s0 freq   -1199 path delay       138
PTP_GMAC[160.143]: master offset 7351347735992 s0 freq   -1199 path delay       125
PTP_GMAC[161.261]: master offset 7351347734832 s1 freq   -2207 path delay       124
PTP_GMAC[162.282]: master offset        -10 s2 freq   -2217 path delay       127
PTP_GMAC[162.284]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
PTP_GMAC_STATUS = 1
PTP_GMAC is the SYNCHRONIZATION SOURCE.
PTP_GMAC[163.282]: master offset        -57 s2 freq   -2267 path delay       126
PTP_GMAC[164.452]: master offset         21 s2 freq   -2206 path delay       127
PTP_GMAC[165.471]: master offset        -29 s2 freq   -2250 path delay       137
PTP_GMAC[166.493]: master offset         10 s2 freq   -2220 path delay       141
PTP_GMAC[167.613]: master offset          5 s2 freq   -2222 path delay       129
PTP_GMAC[168.621]: master offset        -31 s2 freq   -2256 path delay       131
PTP_GMAC[169.622]: master offset        -10 s2 freq   -2245 path delay       139
PTP_GMAC[170.761]: master offset         33 s2 freq   -2205 path delay       140
PTP_GMAC[171.782]: master offset         50 s2 freq   -2178 path delay       136
PTP_GMAC[172.782]: master offset        -27 s2 freq   -2240 path delay       134
PTP_GMAC[173.883]: master offset         17 s2 freq   -2204 path delay       127
PTP_GMAC[174.892]: master offset        -30 s2 freq   -2246 path delay       132
PTP_GMAC[175.892]: master offset        -15 s2 freq   -2240 path delay       131
PTP_GMAC[177.022]: master offset         -2 s2 freq   -2231 path delay       129

  • 0 in reply to Jose Carlos Billalabeitia
    TI__Guru** 106850 points

    Hello Billa,

    We are sorry for the delayed response. I would expect PTP over our CPSW port to support both p2p and e2e. We are out for the next couple days for labor day, but we will get more information to you next week.

    Regards,

    Nick