Utilize TLE7268 and PIC18F57Q43 to simplify automotive networking

Streamlined communication: Unleash the potential of LIN transceivers

Dual LIN Click with Curiosity Nano with PIC18F57Q43

Published Feb 13, 2024

Click board™

Dual LIN Click

Dev. board

Curiosity Nano with PIC18F57Q43

Compiler

NECTO Studio

MCU

PIC18F57Q43

Our LIN transceivers offer unwavering reliability for data exchange in vehicles and industrial systems, contributing to safer and more efficient journeys

Hardware Overview

How does it work?

Dual LIN Click is based on the TLE7268, a dual transceiver for the Local Interconnect Network (LIN) from Infineon with integrated wake-up and protection features. The Dual LIN click is designed for in-vehicle networks using data transmission rates up to 20 kbps. Dual LIN click includes two independent transceivers that operate as bus drivers between the protocol controller and physical LIN networks. The Dual LIN click communicates with the MCU by using the UART RX and TX signals. RX and TX signals are also routed to the header on the edge of the click board™ so they can be used independently of the mikroBUS™ socket. Its most important features are the fact that it is a two separate single-wire LIN transceiver bus for transmission rates up to 20 kbps and it is compliant to ISO 17987-4 and LIN Specification 2.2A. The EN1 and EN2 pins are used to enable the functionality of BUS 1 or BUS 2 of the device. When the EN1 pin is set to a HIGH logic level, the BUS 1 of the device is set to work in the normal mode, with the transmission paths from TXD to LIN and from LIN to RXD both active. When

the EN2 pin is set to a HIGH logic level, the BUS 2 of the device is set to work in the normal mode, with the transmission paths from TXD to LIN and from LIN to RXD both active. When the EN1 pin is set to a LOW state, the BUS 1 of the device is put into silent mode, depending on the TX pin state. The EN1 pin has a pull-down resistor, so it is pulled to Ground if it is left afloat. When the EN2 pin is set to a LOW state, the BUS 2 of the device is put into silent mode, depending on the TX pin state. The EN2 pin has a pull-down resistor, so it is pulled to Ground if it is left afloat. The Dual LIN click supports different modes of operation of the two transceivers for minimizing ECU current consumption in low power modes, a common INH output can be used for controlling external circuitry, for example voltage regulators. Based on the Infineon BiCMOS technology. It provides excellent ESD robustness together with very high electromagnetic compliance (EMC). The TLE7268 reaches a very low level of electromagnetic emission (EME) within a broad frequency range and independent from the battery voltage. The

TLE7268 is AEC qualified and tailored to withstand the harsh conditions of the automotive environment. Some of the key features that are incorporated in the TLE7268 are overtemperature protection, undervoltage detection. The Dual LIN click is digital I/O levels compatible with 3.3 V and 5 V microcontrollers, that it is optimized for high electromagnetic compliance (EMC) with very low electromagnetic emission and high immunity to interference. It also features two independent single-wire LIN transceivers in one device and gives out a transmission rate of up to 20 kbps. Given the features included in this transceiver, the Dual LIN click can be used for Body Control Modules (BCM) and Gateway. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.

Features overview

Development board

PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive

mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI

GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.

PIC18F57Q43 Curiosity Nano double side image

Microcontroller Overview

MCU Card / MCU

Architecture

PIC

MCU Memory (KB)

128

Silicon Vendor

Microchip

Pin count

RAM (Bytes)

8196

You complete me!

Accessories

Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.

Used MCU Pins

mikroBUS™ mapper

Output 1 Enable

PA7

RST

Output 2 Enable

PD4

SCK

MISO

MOSI

Power Supply

3.3V

Ground

GND

PWM

INT

UART TX

PC3

UART RX

PC2

SCL

SDA

Power Supply

Ground

GND

Take a closer look

Click board™ Schematic

Step by step

Project assembly

Curiosity Nano Base for Click boards front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Curiosity Nano with PIC18F57Q43 as your development board.

Charger 27 Click front image hardware assembly

PIC18F47Q10 Curiosity Nano front image hardware assembly

Charger 27 Click complete accessories setup image hardware assembly

Board mapper by product8 hardware assembly

PIC18F57Q43 Curiosity MCU Step hardware assembly

Necto No Display image step 8 hardware assembly

Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support

Library Description

This library contains API for Dual LIN Click driver.

Key functions:

duallin_bus1_status - Sets state of RST pin
duallin_bus2_status - Sets state of CS pin
duallin_send_command - Send command.

Open Source

Code example

The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.

/*!
 * \file 
 * \brief DualLin Click example
 * 
 * # Description
 * This example reads and processes data from Dual LIN Clicks.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes driver, and sets bus.
 * 
 * ## Application Task  
 * Reads the received data.
 * 
 * ## Additional Function
 * - duallin_process ( ) - The general process of collecting presponce 
 *                                   that sends a module.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "duallin.h"
#include "string.h"

#define PROCESS_COUNTER 10
#define PROCESS_RX_BUFFER_SIZE 500

#define TEXT_TO_SEND "MikroE\r\n"

// ------------------------------------------------------------------ VARIABLES

#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITER

static duallin_t duallin;
static log_t logger;

static char current_rsp_buf[ PROCESS_RX_BUFFER_SIZE ];

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    duallin_cfg_t cfg;

    /** 
     * Logger initialization.
     * Default baud rate: 115200
     * Default log level: LOG_LEVEL_DEBUG
     * @note If USB_UART_RX and USB_UART_TX 
     * are defined as HAL_PIN_NC, you will 
     * need to define them manually for log to work. 
     * See @b LOG_MAP_USB_UART macro definition for detailed explanation.
     */
    LOG_MAP_USB_UART( log_cfg );
    log_init( &logger, &log_cfg );
    log_info( &logger, "---- Application Init ----" );

    //  Click initialization.

    duallin_cfg_setup( &cfg );
    DUALLIN_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    duallin_init( &duallin, &cfg );

    duallin_bus1_status( &duallin, DUALLIN_PIN_STATE_HIGH );
    duallin_bus2_status( &duallin, DUALLIN_PIN_STATE_LOW );
    Delay_ms ( 100 );
}

void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
    int32_t rsp_size = duallin_generic_read( &duallin, current_rsp_buf, PROCESS_RX_BUFFER_SIZE );
    if ( rsp_size> 0)
    {
        log_printf( &logger, "%s", current_rsp_buf );
    }
#endif    

#ifdef DEMO_APP_TRANSMITER
    duallin_send_command( &duallin, TEXT_TO_SEND );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );    
#endif
}

int main ( void ) 
{
    /* Do not remove this line or clock might not be set correctly. */
    #ifdef PREINIT_SUPPORTED
    preinit();
    #endif
    
    application_init( );
    
    for ( ; ; ) 
    {
        application_task( );
    }

    return 0;
}

// ------------------------------------------------------------------------ END