Set Advertiser Address to 1 in Extended Header Flags and define Advertiser Addresshttps://devzone.nordicsemi.com/f/nordic-q-a/84482/set-advertiser-address-to-1-in-extended-header-flags-and-define-advertiser-addressUsing NordicSDK 1.6.1 and the following in the bt_le_adv_param and relevant settings in prj.conf The secondary advertising data packet contains the advertiser address but the primary advertising packet does not (Extended header flags= 0x18). Ien-USTelligent Community 13Thu, 10 Feb 2022 16:17:19 GMTRE: Set Advertiser Address to 1 in Extended Header Flags and define Advertiser Addresshttps://devzone.nordicsemi.com/thread/352417?ContentTypeID=1Thu, 10 Feb 2022 16:17:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4f078579-d4b4-430a-bc21-2d01ad843d46Mttrinh<p>Hi,&nbsp;</p> <p>The Bluetooth specification defines where it is allowed to put the advertiser address. In most cases it is not allowed to put the advertiser address when the primary PHY is Coded. I would suggest taking a look at the tables in <a href="https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=521059" rel="noopener noreferrer" target="_blank">Core v5.3, Vol 6, Part B, Section 2.3.1.5 and 2.3.1.6.</a>&nbsp;The SoftDevice Controller will put the address in the primary channel (ADV_EXT_IND) if it is allowed by spec.</p><div style="clear:both;"></div>