<?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>topic Re: imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1842667#M222269</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;&lt;P&gt;There are going to be changes in the kernel as well as the driver itself, probably,&lt;/P&gt;&lt;P&gt;You could go through the release notes for every release and look for the code improvements.&lt;/P&gt;&lt;P&gt;You are advised to move to latest BSP which features fixes to issues like this one.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Mon, 08 Apr 2024 21:31:53 GMT</pubDate>
    <dc:creator>JosephAtNXP</dc:creator>
    <dc:date>2024-04-08T21:31:53Z</dc:date>
    <item>
      <title>imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1839882#M222084</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I am using the ptp4l tool for time synchronization on imxlinux version 4.1.15, when I increase the cpu frequency to 792000, it skips time, but it doesn't happen when I am using linux 5.15, I would like to ask what changes have been made in the higher version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Here is the printout of the time skip&lt;/P&gt;&lt;P&gt;root@imx6ull:~# ptp4l -A -4 -H -m -i eth0&lt;BR /&gt;ptp4l[182.571]: selected /dev/ptp0 as PTP clock&lt;BR /&gt;ptp4l[182.577]: driver changed our HWTSTAMP options&lt;BR /&gt;ptp4l[182.578]: tx_type 1 not 1&lt;BR /&gt;ptp4l[182.578]: rx_filter 1 not 12&lt;BR /&gt;ptp4l[182.579]: port 1: INITIALIZING to LISTENING on INITIALIZE&lt;BR /&gt;ptp4l[182.581]: port 0: INITIALIZING to LISTENING on INITIALIZE&lt;BR /&gt;ptp4l[190.319]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES&lt;BR /&gt;ptp4l[190.319]: selected best master clock e67809.fffe.3d93fe&lt;BR /&gt;ptp4l[190.320]: assuming the grand master role&lt;BR /&gt;ptp4l[194.325]: port 1: new foreign master ce96f5.fffe.4c2be7-1&lt;BR /&gt;ptp4l[198.325]: selected best master clock ce96f5.fffe.4c2be7&lt;BR /&gt;ptp4l[198.326]: port 1: MASTER to UNCALIBRATED on RS_SLAVE&lt;BR /&gt;ptp4l[200.324]: master offset -2434 s0 freq -2876 path delay 1723&lt;BR /&gt;ptp4l[201.324]: master offset -2516 s2 freq -2958 path delay 1721&lt;BR /&gt;ptp4l[201.325]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED&lt;BR /&gt;ptp4l[202.324]: master offset -2598 s2 freq -5556 path delay 1721&lt;BR /&gt;ptp4l[203.324]: master offset -7 s2 freq -3744 path delay 1720&lt;BR /&gt;ptp4l[204.325]: master offset 781 s2 freq -2958 path delay 1720&lt;BR /&gt;ptp4l[205.324]: master offset 789 s2 freq -2716 path delay 1712&lt;BR /&gt;ptp4l[206.325]: master offset 2147484114 s2 freq +32767999 path delay 1712&lt;BR /&gt;ptp4l[207.325]: master offset -24954283 s2 freq -24957551 path delay 1716&lt;BR /&gt;ptp4l[208.325]: master offset -12526340 s2 freq -20015893 path delay 1069&lt;BR /&gt;ptp4l[209.325]: master offset -28330 s2 freq -11275785 path delay 1069&lt;BR /&gt;ptp4l[210.325]: master offset 14538505 s2 freq +3282551 path delay -2068315&lt;BR /&gt;ptp4l[211.325]: master offset 2158479308 s2 freq +32767999 path delay -2068315&lt;BR /&gt;ptp4l[212.325]: master offset -13968519 s2 freq -20862922 path delay -2068315&lt;BR /&gt;ptp4l[213.325]: master offset 2145937382 s2 freq +32767999 path delay -2068315&lt;BR /&gt;ptp4l[214.325]: master offset 2121002525 s2 freq +32767999 path delay -2068315&lt;BR /&gt;ptp4l[215.325]: master offset -53833606 s2 freq -32767999 path delay 279566&lt;BR /&gt;ptp4l[216.325]: master offset -28931120 s2 freq -32767999 path delay 279566&lt;BR /&gt;ptp4l[217.325]: master offset -3931906 s2 freq -15016865 path delay 279566&lt;BR /&gt;ptp4l[218.325]: master offset 8588962 s2 freq -3675568 path delay 279566&lt;BR /&gt;ptp4l[219.325]: master offset 13242000 s2 freq +3554158 path delay -193292&lt;/P&gt;</description>
      <pubDate>Sun, 07 Apr 2024 00:50:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1839882#M222084</guid>
      <dc:creator>Ethane</dc:creator>
      <dc:date>2024-04-07T00:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1842667#M222269</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;&lt;P&gt;There are going to be changes in the kernel as well as the driver itself, probably,&lt;/P&gt;&lt;P&gt;You could go through the release notes for every release and look for the code improvements.&lt;/P&gt;&lt;P&gt;You are advised to move to latest BSP which features fixes to issues like this one.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2024 21:31:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1842667#M222269</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2024-04-08T21:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1844727#M222358</link>
      <description>Problem solved because the fec controller in linux 4.1.15 imx6ul did not add this configuration FEC_QUIRK_BUG_CAPTURE</description>
      <pubDate>Thu, 11 Apr 2024 03:17:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6ull-cpu-frequency-failed-using-1588-time-synchronization/m-p/1844727#M222358</guid>
      <dc:creator>Ethane</dc:creator>
      <dc:date>2024-04-11T03:17:02Z</dc:date>
    </item>
  </channel>
</rss>

