Endianess problem

You have identified the problem. To overcome it, fix the code.

I thought the comm data was in Big-Endian order. Are you talking about control and status registers' content?

----------------------------------------------------------------------- "Big-Endian byte order is known as 'normal', 'intuitive', or 'obvious'. Little-Endian is sometimes called 'perverse', 'annoying', 'dysfunctional', or 'stupid'. These designations do not, of course, imply any bias or preference."

Christopher R. Hertel, "Implementing CIFS" 2004

There is also the possibility that the two machines/compilers will allocate bit fields in a different order. Fortunately for me, the Keil 8051 and MSVC86 compilers both allocate bit fields from LS bit up. This only matters if you are hoping to share structure definitions between machines.

In the past I have written alternate forms of struct definitions, with the bitfields appropriately adjusted to align. One machine uses one definition and the other processor uses the other. An #ifdef selected the proper form based on the target.