Verify your connections easily and save valuable time during the debugging phase using MK64FN1M0VDC12
Effortless diagnostics: The ultimate tool for logic level confirmation
Published Oct 14, 2023
Click board™
Tester Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
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.
Features overview
Development board
Clicker 2 for Kinetis 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 ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG 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 Kinetis 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 Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis 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 Micro-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 Kinetis 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.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
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 hightester_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
