Features Supported

Compatibility with LIN 1.3 , 2.0, and 2.1 protocols.
Configurable baud rate up to 20 kbps.
Two external pins: LINRX and LINTX.
Multi-buffered receive and transmit units.
Identification masks for message filtering.
Automatic commander header generation
- Programmable synchronization break field.
- Synchronization field.
- Identifier field.
Responder Automatic Synchronization
- Synchronization break detection.
- Optional baud rate update.
- Synchronization validation.
231 programmable transmission rates with 7 fractional bits.
Wakeup on LINRX active level from transceiver.
Automatic idle bus detection
Error detection
- Bit error.
- Bus error.
- No-response error.
- Checksum error.
- Synchronization field error.
- Parity error.
Capability to use Direct Memory Access (DMA) to transmit and receive data.
2 interrupt lines (INT0 and INT1) with user-configurable interrupt sources
- Receive.
- Transmit.
- ID, error, and status.
Support for LIN 2.0 checksum.
Enhanced synchronizer finite state machine (FSM) support for frame processing.
Enhanced handling of extended frames.
Enhanced baud rate generator.

SysConfig Features

Note: It is strongly recommend to use SysConfig where it is available instead of using direct SW API calls. This will help simplify the SW application and also catch common mistakes early in the development cycle.

SysConfig can be used to configure below parameters apart from common configurations like Clock,MPU,RAT and others.

LIN module configuration parameters Such as Clock Source, Operating Mode, Transfer Mode, Baud Rate.
LIN instances and pin Configuration for each Instance.
LIN frame specific Configurations such as Parity, LIN Mode(Commander/Responder), Checksum Type, Sync Delimiter, Sync Break.
Based on above parameters, the SysConfig generated code does below as part of Drivers_open and Drivers_close functions.
- Set LIN instance parameter configuration.
- ISR/DMA Configuration for Transactions.

Features not Supported

Extended Frames.
Wake-Up on LINRX active level from transceiver.
Automatic Wake-Up.

Usage Overview

API Sequence

LIN_Params_init(): Fill Default Value in LIN_OpenParams Structure.
LIN_open(): Open an LIN HLD Instance.
LIN_close(): Close an LIN HLD Instance.
LIN_SCI_Frame_init(): Fill Default Value in LIN_SCI_Frame Structure.
LIN_SCI_transferFrame(): Initiate a LIN Transaction.
LIN_getHandle(): Get LIN Handle from index.

Initializing the LIN HLD Driver

LIN_init() must be called before any other LIN Open is called.

LIN_open() must be called before calling any LIN APIs. This function takes index and params to initialize an instance and returns the handle to the LIN instance.

Calling LIN_close() closes the instance passed.

Please note that the initialization of LIN HLD instances is taken care by the SysConfig generated code.

Example Usage

Include the below file to access the APIs

#include <drivers/lin.h>

Instance Open Example

    /* Open Params Structure */
    LIN_OpenParams      params;
 
    /* Initialize parameters */
    LIN_Params_init(&params);
 
    /* Call LIN open */
    gLinHandle = LIN_open(CONFIG_LIN0, &params);
 
    DebugP_assert(gLinHandle != NULL);

Instance Close Example

LIN_close(gLinHandle);

LIN Commander Write

    uint8_t     i = 0;
    int32_t     status = SystemP_SUCCESS;
    uint8_t     txData[8] __attribute__((aligned(CacheP_CACHELINE_ALIGNMENT)));
 
    for (uint8_t i = 0; i < 8; i++)
    {
        txData[i] =  0xA1 + i;
    }
 
    LIN_SCI_Frame linFrame;
 
    LIN_SCI_Frame_init(&linFrame);
 
    linFrame.id = 0x11 + i;
    linFrame.frameLen = i + 1U;
    linFrame.dataBuf = txData;
 
    status = LIN_SCI_transferFrame(gLinHandle, &linFrame);
    DebugP_assert (SystemP_SUCCESS == status);

API

APIs for LIN HLD

Table of Contents