Ensure your devices perform at their peak with NIS6150 and STM32F091RC
eFuse: Unlock reliability, enhance efficiency
Published Feb 26, 2024
Click board™
eFuse 3 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Experience enhanced reliability and efficiency with our cutting-edge eFuse device, where voltage and current are managed effortlessly to safeguard your devices and elevate their performance
A
A
Hardware Overview
How does it work?
eFuse 3 Click is based on the NIS6150, a self-protected, resettable electronic fuse from ON Semiconductor that contains circuits to monitor the input voltage, output voltage, output current, and die temperature. It has an ENABLE feature with a separate ‘flag’ for fault identification, adjustable output current-limit protection with a thermal shutdown, and a current monitoring pin. The NIS6150 also includes an internal temperature sensing circuit that senses the temperature on the die of the power FET. If the temperature reaches 175°C, the device will shut down and remove power from the load. This Click board™ communicates with MCU through the 3-Wire SPI serial interface using the MCP3551, a 22-bit sigma-delta ADC from Microchip. The MCP3551 is used for current monitoring purposes by converting the output current from the NIS6150 IMON pin with a very high resolution of 22 bits and low noise to digital data, which can be obtained via the SPI interface of the Click board™. This ADC uses the
reference voltage, the 4.096V reference voltage level provided by the MCP1541 from Microchip powered from the +5V mikroBUS™ power rail, resulting in high accuracy and stability. A resistor that connects to the middle connector on this Click board™, labeled as Rlim, sets the overload and short circuit current limit levels. The VSL pin routed to the RST pin on the mikroBUS™ socket allows the overvoltage clamp to be set at a 5.7V or 6.5V minimum by pulling this pin to a low logic state. It monitors the output voltage, and if the input exceeds the output voltage, the gate drive of the main FET is reduced to limit the output. This is intended to allow operation through transients while protecting the load. If an overvoltage condition exists for many seconds, the device may overheat due to the voltage drop across the FET combined with the load current. In this event, the thermal protection circuit would shut down the device. The eFuse 3 Click also has two active additional pins of the mikroBUS™ socket, the INT
and PWM pins labeled as FLG and EN. The Enable feature, routed to the PWM pin on the mikroBUS™ socket, provides a digital interface to control the output of the eFuse. That’s why when this pin is pulled to a low logic state - the eFuse is turned OFF. On the other hand, the ‘flag’ pin routed to the INT pin on the mikroBUS™ socket sends information to the MCU regarding the state of the chip. If a thermal fault occurs, the voltage on this pin will go to a low state to signal a monitoring circuit that the device is in thermal shutdown. 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
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo-64 with STM32F091RC MCU 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 eFuse 3 Click driver.
Key functions:
efuse3_get_current- eFuse 3 get current functionefuse3_get_flag- eFuse 3 get flag functionefuse3_reset- eFuse 3 reset function
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 eFuse3 Click example
*
* # Description
* This library contains API for the eFuse 3 Click driver.
* The library contains drivers to enable/disable the device,
* for reading ADC voltage, overflow status, output and current value [ A ].
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI driver and set default configuration.
*
* ## Application Task
* This is an example that demonstrates the use of the eFuse 3 Click board.
* Read and display device status information and current value [ A ].
* The eFuse 3 includes an overvoltage clamp the circuit that limits the output voltage
* during transients but does not shut the unit down,
* thereby allowing the load circuit to continue its operation.
* The Electronic Fuse is to limit current and current limit
* Current limit ( 0.1 A - 1.8 A ) depends on the choice of resistor wired
* on the Rlimit ( 1 Ohm - 15 Ohm ) connector.
* For example, for Rlimit resistance of 1 Ohm, current limit is 1 A
* ( 3.5 Ohm - 0.5 A, 7 Ohm - 0.25 A ).
* Read details from the ON Semiconductor NIS6150 datasheets.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "efuse3.h"
static efuse3_t efuse3;
static log_t logger;
static float voltage;
static float current;
static uint8_t overflow_status;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
efuse3_cfg_t efuse3_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.
efuse3_cfg_setup( &efuse3_cfg );
EFUSE3_MAP_MIKROBUS( efuse3_cfg, MIKROBUS_1 );
err_t init_flag = efuse3_init( &efuse3, &efuse3_cfg );
if ( init_flag == SPI_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
efuse3_default_cfg ( &efuse3 );
log_info( &logger, " Application Task " );
log_printf( &logger, "---------------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void ) {
log_printf( &logger, " Status :" );
if ( efuse3_get_flag( &efuse3 ) == EFUSE3_FLAG_NORMAL_OPERATION ) {
log_printf( &logger, " Normal operation \r\n" );
} else {
log_printf( &logger, " Device OFF \r\n" );
if ( overflow_status == EFUSE3_OVERFLOW_HIGH ) {
log_printf( &logger, " Overflow high in the analog input voltage.\r\n" );
} else if ( overflow_status == EFUSE3_OVERFLOW_LOW ) {
log_printf( &logger, " Overflow low in the analog input voltage.\r\n" );
}
efuse3_reset( &efuse3 );
Delay_ms( 1000 );
}
log_printf( &logger, "- - - - - - - - - - - - - - \r\n" );
efuse3_get_current( &efuse3, ¤t );
log_printf( &logger, " Current : %.5f A\r\n", current );
log_printf( &logger, "---------------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
