Combine NCV7344 with TM4C1299NCZAD for smooth CAN data flow
CAN: Building Intelligent Networks
Published Aug 03, 2023
Click board™
CAN FD 4 Click
Dev. board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
TM4C1299NCZAD
Future-proof your automotive network with our advanced high-speed CAN FD transceiver solution
A
A
Hardware Overview
How does it work?
CAN FD 4 Click is based on the NCV7344, a complete CAN protocol controller, and the physical bus from ON Semiconductor. The Click board™ guarantees additional timing parameters to ensure robust communication at data rates beyond 1 Mbps to cope with CAN flexible data rate requirements (CAN FD). These features make the CAN FD 4 click a good choice for all high speed - controller area network (HS−CAN) networks. The CAN FD 4 click provides two operation modes: selectable pin CS. The first option is normal mode (when the CS pin is LOW), where the transceiver can communicate via the bus line. The CAN controller transmits and receives the signals via
the pins TxD and RxD. The slopes on the bus line outputs are optimized to give low EME. The second option is when the CS pin is HIGH and the CAN FD 4 click is in Standby mode. In standby mode, both the transmitter and receiver are disabled, and a very low−power differential receiver monitors the bus lines for CAN bus activity. When the low−power differential receiver detects a wake−up request, the signal is first filtered and then verified as a valid wake signal after a time period of twake_filt; the RxD pin is driven low by the transceiver (following the bus) to inform the controller of the wake−up request. High-speed CAN (HS CAN) is a serial bus system
that connects microcontrollers, sensors, and actuators for real-time control applications. Compatible with ISO 11898-2 (2016) describes using the Controller Area Network (CAN) within road vehicles. According to the 7-layer OSI reference model, the physical layer of an HS CAN bus system specifies the data transmission from one CAN node to all other available CAN nodes within the network. The CAN transceiver is part of the physical layer. This Click board™ is designed to be operated only with a 5V logic level. A proper logic voltage level conversion should be performed before the Click board™ is used with MCUs with logic levels of 3.3V.
Features overview
Development board
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
212
RAM (Bytes)
262144
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 Fusion for Tiva v8 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 CAN FD 4 Click driver.
Key functions:
canfd4_generic_write- Generic write functioncanfd4_set_dev_mode- Set mode functioncanfd4_generic_read- Generic 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 CanFd4 Click example
*
* # Description
* This example reads and processes data from CAN FD 4 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the click board.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* every 2 seconds.
*
* ## Additional Function
* - canfd4_process ( ) - The general process of collecting the received data.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "canfd4.h"
#include "string.h"
#define PROCESS_RX_BUFFER_SIZE 500
#define TEXT_TO_SEND "MikroE\r\n"
// ------------------------------------------------------------------ VARIABLES
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
static canfd4_t canfd4;
static log_t logger;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void canfd4_process ( void )
{
int32_t rsp_size;
char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
uint8_t check_buf_cnt;
rsp_size = canfd4_generic_read( &canfd4, uart_rx_buffer, PROCESS_RX_BUFFER_SIZE );
if ( rsp_size > 6 )
{
log_printf( &logger, "Received data: " );
for ( check_buf_cnt = 0; check_buf_cnt < rsp_size; check_buf_cnt++ )
{
log_printf( &logger, "%c", uart_rx_buffer[ check_buf_cnt ] );
}
}
Delay_ms ( 100 );
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
canfd4_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.
canfd4_cfg_setup( &cfg );
CANFD4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
canfd4_init( &canfd4, &cfg );
canfd4_set_dev_mode ( &canfd4, CANFD4_NORMAL_MODE );
Delay_ms ( 100 );
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
canfd4_process( );
#endif
#ifdef DEMO_APP_TRANSMITTER
canfd4_generic_write( &canfd4, TEXT_TO_SEND, 8 );
log_info( &logger, "--- The message is 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
