<?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 nano Fusemap Bit Array in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186911#M241444</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/216936"&gt;@danab&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Yes, that is also valid, I said the most quick way to write the fuses, the other end option is the one that you said, you burn/set a fuse bit and later burn another one from the same word, in the next operation you can write 0 to previous burned fuses and have no effect, as described by you.&lt;/P&gt;
&lt;P&gt;Yes, setting lock bits prevent from writing to the protected bits.&lt;/P&gt;
&lt;P&gt;Let me know if you have further questions.&lt;/P&gt;
&lt;P&gt;Regards!&lt;/P&gt;</description>
    <pubDate>Wed, 15 Oct 2025 20:32:22 GMT</pubDate>
    <dc:creator>JosephAtNXP</dc:creator>
    <dc:date>2025-10-15T20:32:22Z</dc:date>
    <item>
      <title>i.MX8M nano Fusemap Bit Array</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186762#M241433</link>
      <description>&lt;P&gt;I am having a difficult time figuring out which fuses on the i.MX8M nano are in the fuse array and which are bank/word. Which fuses can be burned a fuse at a time, and which must be burned a word at at time?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 15:42:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186762#M241433</guid>
      <dc:creator>danab</dc:creator>
      <dc:date>2025-10-15T15:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M nano Fusemap Bit Array</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186790#M241438</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;
&lt;P&gt;You can burn fuses by word, you first need to identify what word you want to burn, e.g. 480 fuse, which is bank 2 word 0.&lt;/P&gt;
&lt;P&gt;Then, confirm the lock bits in the words if the word has lock bits that you want to SET, I would recommend burning lock bits first and then burn the rest of the fuses.&lt;/P&gt;
&lt;P&gt;In summary, all can be word size burned, but I recommend burning first lock bits by word then the rest of the bits of that word.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JosephAtNXP_0-1760545560747.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/360964iA54596A55BD9E832/image-size/large?v=v2&amp;amp;px=999" role="button" title="JosephAtNXP_0-1760545560747.png" alt="JosephAtNXP_0-1760545560747.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 16:34:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186790#M241438</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-10-15T16:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M nano Fusemap Bit Array</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186815#M241440</link>
      <description>&lt;P&gt;Thank you for your reply, Joseph.&amp;nbsp; Let me see if I understand this correctly.&lt;/P&gt;&lt;P&gt;Let's say, for instance, I burn 0x450 bit 8 with 0x00000100, could I then go back and burn 0x450 bit 24 with 0x01000000? Assuming after both writes the fuses would be 0x01000100.&amp;nbsp; Or can I only write to that address 1 time?&lt;BR /&gt;&lt;BR /&gt;Also, if I burn the lock fuses first, wouldn't that prevent me from burning the fuses they are controlling?&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 17:24:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186815#M241440</guid>
      <dc:creator>danab</dc:creator>
      <dc:date>2025-10-15T17:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M nano Fusemap Bit Array</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186911#M241444</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/216936"&gt;@danab&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Yes, that is also valid, I said the most quick way to write the fuses, the other end option is the one that you said, you burn/set a fuse bit and later burn another one from the same word, in the next operation you can write 0 to previous burned fuses and have no effect, as described by you.&lt;/P&gt;
&lt;P&gt;Yes, setting lock bits prevent from writing to the protected bits.&lt;/P&gt;
&lt;P&gt;Let me know if you have further questions.&lt;/P&gt;
&lt;P&gt;Regards!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 20:32:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2186911#M241444</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-10-15T20:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M nano Fusemap Bit Array</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2187492#M241457</link>
      <description>Thanks, Joseph!</description>
      <pubDate>Thu, 16 Oct 2025 11:04:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-nano-Fusemap-Bit-Array/m-p/2187492#M241457</guid>
      <dc:creator>danab</dc:creator>
      <dc:date>2025-10-16T11:04:36Z</dc:date>
    </item>
  </channel>
</rss>

