<?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中的主题 Multiplexing JTAG and EZport Pins In CPLD</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265761#M8573</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my system I will have 2 processors.&amp;nbsp; An iMX6 host processor for the GUI and a Kinetis K10 for real-time processing.&amp;nbsp; The iMX6 will be able to program the K10 through the EZPORT interface.&amp;nbsp; I will also be using a Segger J-link with the K10.&amp;nbsp; On the K10, there are 3 JTAG pins that are multiplexed with EZPORT pins.&amp;nbsp; I was going to route these pins through a CPLD which would have logic to switch these signals between the iMX6 and the Segger J-Link.&amp;nbsp; By default the pins will be switched to the J-link.&amp;nbsp; If the iMX6 wants to program the K10, it will switch the pins using one of its DIO pins.&amp;nbsp; Does anyone see a problem with this?&amp;nbsp; I have attached a diagram to illustrate the idea.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jul 2013 02:16:06 GMT</pubDate>
    <dc:creator>kevinkirspel</dc:creator>
    <dc:date>2013-07-11T02:16:06Z</dc:date>
    <item>
      <title>Multiplexing JTAG and EZport Pins In CPLD</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265761#M8573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my system I will have 2 processors.&amp;nbsp; An iMX6 host processor for the GUI and a Kinetis K10 for real-time processing.&amp;nbsp; The iMX6 will be able to program the K10 through the EZPORT interface.&amp;nbsp; I will also be using a Segger J-link with the K10.&amp;nbsp; On the K10, there are 3 JTAG pins that are multiplexed with EZPORT pins.&amp;nbsp; I was going to route these pins through a CPLD which would have logic to switch these signals between the iMX6 and the Segger J-Link.&amp;nbsp; By default the pins will be switched to the J-link.&amp;nbsp; If the iMX6 wants to program the K10, it will switch the pins using one of its DIO pins.&amp;nbsp; Does anyone see a problem with this?&amp;nbsp; I have attached a diagram to illustrate the idea.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 02:16:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265761#M8573</guid>
      <dc:creator>kevinkirspel</dc:creator>
      <dc:date>2013-07-11T02:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Multiplexing JTAG and EZport Pins In CPLD</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265762#M8574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, in my understanding , the function of the CPLD can be replaced&amp;nbsp; by some jumpers, since JTAG and EZport can not be used in the same time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 03:05:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265762#M8574</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2013-07-11T03:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Multiplexing JTAG and EZport Pins In CPLD</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265763#M8575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kevin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that there is not any problem with multiplexing pins using this method, but there are some points you should consider:&lt;/P&gt;&lt;P&gt;- Jlink supports both JTAG and SWD (SWD using 2 pins only). If you use SWD instead of JTAG, there is only one shared pin.&lt;/P&gt;&lt;P&gt;- Unless you use CPLD for something else already, it is not cost effective to use CPLD just for multiplex 1-3 pins.&lt;/P&gt;&lt;P&gt;- EzPort requires reset circle so do not forget to design it in a way that you can control reset pin of K10&lt;/P&gt;&lt;P&gt;- I am not sure if you had a look at Vybrid platform or not but Vybrid can help to reduce cost and size of the system where both realtime app and rich user interface are needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 11:39:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265763#M8575</guid>
      <dc:creator>Dekiru</dc:creator>
      <dc:date>2013-07-11T11:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: Multiplexing JTAG and EZport Pins In CPLD</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265764#M8576</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I already have a CPLD for other things so it cost me nothing to add this functionality.&amp;nbsp; I will look into the Vybrid platform.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 12:13:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Multiplexing-JTAG-and-EZport-Pins-In-CPLD/m-p/265764#M8576</guid>
      <dc:creator>kevinkirspel</dc:creator>
      <dc:date>2013-07-11T12:13:28Z</dc:date>
    </item>
  </channel>
</rss>

