<?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: i.MX8M Mini JTAG ID  in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978799#M145586</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I asked internally and was adviced, below:&lt;/P&gt;&lt;P&gt;---------&lt;/P&gt;&lt;P&gt;Have you followed i.MX8M Mini HDG chapter 5.5 to enter boundary scan mode? This is how JTAG ID of DFT_TAP (for IEEE1149.1) could be seen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/104680iA908D28D63C59D13/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.jpg" alt="pastedImage_1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt;"&gt;HDG :&lt;/SPAN&gt; &lt;SPAN style="font-size: 10.5pt;"&gt;&lt;A href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.nxp.com.cn%2Fwebapp%2Fsps%2Fdownload%2FpreDownload.jsp%3Frender%3Dtrue" rel="nofollow" target="_blank"&gt;https://www.nxp.com.cn/webapp/sps/download/preDownload.jsp?render=true&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Jan 2020 23:45:15 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2020-01-09T23:45:15Z</dc:date>
    <item>
      <title>i.MX8M Mini JTAG ID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978796#M145583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I used JTAG on our own hardware (called "Verdin") through a Segger J-Link Pro JTAG adapter.&lt;/P&gt;&lt;P&gt;I&amp;nbsp;was able to scan the following JTAG IDs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H1&gt;JTAG DAP&lt;/H1&gt;&lt;P&gt;(BOOT_MODE1; BOOT_MODE0; TEST_MODE; JTAG_MOD) = 1100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;ID = 0x5BA00477&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This is expected&lt;/EM&gt;&lt;/P&gt;&lt;H1&gt;JTAG Bounary Scan&lt;/H1&gt;&lt;P&gt;(BOOT_MODE1; BOOT_MODE0; TEST_MODE; JTAG_MOD) = 1101&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;ID = 0x088E401D&lt;/P&gt;&lt;P&gt;The JTAG ID listed in the BSDL file &lt;EM&gt;IMX8MMINI-BSDL.bsdl&lt;/EM&gt; is 0x1CF80553.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question: Why am I reading this unexpected ID?&lt;/P&gt;&lt;P&gt;I'm aware that my strap pins are not in compliance with the boundary scan requirements, but according to the block diagrams in the reference manual I should still access the boundary scan controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there an error in the BSDL file, or am I accessing a different JTAG unit due to the wrong strapping? Unfortunately I cannot make my hardware strappings compliant, and on NXP's EVK JTAG is currently not working at all for me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2020 16:40:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978796#M145583</guid>
      <dc:creator>andy_kiser</dc:creator>
      <dc:date>2020-01-07T16:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M Mini JTAG ID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978797#M145584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;I'm aware that my strap pins are not in compliance with the boundary scan requirements, but&lt;/P&gt;&lt;P&gt;&amp;gt;according to the block diagrams in the reference manual I should still access the boundary scan controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;according to Figure 4-21. System JTAG Controller (SJC) Block Diagram&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://www.nxp.com/webapp/Download?colCode=IMX8MMRM" target="_blank"&gt;&lt;STRONG&gt;i.MX 8M Mini Applications Processor Reference Manual&lt;/STRONG&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;JTAG_MOD=0 does not allow to access boundary scan controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2020 23:27:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978797#M145584</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2020-01-07T23:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M Mini JTAG ID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978798#M145585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor&lt;/P&gt;&lt;P&gt;I fully agree. With JTAG_MOD=0, I see the JTAG ID = 0x5BA00477 (as expected).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is about JTAG_MOD=1.&lt;/P&gt;&lt;P&gt;Section 4.10.1.5 of the Reference manual states&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;Test mode: JTAG_MOD == 1, SJC is the only TAP controller in the daisy chain.&lt;BR /&gt;1149.1-compliant, and support 1149.6 AC coupled test.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Therefore I would expected to see the JTAG ID which is defined in the BSDL file (0x1CF80553).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards, Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jan 2020 07:45:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978798#M145585</guid>
      <dc:creator>andy_kiser</dc:creator>
      <dc:date>2020-01-08T07:45:22Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M Mini JTAG ID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978799#M145586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I asked internally and was adviced, below:&lt;/P&gt;&lt;P&gt;---------&lt;/P&gt;&lt;P&gt;Have you followed i.MX8M Mini HDG chapter 5.5 to enter boundary scan mode? This is how JTAG ID of DFT_TAP (for IEEE1149.1) could be seen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/104680iA908D28D63C59D13/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.jpg" alt="pastedImage_1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt;"&gt;HDG :&lt;/SPAN&gt; &lt;SPAN style="font-size: 10.5pt;"&gt;&lt;A href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.nxp.com.cn%2Fwebapp%2Fsps%2Fdownload%2FpreDownload.jsp%3Frender%3Dtrue" rel="nofollow" target="_blank"&gt;https://www.nxp.com.cn/webapp/sps/download/preDownload.jsp?render=true&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jan 2020 23:45:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-Mini-JTAG-ID/m-p/978799#M145586</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2020-01-09T23:45:15Z</dc:date>
    </item>
  </channel>
</rss>

