Other Parts Discussed in Thread: BLE-STACK
Hi,
I use a CC2652 and my project is based on the multi-role example application of the CC26X2 SDK 2.10.00.44.
In my multi-role BLE application I need non-connectable and non-scannable undirected advertising with (PDU Type=2)/(TxAdd=1)/(RxAdd=0) fields in PDU header:
In my multi-role.c file I defined new parameters for GAP advertising:
#define GAPADV_PARAMS_LEGACY_NONCONN { \ .eventProps = GAP_ADV_PROP_LEGACY, \ .primIntMin = 160, \ .primIntMax = 160, \ .primChanMap = GAP_ADV_CHAN_ALL, \ .peerAddrType = PEER_ADDRTYPE_RANDOM_OR_RANDOM_ID, \ .peerAddr = { 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa }, \ .filterPolicy = GAP_ADV_WL_POLICY_ANY_REQ, \ .txPower = GAP_ADV_TX_POWER_NO_PREFERENCE, \ .primPhy = GAP_ADV_PRIM_PHY_1_MBPS, \ .secPhy = GAP_ADV_SEC_PHY_1_MBPS, \ .sid = 0 \ }
Also, in my multi-role.c file I changed GAP advertising setup in multi_role_advertInit() to use new parameters for advParamLegacy :
static void multi_role_advertInit(void) { uint8_t status = FAILURE; // Setup and start Advertising // For more information, see the GAP section in the User's Guide: // software-dl.ti.com/.../ // Temporary memory for advertising parameters for set #1. These will be copied // by the GapAdv module //GapAdv_params_t advParamLegacy = GAPADV_PARAMS_LEGACY_SCANN_CONN; GapAdv_params_t advParamLegacy = GAPADV_PARAMS_LEGACY_NONCONN; // Create Advertisement set #1 and assign handle GapAdv_create(&multi_role_advCB, &advParamLegacy, &advHandleLegacy);
However, I did not see TxAdd=1 in the air :
What is wrong in my approach ?
Thanks.