MCUXpresso SDK Documentation
Open on Repo Open an Issue
Source (.md/.rst) Page PDF (.pdf)

Running Passive Entry Scenario with Decision Based Advertising Filtering (DBAF)

Running Passive Entry Scenario with Decision Based Advertising Filtering (DBAF)#

Decision Based Advertising Filtering can be used in the Passive Entry scenario. Using DBAF optimizes the scanning operation performed by the Digital Key Device of the advertisements sent by the Digital Key Car Anchor devices. This is accomplished by using ‘ADV_DECISION_IND’ PDUs, which contain the advertising address in the extended header. Using these PDUs allows the scanner to perform address resolution without the need to retrieve the AUX_ADV_IND PDU sent on the data channels.

The DBAF feature is supported on the following platforms:

  • KW45B41Z-EVK

  • KW47-EVK

  • FRDM-KW43

Enabling DBAF#

To enable DBAF, modify the Digital Key applications as per the steps listed below:

  • In app_preinclude.h file, set gBLE60_DecisionBasedAdvertisingFilteringSupport_d to 1.

Parent topic:Running Passive Entry Scenario with Decision Based Advertising Filtering (DBAF)

Running the Passive Entry with DBAF scenario#

The Passive Entry with DBAF scenario runs after Owner Pairing between a Car Anchor and a Device successfully completes.

  1. To run the Passive Entry with DBAF demo, reset the recently paired boards using either the RST switch or the “reset” command in the shell. Do NOT perform a factory reset, as this removes the bonding information from non-volatile memory.

  2. After reset, run the “sd pe” command on the Car Anchor and “sd pe” command on the Device as shown in Figure 1 and Figure 2.

Passive Entry with DBAF on Device

Figure 1

Passive Entry with DBAF on Car Anchor

Figure 2

After following these steps, the Passive Entry scenario as described in Passive Entry Scenario runs.

Parent topic:Running Passive Entry Scenario with Decision Based Advertising Filtering (DBAF)

Contents