Ensure stable and protected power delivery with HS2950P and MK64FN1M0VDC12
Load protection HotSwitch® for various load conditions
Published Dec 27, 2023
Click board™
Current Limit 10 Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Keep your electronic device safe by controlling the amount of electrical current it uses and protecting it from voltage-related issues
A
A
Hardware Overview
How does it work?
Current Limit 10 Click is based on the HS2950P, a load protection HotSwitch from Semtech. It utilizes flexible and programmable protection features and can handle multiple fault conditions. During fault conditions, automatic output discharge will be activated, thus protecting the load, and the HS2950P will automatically restart from a fault condition. The under-voltage lockout threshold is set to the default position (2.6V). The overvoltage protection can be externally set over the OVP SEL jumper, choosing between values 5.44V, 12.36V,
and 24.13V. The OVP is set by default to 5.44V. The current limit threshold can be set over the MAX5419, a nonvolatile digital potentiometer from Analog Devices. You can also choose the onboard external resistor for a fixed 0.5A value. The selection can be made over the ILIM SEL jumper. The soft start time is set to 0.32 ms, and the turn-on delay is set to 4 ms. Current Limit 10 Click uses a standard 2-wire I2C interface of the MAX5419 to allow the host MCU to set the limit threshold. The HS2950P will alert the host MCU when the fault
condition occurs over the FLT pin, along with the FLT LED indicator. Finally, you can turn off the current limiter over the enable EN pin. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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.
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
Click board™ 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
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Current Limit 10 Click driver.
Key functions:
currentlimit10_set_limit- This function sets the desired current limit threshold using the I2C serial interface.currentlimit10_get_fault- This function gets the state of the fault flag to indicate overcurrent, overtemperature, or reverse-voltage conditions.currentlimit10_enable- This function turns on the power switch and enables the internal MOSFET.
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief Current Limit 10 Click example
*
* # Description
* This library contains API for the Current Limit 10 Click driver for the current limiting
* to a certain value and displays the sources a current proportional to the load current [A].
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of I2C module and log UART.
* After driver initialization, the app executes a default configuration.
*
* ## Application Task
* This example demonstrates the use of the Current Limit 10 Click board.
* The demo application sets the current limit threshold of 750 mA and
* checks the fault flag for overcurrent conditions.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "currentlimit10.h"
static currentlimit10_t currentlimit10;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
currentlimit10_cfg_t currentlimit10_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.
currentlimit10_cfg_setup( ¤tlimit10_cfg );
CURRENTLIMIT10_MAP_MIKROBUS( currentlimit10_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == currentlimit10_init( ¤tlimit10, ¤tlimit10_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( CURRENTLIMIT10_ERROR == currentlimit10_default_cfg ( ¤tlimit10 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
Delay_ms( 100 );
}
void application_task ( void )
{
if ( CURRENTLIMIT10_OK == currentlimit10_set_limit( ¤tlimit10, 0.75 ) )
{
Delay_ms( 100 );
if ( CURRENTLIMIT10_FAULT_FLAG == currentlimit10_get_fault( ¤tlimit10 ) )
{
log_printf( &logger, "Fault flag: Overcurrent\r\n" );
Delay_ms( 100 );
}
else
{
log_printf( &logger, " Current limit is 0.75 A\r\n" );
Delay_ms( 100 );
}
}
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
