NRF52832 16 bit service UUID and 128 bit characteristic UUID

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

Einar Thorsrud — Thu, 07 Feb 2019 13:31:02 GMT

Hi,

The issue is caused by a missing call to sd_ble_uuid_vs_add(). The problem is fixed by adding it back and adjusting it so that you add the base you are actually testing with, which is BLE_NORDIC_VENDOR_BASE_UUID for the DFU service.

In practice, you just have to modify your ble_lbs_c.c function by including ble_dfu.h and add the following snippet in your modified ble_lbs_c_init():

    ble_uuid128_t lbs_base_uuid = BLE_NORDIC_VENDOR_BASE_UUID; // Instead of LBS_UUID_BASE in your test setup

    err_code = sd_ble_uuid_vs_add(&lbs_base_uuid, &p_ble_lbs_c->uuid_type);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
    VERIFY_SUCCESS(err_code);

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

omerKayten — Thu, 07 Feb 2019 07:41:16 GMT

devzone.nordicsemi.com/.../ble_5F00_lbs_5F00_c.c devzone.nordicsemi.com/.../ble_5F00_lbs_5F00_c.h devzone.nordicsemi.com/.../5023.main.cCentral example: ble_app_blinky_c
Peripheral example: secure_bootloader (We didn't use the one in this SDK.
any nRF5_SDK_15.0.0_a53641a \ examples \ dfu \ secure_bootloader \ pca10040_ble instance can be installed.))

Central connects to the peripheral mac address.

ble_lbs_on_db_disc_evt enters this event after the connection is established. However, this function does not match the uuid_type first.
I removed that requirement. Then, after removing this requirement, the value of p_evt-> params.discovered_db.char_count is 2.
But the characteristic UUIDs are always 00. It always enters the default state. The characterisc UUIDs do not appear correctly.

The files I modified in ble_app_blinky_c are as follows.

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

Einar Thorsrud — Tue, 05 Feb 2019 09:00:53 GMT

Can you upload your two projects so I can see what you have done and test on my side? (You can open a private case and refer to this thread if you don't want to share your code with the community).

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

omerKayten — Mon, 04 Feb 2019 10:26:14 GMT

Yes, exactly.

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

Einar Thorsrud — Mon, 04 Feb 2019 09:56:28 GMT

OK, now I am closer to understanding. From the screenshot it seems you have added a 128 bit characteristic to a 16 bit service and that is working and you are able to do service discovery from nRF Connect. So the problem is not with the peripheral side, but that you are having problems discovering this from a nRF central?

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

omerKayten — Mon, 04 Feb 2019 09:39:24 GMT

I guess i couldn't explain my problem well. We can't discover service and characteristic when our service has 16 bit UUID and its characteristic has 128 bit UUID.

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

Einar Thorsrud — Mon, 04 Feb 2019 09:14:51 GMT

Hi,

Ah, yes perhaps there are no examples which as both, but that is very common, and I have never seen any problems with it.

I added the Device Information Service to the NUS example so that you can verify on your side as well that it works without any problems. Just drop the attached example (devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_with_5F00_dis.zip) project in the BLE peripherals folder in SDK 15.2 and build it with SES. If you have problems discovering both the DIS and NUS service from this example, then I would investigate the central side.

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

omerKayten — Mon, 04 Feb 2019 06:15:38 GMT

In example,If the service UUID is 16 bit, the characteristic UUIDs are 16 bits.

If the service UUID is 128 bit, the characteristic UUIDs are 128 bits.

There is no sample project where service uuid is 16 bits and the characteristic UUID is 128 bits. We would like to program the NRF to NRF by discovering the DFU service and its characteristics.

Can you please help?

Good luck with.

RE: NRF52832 16 bit service UUID and 128 bit characteristic UUID

Einar Thorsrud — Fri, 01 Feb 2019 12:56:01 GMT

Hi,

You can find several SDK examples which combine 16 bit and 128 bit UUIDs, for instance the NUS (BLE UART) examples. Are you shore this is the problem?

What do you mean by " we cannot perform the discover operation"? Are you doing service discovery from the nRF or is it the peer doing service discovery? In what way does it not work?

Br,

Einar