Beginner
10 min
0

Create a secure and efficient pathway for your data with ADUM4160 and PIC32MX460F512L

Keep it safe, keep it sound: USB isolation is the key

USB UART 2 Click with Clicker 2 for PIC32MX

Published Nov 07, 2023

Click board™

USB UART 2 Click

Development board

Clicker 2 for PIC32MX

Compiler

NECTO Studio

MCU

PIC32MX460F512L

Enhance the longevity and reliability of your devices by implementing our USB isolation solution, which shields them from power fluctuations

A

A

Hardware Overview

How does it work?

USB UART 2 Click is based on the ADUM4160, a USB port isolator from Analog Devices. The click is designed to run on either 3.3V or 5V power supply. It communicates with the target microcontroller over UART interface, with additional functionality provided the following pins on the mikroBUS™ line: RST, CS, PWM, INT. Use the USB UART 2 click for isolating USB communication, and preventing voltage spikes from destroying sensitive equipment. The ADUM4160BRWZ is a USB port isolator, based on Analog Devices, iCoupler® technology. Combining high-speed CMOS and

monolithic air core transformer technology, these isolation components provide outstanding performance characteristics and are easily integrated with low and full speed USB-compatible peripheral devices. The ADUM4160BRWZ uses the edge detection based iCoupler technology in conjunction with internal logic to implement a transparent, easily configured, upstream facing port isolator. Isolating an upstream facing port provides several advantages in simplicity, power management, and robust operation. The click takes power both from

the development system and from the USB, so both sides of the isolator can function. The FT232RL chip on board to act as a USB-UART converter. 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.

USB UART 2 Click top side image
USB UART 2 Click bottom side image

Features overview

Development board

Clicker 2 for PIC32MX is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit MIPS M4K core PIC32 microcontroller, the PIC32MX460F512L from Microchip, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a mikroProg programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and features quickly. Each part of

the Clicker 2 for PIC32MX development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for PIC32MX programming method, using a USB HID mikroBootloader, an external mikroProg connector for PIC32MX programmer, or through an external ICD2/3 programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Mini-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board or using a Li-Polymer battery via an

onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for PIC32MX is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

Clicker 2 for PIC32MX dimensions image

Microcontroller Overview

MCU Card / MCU

default

Architecture

PIC32

MCU Memory (KB)

512

Silicon Vendor

Microchip

Pin count

100

RAM (Bytes)

32768

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
UART CTS
RE2
RST
Sleep Mode
RG13
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Power Enable
RD4
PWM
UART RTS
RE8
INT
UART TX
RF8
TX
UART RX
RF2
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

USB UART 2 Click Schematic schematic

Step by step

Project assembly

Clicker 2 for PIC18FJ front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Clicker 2 for PIC32MX as your development board.

Clicker 2 for PIC18FJ front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Mini B Connector Clicker 2 Access - 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
Flip&Click PIC32MZ MCU step 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 USB UART 2 Click driver.

Key functions:

  • usbuart2_pwr_ctrl - This function sets the click turns click on.

  • usbuart2_set_cts - This function sets CTS pin.

  • usbuart2_send_command - This function is used for sending commands.

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 main.c
 * @brief USB UART 2 Click Example.
 *
 * # Description
 * This example reads and processes data from USB UART 2 clicks.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes driver and power module.
 * 
 * ## Application Task  
 * Reads data and echos it back to device and logs it to board.
 *
 * @author Stefan Ilic
 *
 */

#include "board.h"
#include "log.h"
#include "usbuart2.h"
#include "string.h"

#define PROCESS_BUFFER_SIZE 500

static usbuart2_t usbuart2;
static log_t logger;

static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;

void application_init ( void ) {
    log_cfg_t log_cfg;  /**< Logger config object. */
    usbuart2_cfg_t usbuart2_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 " );
    Delay_ms( 100 );

    // Click initialization.

    usbuart2_cfg_setup( &usbuart2_cfg );
    USBUART2_MAP_MIKROBUS( usbuart2_cfg, MIKROBUS_1 );
    
    err_t init_flag  = usbuart2_init( &usbuart2, &usbuart2_cfg );
    if ( UART_ERROR == init_flag ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    app_buf_len = 0;
    
    usbuart2_pwr_ctrl( &usbuart2, USBUART2_POWER_ON );
    usbuart2_set_cts( &usbuart2, USBUART2_CTS_NO_ACTIVE );
    usbuart2_set_mode( &usbuart2, USBUART2_MODE_NORMAL );
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) {
    app_buf_len = usbuart2_generic_read( &usbuart2, app_buf, PROCESS_BUFFER_SIZE );
    
    if ( app_buf_len > 0 ) {
        log_printf( &logger, "%s", app_buf );
        memset( app_buf, 0, PROCESS_BUFFER_SIZE );
    }
}

void main ( void ) {
    application_init( );

    for ( ; ; ) {
        application_task( );
    }
}

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

Additional Support

Resources