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.

CCS/TM4C129ENCPDT: Big endian? target endianness? ccxml? gel file?

Part Number: TM4C129ENCPDT

Tool/software: Code Composer Studio

I would like to optimize my firmware by switching to big-endian (network byte) order.

I have an lwIP networking firmware that's working fine in the default little-endian byte order, so it should be a simple matter to rebuild. (?)

I was linking to driverlib.lib, but see that it's compiled for little-endian order. The solution here was simple: remove the linker entry and compile from source instead.

Now I'm getting a warning that my binary can't be loaded because it doesn't match the target endianness, and the dialog refers to the ccxml file. When I look in that file with the CCS editor, no options are seen for endianness, so I can't figure out what to change. In addition, my ccxml refers to a GEL file, ../../emulation/gel/tm4c129encpdt.gel, that doesn't seem to have any endianness settings.

I did a clean build after changing the Properties : CCS General : Tool-chain : Device endianness: big

What else do I need to change?

p.s. I tried scanning the Guidelines and FAQ, but didn't see anything on endianness for the TM4C. Note that a couple of links in the Guidelines are dead links!