<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125551/how-to-keep-the-same-mac-address-after-consecutive-build-and-flash-operations</link><description>I&amp;#39;m developing an OpenThread Sleepy End Device (SED) that periodically sends a payload to a CoAP server, including its own MAC address as one of the values. However, I noticed that the MAC address changes every time I build and flash the firmware. How</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 04 Dec 2025 20:25:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125551/how-to-keep-the-same-mac-address-after-consecutive-build-and-flash-operations" /><item><title>RE: How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/thread/556285?ContentTypeID=1</link><pubDate>Thu, 04 Dec 2025 20:25:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95b0cafe-2078-487d-9b40-4fc90f272323</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;It will be erased.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/thread/556277?ContentTypeID=1</link><pubDate>Thu, 04 Dec 2025 17:39:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec06954a-21d6-47cc-ac1a-b6b3ad1b1995</guid><dc:creator>gc0rreiab</dc:creator><description>&lt;p&gt;What is the expected behavior if the flash memory is erased in the middle of a flashing operation? For example, what happens when I use the Erase Board function while an nRF54L15 DK is connected to my laptop? Will the persistent&amp;nbsp;IEEE 802.15.4 Extended Address be erased and regenerated?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/thread/554168?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2025 16:34:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f57baf3-38aa-4b15-bdfa-7d8e1a47dc3b</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;That&amp;#39;s correct.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/thread/554098?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2025 11:06:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ea943e8-c698-448e-91bc-2354ab5c4a4f</guid><dc:creator>gc0rreiab</dc:creator><description>&lt;p&gt;If I understand correctly, the IEEE EUI-64 address is a globally unique identifier assigned by the IEEE Registration Authority and consists of a 24-bit Organizationally Unique Identifier (OUI) and a 40-bit unique extension. Nordic Semiconductor likely purchases a block of these addresses and programs one unique EUI-64 into each nRF54x device during manufacturing.&lt;/p&gt;
&lt;p&gt;The IEEE 802.15.4 extended address, on the other hand, is a 64-bit MAC address used in IEEE 802.15.4 networks (such as Thread or Zigbee) and it is typically derived from the EUI-64 either by hardware or during software stack initialization. This means the &lt;span&gt;IEEE 802.15.4&lt;/span&gt;&amp;nbsp;extended address can change between resets or reinitializations unless it is explicitly stored and made persistent?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to keep the same MAC address after consecutive build and flash operations</title><link>https://devzone.nordicsemi.com/thread/554017?ContentTypeID=1</link><pubDate>Tue, 11 Nov 2025 18:24:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d1a5837-3c6b-484d-a7de-c0e77962c58d</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you mean the&amp;nbsp;&lt;span&gt;IEEE 802.15.4 extended address or the IEEE EUI-64 address? Check&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/98646/extended-address-of-sed-changed-abruptly/420003"&gt;this post&lt;/a&gt;.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;otLinkGetExtendedAddress() function would gets the IEEE 802.15.4 Extended Address.&amp;nbsp;&lt;span&gt;It could be that you are not &lt;a href="https://github.com/nrfconnect/sdk-nrfxlib/blob/v3.1.1/openthread/include/openthread/link.h#L556-L569"&gt;setting the extended address&lt;/a&gt; persistent, so it is changed upon reset/flash.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Amanda H.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>