ble advdata set deprecation problem

RE: ble advdata set deprecation problem

Vidar Berg — Mon, 12 Jun 2023 06:47:55 GMT

Hi,

This explains why you have been getting the size error. I just assumed you were advertising with a single UUID. With legacy advertising, you can include up to 31 bytes in the advertisement and scan response packets. Therefore, you either have to place the manufacturer field in the advertisement packet or consider including fewer UUIDs in the scan response.

RE: ble advdata set deprecation problem

kenyon — Mon, 12 Jun 2023 06:09:24 GMT

hi Vidar Berg.
I tried to block those two pieces of code. It is found that there is no data_size overflow problem, And I tested that the uuid takes 26 bytes, so is there any way to broadcast more data in the app? Same as herreraVanHalen below.

RE: ble advdata set deprecation problem

HerreraVanHalen — Sat, 10 Jun 2023 19:35:55 GMT

Hello everyone!

I have the same problem with ble_advertising_advdata_update() function, I comment the 2 lines that you suggest:

//scanrsp.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
//scanrsp.uuids_complete.p_uuids = m_adv_uuids;

With this modification, the project works, and the manufacturer specific data is updated, but I need broadcast parameters (device name,UUID service) to filter devices in my app (Central).

How can I do that?

thank you!

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 12:02:15 GMT

So p_offset was 26? The question then is what is taking up 26 bytes. The scan response should only include the UUID and manufacturer field. As a test, can you try to comment these 2 lines in your update function:

scanrsp.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
scanrsp.uuids_complete.p_uuids = m_adv_uuids;

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 09:54:15 GMT

data_size = 0x06;
max_size = 0x1F.

I calculated that the left side is 0X20 which exceeds the max size

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 09:48:41 GMT

Thanks. Now, can you check what the value of 'data_size' and 'max_size' is?

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 09:46:25 GMT

hi vidar berg.
I'm sorry I didn't get what you meant. My final debugging result is that an error occurred here.

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 09:18:19 GMT

You need to place the breakpoint(s) inside the ble_advertising_advdata_update() function to figure out where the error was raised.

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 09:16:50 GMT

hi.i didn't change your code,i debug and use breakpoints.0x0c means NRF_ERROR_DATA_SIZE ,right?

Eventually he will jump to the app error fault handler

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 08:29:14 GMT

Hi,

Please use breakpoints in ble_advertising_advdata_update() to find out if NRF_ERROR_DATA_SIZE is returned when encoding the advertising or the scan response payload. Also, did you make any changes to the code I made?

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 07:48:14 GMT

hi vidar berg.

I turned off the crc check and went to debug. err_code = ble_advertising_advdata_update(&m_advertising, &adv, &scanrsp);

APP_ERROR_CHECK(err_code);
With the breakpoint hit, err_code returns the NRF_ERROR_DATA_SIZE error

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 06:54:19 GMT

The settings.hex file is only for the inital programming of the device. The bootloader will take care of updating the settings page when updating through DFU.

To disable boot validation, you can include ''--app-boot-validation NO_VALIDATION" in your nrfutil settings generate command.

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 06:49:57 GMT

'The settings page includes the expected CRC value of the application.'
Can this be turned off? If yes, how should it be turned off? After it is turned off, does setting.hex need not be updated with application update?
After doing this, I test the broadcast data to see if it is normal.

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 06:44:53 GMT

Yes, when the bootloader fails to boot the application, it usually means that the bootloader settings page is either not programmed or programmed with incorrect settings. The settings page includes the expected CRC value of the application, which is used for boot validation.

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 06:36:00 GMT

Oh yes, I haven't changed the bootloader part in a long time. It's just that setting.hex is updated as the application is updated. Does this operation have anything to do with my failure to enter the application?

RE: ble advdata set deprecation problem

Vidar Berg — Fri, 09 Jun 2023 06:19:00 GMT

This indicates that the Boot validation of the application failed, or have you updated the Bootloader settings page so it matches the new application?

RE: ble advdata set deprecation problem

kenyon — Fri, 09 Jun 2023 02:17:24 GMT

According to my debugging situation on keil5, it stays in the bootloader and not run into the application, set the breakpoint and did not run to it.(ㄒoㄒ)

RE: ble advdata set deprecation problem

Vidar Berg — Thu, 08 Jun 2023 12:43:02 GMT

Could it be that the APP_ERROR_CHECK() check at the end is failing? Will your app reset into bootloader dfu mode if an assert is raised?

RE: ble advdata set deprecation problem

kenyon — Thu, 08 Jun 2023 12:41:15 GMT

It's very strange. After I update, when it runs to LL_BLE_SetAdManu, it will enter the bootloader mode！

RE: ble advdata set deprecation problem

Vidar Berg — Thu, 08 Jun 2023 12:14:56 GMT

Hi,

LL_BLE_SetAdManu() will replace your original advertisement payload so it only includes the manufacturer field in the scan response.If you want to keep the original data, then you have to populate the ble_advdata_t fields again with the same values used in advertising_init()

