<?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>Embedded Software and Tools Clinic中的主题 Re: ptp / enet driver problem</title>
    <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1329632#M201</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm interested in this code. Did you make any progress on this?&lt;/P&gt;</description>
    <pubDate>Wed, 25 Aug 2021 16:56:29 GMT</pubDate>
    <dc:creator>xabiermarquiegu</dc:creator>
    <dc:date>2021-08-25T16:56:29Z</dc:date>
    <item>
      <title>ptp / enet driver problem</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1192368#M154</link>
      <description>&lt;P&gt;I am porting the&amp;nbsp;AN12149 ptp application note to the most recent SDK.&lt;/P&gt;&lt;P&gt;There are a very big differences between the fsl_enet.c&amp;nbsp;FSL_ENET_DRIVER_VERSION (MAKE_VERSION(2, 3, 0)) and&amp;nbsp;FSL_ENET_DRIVER_VERSION (MAKE_VERSION(2, 2, 3)), there are literally missing a lot of ieee1588 functionality&amp;nbsp; like&amp;nbsp;ENET_GetRxFrameTime just to mention one.&lt;/P&gt;&lt;P&gt;This makes it impossible to port the application.&lt;/P&gt;&lt;P&gt;It is somehow surprising that the library exist without being recently backwards compatible.&lt;/P&gt;&lt;P&gt;Do there exist any workaround to fix the incompatibility or an explanation&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;Regards Andy&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 13:27:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1192368#M154</guid>
      <dc:creator>andylime</dc:creator>
      <dc:date>2020-12-02T13:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: ptp / enet driver problem</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1329632#M201</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm interested in this code. Did you make any progress on this?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Aug 2021 16:56:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1329632#M201</guid>
      <dc:creator>xabiermarquiegu</dc:creator>
      <dc:date>2021-08-25T16:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: ptp / enet driver problem</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1611080#M352</link>
      <description>&lt;P&gt;I too am looking at these same missing functions. We had AN12149-based PTP working with a (much) older version of the SDK, but it's hard to know where to start without ENET_GetRxFrameTime() and ENET_GetTxFrameTime() to name but two, these are such low-level functions.&lt;/P&gt;&lt;P&gt;Or is PTP basically not supported any more?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 17:48:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/ptp-enet-driver-problem/m-p/1611080#M352</guid>
      <dc:creator>np</dc:creator>
      <dc:date>2023-03-07T17:48:23Z</dc:date>
    </item>
  </channel>
</rss>

