Hi linuxptp community,

I could put my hands on a TI AM5728 box (Elesar Titanium) running Linux arm
4.1.6-01294--g8406366 #6 SMP PREEMPT armv7l (Debian Jessy) and ethtool is
reporting this:
user@arm:~/linuxptp-1.8$ sudo ethtool -T eth1
Time stamping parameters for eth1:
Capabilities:
        hardware-transmit     (SOF_TIMESTAMPING_TX_HARDWARE)
        software-transmit     (SOF_TIMESTAMPING_TX_SOFTWARE)
        hardware-receive      (SOF_TIMESTAMPING_RX_HARDWARE)
        software-receive      (SOF_TIMESTAMPING_RX_SOFTWARE)
        software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
        hardware-raw-clock    (SOF_TIMESTAMPING_RAW_HARDWARE)
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
        off                   (HWTSTAMP_TX_OFF)
        on                    (HWTSTAMP_TX_ON)
Hardware Receive Filter Modes:
        none                  (HWTSTAMP_FILTER_NONE)
        ptpv2-event           (HWTSTAMP_FILTER_PTP_V2_EVENT)

I'm observing strange behaviour of ptp4l:
user@arm:~/linuxptp-1.8$ sudo ./ptp4l -i eth1 -s -m -q
ptp4l[296.574]: selected /dev/ptp0 as PTP clock
ptp4l[296.593]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[296.593]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[296.593]: port 1: link up
ptp4l[297.202]: port 1: new foreign master 0050c2.fffe.39e7e1-8
ptp4l[299.202]: selected best master clock 000b72.fffe.0587fa
ptp4l[299.202]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[299.301]: port 1: minimum delay request interval 2^3
ptp4l[300.202]: rms 9169381730255 max 9169405598321 freq +500000 +/- 500000
delay -15782702 +/-   0
ptp4l[302.202]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[302.702]: rms 140849798 max 155677350 freq +1000000 +/-   0 delay
-14387879 +/-   0
ptp4l[303.702]: rms 202019230 max 217113647 freq +1000000 +/-   0 delay
-12993056 +/-   0
ptp4l[304.702]: rms 264705365 max 279944980 freq +1000000 +/-   0
ptp4l[305.702]: rms 322793382 max 336658462 freq +1000000 +/-   0 delay
-8404950 +/- 1529368
ptp4l[306.702]: rms 384104196 max 399489358 freq +1000000 +/-   0
ptp4l[307.702]: rms 446890503 max 462320408 freq +1000000 +/-   0
ptp4l[308.702]: rms 509687509 max 525151217 freq +1000000 +/-   0
ptp4l[309.702]: rms 572309716 max 587627646 freq +1000000 +/-   0 delay
-6521028 +/-   0
ptp4l[310.702]: rms 634949321 max 650458738 freq +1000000 +/-   0
ptp4l[311.702]: rms 697764821 max 713293606 freq +1000000 +/-   0
ptp4l[312.702]: rms 760581017 max 776124411 freq +1000000 +/-   0
ptp4l[313.702]: rms 823400790 max 838959051 freq +1000000 +/-   0
ptp4l[314.701]: rms 886218407 max 901783909 freq +1000000 +/-   0
ptp4l[315.701]: rms 949038000 max 964613935 freq +1000000 +/-   0
ptp4l[316.701]: rms 1011862805 max 1027444991 freq +1000000 +/-   0
ptp4l[317.701]: rms 1074684725 max 1090275855 freq +1000000 +/-   0
ptp4l[318.701]: rms 1137696718 max 1153460190 freq +1000000 +/-   0 delay
-6875582 +/-   0
ptp4l[319.701]: rms 1200688978 max 1216292064 freq +1000000 +/-   0
ptp4l[320.701]: rms 1263514719 max 1279122947 freq +1000000 +/-   0
ptp4l[321.701]: rms 1326341090 max 1341953920 freq +1000000 +/-   0
ptp4l[322.701]: rms 1389167792 max 1404784827 freq +1000000 +/-   0
ptp4l[323.701]: rms 1451994939 max 1467616429 freq +1000000 +/-   0
ptp4l[324.701]: rms 1514822314 max 1530446698 freq +1000000 +/-   0

To me it looks like there is trouble correctly adjusting the frequency of
the PHC, it's always remaining +1000000, but also delays are ridicously high
and negative (that doesn't make sense, does it?).

Has anybody ever seen such behaviour and/or has experience with the AM5728
(or similar)?

Thank you!
Axel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to