void LL_BLE_SetAdManu(unsigned short manu)
{
    uint32_t err_code;
    static unsigned char spec_data[4];

    ble_advdata_manuf_data_t manufacturer_data;

    ble_advdata_t scanrsp;
    ble_advdata_t adv;

    memset(&scanrsp, 0, sizeof(scanrsp));
    
    scanrsp.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    scanrsp.uuids_complete.p_uuids  = m_adv_uuids;

    memset(&adv, 0, sizeof(adv));

    adv.name_type = BLE_ADVDATA_FULL_NAME;
    adv.include_appearance = true;
    adv.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

    // 4 bytes version info
    spec_data[0] = 0;
    spec_data[1] = 1;
    spec_data[2] = (unsigned char) ((0x3f15 & 0xFF00) >> 8);
    spec_data[3] = (unsigned char) ((0x3f15 & 0x00FF) >> 0);

    manufacturer_data.company_identifier = manu;
    manufacturer_data.data.p_data = spec_data;
    manufacturer_data.data.size   = sizeof(spec_data);
			
    scanrsp.p_manuf_specific_data = &manufacturer_data;
 
    //ble_advdata_set(0, &scanrsp); 
    err_code = ble_advertising_advdata_update(&m_advertising, &adv, &scanrsp);
    APP_ERROR_CHECK(err_code);
}

RE: ble advdata set deprecation problem

kenyon — Thu, 08 Jun 2023 12:00:11 GMT

hi,Vidar Berg.
I modified LL_BLE_MANU according to your instructions. After the changes, I can see the updated manu_data on ios. But the service information was missing from the broadcast data.
Also, I couldn't find the device on nrf connect on Android. This is a very strange phenomenon.

RE: ble advdata set deprecation problem

Vidar Berg — Thu, 08 Jun 2023 11:35:56 GMT

Hi,

I guess p_manuf_specific_data is a NULL pointer since the updated manuf. field is not encoded into the adv. payload and you don't get any errors.

Try this:

void LL_BLE_SetAdManu(unsigned short manu)
{
    static unsigned char spec_data[4];
    
    ble_advdata_manuf_data_t manufacturer_data;

    // 4 bytes version info
    spec_data[0] = 0;
    spec_data[1] = 1;
    spec_data[2] = (unsigned char) ((0x3f15 & 0xFF00) >> 8);
    spec_data[3] = (unsigned char) ((0x3f15 & 0x00FF) >> 0);
		
    manufacturer_data.company_identifier = manu;
    manufacturer_data.data.p_data = spec_data;
    manufacturer_data.data.size   = sizeof(spec_data);
			
    scanrsp.p_manuf_specific_data = &manufacturer_data;
    
	err_code1 = ble_advertising_advdata_update(&m_advertising, NULL, &scanrsp);
}

RE: ble advdata set deprecation problem

kenyon — Thu, 08 Jun 2023 10:02:49 GMT

hi Vidar Berg.
i tried to use the ble_advertising_advdata_update() .But it doesn't seem to work that well.
When I use this function in my program, I don't see any broadcast messages in nrf connect.The difference can be seen in the scanner.It looks as if the broadcast parameters were turned off directly after the adv parameter was updated.

i simplified the flow of the code so that you can help me analyze the problem more easily.

ble_advdata_t advdata;
ble_advdata_t scanrsp;
ble_advdata_manuf_data_t    m_manuf_specific_data;

int main(void)
{
    advertising_init();
    advertising_start();
    
    while(1)
    {
        if(button_press){
            LL_BLE_SetAdManu(0x0101);
        }
    }
}
static unsigned char spec_data[4 + BLE_DEVICE_ADDR_LEN]; // 4 bytes version info, BLE_DEVICE_ADDR_LEN bytes ID of paired app
/**@brief Function for starting advertising.
 */
void advertising_start(void)
{
    uint32_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
    APP_ERROR_CHECK(err_code);
}

uint32_t   err_code1;
/**@brief Function for updating advertising.
 */
void LL_BLE_SetAdManu(unsigned short manu)
{
    static unsigned char spec_data[4];

    // 4 bytes version info
    spec_data[0] = 0;
    spec_data[1] = 1;
    spec_data[2] = (unsigned char) ((0x3f15 & 0xFF00) >> 8);
    spec_data[3] = (unsigned char) ((0x3f15 & 0x00FF) >> 0);
		
	scanrsp.p_manuf_specific_data->data.p_data = spec_data;		
	scanrsp.p_manuf_specific_data->data.size = sizeof(spec_data);		
    scanrsp.p_manuf_specific_data->company_identifier = manu;
    //ble_advdata_set(0, &scanrsp); 
	err_code1 = ble_advertising_advdata_update(&m_advertising, NULL, &scanrsp);
}

/**@brief Function for initializing the Advertising functionality.
 */
static void advertising_init(void)
{
    uint32_t               err_code;
    ble_advertising_init_t init;

    memset(&init, 0, sizeof(init));
	
    m_manuf_specific_data.company_identifier = 0x0000;
	
	init.srdata.p_manuf_specific_data = &m_manuf_specific_data;
		
    init.advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance = true;
    init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

    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 = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
    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);
}

I read err_code1 = ble_advertising_advdata_update(&m_advertising, NULL, &scanrsp); The err_code1 value returned by the function is 0x0000. That means the update was successful, right?
So can you help me figure out what went wrong？

Thanks a lot！

RE: ble advdata set deprecation problem

Vidar Berg — Wed, 07 Jun 2023 11:10:04 GMT

Hello,

The Softdevice advertising API was overhauled in v6.x to accommodate the new advertisement features introduced in Bluetooth 5. The easiest way to update the adv. payload now is to use the ble_advertising_advdata_update() function from the Advertising Module.

You may also want to have a look at this tutorial:

How to update advertising data dynamically using BLE Advertising library

Best regards,

Vidar

RE: ble advdata set deprecation problem

kenyon — Wed, 07 Jun 2023 03:00:29 GMT

In particular, our device needs to update the adv data every time it connects to the app. Therefore, this function ble_advdata_set should be used frequently.