i tried to build the project as big-endian but failed.
the linker complained:
.\out\xxx.axf: error: L6009U: File ..\..\..\..\patch_code\DA14580\obj\atts_task.obj : Endianness mismatch.
looks like the big-endian pacth_code is not there...
Device:
嗨Shuaiwei Yun,
Sorry, i dont fully get the question, the ARM M0 on the 580 has Little Endian architecture, and the patches should also be builded in Little endian.
Thanks MT_dialog
Hi MT_dialog,
i'm working on data exchange between mobile app and da14580 via bluetooth low energy. we expect the data exchanged in the byte order as big endian. we have to swap byte order, if the data stored in da14580 is in little-endian.
as i know, cortex-m0 supports both big-endian and little-endian. keil-mdk provides an option to build project as big-endian as well.
it seems 580 sdk does not support big-endian...
Hi Shuaiwei Yin,
As i ve mentioned the ARM on the 580 is Little Endian and not Big Endian ( In general the M0 supports Big or Little endian but this is defined when the M0 is builded during design and the end user isn't be able to modify that). Regarding the data format on the characteristics, this doesn't depend on the Endianess of the ARM but how the BLE specification defines the format of the characteristics. You will be able to check that in the BLE core specification. In other words you will have to perform on your end application this inversion since even if you could change the endianess of the characteristics you would be violating the BLE specification.
Thanks MT_dialog
非常感谢. ..MT_dialog