Intermediate
30 min
0

Verify your connections easily and save valuable time during the debugging phase using TM4C1299NCZAD

Effortless diagnostics: The ultimate tool for logic level confirmation

Tester Click with UNI Clicker

Published Oct 14, 2023

Click board™

Tester Click

Development board

UNI Clicker

Compiler

NECTO Studio

MCU

TM4C1299NCZAD

Our mission is to empower developers with a convenient and user-friendly diagnostic tool that simplifies the hardware testing process, ensuring a smoother development journey

A

A

Hardware Overview

How does it work?

Tester Click is a Click board™ used as a diagnostic tool on the mikroBUS™ socket. It contains an array of 2x6 LEDs, which signalize the presence of the HIGH/LOW logic level on each pin, providing a visual feedback to the developer. Two additional LEDs indicate the presence of +3.3V and +5V on the mikroBUS™ power rails. This simple diagnostic tool can save hours of troubleshooting, saving the

application developer from having to connect various complicated measurement instruments, only to test logic states on the specific mikroBUS™ pins. Each pin of the mikroBUS™ is routed to a red colored LED, which is protected by 1K resistor. This allows voltages up to VCC to be handled with no issues, providing a simple and clean solution for pin state testing. Once placed on the mikroBUS™

socket, no additional settings are required. There are no ICs or other active elements besides the LEDs. Its simplicity makes it very simple to use: as soon as it is connected, red and green power indication LEDs will signalize the presence of +3.3V and +5V on both the mikroBUS™ power rails. The rest of the LED array will be lit according to the state on the respective pin.

Tester Click top side image
Tester Click bottom side image

Features overview

Development board

UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build

gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li

Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker 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.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU

default

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

Analog Output
PE3
AN
Reset
PB6
RST
SPI Chip Select
PE7
CS
SPI Clock
PA2
SCK
SPI Data OUT
PA5
MISO
SPI Data IN
PA4
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
PWM Input
PD0
PWM
Interrupt
PB4
INT
UART TX
PA1
TX
UART RX
PA0
RX
I2C Clock
PB2
SCL
I2C Data
PB3
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Tester Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
Thermo 28 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
UNI Clicker MB 1 - upright/with-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 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 Tester Click driver.

Key functions:

  • tester_set_pin_high - This function sets the output voltage on the specified pin to high

  • tester_set_pin_low - This function sets the output voltage on the specified pin to low

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 Tester Click example
 * 
 * # Description
 * This example showcases how to initialize, configure and use the Tester click. It is a simple
 * GPIO click which is used to test if all the pins on a MikroBUS are working correctly.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * This function initializes and configures the click and logger modules.
 * 
 * ## Application Task  
 * This function sets the output on all the pins (one by one) on the left side to high, going
 * from top to bottom and then does the same with the ones on the right side, after which it 
 * sets all pins to high and after one second sets them back to low. 
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "tester.h"

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

static tester_t tester;
static log_t logger;

static digital_out_t *pin_addr[ 12 ] =
{
    &tester.mosi,    // 0 MOSI
    &tester.miso,    // 1 MISO
    &tester.sck,     // 2 SCK
    &tester.cs,      // 3 CS
    &tester.rst,     // 4 RST
    &tester.an,      // 5 AN
    &tester.pwm,     // 6 PWM
    &tester.int_pin, // 7 INT
    &tester.tx_pin,  // 8 TX
    &tester.rx_pin,  // 9 RX
    &tester.scl,     // 10 SCL
    &tester.sda      // 11 SDA
};

// ------------------------------------------------------- ADDITIONAL FUNCTIONS

static void blink ( digital_out_t *pin ) 
{
    tester_set_pin_high( pin );
    Delay_100ms( );
    tester_set_pin_low( pin );
}

static void all_on ( )
{
   int i;

   for( i = 0; i < 12; i++ )
   {
        tester_set_pin_high( pin_addr[ i ] );
   }
}

static void all_off ( )
{
   int i;

   for( i = 0; i < 12; i++ )
   {
        tester_set_pin_low( pin_addr[ i ] );
   }
}

// ------------------------------------------------------ APPLICATION FUNCTIONS

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

    tester_cfg_setup( &cfg );
    TESTER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    tester_init( &tester, &cfg );
}

void application_task ( )
{
    int i;

    for( i = 0; i < 12; i++ )
    {
        blink( pin_addr[ i ] );
    }

    all_on( );
    Delay_1sec( );
    all_off( );
}

void main ( )
{
    application_init( );

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

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

Additional Support

Resources