<?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>Kinetis MicrocontrollersのトピックRe: K64F120M  communication with Micrel KSZ8863 problem</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444635#M26221</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you require a professional solution to your problem you can obtain all that you require from the uTasker project for the K64.&lt;/P&gt;&lt;P&gt;It contains Micrel SMI mode of operation (this cannot be performed with the usual MDIO mode) and also supports the KSZ8863 tail-tagging mode to allow it to be used as if there were two independent Ethernet controllers.&lt;/P&gt;&lt;P&gt;The uTasker TCP/IP stack support multi-homed network operation, which can be achieved with the K64 and this PHY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kinetis: &lt;A href="http://www.utasker.com/kinetis.html" title="http://www.utasker.com/kinetis.html"&gt;µTasker Kinetis support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;K64: &lt;A href="http://www.utasker.com/kinetis/FRDM-K64F.html" title="http://www.utasker.com/kinetis/FRDM-K64F.html"&gt;µTasker Kinetis FRDM-K64F support&lt;/A&gt;&amp;nbsp; / &lt;A href="http://www.utasker.com/kinetis/TWR-K64F120M.html" title="http://www.utasker.com/kinetis/TWR-K64F120M.html"&gt;µTasker Kinetis TWR-K64F120M support&lt;/A&gt;&amp;nbsp; / &lt;A href="http://www.utasker.com/kinetis/TWR-K65F180M.html" title="http://www.utasker.com/kinetis/TWR-K65F180M.html"&gt;µTasker Kinetis TWR-K65F180M support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;EM&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market &lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Jul 2015 18:37:35 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2015-07-24T18:37:35Z</dc:date>
    <item>
      <title>K64F120M  communication with Micrel KSZ8863 problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444634#M26220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Now our project encountered a problem: the k64 cpu want to&lt;BR /&gt;communicate with micrel ksz8863 through SMI mode to visit the internal register&lt;BR /&gt;from 0~198. According to the SMI mode visit protocol, the different is below:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;PAGE 1172 in attached k64 cpu&lt;BR /&gt;datasheet:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_7.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/52652i8E2D5C04DF23CC9C/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_7.png" alt="pastedImage_7.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;OP= 00 WRITE/OP=11 READ&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;And in 8863 datasheet (page33 ):&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/52569iD3B790C1ADD54AC2/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;OP = 00 read/write function&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;It seems the two datasheet about&lt;BR /&gt;the OP is contradictory.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;Do you have any guidance or&lt;BR /&gt;information according to your experience?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jul 2015 07:45:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444634#M26220</guid>
      <dc:creator>wulinweng</dc:creator>
      <dc:date>2015-07-24T07:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: K64F120M  communication with Micrel KSZ8863 problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444635#M26221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you require a professional solution to your problem you can obtain all that you require from the uTasker project for the K64.&lt;/P&gt;&lt;P&gt;It contains Micrel SMI mode of operation (this cannot be performed with the usual MDIO mode) and also supports the KSZ8863 tail-tagging mode to allow it to be used as if there were two independent Ethernet controllers.&lt;/P&gt;&lt;P&gt;The uTasker TCP/IP stack support multi-homed network operation, which can be achieved with the K64 and this PHY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kinetis: &lt;A href="http://www.utasker.com/kinetis.html" title="http://www.utasker.com/kinetis.html"&gt;µTasker Kinetis support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;K64: &lt;A href="http://www.utasker.com/kinetis/FRDM-K64F.html" title="http://www.utasker.com/kinetis/FRDM-K64F.html"&gt;µTasker Kinetis FRDM-K64F support&lt;/A&gt;&amp;nbsp; / &lt;A href="http://www.utasker.com/kinetis/TWR-K64F120M.html" title="http://www.utasker.com/kinetis/TWR-K64F120M.html"&gt;µTasker Kinetis TWR-K64F120M support&lt;/A&gt;&amp;nbsp; / &lt;A href="http://www.utasker.com/kinetis/TWR-K65F180M.html" title="http://www.utasker.com/kinetis/TWR-K65F180M.html"&gt;µTasker Kinetis TWR-K65F180M support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;EM&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market &lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jul 2015 18:37:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444635#M26221</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2015-07-24T18:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: K64F120M  communication with Micrel KSZ8863 problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444636#M26222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mark,&lt;/P&gt;&lt;P&gt;Thank you so much for your quick reply.&lt;/P&gt;&lt;P&gt;I have download the uTasker source code and checked the source code about the SMI mode, but the result is that the SMI mode in the source code used OP = 01/10,&lt;/P&gt;&lt;P&gt;So I think it is the MIIM mode not SMI mode indeed.&lt;/P&gt;&lt;P&gt;Now we want to use OP=00 to read/write internal register 0-198 from ksz8863.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jul 2015 01:53:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444636#M26222</guid>
      <dc:creator>wulinweng</dc:creator>
      <dc:date>2015-07-28T01:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: K64F120M  communication with Micrel KSZ8863 problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444637#M26223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the code you need to search for the define &lt;STRONG&gt;PHY_MICREL_SMI&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;For writes the code used is &lt;STRONG&gt;(MII_TA | MII_ST)&lt;/STRONG&gt;, instead of &lt;STRONG&gt;(MII_TA | MII_ST | WRITE_OP)&lt;/STRONG&gt;, as used for normal MIIM: &lt;EM&gt;fnMIIwrite()&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;For reads it is not possible to use the MIIM so you will find that the reads are performed by bit-banging the interface: &lt;EM&gt;fnMIIread()&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;In the solution the MIIM mode is used when the routines are passed an address != 0. When the address is 0, the SMI mode is used instead. Therefore you can certainly find this if you search.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kinetis: &lt;A class="jive-link-external-small" data-content-finding="Community" href="http://www.utasker.com/kinetis.html" rel="nofollow"&gt;µTasker Kinetis support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;K64: &lt;A class="jive-link-external-small" data-content-finding="Community" href="http://www.utasker.com/kinetis/FRDM-K64F.html" rel="nofollow"&gt;µTasker Kinetis FRDM-K64F support&lt;/A&gt;&amp;nbsp; / &lt;A class="jive-link-external-small" data-content-finding="Community" href="http://www.utasker.com/kinetis/TWR-K64F120M.html" rel="nofollow"&gt;µTasker Kinetis TWR-K64F120M support&lt;/A&gt;&amp;nbsp; / &lt;A class="jive-link-external-small" data-content-finding="Community" href="http://www.utasker.com/kinetis/TWR-K65F180M.html" rel="nofollow"&gt;µTasker Kinetis TWR-K65F180M support&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;EM&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market &lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jul 2015 02:29:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K64F120M-communication-with-Micrel-KSZ8863-problem/m-p/444637#M26223</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2015-07-28T02:29:19Z</dc:date>
    </item>
  </channel>
</rss>

