We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.13
mikroSDK Library: 2.0.0.0
Category: CAN
Downloaded: 391 times
Not followed.
License: MIT license
MCP251863 Click is a compact add-on board representing a complete CAN solution used as a control node in a CAN network. This board features the MCP251863, IC representing a compact solution with a controller and a transceiver in one package, the MCP2518FD and ATA6563 from Microchip. The ATA6563, a low-level physical layer IC (PHY), provides a physical connection with the CAN bus itself, while the CAN controller MCP2518FD represents an interface between the MCU and the PHY. It features three operating modes with dedicated fail-safe features, remote wake-up via CAN, and ideally passive behavior when powered off on the CAN bus. This Click board™ is suitable for developing a wide range of automotive diagnostic applications, even on MCUs that don’t support CAN interface.
Do you want to subscribe in order to receive notifications regarding "MCP251863 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "MCP251863 Click" changes.
Do you want to report abuse regarding "MCP251863 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
4905_mcp251863_click.zip [1.03MB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for AVR mikroC AI for dsPIC XC16 |
|
MCP251863 Click is a compact add-on board representing a complete CAN solution used as a control node in a CAN network. This board features the MCP251863, IC representing a compact solution with a controller and a transceiver in one package, the MCP2518FD and ATA6563 from Microchip. The ATA6563, a low-level physical layer IC (PHY), provides a physical connection with the CAN bus itself, while the CAN controller MCP2518FD represents an interface between the MCU and the PHY. It features three operating modes with dedicated fail-safe features, remote wake-up via CAN, and ideally passive behavior when powered off on the CAN bus. This Click board™ is suitable for developing a wide range of automotive diagnostic applications, even on MCUs that don’t support CAN interface.
We provide a library for the MCP251863 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.
Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
This library contains API for MCP251863 Click driver.
mcp251863_cfg_setup
Config Object Initialization function.
void mcp251863_cfg_setup ( mcp251863_cfg_t *cfg );
mcp251863_init
Initialization function.
err_t mcp251863_init ( mcp251863_t *ctx, mcp251863_cfg_t *cfg );
mcp251863_default_cfg
Click Default Configuration function.
err_t mcp251863_default_cfg ( mcp251863_t *ctx );
mcp251863_transmit_message
Transmits the desired message and checks is message successfully sent.
err_t mcp251863_transmit_message ( mcp251863_t *ctx, uint8_t *data_in, uint16_t data_len );
mcp251863_receive_message
Receives the message and checks is message successfully received.
err_t mcp251863_receive_message ( mcp251863_t *ctx, uint8_t *data_out, uint16_t *data_len );
mcp251863_operation_mode_select
Function for select operation mode.
err_t mcp251863_operation_mode_select ( mcp251863_t *ctx, uint8_t op_mode );
This example demonstrates the use of an MCP251863 Click board by showing the communication between the two Click boards configured as a receiver and transmitter.
The demo application is composed of two sections :
Initializes the driver and logger, performs the Click default configuration and displays the selected application mode.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
mcp251863_cfg_t mcp251863_cfg; /**< Click config object. */
/**
* 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.
mcp251863_cfg_setup( &mcp251863_cfg );
MCP251863_MAP_MIKROBUS( mcp251863_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == mcp251863_init( &mcp251863, &mcp251863_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( MCP251863_ERROR == mcp251863_default_cfg ( &mcp251863 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
#ifdef DEMO_APP_TRANSMITTER
log_printf( &logger, " Application Mode: Transmitter\r\n" );
#else
log_printf( &logger, " Application Mode: Receiver\r\n" );
#endif
log_info( &logger, " Application Task " );
}
Depending on the selected mode, it sends a desired message using CAN protocol or reads all the received data and displays them on the USB UART.
void application_task ( void )
{
#ifdef DEMO_APP_TRANSMITTER
if ( MCP251863_OK == mcp251863_transmit_message( &mcp251863, DEMO_TEXT_MESSAGE, strlen( DEMO_TEXT_MESSAGE ) ) )
{
log_printf( &logger, " The message \"%s\" has been sent!\r\n", ( char * ) DEMO_TEXT_MESSAGE );
}
Delay_ms ( 1000 );
Delay_ms ( 1000 );
#else
uint8_t data_buf[ 256 ] = { 0 };
uint16_t data_len = 0;
if ( MCP251863_OK == mcp251863_receive_message( &mcp251863, data_buf, &data_len ) )
{
log_printf( &logger, " A new message has received: \"" );
for ( uint16_t cnt = 0; cnt < data_len; cnt++ )
{
log_printf( &logger, "%c", data_buf[ cnt ] );
}
log_printf( &logger, "\"\r\n" );
}
#endif
}
The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
Other Mikroe Libraries used in the example:
Additional notes and informations
Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all MikroElektronika compilers, or any other terminal application of your choice, can be used to read the message.