<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LayerscapeのトピックRe: PTP with L2 Forwarding switch (LS1028ARDB)</title>
    <link>https://community.nxp.com/t5/Layerscape/PTP-with-L2-Forwarding-switch-LS1028ARDB/m-p/1305136#M8391</link>
    <description>&lt;P&gt;&lt;SPAN&gt;ls1028 is working in the L2 bridge mode.&amp;nbsp; "ptp4l -i eth0" command is sending the ptp4l as UDP packages for synchronizing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;ls1021 traps the L2 ptp package to CPU port for ptp sync. But not for the L4 level package to CPU port. UDP package will forward directly.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;ls1028 would trap both L2 ptp package and L4 ptp package to CPU port not forward to other ports. We suppose user to run the ptp4l in ls1028 as default since it own the capability of ptp syncing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We suggest customer to run the ptp4l in the L2 mode with -2 parameter. &lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jul 2021 03:59:19 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2021-07-09T03:59:19Z</dc:date>
    <item>
      <title>PTP with L2 Forwarding switch (LS1028ARDB)</title>
      <link>https://community.nxp.com/t5/Layerscape/PTP-with-L2-Forwarding-switch-LS1028ARDB/m-p/1303249#M8358</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have two boards (i.MX8M Plus) connected to each other via a switch (LS1028ARDB).&lt;/P&gt;&lt;P&gt;I run the following script to configure the switch in L2 forwarding mode:&lt;/P&gt;&lt;P&gt;#!/bin/bash&lt;BR /&gt;INTERFACES = "swp0 swp1 swp2 swp3"&lt;BR /&gt;ip link set eno2 up&lt;BR /&gt;ip link add name br0 type bridge&lt;BR /&gt;for if in $INTERFACES;&lt;BR /&gt;do&lt;BR /&gt;&amp;nbsp; &amp;nbsp; ip link set $if up&lt;BR /&gt;&amp;nbsp; &amp;nbsp; ip link set dev $if master br0&lt;BR /&gt;done&lt;BR /&gt;ip link set br0 up&lt;/P&gt;&lt;P&gt;I then run ptp4l on both i.MX8M Plus boards. I emphasize that I don't run ptp4l on the LS1028ARDB because I would like to test to what extent adding a "classic" switch between two PTP clocks affects performance.&lt;/P&gt;&lt;P&gt;However, the synchronization doesn't work. I have the following display (on both i.MX8M Plus boards):&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;# ptp4l -i eth0 -m&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: selected /dev/ptp1 as PTP clock&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: port 0:&amp;nbsp;INITIALIZING to LISTENING on INIT_COMPLETE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: selected local clock yyyyyy.yyyy.yyyyyy as best master&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ptp4l[xxxx.xxx]: assuming the grand master role&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Could you explain me why it doesn't work please?&lt;/P&gt;&lt;P&gt;PS1: I tried to perform this operation with a LS1021ATSN switch and it worked perfectly...&lt;BR /&gt;PS2: Ping also works fine&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jul 2021 06:57:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PTP-with-L2-Forwarding-switch-LS1028ARDB/m-p/1303249#M8358</guid>
      <dc:creator>ceroone</dc:creator>
      <dc:date>2021-07-07T06:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: PTP with L2 Forwarding switch (LS1028ARDB)</title>
      <link>https://community.nxp.com/t5/Layerscape/PTP-with-L2-Forwarding-switch-LS1028ARDB/m-p/1305136#M8391</link>
      <description>&lt;P&gt;&lt;SPAN&gt;ls1028 is working in the L2 bridge mode.&amp;nbsp; "ptp4l -i eth0" command is sending the ptp4l as UDP packages for synchronizing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;ls1021 traps the L2 ptp package to CPU port for ptp sync. But not for the L4 level package to CPU port. UDP package will forward directly.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;ls1028 would trap both L2 ptp package and L4 ptp package to CPU port not forward to other ports. We suppose user to run the ptp4l in ls1028 as default since it own the capability of ptp syncing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We suggest customer to run the ptp4l in the L2 mode with -2 parameter. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 03:59:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PTP-with-L2-Forwarding-switch-LS1028ARDB/m-p/1305136#M8391</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-07-09T03:59:19Z</dc:date>
    </item>
  </channel>
</rss>

