<?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>i.MX Processors中的主题 Boundary scan test issue on IMX6</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502960#M81446</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On a design with IMX6 solo MCIMX6S7CVM08AC, connect to a Goepel tool, we have the following issue:&lt;/P&gt;&lt;P&gt;- TMS=1, 5 clocks -&amp;gt; state machine is in TLR state (OK).&lt;/P&gt;&lt;P&gt;- go to shift DR, put on TDI 52H (01010010), after 32+8 clocks we read on TDO:&lt;/P&gt;&lt;P&gt; 0101010 00011000100100011011000000011101 (first bit right) where&lt;/P&gt;&lt;P&gt; -first "1" IEE1149.1 requirement&lt;/P&gt;&lt;P&gt; -"00000001110"&amp;nbsp; &amp;amp; -- Manufacturer Identity&lt;/P&gt;&lt;P&gt; -"1000100100011011"&amp;nbsp; &amp;amp; -- Part Number&lt;/P&gt;&lt;P&gt; -"0010"&amp;nbsp; &amp;amp; -- Version&lt;/P&gt;&lt;P&gt; -"01010010" (52H) Goepel "Testbyte" :&amp;nbsp; this testbyte is shifted through test bus chain to verified test bus.&lt;/P&gt;&lt;P&gt; ---&amp;gt; This test is OK&lt;/P&gt;&lt;P&gt; - go to IR, load bypass instruction.&lt;/P&gt;&lt;P&gt; - return to DR shift, put Testbyte on TDI, read on TDO:&lt;/P&gt;&lt;P&gt; - 010100100 (first bit right):&lt;/P&gt;&lt;P&gt; - first "0" : bypass register&lt;/P&gt;&lt;P&gt; - 01010010: Test byte&lt;/P&gt;&lt;P&gt; ---&amp;gt; This test is OK&lt;/P&gt;&lt;P&gt; - go to IR, load sample/preload instruction.&lt;/P&gt;&lt;P&gt; - return to DR shift, put on TDI Testbyte (01010010) then 010101...(652 bit, it's the boundary scan lenght).&lt;/P&gt;&lt;P&gt; - after 652 + 8 clock&amp;nbsp; we must read Testbyte --&amp;gt; This test fail, all bit are set at 0.&lt;/P&gt;&lt;P&gt; In fact, we cannot control the BSR (Boundary Scan Register), we try also with Extest instruction, it's the same answer.&lt;/P&gt;&lt;P&gt; Fuse are not burned on the board.&lt;/P&gt;&lt;P&gt; We try the same test on a SABRE PLATEFORM, with a PCIMX6U8DVM10AB, the same test is OK.&lt;/P&gt;&lt;P&gt; Compliance pattern are the same in the two case :&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "(TEST_MODE, JTAG_MOD, POR_B)= (011)".&lt;/P&gt;&lt;P&gt;Could you help us, please.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Luc Dalongeville&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 May 2016 06:54:41 GMT</pubDate>
    <dc:creator>luc410</dc:creator>
    <dc:date>2016-05-26T06:54:41Z</dc:date>
    <item>
      <title>Boundary scan test issue on IMX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502960#M81446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On a design with IMX6 solo MCIMX6S7CVM08AC, connect to a Goepel tool, we have the following issue:&lt;/P&gt;&lt;P&gt;- TMS=1, 5 clocks -&amp;gt; state machine is in TLR state (OK).&lt;/P&gt;&lt;P&gt;- go to shift DR, put on TDI 52H (01010010), after 32+8 clocks we read on TDO:&lt;/P&gt;&lt;P&gt; 0101010 00011000100100011011000000011101 (first bit right) where&lt;/P&gt;&lt;P&gt; -first "1" IEE1149.1 requirement&lt;/P&gt;&lt;P&gt; -"00000001110"&amp;nbsp; &amp;amp; -- Manufacturer Identity&lt;/P&gt;&lt;P&gt; -"1000100100011011"&amp;nbsp; &amp;amp; -- Part Number&lt;/P&gt;&lt;P&gt; -"0010"&amp;nbsp; &amp;amp; -- Version&lt;/P&gt;&lt;P&gt; -"01010010" (52H) Goepel "Testbyte" :&amp;nbsp; this testbyte is shifted through test bus chain to verified test bus.&lt;/P&gt;&lt;P&gt; ---&amp;gt; This test is OK&lt;/P&gt;&lt;P&gt; - go to IR, load bypass instruction.&lt;/P&gt;&lt;P&gt; - return to DR shift, put Testbyte on TDI, read on TDO:&lt;/P&gt;&lt;P&gt; - 010100100 (first bit right):&lt;/P&gt;&lt;P&gt; - first "0" : bypass register&lt;/P&gt;&lt;P&gt; - 01010010: Test byte&lt;/P&gt;&lt;P&gt; ---&amp;gt; This test is OK&lt;/P&gt;&lt;P&gt; - go to IR, load sample/preload instruction.&lt;/P&gt;&lt;P&gt; - return to DR shift, put on TDI Testbyte (01010010) then 010101...(652 bit, it's the boundary scan lenght).&lt;/P&gt;&lt;P&gt; - after 652 + 8 clock&amp;nbsp; we must read Testbyte --&amp;gt; This test fail, all bit are set at 0.&lt;/P&gt;&lt;P&gt; In fact, we cannot control the BSR (Boundary Scan Register), we try also with Extest instruction, it's the same answer.&lt;/P&gt;&lt;P&gt; Fuse are not burned on the board.&lt;/P&gt;&lt;P&gt; We try the same test on a SABRE PLATEFORM, with a PCIMX6U8DVM10AB, the same test is OK.&lt;/P&gt;&lt;P&gt; Compliance pattern are the same in the two case :&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "(TEST_MODE, JTAG_MOD, POR_B)= (011)".&lt;/P&gt;&lt;P&gt;Could you help us, please.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Luc Dalongeville&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 06:54:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502960#M81446</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2016-05-26T06:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary scan test issue on IMX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502961#M81447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN style="font-size: 14.6667px; font-family: Calibri, sans-serif;"&gt;If boundary scan test is used, PCIE_VP, PCIE_VPH, and PCIE_VPTX must remain powered.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Please check it. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Have a great day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Yuri&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Note: If this post answers your question, please click the Correct &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;Answer &lt;/SPAN&gt;&lt;SPAN class="tm7"&gt;button. Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="tm6 tm5 a______"&gt;&lt;SPAN class="tm7"&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 07:01:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502961#M81447</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2016-05-26T07:01:25Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary scan test issue on IMX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502962#M81448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Yuri,&lt;/P&gt;&lt;P&gt;Information in HW manual is ambiguous:&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;SATA and PCIe are not digital interfaces, but these modules provide built-in support for the &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #ff3333; font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;IEEE 1149.6 &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;extension for AC testing of their pins. Therefore,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt; these modules must also be powered when utilizing a scan chain&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000; font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;that contains the pins from these modules, or the scan chain does not function properly."&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;We use &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #ff3333; font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;IEEE 1149.1 &lt;/SPAN&gt;&lt;/SPAN&gt; , so we skip this comment.&lt;/P&gt;&lt;P&gt;I think this mandatory information could be available in bsdl file, under "Design-warning" attribute,&lt;BR /&gt;to help test engineering team.&lt;BR /&gt;About the issue, we check the design and PCIE interface is not powered...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a nice day&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt; font-family: TimesNewRomanPSMT,serif;"&gt;&lt;SPAN lang="en-US"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 08:46:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-scan-test-issue-on-IMX6/m-p/502962#M81448</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2016-05-26T08:46:26Z</dc:date>
    </item>
  </channel>
</rss>

