pasetti
commented
5 years ago This must be treated as a framework configuration issue because all the functions which might have to perform a byte swap are user-defined. I must therefore add the following constraints:
- If the endianity of the representation in the host computer is different from the endianity in the network representation, then the following functions must be configured to perform byte swaps: (a) all the packet accessor functions, (b) the packet accessor functions in
CrFwPckt.hand (c) thegetDpValueExfunction. - The
getDpValueExfunction may only be used for transferring data from the data pool to a (possibly swapped) network representation
The CORDET Editor has a "byte swap flag" in the configuration of the Packet Code Generator. If the flag is set, then the packet accessor functions perform a byte swap. As long as data in a packet is accessed using the packet accessor functions, consistency is preserved. There are however two problems here:
(1) The packet accessor functions defined at framework level in
CrFwPckt.hdo not have a "byte swap flag"(2) The function
CrPsHkConfigUpdateRepwhich updates the data part of a HK Report calls functiongetDpValueExto perform amemcpyfrom the data pool to the packet and therefore it does not take account of byte ordering.