CODED PHY using the BLE Advertising module - INVALID PARAMS

[Ivan Herrera]

Hi! I'm using S140 and I'm using the ble_advertising module to set up advertising.

This is my advertising_init function which is working properly until I uncomment the enabling of the extended advertising. When executing advertising_start, an INVALID_PARAMS error gets thrown in the sd_ble_gap_adv_set_configure function which by the docs points at an invalid adv_params or adv_data. I've verified through the debugger that in adv_params passed into this function, properties->type is set to 0x06 (BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED).

On first glance it looks a lot like https://devzone.nordicsemi.com/f/nordic-q-a/34543/ble-long-range but seeing how in my case the type is set correctly, I'm at a bit of an ends on how to proceed. I can't seem to step further into the functions to see what part of my adv_params or adv_data is invalid. 

/**@brief Function for initializing the Advertising functionality.
 */
static void advertising_init(uint16_t interval_ms)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;
    memset(&init, 0, sizeof(init));
    NRF_LOG_INFO("Initializing advertising with interval %d", interval_ms);

    init.advdata = get_prox_advdata();
    
    init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.srdata.uuids_complete.p_uuids  = m_adv_uuids;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = MSEC_TO_UNITS(interval_ms, UNIT_0_625_MS);
    init.config.ble_adv_fast_timeout  = 0; //Set advertising to permanent

    //init.config.ble_adv_extended_enabled = true;
    //init.config.ble_adv_primary_phy = BLE_GAP_PHY_CODED;
    //init.config.ble_adv_secondary_phy   = BLE_GAP_PHY_CODED;
   
    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

[Einar Thorsrud]

Hi,

The INVALID_PARAMS error is probably returned from the sd_ble_gap_adv_set_configure() called from ble_advertising_start(). You will get INVALID_PARAMS if you set configure the primary PHY as BLE_GAP_PHY_CODED, and disable advertising extension. This is because it is an illegal configuration which is not allowed by the SoftDevice. So the fix is to enable advertising extensions. (Note that you can use coded PHY on the secondary PHY without extended advertising, but not on the primary PHY.) 

[Ivan Herrera]

Hi! Thanks for your swift response! Yes, I mentioned that in my initial post. The error is coming from adv_set_configure() but it's happening even with GAP_PHY_CODED disabled and adv_extended_enabled set to true, so it's definitely the advertising extensions causing the INVALID_PARAMS error. Is there anything else I need to look for? Does the length of the advertising data change? Do I need to change something in SDK_CONFIG? 

On a different note, I was able to enable coded PHY on the secondary PHY so at least that's working :) 

[Ivan Herrera]

UPDATE: Removing the scan-response data did the trick! Any ideas as to why? (I commented the 2 lines adding the UUID's to the SR). 

[Einar Thorsrud]

Hi,

Thanks for letting us know. That makes sense. It is not legal for extended advertisement packets to be scannable and connectable. You can see this from BLUETOOTH CORE SPECIFICATION Version 5.1 | Vol 6, Part B, Section 2.3.4 Common Extended Advertising Payload Format.