Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

SOME/IP Wire Format: Byte Layout

Pythonsomeip_serialise.py
import struct

# SOME/IP serialisation: big-endian (network byte order) by default per PRS_SOMEIP_00077
# Data types: uint8/16/32/64, sint8/16/32/64, float32/64, string (4B length + UTF-8), array (4B length + elements)

class SomeIpSerializer:
    def __init__(self):
        self.buf = bytearray()

    def write_uint8(self, v):   self.buf += struct.pack(">B", v)
    def write_uint16(self, v):  self.buf += struct.pack(">H", v)
    def write_uint32(self, v):  self.buf += struct.pack(">I", v)
    def write_float32(self, v): self.buf += struct.pack(">f", v)

    def write_string(self, s: str):
        encoded = s.encode("utf-8")
        self.buf += struct.pack(">I", len(encoded))  # 4-byte length prefix
        self.buf += encoded

    def write_array_uint16(self, arr):
        self.buf += struct.pack(">I", len(arr) * 2)  # 4-byte length prefix in bytes
        for v in arr: self.write_uint16(v)

    def bytes(self): return bytes(self.buf)

# Example: serialise a VehicleData struct
ser = SomeIpSerializer()
ser.write_float32(100.0)   # speed_kmh
ser.write_uint8(3)          # gear
ser.write_string("ECU_01")  # ecu_name
print(f"Serialised: {ser.bytes().hex()}")
# → 42c80000 (100.0f) 03 (gear) 00000006 (len=6) 454355_3031 (ECU_01)

AUTOSAR Transformer Chain

AUTOSAR Classic Transformer Chain
  COM signal (AUTOSAR internal)
        │
        ▼
  SOME/IP Transformer
  (I-Signal → SOME/IP wire format, big-endian, length prefix)
        │
        ▼
  E2E Transformer (optional)
  (append CRC + counter to payload)
        │
        ▼
  SoAd (Socket Adaptor)
  (wrap in UDP/TCP socket)
        │
        ▼
  EthIf → Eth MAC → 100BASE-T1 wire
XMLSomeIp_Transformer_Config.arxml


  SomeIpProps_VehicleSpeed
  MOST-SIGNIFICANT-BYTE-FIRST  
  1
  NOTIFICATION
  4  

Endianness Per-Field Override

Field TypeDefaultOverride Use CaseConfig
uint16, uint32Big-endian (network order)Interfacing with legacy CAN signal (little-endian)SomeipDataPrototype.byteOrder = MOST-SIGNIFICANT-BYTE-LAST
float32Big-endianSensor data from Cortex-M (little-endian native)Per-field override in SomeipTransformationProps
StructPer-fieldMixed-endian struct: some big, some littleEach field has independent byteOrder setting

Deserialization Error Handling

Error ConditionDetectionAUTOSAR Action
Length field mismatch (array longer than message)SomeipTp reassembly checkDESERIALIZATION_FAILED → message dropped; DEM event logged
Array element count > MAX_ELEMENTSApplication-layer validationError code returned to caller; event dropped
Malformed UTF-8 stringString decoderError code; string replaced with empty or error marker
E2E CRC/counter failureE2E TransformerE2E_STATUS_ERROR → ProxyEvent enters Error state; GetSubscriptionState() returns ERROR
Session ID not incrementingApplication monitoringIndicates TCP socket reconnection or server restart — trigger reconnect

Summary

SOME/IP serialisation follows a simple rule: big-endian by default, 4-byte length prefix for dynamic types (strings, arrays), struct fields in declaration order. Per-field endianness overrides are needed when bridging SOME/IP to legacy CAN signals. Deserialization errors must be handled gracefully — the most critical is E2E failure, which signals a potential data integrity problem and must trigger a safe-state response in safety-relevant applications.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousEvents, Methods, and FieldsNext →SOME/IP-TP for Large Payloads