error: invalid length in advertising init

RE: error: invalid length in advertising init

Petter Myhre — Fri, 24 Oct 2014 14:10:36 GMT

As @scytulip says, you cannot have more than 31 bytes of data in the advertising packets. He has given you a solution, to use scan request and scan response to obtain additional data.

This and this may also be helpful to you.

RE: error: invalid length in advertising init

sruthiraj koodathil — Mon, 20 Oct 2014 08:39:30 GMT

but i want to advertise battery level as a service....

RE: error: invalid length in advertising init

scytulip — Fri, 17 Oct 2014 15:42:19 GMT

A BLE advertising packet contains at most 31 bytes data. You can try putting some data into the scan response, another 31bytes packet. For instance,

uint32_t      err_code;
ble_advdata_t advdata;
ble_advdata_t scanrsp;

uint8_t       flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

ble_uuid_t adv_uuids[] =
{
    {BLE_UUID_BATTERY_SERVICE,                  BLE_UUID_TYPE_BLE},
    {BLE_UUID_HEART_RATE_SERVICE,               BLE_UUID_TYPE_BLE},
    {BLE_UUID_DEVICE_INFORMATION_SERVICE,       BLE_UUID_TYPE_BLE},
    {BLE_UUID_NUS_SERVICE,                      m_nus.uuid_type}
}; // Too long to fit all in advdata

// Build and set advertising data
memset(&advdata, 0, sizeof(advdata));
memset(&scanrsp, 0, sizeof(scanrsp));

advdata.name_type               = BLE_ADVDATA_FULL_NAME;
advdata.include_appearance      = true;
advdata.flags.size              = sizeof(flags);
advdata.flags.p_data            = &flags;
scanrsp.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
scanrsp.uuids_complete.p_uuids  = adv_uuids;

err_code = ble_advdata_set(&advdata, &scanrsp);
APP_ERROR_CHECK(err_code);

RE: error: invalid length in advertising init

Vebjørn — Fri, 17 Oct 2014 13:28:23 GMT

I'm guessing it's sd_ble_gap_adv_data_set that is throwing the NRF_ERROR_INVALID_LENGTH? I would perhaps try printing both dlen and srdlen before the call to this function to see what they are