128-bit UUID byte swap problem

[kerem]

I'm implementing a custom service with one characteristic and 128-bit UUID.

I am able to set the custom base UUID using sd_ble_uuid_vs_add() but the resulting bytes look swapped in nRF MCP Android application. This is on Softdevice 7.0.0 and SDK 6.1.0.

#define BASE_UUID {0xAB, 0xCD, .., 0x12, 0x34}

the resulting UUID I see is first and last 2 octets swapped, also within themselves like this;

{0x34, 0x12, .., 0xCD, 0xAB}

All the octets in between these 4 are fine.

Any idea what could cause this behavior?

EDIT Attaching screenshot from Android MCP:

[RK]

There's nothing wrong with that, the bytes are little-endian and the number is displayed in the MCP as a big-endian number.

You say all the octets between those are fine ... well all the octets between those are all 0x00 so you wouldn't be able to tell which order they were in.

Why are they all zero by the way, it's probably a legal UUID but certainly not one you randomly generated.

[RK]

It's just a corollory of the BTLE spec. Each parameter is transferred little-endian and the way it's specified in the code is in the order the data is going to be transmitted, so least significant byte first. That saves I suppose, the softdevice having to flip it all around before storing it/sending it. The conventional way for humans to look at UUIDs however is big-endian in groups with dashes.

It's quite easy to look at UUIDs in the MCP or other place they're displayed and not even think about the order they were specified in code originally, seems that this particular time you did look closely and saw it, but it will have been that way forever.