Different byte order in nRF Connect 2.0 iOS App and nRF Connect v3.1.0 for Desktop

[hannes]

In an BLE example I have a characteristic with the value 0x00001234. In the nRF Connect 2.0 for iOS i see the value 0x00001234 and in nRF Connect for Desktop v3.1 i see "34 12 00 00".  Also when I enable Notification the log says "[...] INFO Attribute value changed, handle: 0x12, value (0x): 34-12-00-00" It's always the same example without any changes to the code. Is there a possibility to change the byte order or is this for some reason?

[Bjørn Kvaale]

I believe this is due to little endian vs big endian notation. I will ask internally & get back to you soon.

[hannes]

Yes, I also think so. It's the same as the following code is producing different outputs. But I also think that there should be a possibility to get (or to have) the same output in the moblie app and desktop app. In the case of creating or testing code it's confusing getting 2 different Outputs by the same application...

uint16_t buf_16 = 0x1234;
//producing output 12 34
NRF_LOG_INFO("buf_16 = 0x%X", buf_16);

//producing output 34 12
NRF_LOG_HEXDUMP_INFO(&buf_16, 2);

[Dinesh Harjani]

Hi hannes

Developer for nRF Connect for iOS speaking, here. Thank you very much for filing this bug report, we were able to fix it and put it in our upcoming 2.0.2 bug-fix release, which we expect to have ready by the end of this week or early next week.

Thank you very much for your support !

[hannes]

Thank's for the feedback! Looking forward to the update ;-)