https://devzone.nordicsemi.com/f/nordic-q-a/13877/radio-device-addressHello, is there a trick, how the Radio peripherals device address match feature could be used to implement those advertising filter policies that filters based on the PDU type. BLE defines 4 different advertising filter policies, from which are 2en-USTelligent Community 13Mon, 23 May 2016 09:13:14 GMThttps://devzone.nordicsemi.com/thread/53002?ContentTypeID=1Mon, 23 May 2016 09:13:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:58a28024-4447-4632-b504-5de6d5a35806Torsten Robitzki<p>Hi, thank you for your response and thank your for your tipp with the AAR. Crypto is out of focus in my project (for now). I understand your answer so, that there is no hardware support to implement the 3rd and 4th Advertising Filter Policy (BLE Code 4.2 / Vol.6; part B 4.3.2).</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/53001?ContentTypeID=1Fri, 20 May 2016 07:22:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8dc389f6-93d0-49f6-8c35-3c3ea54444e5run_ar<p>The Device address match feature will only check the address against the registers and set a bit if there is a match. So the filter policy will have to be handled in the radio interrupt.</p> <p>I assume you are already aware that you should also use the AAR in addition to the device address match, where the AAR is used for resolvable addresses (so if you get a device address match you simply stopp the AAR, if you don&#39;t get a address match you wait for the result of the AAR as well). In both cases the filter policies will have to be handled in firmware.</p><div style="clear:both;"></div>