Trust in our LIN transceiver for robust real-time monitoring and control in demanding industrial environments, ensuring precision and uptime.
A
A
Hardware Overview
How does it work?
LIN Click is based on the TLE7259-3, a LIN transceiver with an integrated wake-up feature from Infineon Technologies. The TLE7259-3 operates as a bus driver between the protocol controller and the physical LIN bus designed for in-vehicle networks using data transmission rates from 2.4kbps to 20kbps. It is compliant with all LIN standards and has built-in protection features against over-voltage and overtemperature conditions and a wide operating supply range, making the TLE7259-3 ideal for various automotive applications. LIN Click communicates with MCU using the UART interface with commonly used UART RX and TX pins at 9600 bps by default configuration to transmit and exchange data with the host MCU. The transmit data stream on the TX input is converted to a LIN bus signal with an optimized slew rate, while the RX output reads back the information from the LIN bus to the MCU. The receiver also has an integrated filter network
to suppress noise on the LIN bus and increase the transceiver's EMI (Electromagnetic immunity) level. This Click board™ provides the ability to work in both Host or Peripheral mode, where selection can be performed by onboard SMD jumper labeled as MODE to an appropriate position. The TLE7259-3 also operates in three major operational modes: Stand-by, Normal, and Sleep mode, selected by the logic state of the enable pin labeled as EN and routed to the CS pin of the mikroBUS™ socket. In Normal Operation mode, the LIN bus receiver and the LIN bus transmitter are active, whereby communication occurs as usual, while in the Stand-by mode, no communication on the LIN bus is possible. Sleep mode significantly reduces the current consumption of the TLE7259-3. The LIN bus also has a wake-up event often called remote Wake-Up, a falling edge on the LIN bus followed by a specific duration, resulting in a wake-up event
that changes the operation mode from Sleep mode to Stand-by mode. Besides the remote wake-up, a wake-up of the TLE7259-3 via the WK pin routed to the PWM pin of the mikroBUS™ socket is possible, called local wake-up. This Click board™ supports an external power supply connected to the input terminal labeled as VS and should be within the range of 5.5V to 27V, suitable for both 12V and 24V board net, while the LIN bus line can be connected to the terminal labeled as BUS. 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
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project 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 LIN Click driver.
Key functions:
lin_generic_write
- Generic write functionlin_generic_read
- Generic read functionlin_set_enable
- Set enable pin state.
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 Lin Click example
*
* # Description
* This example reads and processes data from LIN clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and makes an initial log.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* every 2 seconds.
*
* ## Additional Function
* - lin_process ( ) - The general process of collecting the received data.
*
* @note
* Make sure to set the onboard Master/Slave jumpers properly and to connect and power two click
* boards according to LIN Specification 2.2A.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "lin.h"
#include "string.h"
#define PROCESS_RX_BUFFER_SIZE 500
#define TEXT_TO_SEND "MikroE - LIN click board\r\n"
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
// ------------------------------------------------------------------ VARIABLES
static lin_t lin;
static log_t logger;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void lin_process ( void )
{
int32_t rsp_size;
char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
rsp_size = lin_generic_read( &lin, uart_rx_buffer, PROCESS_RX_BUFFER_SIZE );
if ( rsp_size > 0 )
{
for ( uint8_t cnt = 0; cnt < rsp_size; cnt++ )
{
log_printf( &logger, "%c", uart_rx_buffer[ cnt ] );
if ( uart_rx_buffer[ cnt ] == '\n' )
{
log_printf( &logger, "---------------------------\r\n" );
}
}
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
lin_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.
lin_cfg_setup( &cfg );
LIN_MAP_MIKROBUS( cfg, MIKROBUS_1 );
lin_init( &lin, &cfg );
Delay_ms ( 100 );
lin_set_enable ( &lin, 1 );
lin_set_wake_up ( &lin, 0 );
Delay_ms ( 100 );
#ifdef DEMO_APP_RECEIVER
log_info( &logger, "---- Receiver mode ----" );
#endif
#ifdef DEMO_APP_TRANSMITTER
log_info( &logger, "---- Transmitter mode ----" );
#endif
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
lin_process( );
#endif
#ifdef DEMO_APP_TRANSMITTER
lin_generic_write( &lin, TEXT_TO_SEND, strlen( TEXT_TO_SEND ) );
log_info( &logger, "---- Data sent ----" );
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
/*!
* \file
* \brief Lin Click example
*
* # Description
* This example reads and processes data from LIN clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and makes an initial log.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* every 2 seconds.
*
* ## Additional Function
* - lin_process ( ) - The general process of collecting the received data.
*
* @note
* Make sure to set the onboard Master/Slave jumpers properly and to connect and power two click
* boards according to LIN Specification 2.2A.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "lin.h"
#include "string.h"
#define PROCESS_RX_BUFFER_SIZE 500
#define TEXT_TO_SEND "MikroE - LIN click board\r\n"
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
// ------------------------------------------------------------------ VARIABLES
static lin_t lin;
static log_t logger;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void lin_process ( void )
{
int32_t rsp_size;
char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
rsp_size = lin_generic_read( &lin, uart_rx_buffer, PROCESS_RX_BUFFER_SIZE );
if ( rsp_size > 0 )
{
for ( uint8_t cnt = 0; cnt < rsp_size; cnt++ )
{
log_printf( &logger, "%c", uart_rx_buffer[ cnt ] );
if ( uart_rx_buffer[ cnt ] == '\n' )
{
log_printf( &logger, "---------------------------\r\n" );
}
}
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
lin_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.
lin_cfg_setup( &cfg );
LIN_MAP_MIKROBUS( cfg, MIKROBUS_1 );
lin_init( &lin, &cfg );
Delay_ms ( 100 );
lin_set_enable ( &lin, 1 );
lin_set_wake_up ( &lin, 0 );
Delay_ms ( 100 );
#ifdef DEMO_APP_RECEIVER
log_info( &logger, "---- Receiver mode ----" );
#endif
#ifdef DEMO_APP_TRANSMITTER
log_info( &logger, "---- Transmitter mode ----" );
#endif
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
lin_process( );
#endif
#ifdef DEMO_APP_TRANSMITTER
lin_generic_write( &lin, TEXT_TO_SEND, strlen( TEXT_TO_SEND ) );
log_info( &logger, "---- Data sent ----" );
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