<?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のトピックRe: Burning fuses</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1626644#M203607</link>
    <description>&lt;P&gt;Sure&lt;/P&gt;</description>
    <pubDate>Mon, 03 Apr 2023 07:09:43 GMT</pubDate>
    <dc:creator>yanz</dc:creator>
    <dc:date>2023-04-03T07:09:43Z</dc:date>
    <item>
      <title>Burning fuses</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1619156#M203022</link>
      <description>&lt;P&gt;How can I burn fuses using NXP-MCUBootUtility tool without connect to flashloader first (there are no SW6 related GPIOs on custom board)?&lt;/P&gt;&lt;P&gt;Is it possible?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 11:38:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1619156#M203022</guid>
      <dc:creator>yanz</dc:creator>
      <dc:date>2023-03-21T11:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: Burning fuses</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1620783#M203140</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/199488"&gt;@yanz&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I hope you are doing well.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please make sure the imx board one is using is supported by NXP-MCUBootUtility.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-NXP-MCUBootUtility supports given below boards.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;i.MXRT1021, i.MXRT1051/1052, i.MXRT1061/1062, i.MXRT1064 SIP&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-NXP-MCUBootUtility supports common eFuse memory operation (eFuse Programmer)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt;The flash loader is responsible for initializing the microcontroller and setting up the communication channel between the microcontroller and the host computer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt;Without the flash loader, the NXP-MCUBootUtility tool will not be able to communicate with the microcontroller and access its registers to program the fuses.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;Dhruvit Vasavada&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 10:04:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1620783#M203140</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2023-03-23T10:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: Burning fuses</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1623913#M203394</link>
      <description>&lt;P&gt;The correct answer is:&lt;/P&gt;&lt;P&gt;It seems this is because blhost send configure-memory command to flashloader, but flashloader fail to configure flash and hung by the process. So, MCUBootUtility cannot communication with flashloader anymore.&lt;BR /&gt;You can&amp;nbsp;set the "Boot Device" to "LPSPI NOR/EEPROM" and connect.&lt;/P&gt;&lt;P&gt;MCUBootUtility will not check eeprom so that it can connect successfully. After that you can scan and burn the fuse.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2023 07:09:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1623913#M203394</guid>
      <dc:creator>yanz</dc:creator>
      <dc:date>2023-03-29T07:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Burning fuses</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1626642#M203605</link>
      <description>&lt;DIV id="bodyDisplay_0" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;&lt;SPAN class="im"&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/199488"&gt;@yanz&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;I hope you are doing well.&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Thanks for the clarification.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;You can set the "Boot Device" to "LPSPI NOR/EEPROM" and connect.&lt;BR /&gt;MCUBootUtility will not check eeprom so that it can connect successfully. After that, you can scan and burn the fuse.&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt;If this answers your query, can I close this case?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks &amp;amp; Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Dhruvit Vasavada&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 03 Apr 2023 07:07:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1626642#M203605</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2023-04-03T07:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: Burning fuses</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1626644#M203607</link>
      <description>&lt;P&gt;Sure&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 07:09:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Burning-fuses/m-p/1626644#M203607</guid>
      <dc:creator>yanz</dc:creator>
      <dc:date>2023-04-03T07:09:43Z</dc:date>
    </item>
  </channel>
</rss>

