UUID comparison in different endinaess

RE: UUID comparison in different endinaess

Simon — Mon, 27 Jan 2020 13:08:28 GMT

Could you upload your application code? Both the modified ble_app_hrs_c and the peripheral example.

Best regards,

Simon

RE: UUID comparison in different endinaess

Embedded_Engineer — Tue, 21 Jan 2020 10:31:05 GMT

@Simon Any update on this. Please check with ble_app_hrs_c.

RE: UUID comparison in different endinaess

Embedded_Engineer — Tue, 14 Jan 2020 06:38:13 GMT

Hi Simon, Thank you for your assistance. Please make correction, I tested it with ble_app_hrs_c not with uart example ( I took uart example as reference for uuid filtering but implemented it on ble_app_hrs_c ) . Can you check it at your end.

I added the base UUID LSB first ( as you did).

Thank you

RE: UUID comparison in different endiaess

Simon — Mon, 13 Jan 2020 16:14:37 GMT

I was not able to recreate your issue.

Could you try to program respectively ble_app_uart peripheral and ble_app_uart central and see if you are able to connect them? In your peripheral device, how did you add the base UUID? Be aware that they are stored with the LSBits first in memory. E.g. if you are working with the UUID 70786e86-fa13-4a65-ab89-d7b199fd0bc2 (this shows up in nRF Connect app for mobile), you should store the base UUID in the advertising peripheral device as followed:

ble_uuid128_t nus_base_uuid = {{0xC2, 0x0B, 0xFD ..... 0x78, 0x70}} /**< Used vendor specific UUID. */
.
.
err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_nus->uuid_type);

Best regards,

Simon

RE: UUID comparison in different endiaess

Embedded_Engineer — Sat, 11 Jan 2020 03:58:22 GMT

I have implemented current workaround by swapping the entire raw_uuid to match the p_parsed_uuid and the filter matches. But I strongly believe I may have missed something and Nordic would have posted a tested example in its sdk.