Endianness & Data Serialization - Embedded C/C++ for Automotive

Big-Endian vs Little-Endian

32-bit Value 0x12345678 in Memory

  Little-Endian (e.g., Aurix TriCore, ARM Cortex-M):
  Address:  +0    +1    +2    +3
  Memory:  [0x78][0x56][0x34][0x12]   ← LSB at lowest address

  Big-Endian (e.g., Motorola 68K, network byte order):
  Address:  +0    +1    +2    +3
  Memory:  [0x12][0x34][0x56][0x78]   ← MSB at lowest address

  CAN signal byte orders:
  Intel format (little-endian): start bit is LSB position in byte stream
  Motorola format (big-endian):  start bit is MSB position in byte stream

  Impact: a uint32_t g_value = 0x12345678 read as bytes[0..3] gives:
  Aurix (LE): bytes = {0x78, 0x56, 0x34, 0x12}
  M68K  (BE): bytes = {0x12, 0x34, 0x56, 0x78}
  → cross-platform communication MUST explicitly specify byte order

Portable Data Serialisation

Cserialization.c

#include 

/* Portable big-endian serialisation (network byte order) */
/* Works correctly regardless of host endianness */

/* Encode uint32 into 4 bytes, big-endian (MSB first) */
void encode_u32_be(uint8_t *buf, uint32_t val)
{
    buf[0] = (uint8_t)((val >> 24u) & 0xFFu);
    buf[1] = (uint8_t)((val >> 16u) & 0xFFu);
    buf[2] = (uint8_t)((val >>  8u) & 0xFFu);
    buf[3] = (uint8_t)((val >>  0u) & 0xFFu);
}

/* Decode uint32 from 4 bytes, big-endian */
uint32_t decode_u32_be(const uint8_t *buf)
{
    return ((uint32_t)buf[0] << 24u)
         | ((uint32_t)buf[1] << 16u)
         | ((uint32_t)buf[2] <<  8u)
         | ((uint32_t)buf[3]);
}

/* Little-endian variants (for AUTOSAR/UDS data that uses LE) */
void encode_u16_le(uint8_t *buf, uint16_t val)
{
    buf[0] = (uint8_t)(val & 0xFFu);
    buf[1] = (uint8_t)((val >> 8u) & 0xFFu);
}

uint16_t decode_u16_le(const uint8_t *buf)
{
    return (uint16_t)(buf[0] | ((uint16_t)buf[1] << 8u));
}

/* Byte swap macros using GCC built-ins (compile to single SWAP instruction) */
#define BSWAP16(x)  __builtin_bswap16(x)
#define BSWAP32(x)  __builtin_bswap32(x)
#define BSWAP64(x)  __builtin_bswap64(x)

CAN Signal Byte Order (Intel vs Motorola)

Ccan_signals.c

#include 

/* J1939 / DBC: engine speed signal
   Motorola format (big-endian), start bit 24, length 16, factor 0.25 rpm/bit
   CAN data bytes: [0][1][2][3][4][5][6][7]
   Engine speed occupies bytes [3][4] = data[3]:data[4] */

float decode_engine_speed_motorola(const uint8_t *data)
{
    /* Motorola: start bit = MSB position; reconstruct MSB-first */
    uint16_t raw = ((uint16_t)data[3] << 8u) | (uint16_t)data[4];
    return (float)raw * 0.25f;   /* physical = raw × factor */
}

/* Intel (little-endian) signal: vehicle speed
   Intel format, start bit 16 (byte 2 bit 0), length 16 */
float decode_vehicle_speed_intel(const uint8_t *data)
{
    /* Intel: start bit = LSB; reconstruct LSB-first */
    uint16_t raw = (uint16_t)data[2] | ((uint16_t)data[3] << 8u);
    return (float)raw * 0.00390625f;  /* 1/256 km/h per bit */
}

/* Encoding: reverse the decode process */
void encode_engine_speed_motorola(uint8_t *data, float rpm)
{
    uint16_t raw = (uint16_t)(rpm / 0.25f);
    data[3] = (uint8_t)((raw >> 8u) & 0xFFu);
    data[4] = (uint8_t)(raw & 0xFFu);
}

Summary

Endianness bugs are among the most insidious in automotive software: the code compiles and runs without error, but numerical values are silently wrong. The safe approach is always explicit serialisation (shift-and-mask byte-by-byte) rather than casting a uint32_t pointer to uint8_t* — the latter relies on host endianness and violates MISRA Rule 11.3 (strict aliasing). CAN signal byte order (Intel vs Motorola in DBC files) is a separate concept from CPU endianness and must be decoded according to the database specification, not assumed.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.