Reading out MAC address via NRFJPROG &quot;seems&quot; to output one wrong bytehttps://devzone.nordicsemi.com/f/nordic-q-a/102547/reading-out-mac-address-via-nrfjprog-seems-to-output-one-wrong-byteFollowing on from I tried this out, on both a NRF52840 DK and on our NRF5340 product. On the 52 DK I get the following which is &quot;correct&quot; as it matches the advertised MAC address in nRF Connect Android app. 0x100000A4: 283E7B77 B0C8CF3E |w{&gt;(&gt;...en-USTelligent Community 13Fri, 04 Aug 2023 09:29:19 GMTRE: Reading out MAC address via NRFJPROG "seems" to output one wrong bytehttps://devzone.nordicsemi.com/thread/439866?ContentTypeID=1Fri, 04 Aug 2023 09:29:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2ef858ce-42c7-4b4e-86e8-252d84185669Hieu<p>Hi Matthew,</p> <p>The reason for the difference between the DEVICEADDR registers and the actual Bluetooth address is explained in this DevZone question:</p> <p>&nbsp;<a href="https://devzone.nordicsemi.com/f/nordic-q-a/10758/why-is-hardware-address-of-bluetooth-device-different-than-device-address">Why is Hardware Address of Bluetooth Device different than Device Address.</a>&nbsp;</p> <p>Hieu</p><div style="clear:both;"></div>