This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCE v3 hex430 byteorder puzzle

Hi all,

The hex430 utility used to convert MSP430 COFF executables into various text formats (Intel MCS-86, Motorola-S, TI-Tagged,...) swaps bytes when a 16 bits ROM width is selected. This is the case with most of the output formats I have checked, TI-Txt being the exception.

For instance, if I convert a file test.out into Motorola-S like this:

hex430 -m --order LS -romwidth 16 -o test.s19 test.out

then the sequence ...01 02 03 04... in the .out file will appear as ...02010403... in the .s19 file.

Given that the host computer, the COFF input file and the target platform are all little endian, why is that so?