TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (385 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (118 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (139845 times)
  2. FAT32 Library (72209 times)
  3. Network Ethernet Library (57392 times)
  4. USB Device Library (47740 times)
  5. Network WiFi Library (43364 times)
  6. FT800 Library (42700 times)
  7. GSM click (29980 times)
  8. mikroSDK (28440 times)
  9. PID Library (26989 times)
  10. microSD click (26398 times)
Libstock prefers package manager

Package Manager

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]

< Back
mikroSDK Library

MCP2517FD Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.5

mikroSDK Library: 2.0.0.0

Category: CAN

Downloaded: 113 times

Not followed.

License: MIT license  

MCP2517FD Click is a complete CAN solution which carries the MCP2517FD CAN FD controller and ATA6563 high-speed CAN transceiver from Microchip, as well as a DB9 9-pin connector.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "MCP2517FD Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "MCP2517FD Click" changes.

Do you want to report abuse regarding "MCP2517FD Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


MCP2517FD Click

MCP2517FD Click is a complete CAN solution which carries the MCP2517FD CAN FD controller and ATA6563 high-speed CAN transceiver from Microchip, as well as a DB9 9-pin connector.

mcp2517fd_click.png

Click Product page


Click library

  • Author : Mikroe Team
  • Date : Oct 2021.
  • Type : SPI type

Software Support

We provide a library for the MCP2517FD 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.

Library Description

This library contains API for MCP2517FD Click driver.

Standard key functions :

  • mcp2517fd_cfg_setup Config Object Initialization function.

    void mcp2517fd_cfg_setup ( mcp2517fd_cfg_t *cfg );
  • mcp2517fd_init Initialization function.

    err_t mcp2517fd_init ( mcp2517fd_t *ctx, mcp2517fd_cfg_t *cfg );
  • mcp2517fd_default_cfg Click Default Configuration function.

    err_t mcp2517fd_default_cfg ( mcp2517fd_t *ctx );

Example key functions :

  • mcp2517fd_transmit_message Transmits the desired message and checks is message successfully sent.

    err_t mcp2517fd_transmit_message ( mcp2517fd_t *ctx, uint8_t *data_in, uint16_t data_len );
  • mcp2517fd_receive_message Receives the message and checks is message successfully received.

    err_t mcp2517fd_receive_message ( mcp2517fd_t *ctx, uint8_t *data_out, uint16_t *data_len );
  • mcp2517fd_reset Function for reset using generic transfer

    err_t mcp2517fd_reset ( mcp2517fd_t *ctx );

Example Description

This example demonstrates the use of an MCP2517FD 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 :

Application Init

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. */
    mcp2517fd_cfg_t mcp2517fd_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.
    mcp2517fd_cfg_setup( &mcp2517fd_cfg );
    MCP2517FD_MAP_MIKROBUS( mcp2517fd_cfg, MIKROBUS_1 );
    if ( SPI_MASTER_ERROR == mcp2517fd_init( &mcp2517fd, &mcp2517fd_cfg ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }

    if ( MCP2517FD_ERROR == mcp2517fd_default_cfg ( &mcp2517fd ) )
    {
        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 " );
}

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 ( MCP2517FD_OK == mcp2517fd_transmit_message( &mcp2517fd, 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 ( MCP2517FD_OK == mcp2517fd_receive_message( &mcp2517fd, 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:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.MCP2517FD

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.


ALSO FROM THIS AUTHOR

nvSRAM Click

0

nvSRAM Click is a compact add-on board that contains the most reliable nonvolatile memory. This board features the CY14B101J, a 1-Mbit nvSRAM organized as 128K words of 8 bits each with a nonvolatile element in each memory cell from Cypress Semiconductor. The embedded nonvolatile elements incorporate the QuantumTrap technology and provide highly reliable nonvolatile storage of data.

[Learn More]

OLED C click

5

OLED C click arries the PSP27801 OLED display, the same one that we have used on Hexiwear. The click is designed to run on 3.3V power supply only. It communicates with the target microcontroller over an SPI interface.

[Learn More]

Wheatstone click

5

Wheatstone Click is a measurement Click board which utilizes a Wheatstone bridge circuit onboard, in order to precisely measure the resistance of an external element. Besides the wheatstone bridge circuit, this Click board also utilizes MAX4208 – an ultra-low offset/drift, precision instrumentation amplifier, from Maxim Integrated.

[Learn More]