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.

TMDSICE3359: TMDSICE3359 ptpv2

Part Number: TMDSICE3359
Other Parts Discussed in Thread: AM3359, AM3358

I have a next issue. 

1) Ping time in CPSW mode less then 1ms, however in dual emac & prp mode i have ping time 10 time higher. 

Is it possible to reduce it ?

2) 

Why Ptpv2 daemon not working , then TMDSICE3359 in dual emac or prp mode? In CPSW mode it works coorectly. 

SDK version 6.

tcpdump see packets from ptpv2 master.

  • Hello Fed,

    SDK version 6 is not clear. Are you running Linux on the arm core? What version of the Linux kernel is running?

    Regards,

    Nick

  • AM3359. I use evaluation board.

    uname -a return :

    Linux am335x-evm 4.19.94-gbe5389fd85 #48 PREEMPT Mon Jul 26 12:49:42 MSK 2021 armv7l GNU/Linux

  • Hi,

    Do you notice longer ping response with dual mac mode only?

    Best Regards,

    Schuyler

  • HI,

    No in prp mode also.

  • ping in cpsw mode:

    PING 192.168.102.205 (192.168.102.205): 56 data bytes
    64 bytes from 192.168.102.205: seq=0 ttl=63 time=0.904 ms
    64 bytes from 192.168.102.205: seq=1 ttl=63 time=0.597 ms
    64 bytes from 192.168.102.205: seq=2 ttl=63 time=0.612 ms
    64 bytes from 192.168.102.205: seq=3 ttl=63 time=0.604 ms
    64 bytes from 192.168.102.205: seq=4 ttl=63 time=0.601 ms
    64 bytes from 192.168.102.205: seq=5 ttl=63 time=0.624 ms
    64 bytes from 192.168.102.205: seq=6 ttl=63 time=0.709 ms
    64 bytes from 192.168.102.205: seq=7 ttl=63 time=0.593 ms
    64 bytes from 192.168.102.205: seq=8 ttl=63 time=0.607 ms
    64 bytes from 192.168.102.205: seq=9 ttl=63 time=0.602 ms
    64 bytes from 192.168.102.205: seq=10 ttl=63 time=0.602 ms
    64 bytes from 192.168.102.205: seq=11 ttl=63 time=0.601 ms
    64 bytes from 192.168.102.205: seq=12 ttl=63 time=0.656 ms
    64 bytes from 192.168.102.205: seq=13 ttl=63 time=0.593 ms
    64 bytes from 192.168.102.205: seq=14 ttl=63 time=0.638 ms

    ping in prp mode 

    PING 192.168.102.205 (192.168.102.205): 56 data bytes
    64 bytes from 192.168.102.205: seq=0 ttl=63 time=0.975 ms
    64 bytes from 192.168.102.205: seq=1 ttl=63 time=4.998 ms
    64 bytes from 192.168.102.205: seq=2 ttl=63 time=4.069 ms
    64 bytes from 192.168.102.205: seq=3 ttl=63 time=3.298 ms
    64 bytes from 192.168.102.205: seq=4 ttl=63 time=2.374 ms
    64 bytes from 192.168.102.205: seq=5 ttl=63 time=1.149 ms
    64 bytes from 192.168.102.205: seq=6 ttl=63 time=5.650 ms
    64 bytes from 192.168.102.205: seq=7 ttl=63 time=5.006 ms
    64 bytes from 192.168.102.205: seq=8 ttl=63 time=1.919 ms
    64 bytes from 192.168.102.205: seq=9 ttl=63 time=3.114 ms
    64 bytes from 192.168.102.205: seq=10 ttl=63 time=2.076 ms
    64 bytes from 192.168.102.205: seq=11 ttl=63 time=6.037 ms
    64 bytes from 192.168.102.205: seq=12 ttl=63 time=5.338 ms
    64 bytes from 192.168.102.205: seq=13 ttl=63 time=4.385 ms
    64 bytes from 192.168.102.205: seq=14 ttl=63 time=3.609 ms
    64 bytes from 192.168.102.205: seq=15 ttl=63 time=2.834 ms
    64 bytes from 192.168.102.205: seq=16 ttl=63 time=2.054 ms
    64 bytes from 192.168.102.205: seq=17 ttl=63 time=6.008 ms
    64 bytes from 192.168.102.205: seq=18 ttl=63 time=5.263 ms
    64 bytes from 192.168.102.205: seq=19 ttl=63 time=4.194 ms
    64 bytes from 192.168.102.205: seq=20 ttl=63 time=3.466 ms
    64 bytes from 192.168.102.205: seq=21 ttl=63 time=2.479 ms
    64 bytes from 192.168.102.205: seq=22 ttl=63 time=1.975 ms
    64 bytes from 192.168.102.205: seq=23 ttl=63 time=0.907 ms
    64 bytes from 192.168.102.205: seq=24 ttl=63 time=5.097 ms
    64 bytes from 192.168.102.205: seq=25 ttl=63 time=4.341 ms
    64 bytes from 192.168.102.205: seq=26 ttl=63 time=3.564 ms
    64 bytes from 192.168.102.205: seq=27 ttl=63 time=2.605 ms
    64 bytes from 192.168.102.205: seq=28 ttl=63 time=1.783 ms
    64 bytes from 192.168.102.205: seq=29 ttl=63 time=5.825 ms
    64 bytes from 192.168.102.205: seq=30 ttl=63 time=5.084 ms
    64 bytes from 192.168.102.205: seq=31 ttl=63 time=4.120 ms
    64 bytes from 192.168.102.205: seq=32 ttl=63 time=3.345 ms
    64 bytes from 192.168.102.205: seq=33 ttl=63 time=2.510 ms
    64 bytes from 192.168.102.205: seq=34 ttl=63 time=1.904 ms
    64 bytes from 192.168.102.205: seq=35 ttl=63 time=6.105 ms
    64 bytes from 192.168.102.205: seq=36 ttl=63 time=5.206 ms
    64 bytes from 192.168.102.205: seq=37 ttl=63 time=4.415 ms
    64 bytes from 192.168.102.205: seq=38 ttl=63 time=1.951 ms

  • Hi,

    Could you describe how your network topology is setup? Also your link partners, are they in PRP mode as well? Also please provide the results of "ip link show".

    Best Regards,

    Schuyler

  • Eth0 (LAN A) & Eth1(LAN B) enter in RedBox, RedBox enter in switch with other computers.


    [ 349.918754] remoteproc remoteproc1: Booting fw image ti-pruss/am335x-pru0-pruprp-fw.elf, size 7864
    [ 349.930073] pruss 4a300000.pruss: configured system_events[63-0] = 00000600,00900000
    [ 349.939751] pruss 4a300000.pruss: configured intr_channels = 0x00000095 host_intr = 0x00000115
    [ 349.950178] remoteproc remoteproc1: remote processor 4a334000.pru is now up
    [ 349.958857] remoteproc remoteproc2: powering up 4a338000.pru
    [ 349.969651] remoteproc remoteproc2: Booting fw image ti-pruss/am335x-pru1-pruprp-fw.elf, size 7588
    [ 349.980859] pruss 4a300000.pruss: configured system_events[63-0] = 00600000,01200000
    [ 349.991116] pruss 4a300000.pruss: configured intr_channels = 0x0000012a host_intr = 0x0000022a
    [ 350.001527] remoteproc remoteproc2: remote processor 4a338000.pru is now up
    [ 460.246145] prueth pruss_eth eth0: Link is Up - 100Mbps/Full - flow control off
    [ 467.524939] prueth pruss_eth eth1: Link is Up - 100Mbps/Full - flow control off

    root@am335x-evm:~# ifconfig
    eth0 Link encap:Ethernet HWaddr 70:FF:76:1C:0E:8C
    inet6 addr: fe80::72ff:76ff:fe1c:e8c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:63916 errors:0 dropped:3456 overruns:0 frame:13
    TX packets:9062 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:6085976 (5.8 MiB) TX bytes:1186739 (1.1 MiB)

    eth1 Link encap:Ethernet HWaddr 70:FF:76:1C:0E:8C
    inet6 addr: fe80::72ff:76ff:fe1c:e8c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:56852 errors:0 dropped:2468 overruns:0 frame:16
    TX packets:8980 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:5104145 (4.8 MiB) TX bytes:1175060 (1.1 MiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:382 errors:0 dropped:0 overruns:0 frame:0
    TX packets:382 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:87560 (85.5 KiB) TX bytes:87560 (85.5 KiB)

    prp0 Link encap:Ethernet HWaddr 70:FF:76:1C:0E:8C
    inet addr:192.168.102.111 Bcast:192.168.255.255 Mask:255.255.0.0
    inet6 addr: fe80::72ff:76ff:fe1c:e8c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:59694 errors:0 dropped:16864 overruns:0 frame:0
    TX packets:8887 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:6529979 (6.2 MiB) TX bytes:1109300 (1.0 MiB)

    root@am335x-evm:~# ip link show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
    3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 70:ff:76:1c:0e:8c brd ff:ff:ff:ff:ff:ff
    4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 70:ff:76:1c:0e:8c brd ff:ff:ff:ff:ff:ff
    5: prp0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 70:ff:76:1c:0e:8c brd ff:ff:ff:ff:ff:ff

  • root@am335x-evm:~# ptp4l -s -H -i prp0 -m -f oc.cfg
    ptp4l[10543.192]: selected /dev/ptp1 as PTP clock
    ptp4l[10543.197]: port 2: PHC device mismatch
    ptp4l[10543.199]: port 2: /dev/ptp1 requested, ptp0 attached
    ptp4l[10543.202]: failed to open port eth0
    failed to create a clock

  • Good day, I have waited for reply for 3 weeks.

  • Hello Fed,

    We apologize for the delay. Schuyler is on vacation today, but he will be back in the office on Monday. Please ping the thread again if you have not received a response by Tuesday.

    Regards,

    Nick

  • Hi,

    I have asked for assistance from the development team to answer this question. 

    One thing I noticed, you mentioned CPSW but looking at the posted console output the PRU ethernet ports are being used. Which ports did you want to use?

    [ 460.246145] prueth pruss_eth eth0: Link is Up - 100Mbps/Full - flow control off
    [ 467.524939] prueth pruss_eth eth1: Link is Up - 100Mbps/Full - flow control off

    On the AM3358 ICE board there are jumpers that are used to set either CPSW or PRU eth ports. 

    Best Regards,

    Schuyler

  • I have decided problem with PTP via PRP. 

    But problem with high ping remained as is.

  • Hello Fed,

    Please note that HSR/PRP is not supported on AM335x PRU Ethernet in Processor SDK Linux 7.3. So you would want to use CPSW ports instead of PRU Ethernet ports if you want to use HSR/PRP.

    Regards,

    Nick

  • I use SDK 06.03 version. 

    What about high ping ?

  • Do I understand correctly , that in SDK 7 PTP realized in CPSW mode (software realization)?

    In SDK 5.3 PRP via PRU or CPSW ?

  • Hi,

    PRP with CPSW is done in SW (the Kernel), the PRU implementation reduces the latency as the PRU FW manages the PRP portion. Could you describe the topology that using for your test? 

    Best Regards,

    Schuyler

  • Eth0 connected with LAN A in RedBox.

    Eth1 connected with LAN B in RedBox.

    Redbox connected with PC via switch. (from local port).

  • Can i present some additional information for your help ?

  • Can i present some additional information for your help ?

  • Also i make experiments with SDK 0503 and SDK 0501. With next net topology

    1) ICEv2 <===> RedBox<-->switch<---> PC

    2) ICEv2 <===> RedBox<----> PC

    3) ICEv2 <---> PC (via eth0 or eth1)

    All tests have same results:

    2) 2-topology type

          64 bytes from 192.168.11.80: seq=877 ttl=60 time=8.618 ms
          64 bytes from 192.168.11.80: seq=878 ttl=60 time=7.791 ms
          64 bytes from 192.168.11.80: seq=879 ttl=60 time=6.842 ms
          64 bytes from 192.168.11.80: seq=880 ttl=60 time=6.148 ms
          64 bytes from 192.168.11.80: seq=881 ttl=60 time=5.457 ms
          64 bytes from 192.168.11.80: seq=882 ttl=60 time=4.780 ms
          64 bytes from 192.168.11.80: seq=883 ttl=60 time=4.101 ms
          64 bytes from 192.168.11.80: seq=884 ttl=60 time=3.428 ms
          64 bytes from 192.168.11.80: seq=885 ttl=60 time=2.605 ms
          64 bytes from 192.168.11.80: seq=886 ttl=60 time=4.727 ms
          64 bytes from 192.168.11.80: seq=887 ttl=60 time=3.995 ms
          64 bytes from 192.168.11.80: seq=888 ttl=60 time=3.486 ms
          64 bytes from 192.168.11.80: seq=889 ttl=60 time=10.127 ms
          64 bytes from 192.168.11.80: seq=890 ttl=60 time=9.190 ms
          64 bytes from 192.168.11.80: seq=891 ttl=60 time=8.517 ms
          64 bytes from 192.168.11.80: seq=892 ttl=60 time=20.154 ms
          64 bytes from 192.168.11.80: seq=893 ttl=60 time=7.198 ms
          64 bytes from 192.168.11.80: seq=894 ttl=60 time=6.524 ms
          64 bytes from 192.168.11.80: seq=895 ttl=60 time=5.847 ms

    3) 3-topology type

    64 bytes from 192.168.11.210: seq=75 ttl=64 time=4.397 ms
    64 bytes from 192.168.11.210: seq=76 ttl=64 time=3.675 ms
    64 bytes from 192.168.11.210: seq=77 ttl=64 time=2.950 ms
    64 bytes from 192.168.11.210: seq=78 ttl=64 time=2.625 ms
    64 bytes from 192.168.11.210: seq=79 ttl=64 time=2.700 ms
    64 bytes from 192.168.11.210: seq=80 ttl=64 time=10.849 ms
    64 bytes from 192.168.11.210: seq=81 ttl=64 time=10.149 ms
    64 bytes from 192.168.11.210: seq=82 ttl=64 time=9.102 ms
    64 bytes from 192.168.11.210: seq=83 ttl=64 time=8.135 ms
    64 bytes from 192.168.11.210: seq=84 ttl=64 time=7.463 ms