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.

AM3359: PTP issue with both PRP ports connected

Part Number: AM3359

Hello TI,

I have two boards, both have PRP configured, also both have linuxptp installed.

I followed the document "

and able to run ptp4l in prp mode using prp0.cfg file. Both board work fine as one grandmaster and another is ordinary clock. But when I connect both the prp ports to router everything other than ptp work fine. Below are the outputs

When only one port is connected of both boards to network.

ptp4l[8308.071]: master offset          5 s2 freq   +1838 path delay     16181
ptp4l[8309.072]: master offset        161 s2 freq   +1996 path delay     16188
ptp4l[8310.072]: master offset          7 s2 freq   +1890 path delay     16194
ptp4l[8311.072]: master offset        -22 s2 freq   +1863 path delay     16188
ptp4l[8312.072]: master offset        -46 s2 freq   +1833 path delay     16194
ptp4l[8313.072]: master offset       -229 s2 freq   +1636 path delay     16194
ptp4l[8314.073]: master offset        199 s2 freq   +1995 path delay     16194
ptp4l[8315.073]: master offset        164 s2 freq   +2020 path delay     16212
ptp4l[8316.075]: master offset         89 s2 freq   +1994 path delay     16212
ptp4l[8317.075]: master offset       -210 s2 freq   +1722 path delay     16212
ptp4l[8318.075]: master offset          7 s2 freq   +1876 path delay     16212
ptp4l[8319.076]: master offset         53 s2 freq   +1924 path delay     16208
ptp4l[8320.076]: master offset       -100 s2 freq   +1787 path delay     16183
ptp4l[8321.078]: master offset         78 s2 freq   +1935 path delay     16194
ptp4l[8322.078]: master offset        -95 s2 freq   +1785 path delay     16183
ptp4l[8323.077]: master offset        -18 s2 freq   +1834 path delay     16160
ptp4l[8324.078]: master offset        161 s2 freq   +2007 path delay     16157
ptp4l[8325.078]: master offset        -17 s2 freq   +1878 path delay     16157
ptp4l[8326.079]: master offset       -169 s2 freq   +1720 path delay     16170
ptp4l[8327.079]: master offset         12 s2 freq   +1851 path delay     16170
ptp4l[8328.080]: master offset          6 s2 freq   +1848 path delay     16158
ptp4l[8329.082]: master offset        393 s2 freq   +2237 path delay     16148
ptp4l[8330.083]: master offset        -67 s2 freq   +1895 path delay     16148
ptp4l[8331.083]: master offset       -197 s2 freq   +1745 path delay     16148
ptp4l[8332.083]: master offset         81 s2 freq   +1964 path delay     16155
ptp4l[8333.082]: master offset         19 s2 freq   +1926 path delay     16164
ptp4l[8334.084]: master offset       -120 s2 freq   +1793 path delay     16171
ptp4l[8335.083]: master offset       -103 s2 freq   +1774 path delay     16155

This is what I get as soon as I connect second port of grandmaster or ordinary clock.

ptp4l[8401.113]: master offset         28 s2 freq   +1910 path delay     16184
ptp4l[8402.114]: master offset        -95 s2 freq   +1796 path delay     16184
ptp4l[8403.114]: master offset        -64 s2 freq   +1798 path delay     16181
ptp4l[8404.115]: master offset        134 s2 freq   +1977 path delay     16181
ptp4l[8405.115]: master offset          7 s2 freq   +1890 path delay     16184
[ 8405.407554] prueth pruss_eth eth0: Link is Up - 100Mbps/Full - flow control rx/tx
ptp4l[8405.494]: timed out while polling for tx timestamp
ptp4l[8405.494]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[8405.495]: port 3: send peer delay response failed
ptp4l[8405.495]: port 3 (eth1): SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[8405.526]: port 2: link up
ptp4l[8405.538]: red port 2 (eth0): FAULTY to LISTENING on INIT_COMPLETE
ptp4l[8406.116]: port 2: new foreign master 2c6b7d.fffe.49e929-3
ptp4l[8406.547]: red port 3 (eth1): FAULTY to LISTENING on INIT_COMPLETE
ptp4l[8406.549]: port 3 lanid=1: rogue peer delay response
ptp4l[8406.551]: port 3 (eth1): LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[8407.567]: red port 3 (eth1): FAULTY to LISTENING on INIT_COMPLETE
ptp4l[8408.117]: port 3: new foreign master 2c6b7d.fffe.49e929-3
ptp4l[8408.120]: selected best master clock 2c6b7d.fffe.49e929 on port 2
ptp4l[8408.120]: selected best master clock 2c6b7d.fffe.49e929
ptp4l[8408.120]: red port 2 (eth0): LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[8409.576]: port 2 lanid=0: rogue peer delay response
ptp4l[8409.581]: port 2 (eth0): UNCALIBRATED to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)

My current config file is

[global]
sanity_freq_limit            0
step_threshold               0.00002
tx_timestamp_timeout         10

domainNumber                 0
priority1                    128
priority2                    123
slaveOnly                    0

twoStepFlag                  1
summary_interval             0
doubly_attached_clock        1

[prp0]
redundancy                   2
delay_mechanism              P2P
network_transport            L2

[eth2]
redundancy                    2
redundancy_master_interface   prp0
redundancy_slave_number       1

logAnnounceInterval           0
logSyncInterval               0
logMinPdelayReqInterval       0
announceReceiptTimeout        3
syncReceiptTimeout            2

delay_mechanism               P2P
egressLatency                 726
ingressLatency                186
network_transport             L2
fault_reset_interval          0

[eth3]
redundancy                    2
redundancy_master_interface   prp0
redundancy_slave_number       2

logAnnounceInterval           0
logSyncInterval               0
logMinPdelayReqInterval       0
announceReceiptTimeout        3
syncReceiptTimeout            2

delay_mechanism               P2P
egressLatency                 726
ingressLatency                186
network_transport             L2
fault_reset_interval          0

I run command on master ptp4l -f <path to prp0.cfg> -m

Also on slave ptp4l -f <path to prp0.cfg> -m -s