NRF52832 16 bit service UUID and 128 bit characteristic UUID

[omerKayten]

Hello everyone,

We want to program the other NRF52832 chip from the NRF52832 chip via OTA. The DFU service UUID is 16 bits (0xfe59). However, the characteristic UUIDs are 128 bits. We are having problems in the process of discovering them. Both service and characteristic UUIDs are 128-bit or 16-bit, no problem. But when one is 16 bits and the other is 128 bits, we cannot perform the discover operation.
Is there a solution for this? Or is there a sample project?

[Einar Thorsrud]

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

[omerKayten]

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.

[Einar Thorsrud]

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 (ble_app_uart_with_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.

[omerKayten]

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.

 

[Einar Thorsrud]

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?