Contents

Platform services on the smart node / LIN slave

A small LIN node provides identification, configuration and simple health information so its master can integrate and diagnose a local sensor or actuator.

What runs here

On this small MCU or ASIC, platform services are a compact set of configuration handlers and status functions supporting a fixed application. An ASIC may implement these functions in logic rather than software. LIN specifications also use the terms commander and responder for master and slave.

Component Role
Identification handler Returns supported product identification, such as supplier, function and variant.
Configuration handler Applies supported node-address and frame-identifier configuration services.
Communication status reporting Makes protocol error information available to the master.
Application status reporting Exposes agreed conditions such as actuator blockage or sensor invalidity, where implemented.
Optional parameter storage Retains configuration or calibration when persistence is required and supported.

The node address, NAD, selects a diagnostic recipient; a frame identifier selects a LIN frame. They serve different purposes. Configuration services such as Read by Identifier (0xB2), Assign NAD (0xB0) and Assign Frame Identifier Range (0xB7) have defined roles, but support depends on the selected specification and node capabilities. Infineon configuration documentation

A minimal node need not contain a full UDS server or persistent diagnostic trouble-code memory. LIN 2.2A distinguishes diagnostic capability classes; its smallest class supports configuration and identification without requiring the richer diagnostic services of larger nodes. LIN Specification Package 2.2A

Why it looks like this

The engineering aim is to support an inexpensive, predictable endpoint. RAM, program memory and nonvolatile storage may be limited; an ASIC may have no field-changeable application at all. Configuration handling should therefore require little state and bounded execution time.

The master controls bus scheduling. Diagnostic activity must fit alongside normal commands and feedback without delaying the actuator or sensor function beyond its requirements. Rich transport and diagnostic capabilities add implementation work and resource demand; ISO 17987-2 explicitly distinguishes their intended use on more capable nodes. ISO 17987-2

This grid cell assumes QM development. That assumption must follow the vehicle safety allocation: it does not follow automatically from using LIN or a small chip. Likewise, infrequent application changes can justify simple configuration services, but any required reprogramming needs a separately specified bootloader and update process.

How it connects

Above this layer, the fixed application supplies measurements, operating state and fault indications. It consumes validated configuration and parameters. Below it, LIN protocol handling transports requests and responses; peripheral drivers or ASIC logic operate the hardware. This is a logical separation, even when one small implementation combines the functions.

The master schedules request frames and response opportunities. A slave cannot independently transmit a diagnostic reply whenever it chooses. A zone controller or another master ECU can translate local status into vehicle-level diagnostics or route supported diagnostic requests; that behavior requires an explicit integration design.

Keep communication health separate from application health. In LIN 2.2A, response_error reports qualifying frame-response errors and clears after successful transmission of the unconditional frame carrying it. It does not mean “the motor is blocked.” The master must also detect missing responses. LIN Specification Package 2.2A

Compared with other node classes

  • HPC application processor: platform services can include OTA orchestration, SOVD, host intrusion detection and extensive logging; this endpoint exposes a much smaller local contract.
  • HPC safety island: watchdog supervision, E2E checks and fault memory support allocated safety responsibilities; this QM node has a different assurance scope.
  • Zone controller: coordinates multiple endpoints, power functions and diagnostic aggregation, making it a natural place to interpret LIN status.
  • MCU-based ECU: may use AUTOSAR Diagnostic Communication Manager (Dcm), Diagnostic Event Manager (Dem), NVRAM Manager (NvM) and security modules; those modules are not prerequisites for this cell.

Best practices

  • Specify the LIN revision, supported services, identifiers and configuration persistence explicitly; keep node capability information and the LIN Description File consistent.
  • Budget diagnostic schedules, retries and timeouts against normal control traffic, including startup and replacement-node configuration.
  • Define each status signal’s meaning, validity and clearing behavior, and document how the master converts it into a workshop-visible fault.
  • Validate parameter ranges and configuration changes before applying them; define recovery from interrupted nonvolatile writes where storage exists.
  • Test wrong addresses, malformed requests, missing responses, resets and sleep/wake transitions with the actual master schedule.

Common pitfalls

  • Treating NAD assignment as automatic discovery, or confusing diagnostic addresses with frame identifiers.
  • Assuming every slave supports full UDS, persistent DTCs or flashing over LIN.
  • Treating a checksum or product identifier as authentication, or treating response_error as proof that the application is healthy.

What it means for your discipline

  • Networks & communication Core

    Define node addressing, frame configuration and master schedules. Check that configuration and diagnostic traffic preserve required command and feedback timing.

  • Diagnostics & lifecycle Core

    Specify supported identification services and status semantics. Define whether the master translates local faults into its own DTCs or routes diagnostic requests to the node.

  • HPC & application software Partial

    Implement bounded configuration handlers and application status interfaces on programmable nodes. Verify parameter validation, reset behavior and any persistent storage.

  • Hardware & silicon Partial

    Confirm which identification, fault indications and configuration storage the MCU or ASIC actually provides. Make those capabilities available in the node integration contract.

  • Software update & OTA Partial

    Check supported identification, addressing and diagnostic routing before including a node in a flashing campaign. Distinguish configuration services from actual reprogramming support and coordinate request schedules with the LIN master.

No direct stake: E/E architecture · Cybersecurity · Functional safety · Base software