10 min

Revolutionize automotive and industrial communication with MCP2542 and PIC18F25K42

CAN: Empowering Embedded Communication

MCP2542 Click with Curiosity HPC

Published Jan 23, 2024

Click board™

MCP2542 Click

Development board

Curiosity HPC


NECTO Studio



Experience reliable and high-speed data communication with our advanced CAN transceiver, designed to facilitate seamless integration and robust performance within your network



Hardware Overview

How does it work?

MCP2542 Click is based on the MCP2542WFD, a CAN transceiver with a wake-up pattern from Microchip. This IC supports both CAN and recently established CAN FD protocols with up to 8Mbps. The communication through the CAN bus is differential and performed through the twisted pairs with the characteristic impedance of 120 Ω. The CANH and CANL drivers drive the differential lines integrated into the MCP2542WFD IC. This provides robustness and immunity to electromagnetic interferences, typically observed in automotive systems. The ISO 11898 standard defines a signal line of twisted-pair cable as the network topology, terminated by the resistors with the characteristic impedance of the CAN bus (120 Ω), at both ends of the bus - to prevent signal reflection. This Click board™ does not need a termination resistor and includes additional protection on the CAN bus. The CAN bus uses two states: dominant and recessive. The dominant state is when the differential voltage between the CANH and CANL bus lines is above the dominant state detection level (0.9V), while the recessive state is below the recessive state detection level

(0.5V). Allowed differential voltage on the CAN bus can range between -12V and 12V. The logic level on the TX pin controls CANH and CANL drivers. A HIGH logic level on the TX line results in the recessive state on the CAN bus, while a LOW logic level results in the dominant state on the CAN bus. TXD line has the internal pull-up resistor (HIGH), making the MCP2542WFD device stay in recessive mode if the pin is left floating. The dominant/recessive states on the CAN bus are used for the message priority arbitration: the node that transmits the signal with the higher priority (the lower the binary message identifier number, the higher the priority) will win the arbitration, and the node with the lower priority will abort the transmission, waiting for the bus to become available again. The CAN bus states are reflected on the RX pin: the dominant state will drive the RX pin to a LOW logic level, while the recessive state will drive it to a HIGH logic level. This pin is also connected to the power supply via the internal pull-up resistor. MCP2542 Click uses a standard 2-Wire UART interface to communicate with the host MCU with commonly used UART RX and TX

lines. These lines are also routed to the header on the side of the Click board™, allowing them to be used with some other device. Besides TX and RX lines, CANH and CANL bus lines are also routed to a header next to the RX and TX header. The MCP2542WFD supports a standby mode. This function can be selected over the MODE SEL jumper. If this jumper is set to the STB position, the STBY of the transceiver pin will be routed to the STB pin of the mikroBUS™ socket., allowing the MCU to control it. If the jumper is set to the ON position, it will be routed to the GND directly, not allowing the MCP2542WFD device to enter the Standby mode. Finally, a D-SUB 9 male connector on the Click board™ connects to a CAN bus directly. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VIO 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.

MCP2542 Click hardware overview image

Features overview

Development board

Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All

these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware

quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.

Curiosity HPC double image

Microcontroller Overview

MCU Card / MCU




MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Standby Mode
Power Supply
Power Supply

Take a closer look


MCP2542 Click Schematic schematic

Step by step

Project assembly

Curiosity HPC front no-mcu image hardware assembly

Start by selecting your development board and Click board™. Begin with the Curiosity HPC as your development board.

Curiosity HPC front no-mcu image hardware assembly
LTE Cat.1 2 Click front image hardware assembly
MCU DIP 28 hardware assembly
Prog-cut hardware assembly
LTE Cat.1 2 Click complete accessories setup image hardware assembly
Curiosity HPC Access 28pin-DIP - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto DIP image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for MCP2542 Click driver.

Key functions:

  • mcp2542_generic_single_read - Generic single read function

  • mcp2542_generic_single_write - Generic single write function

  • mcp2542_generic_multi_write - Generic multi write function

Open Source

Code example

This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.

 * \file 
 * \brief Mcp2542 Click example
 * # Description
 * This application use for comunication.
 * The demo application is composed of two sections :
 * ## Application Init 
 * Driver intialization.
 * ## Application Task  
 * Checks if new data byte have received in rx buffer (ready for reading),
 * and if ready than reads one byte from rx buffer. In second case aplication task writes
 * message data via UART.
 * \author MikroE Team
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "mcp2542.h"

// ------------------------------------------------------------------ VARIABLES


static mcp2542_t mcp2542;
static log_t logger;

static char demo_message[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13, 10, 0 };

void application_init ( void )
    log_cfg_t log_cfg;
    mcp2542_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.

    mcp2542_cfg_setup( &cfg );
    MCP2542_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    mcp2542_init( &mcp2542, &cfg );

     mcp2542_default_cfg( &mcp2542 );

void application_task ( void )
    char tmp;
    //  Task implementation.

       // RECEIVER - UART polling

       tmp = mcp2542_generic_single_read( &mcp2542 );
       log_printf( &logger, "%c\r\n", tmp );

       // TRANSMITER - TX each 2 sec
       mcp2542_generic_multi_write( &mcp2542, demo_message, 9 );
       Delay_ms( 2000 );


void main ( void )
    application_init( );

    for ( ; ; )
        application_task( );

// ------------------------------------------------------------------------ END

Additional Support