<?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 Ethernet Transceiver Custom Implementation in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Ethernet-Transceiver-Custom-Implementation/m-p/1490163#M16396</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5" color="#3366FF"&gt;Context:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Platform:&lt;/STRONG&gt; S32K3**&lt;/P&gt;&lt;P&gt;We are implementing our own &lt;EM&gt;EthTrcv &lt;/EM&gt;MCAL driver for an Ethernet Transceiver. We are also using the MCAL Hardware Drivers. (SW32K344_RTD_4_4_2_0_0_D2203)&lt;/P&gt;&lt;P&gt;However, there’s also a stub file for EthTrcv, under the MCAL folder of the SDK path shown below:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MateoSegura413_0-1657872344887.png" style="width: 756px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/186773i80D4078E4A59A857/image-dimensions/756x17?v=v2" width="756" height="17" role="button" title="MateoSegura413_0-1657872344887.png" alt="MateoSegura413_0-1657872344887.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This file only has the 2 following methods in it, and they’re undefined. I’m guessing these are the Read/Write methods for the transceiver using the MDIO bus...&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MateoSegura413_1-1657872375308.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/186774iBABEA73A0748748A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MateoSegura413_1-1657872375308.png" alt="MateoSegura413_1-1657872375308.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5" color="#3366FF"&gt;Questions:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;How should this&amp;nbsp;&lt;EM&gt;stub&amp;nbsp;&lt;/EM&gt;file be implemented?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If I’ve understood things correctly, the &lt;EM&gt;GMAC_IP &lt;/EM&gt;driver API must be used here to call the correct MDIO_Write/MDIO_Read methods. Is this a correct statement?&lt;/LI&gt;&lt;LI&gt;How can I Implement this in my own source code and not in the SDK folder under the S32DS location?&lt;/LI&gt;&lt;LI&gt;Are these methods used internally by the MCAL &lt;EM&gt;Eth&lt;/EM&gt; Driver?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for your time and help!&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jul 2022 08:11:38 GMT</pubDate>
    <dc:creator>MateoSegura413</dc:creator>
    <dc:date>2022-07-15T08:11:38Z</dc:date>
    <item>
      <title>Ethernet Transceiver Custom Implementation</title>
      <link>https://community.nxp.com/t5/S32K/Ethernet-Transceiver-Custom-Implementation/m-p/1490163#M16396</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5" color="#3366FF"&gt;Context:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Platform:&lt;/STRONG&gt; S32K3**&lt;/P&gt;&lt;P&gt;We are implementing our own &lt;EM&gt;EthTrcv &lt;/EM&gt;MCAL driver for an Ethernet Transceiver. We are also using the MCAL Hardware Drivers. (SW32K344_RTD_4_4_2_0_0_D2203)&lt;/P&gt;&lt;P&gt;However, there’s also a stub file for EthTrcv, under the MCAL folder of the SDK path shown below:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MateoSegura413_0-1657872344887.png" style="width: 756px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/186773i80D4078E4A59A857/image-dimensions/756x17?v=v2" width="756" height="17" role="button" title="MateoSegura413_0-1657872344887.png" alt="MateoSegura413_0-1657872344887.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This file only has the 2 following methods in it, and they’re undefined. I’m guessing these are the Read/Write methods for the transceiver using the MDIO bus...&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MateoSegura413_1-1657872375308.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/186774iBABEA73A0748748A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MateoSegura413_1-1657872375308.png" alt="MateoSegura413_1-1657872375308.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5" color="#3366FF"&gt;Questions:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;How should this&amp;nbsp;&lt;EM&gt;stub&amp;nbsp;&lt;/EM&gt;file be implemented?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If I’ve understood things correctly, the &lt;EM&gt;GMAC_IP &lt;/EM&gt;driver API must be used here to call the correct MDIO_Write/MDIO_Read methods. Is this a correct statement?&lt;/LI&gt;&lt;LI&gt;How can I Implement this in my own source code and not in the SDK folder under the S32DS location?&lt;/LI&gt;&lt;LI&gt;Are these methods used internally by the MCAL &lt;EM&gt;Eth&lt;/EM&gt; Driver?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for your time and help!&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 08:11:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Ethernet-Transceiver-Custom-Implementation/m-p/1490163#M16396</guid>
      <dc:creator>MateoSegura413</dc:creator>
      <dc:date>2022-07-15T08:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet Transceiver Custom Implementation</title>
      <link>https://community.nxp.com/t5/S32K/Ethernet-Transceiver-Custom-Implementation/m-p/1491435#M16476</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/196282"&gt;@MateoSegura413&lt;/a&gt;,&lt;/P&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;In fact, Eth_WriteMii/Eth_ReadMii are two functions which&lt;STRONG&gt; writes/reads a transceiver (physical layer driver) register&lt;/STRONG&gt;, and EthTrcv_WriteMiiIndication/&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;EthTrcv_ReadMiiIndication are two callback functions which are called by Eth_WriteMii/Eth_ReadMii to notify to EthTrcv the status of MII write/read. To implement these stubs, you can contact your local FAE to get the Eth transceiver driver package.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Regarding your questions:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;1. Like below,&amp;nbsp;EthTrcv_WriteMiiIndication/EthTrcv_ReadMiiIndication are just two callback functions to notify to EthTrcv the status of MII write/read, and Eth_WriteMii/Eth_ReadMii calls the correct MDIO_Write/MDIO_Read methods (throug Gmac_Ip).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;2. and 3. These EthTrcv functions are stubs, so you can do whatever with these functions. Also, you can refer to the Eth Transceiver package provides by NXP. As far as I concern, you can even ignore the EthTrcv, since the Eth/Gmac_IP provides enough methods to&amp;nbsp;writes/reads a transceiver (physical layer driver) register.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Hope it helps.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Nam&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 19 Jul 2022 04:45:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Ethernet-Transceiver-Custom-Implementation/m-p/1491435#M16476</guid>
      <dc:creator>namnguyenviet</dc:creator>
      <dc:date>2022-07-19T04:45:45Z</dc:date>
    </item>
  </channel>
</rss>

