<?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: Boundary Scan test issue on IMX6UL device in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747759#M116278</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;So the only way to avoid the timeout is to reprogram the IMX register but how can we do that ?&lt;/P&gt;&lt;P&gt;Do we have to replace the IMX on our board or can we use a tool to reprogram it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Jul 2018 14:44:41 GMT</pubDate>
    <dc:creator>luc410</dc:creator>
    <dc:date>2018-07-02T14:44:41Z</dc:date>
    <item>
      <title>Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747753#M116272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3333ff;"&gt; I run a boundary scan test (Goepel) on a design with an IMX6UL, a PMIC MC32PF3001, a Nand Flash, a DDR3 and some other glue.&lt;BR /&gt; When I test Nand Flash or DDR3 and if the test time is lower than about 5s, there is no problem.&lt;BR /&gt; If the test time is upper than about 5s (I decrease tester clock) , when the tester release the tap JTAG (state machin is in TLR- Test Logic Reset), immediatly the IMX6 drive a low on "PMIC_ON_REQ" (pin T9), so the PMIC is turned off, then it send a low state on POR_B (pin T8) of IMX6.&lt;BR /&gt; Port_B is a compliant pattern, it must be high to permit the control of JTAG tap. So, it's impossible to &lt;/SPAN&gt;&lt;SPAN style="color: #3333ff;"&gt;have control of the IMX through jtag bus.&lt;BR /&gt; To do that, the only way is to disconnect (hardware) the main power, and wait until discharge of all capacitors.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3333ff;"&gt;This problem doesn't appear on INFRA test, even if the tester wait 10 mn.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3333ff;"&gt;Thanks for your help.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3333ff;"&gt;Luc Dalongeville&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 May 2018 13:58:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747753#M116272</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2018-05-11T13:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747754#M116273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Luc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;problem may be caused by Power-down counter described in&lt;/P&gt;&lt;P&gt;sect.57.5.3 Power-down counter event i.MX6UL Reference Manual &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Freference-manual%2FIMX6ULRM.pdf" rel="nofollow" target="_blank"&gt;http://www.nxp.com/docs/en/reference-manual/IMX6ULRM.pdf&lt;/A&gt;&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>Mon, 21 May 2018 10:44:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747754#M116273</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-05-21T10:44:53Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747755#M116274</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;Thanks for these informations.&lt;/P&gt;&lt;P&gt;I have studied this paragraph in the document cited but I have not found any connection with our problem.&lt;BR /&gt; In fact, the component reacted as the pin ONOFF was activated: after 5 seconds, the pin "PMIC_ON_REQ" falls to 0.&lt;BR /&gt; Is it possible that during the boundary scan test the internal circuitry of the ON / OFF signal is activated?&lt;BR /&gt; Because the result we see is exactly that situation. &lt;BR /&gt;Note that in the design this pin is left unconnected&amp;nbsp; (logic level 1) and never activated.&lt;BR /&gt;This problem appear only when we use BSR register, not if we use IDCODE or BYPASS register.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Luc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2018 09:45:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747755#M116274</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2018-06-14T09:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747756#M116275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Luc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;power-down counter behaves exactly as the pin ONOFF so it has connection to observed problem.&lt;/P&gt;&lt;P&gt;Can issue be reproduced on NXP i.MX6UL EVK reference board.&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>Fri, 15 Jun 2018 01:42:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747756#M116275</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-06-15T01:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747757#M116276</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;Infortunatly, I have no reference board.&lt;/P&gt;&lt;P&gt;I am not a designer, my job is to do boundary scan test program to test&amp;nbsp; a board, and on this board there is an IMX6UL device.&lt;/P&gt;&lt;P&gt;So, I use JTAG TAP as define in 1149.1 rules. When the IMX stay in "extest" more than 5 s, even if we execute tapreset or not, output are controlled by logic core and not the Boundary Scan cells, so the signal "PMIC_ON_REQ" falls to 0, even when there is a 1 in the corresponding BS cells.&lt;/P&gt;&lt;P&gt;Is it possible to disable this timeout by boundary scan action ? &lt;BR /&gt;In our JTAG tools (Goepel), we can only access boundary scan register (ID_CODE, BYPASS, Instruction REGISTER,BSR).&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jun 2018 12:54:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747757#M116276</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2018-06-26T12:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747758#M116277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Luc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;timeout can be disabled by bit PDE register WDOGx_WMCR,&lt;BR /&gt;as described in sect.57.7.5 Watchdog Miscellaneous Control Register&lt;BR /&gt;(WDOGx_WMCR) i.MX6UL Reference Manual, it can not&lt;BR /&gt;be disabled by boundary scan action.&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>Tue, 26 Jun 2018 23:07:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747758#M116277</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-06-26T23:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747759#M116278</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;So the only way to avoid the timeout is to reprogram the IMX register but how can we do that ?&lt;/P&gt;&lt;P&gt;Do we have to replace the IMX on our board or can we use a tool to reprogram it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jul 2018 14:44:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747759#M116278</guid>
      <dc:creator>luc410</dc:creator>
      <dc:date>2018-07-02T14:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Scan test issue on IMX6UL device</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747760#M116279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Luc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it can not be reprogramed. One can attach jtag debugger&lt;/P&gt;&lt;P&gt;and write to register appropriate value, as for example described in AN5229&lt;/P&gt;&lt;P&gt;ARM DS-5 Development Studio Debug i.MX6UL-EVK.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN5229.pdf" title="https://www.nxp.com/docs/en/application-note/AN5229.pdf"&gt;https://www.nxp.com/docs/en/application-note/AN5229.pdf&lt;/A&gt;&amp;nbsp;&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>Tue, 03 Jul 2018 01:57:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Boundary-Scan-test-issue-on-IMX6UL-device/m-p/747760#M116279</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-07-03T01:57:38Z</dc:date>
    </item>
  </channel>
</rss>

