Upgrade industrial systems with LIN transceiver solution based on ATA663211 and ATmega328P
The backbone of reliable vehicle and industrial networking
Published Feb 14, 2024
Click board™
ATA663254 Click
Dev. board
Arduino UNO Rev3
Compiler
NECTO Studio
MCU
ATmega328P
Achieve unparalleled reliability in data communication for vehicles and industrial applications, thanks to our cutting-edge LIN transceiver technology
A
A
Hardware Overview
How does it work?
ATA663254 Click is based on the ATA663254, an integrated LIN bus transceiver with the 5V voltage regulator from Microchip. The ATA663254 communicates with the MCU by using the UART RX and TX signals. Besides for communication, these pins also serve to signal the failsafe condition. The failsafe condition can be caused by the undervoltage on the LIN connector: less than 3.9V will cause the undervoltage condition, signaled by the LOW logic state on RX pin and HIGH logic state on the TX pin. A wake-up event from either silent or sleep mode is signaled by the LOW logic state on both of the RX and TX pins. This event is being received via the LIN bus and it is used to switch the ATA663254 click to an active state. 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. The NRES pin of the ATA663254 IC is routed to the RST pin on the mikroBUS™. RST pin is used to signal the undervoltage condition on the LDO regulator section. When the LDO voltage falls under the predefined threshold, the RST pin will be set to a LOW logic state, signaling this condition to the MCU. The LDO output is routed to a header located on the edge of the click so that the LDO can be used independently of the mikroBUS™ socket. Also, there is an SMD jumper that can be shorted if powering up the MCU via the mikroBUS™ 5V pin is required, on a custom board design. Note that the MikroElektronika development systems are not meant to be
powered up by the mikroBUS™ power supply pins, so the ATA663254 click comes without the SMD jumper, by default. The EN pin is used to enable the functionality of the device. When the EN pin is set to a HIGH logic level, 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 EN pin is set to a LOW state, the device is put into silent mode, depending on the TX pin state. The EN pin has a pull-down resistor, so it is pulled to Ground if it is left afloat. Besides the 5V LDO output header and the external UART header, the click is equipped with the three pole connector for an easy and secure connection to the LIN network and the 12V battery power supply.
Features overview
Development board
Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an
ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the
first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
2048
You complete me!
Accessories
Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P 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 Arduino UNO board with our Click Shield for Arduino UNO, 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
Start by selecting your development board and Click board™. Begin with the Arduino UNO Rev3 as your development board.
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 ATA663254 Click driver.
Key functions:
ata663254_get_rst_state- Undervoltage detect functionata663254_generic_write- Generic multi write functionata663254_generic_read- Generic multi read function.
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 Ata663254 Click example
*
* # Description
* This application demonstates the use of ATA663254 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the click driver and enables the click board.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* each 2 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ata663254.h"
// ------------------------------------------------------------------ VARIABLES
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
static ata663254_t ata663254;
static log_t logger;
static char demo_message[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13, 10, 0 };
static char rec_buf[ 50 ] = { 0 };
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
ata663254_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.
ata663254_cfg_setup( &cfg );
ATA663254_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ata663254_init( &ata663254, &cfg );
ata663254_enable( &ata663254, 1 );
Delay_ms ( 1000 );
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
// RECEIVER - UART polling
int32_t len = ata663254_generic_read( &ata663254, rec_buf, 50 );
if ( len > 0 )
{
log_printf( &logger, "Received data: " );
for ( int32_t cnt = 0; cnt < len; cnt++ )
{
log_printf( &logger, "%c", rec_buf[ cnt ] );
}
memset( rec_buf, 0 , 50 );
}
Delay_ms ( 100 );
#endif
#ifdef DEMO_APP_TRANSMITTER
// TRANSMITER - TX each 2 sec
ata663254_generic_write( &ata663254, demo_message, 9 );
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 Ata663254 Click example
*
* # Description
* This application demonstates the use of ATA663254 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the click driver and enables the click board.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* each 2 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ata663254.h"
// ------------------------------------------------------------------ VARIABLES
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
static ata663254_t ata663254;
static log_t logger;
static char demo_message[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13, 10, 0 };
static char rec_buf[ 50 ] = { 0 };
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
ata663254_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.
ata663254_cfg_setup( &cfg );
ATA663254_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ata663254_init( &ata663254, &cfg );
ata663254_enable( &ata663254, 1 );
Delay_ms ( 1000 );
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
// RECEIVER - UART polling
int32_t len = ata663254_generic_read( &ata663254, rec_buf, 50 );
if ( len > 0 )
{
log_printf( &logger, "Received data: " );
for ( int32_t cnt = 0; cnt < len; cnt++ )
{
log_printf( &logger, "%c", rec_buf[ cnt ] );
}
memset( rec_buf, 0 , 50 );
}
Delay_ms ( 100 );
#endif
#ifdef DEMO_APP_TRANSMITTER
// TRANSMITER - TX each 2 sec
ata663254_generic_write( &ata663254, demo_message, 9 );
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
