ble name for OTA buttonless dfu

RE: ble name for OTA buttonless dfu

Susheel Nuguru — Fri, 26 Jan 2024 11:03:21 GMT

[quote user="AndrewDF"]The architecture is as follows: a NRF52840 that uses multiprotocol (zigbee and ble) and a NRF52811 that was intended to be the primary ble interface. These chips share data via UART. Both chips now use butonless dfu for OTA updates. Which means there are now two ble advertisers[/quote]

If you want to do a DFU via only one chip and do not want to display the advertiser name of the other then it should be possible. Which SDK version are you using? The advertiser do not need to contain the name of the device, so at the time of DFU, you can communicate to the other core to advertise info other than device name.

in nRF5SDK

you can have something like below

static void advertising_init(void)
{
    uint32_t      err_code;
    ble_advdata_t advdata;
    uint8_t       flags = BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED;

    ble_advdata_manuf_data_t manuf_specific_data;

    manuf_specific_data.company_identifier = APP_COMPANY_IDENTIFIER;

    manuf_specific_data.data.p_data = (uint8_t *) m_beacon_info;
    manuf_specific_data.data.size   = APP_BEACON_INFO_LENGTH;

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

    advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;

    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = NON_CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = 0;       // Never time out.

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);
}

In our NCS

you just do not populate the advertising or response data with the name when calling bt_le_adv_start

RE: ble name for OTA buttonless dfu

AndrewDF — Tue, 23 Jan 2024 21:30:24 GMT

The architecture is as follows: a NRF52840 that uses multiprotocol (zigbee and ble) and a NRF52811 that was intended to be the primary ble interface. These chips share data via UART. Both chips now use butonless dfu for OTA updates. Which means there are now two ble advertisers. The 52811 functions as both the address to use the DFU and its primary function. The addition of softdevice 140 to 52840 adds an additional ble name that I would like to be hidden, exposed only to the DFU updater.

RE: ble name for OTA buttonless dfu

Susheel Nuguru — Tue, 23 Jan 2024 18:12:54 GMT

Hi Andrew,

[quote user=""]I recently added multiprotocol for the other chip so that I can update it via Ble. Ideally I would have the is new ble name be only visible to my app as it will be confusing to the user if there were two products that identified similarly. [/quote]

It is a bit unclear about your architecture based on your limited description. I am also not sure which SDK version you are using, but DFU and running your application do not normally happen at the same time.

Can you show me in the schematics how the two radios? If your product have two cores then will each core be controlling the radio individually? If so you can have a different name for each radio transmission. If I misunderstood your description, then my apologies and I request you to be more descriptive on your setup on how you initiate a firmware update and how your two radios are used and controlled by which core of your product. Also which core will be running Nordic solution based firmware? Assuming there are two cores.