<?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: IMX6Q processor MAC ID fusing is happing in the second attempt</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-processor-MAC-ID-fusing-is-happing-in-the-second-attempt/m-p/1833855#M221674</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/231298"&gt;@RojeshAK&lt;/a&gt;!&lt;BR /&gt;Thank you for contacting NXP Support!&lt;BR /&gt;&lt;BR /&gt;You should use the "MAC_ADDR_LOCK" fuses.&lt;BR /&gt;&lt;BR /&gt;00 - Unlock (The controlled field can be read, sensed, burned or overridden in the corresponded.&lt;BR /&gt;1x - Override Protect (OP)&lt;BR /&gt;x1 - Write Protect (WP)&lt;BR /&gt;11 - Both OP and WP&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Chavira_0-1711123163175.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/269998iF0C80913424DA8B7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Chavira_0-1711123163175.png" alt="Chavira_0-1711123163175.png" /&gt;&lt;/span&gt;&lt;BR /&gt;Best Regards!&lt;BR /&gt;Chavira&lt;/P&gt;</description>
    <pubDate>Fri, 22 Mar 2024 16:01:49 GMT</pubDate>
    <dc:creator>Chavira</dc:creator>
    <dc:date>2024-03-22T16:01:49Z</dc:date>
    <item>
      <title>IMX6Q processor MAC ID fusing is happing in the second attempt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-processor-MAC-ID-fusing-is-happing-in-the-second-attempt/m-p/1833559#M221653</link>
      <description>&lt;P&gt;Hi NXP Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to fuse MAC ID to the imx6q processor, the following is the behaviour&lt;/P&gt;&lt;P&gt;Existing MAC ID:&lt;/P&gt;&lt;P&gt;=&amp;gt; printenv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ethaddr=00:23:4a:f0:00:01&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trying to fuse the same MAC ID in the first attempt&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 2 0x4AF00001&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 3 0x0023&lt;/P&gt;&lt;P&gt;=&amp;gt; printenv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ethaddr=00:23:4a:f0:00:01&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trying to fuse another MAC ID in the second attempt&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 2 0x4AF00007&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 3 0x0023&lt;/P&gt;&lt;P&gt;=&amp;gt; printenv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ethaddr=00:23:4a:f0:00:07&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the MAC ID was updated&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Third attempt to fuse the MAC ID with the first MAC address&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 2 0x4AF00001&lt;/P&gt;&lt;P&gt;=&amp;gt; fuse prog 4 3 0x0023&lt;/P&gt;&lt;P&gt;=&amp;gt; printenv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ethaddr=00:23:4a:f0:00:07&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Observation we made&lt;/P&gt;&lt;P&gt;1) First Attempt - Fuse Not happened&lt;/P&gt;&lt;P&gt;2) Second Attempt - Fuse Happened&lt;/P&gt;&lt;P&gt;3) Third Attempt - Fuse not happened&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above is not expected behaviour, MAC id is OTP (one-time programmable ) single non-volatile memory, it should happen in the first attempt only but it happens in the second attempt&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For complete logs, please refer to the attachment&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please provide us with the user document for fusing the Mac address in the imx6q processor&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;If possible please share with us the steps/procedure for fusing the MAC address on the first attempt&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;We are waiting for your feedback&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Fri, 22 Mar 2024 08:25:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-processor-MAC-ID-fusing-is-happing-in-the-second-attempt/m-p/1833559#M221653</guid>
      <dc:creator>RojeshAK</dc:creator>
      <dc:date>2024-03-22T08:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: IMX6Q processor MAC ID fusing is happing in the second attempt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-processor-MAC-ID-fusing-is-happing-in-the-second-attempt/m-p/1833855#M221674</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/231298"&gt;@RojeshAK&lt;/a&gt;!&lt;BR /&gt;Thank you for contacting NXP Support!&lt;BR /&gt;&lt;BR /&gt;You should use the "MAC_ADDR_LOCK" fuses.&lt;BR /&gt;&lt;BR /&gt;00 - Unlock (The controlled field can be read, sensed, burned or overridden in the corresponded.&lt;BR /&gt;1x - Override Protect (OP)&lt;BR /&gt;x1 - Write Protect (WP)&lt;BR /&gt;11 - Both OP and WP&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Chavira_0-1711123163175.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/269998iF0C80913424DA8B7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Chavira_0-1711123163175.png" alt="Chavira_0-1711123163175.png" /&gt;&lt;/span&gt;&lt;BR /&gt;Best Regards!&lt;BR /&gt;Chavira&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 16:01:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-processor-MAC-ID-fusing-is-happing-in-the-second-attempt/m-p/1833855#M221674</guid>
      <dc:creator>Chavira</dc:creator>
      <dc:date>2024-03-22T16:01:49Z</dc:date>
    </item>
  </channel>
</rss>

