Secure DFU from s130/s132

RE: Secure DFU from s130/s132

braymond — Tue, 08 Sep 2020 12:37:06 GMT

Hi all,

I faced the same issue on my project. The DFU characteristics uuid returned by the db discovery were always 0x0000. I was able to solve it by registering the DFU service to the BLE stack before initiating the db discovery. This way, the BLE stack knows this custom service and can bisect it. At least, that is my understanding.

Hope this could help others.

Ben

uint32_t ble_dfu_init (ble_dfu_t * p_dfu, ble_dfu_evt_handler_t evt_handler)
{
    uint32_t        err_code;
    ble_uuid_t      service_uuid;
    ble_uuid128_t   nordic_base_uuid = { 0x50, 0xEA, 0xDA, 0x30, 0x88, 0x83, 0xB8, 0x9F,
                                         0x60, 0x4F, 0x15, 0xF3, 0x00, 0x00, 0xC9, 0x8E };

    VERIFY_PARAM_NOT_NULL(p_dfu);

    // Initialize the service structure
    p_dfu->conn_handle                  = BLE_CONN_HANDLE_INVALID;
    p_dfu->evt_handler                  = evt_handler;

    BLE_UUID_BLE_ASSIGN(service_uuid, BLE_DFU_SERVICE_UUID);

    // Add proprietary service
    err_code = sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY,
                                        &service_uuid,
                                        &(p_dfu->service_handle));
    VERIFY_SUCCESS(err_code);

    // Add vendor specific UUID to use with the DFU characteristic
    err_code = sd_ble_uuid_vs_add(&nordic_base_uuid, &p_dfu->uuid_type);
    VERIFY_SUCCESS(err_code);

    return (NRF_SUCCESS);
}

RE: Secure DFU from s130/s132

bama — Mon, 26 Feb 2018 14:29:59 GMT

Hi Elias, is there the possibiliy that you could share your DFU-Central source code?

RE: Secure DFU from s130/s132

Gili Elias — Sun, 30 Apr 2017 05:48:04 GMT

Hi Bjorn, any update on this issue?

RE: Secure DFU from s130/s132

Gili Elias — Thu, 20 Apr 2017 08:22:09 GMT

Unfortunately, I can't share the project at the moment. Is there any other specific part of code you'd like to see?

How do I read the 128bit of the discovered characteristics? The ble_gattc_char_t struct that is passed to the event handler has only 16bit (or octets 12-13 of 128-bit UUID), but as I said, both handles has 0 in this parameter.

For now, the only way I've managed to bypass this issue is to hard code char[0] as the packet handle and char[1] as the control point (I based this on the properties values). Obviously this is not ideal.

RE: Secure DFU from s130/s132

bjorn-spockeli — Wed, 19 Apr 2017 14:55:03 GMT

No, both the DFU Packet and DFU Control Point characteristics should have different 128-bit UUIDs. Would it be possible for you to share the project either here on DevZone or Mypage?