Monitor and regulate the performance of various hardware components with LM96080 and STM32F091RC
Your system's guardian
Published Feb 26, 2024
Click board™
HW Monitor Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Ensure the stability and performance of your embedded solutions
A
A
Hardware Overview
How does it work?
HW Monitor Click is based on the LM96080, a system hardware monitor from Texas Instruments that performs power supply, temperature, and fan monitoring for various embedded systems. The LM96080 provides seven analog inputs spread across the terminals on the top of the board labeled from IN0 to IN6, a temperature sensor, a delta-sigma ADC, two fan speed counters, watchdog registers, and a variety of inputs and outputs on a single chip. It continuously converts analog inputs to 10-bit resolution with a 2.5mV LSB, yielding input ranges of 0 to 2.56V. The analog inputs are intended to be connected to the several power supplies present in a typical communications infrastructure system. This Click board™ communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings with a maximum frequency of 400kHz. The LM96080 includes an analog filter on the I2C lines that improves noise immunity and supports the timeout reset function on SDA and SCL pins, preventing I2C bus lockup. Also, the LM96080 allows choosing the least significant bits (LSB) of its I2C slave address using the SMD jumpers labeled ADDR SEL. The LM96080 is especially suited to interface with linear and digital temperature sensors such as LM73, LM75, LM56, LM57,
LM26, LM27, LM26LV, or other LM96080 via the BTI pin on one of the unpopulated headers. Temperature can be converted to a 9-bit or 12-bit two's complement word with resolutions of 0.5°C or 0.0625°C LSB, respectively. On the same header, in addition to the BTI pin, there is also a GPI pin, which, in addition to its function as a general-purpose input pin, can also serve as a chassis intrusion detection input. The chassis intrusion input is designed to accept an active high signal from an external circuit that latches, such as when the cover is removed from the computer. Next in this board's series of additional features are the fan inputs, labeled FAN1 and FAN2, that can be programmed to accept either fan failure indicator programmed to be active high or active low or tachometer signals. Fan inputs measure the period of tachometer pulses from the fans, providing a higher count for lower fan speeds. The full-scale fan counts are 255 (8-bit counter), representing a stopped or slow fan. Based on a count of 153, nominal speeds are programmable from 1100 to 8800 RPM. Signal conditioning circuitry is also included to accommodate the slow rise and fall times. The last header contains functions such as an external interrupt input INT IN, a master reset for external purposes RST OUT,
and a single power switch pin GPO. The INT IN active low interrupt provides a way to chain the interrupts from other devices through the LM96080 to the host, the RST_OUT is intended to provide a master reset to devices connected to this line, while the GPO pin is an active low NMOS open drain output intended to drive an external power PMOS for software power control or can be utilized to control power to a cooling fan. The LM96080 also possesses a general reset signal routed on the RST pin of the mikroBUS™ socket to reset the LM96080, and an additional interrupt signal, routed on the INT pin of the mikroBUS™ socket whenever some of the external interrupts like INT_OUT, interrupt from the temperature sensor, or when a chassis detection event occurs. 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. However, the 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 HW Monitor Click driver.
Key functions:
hwmonitor_get_analog_inputsHW Monitor gets analog inputs voltage function.hwmonitor_get_temperatureHW Monitor gets temperature function.hwmonitor_set_configHW Monitor set the configuration 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 HW Monitor Click example
*
* # Description
* This example demonstrates the use of the HW Monitor Click board™.
* The demo application monitors analog voltage inputs and local temperature data.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The initialization of the I2C module, log UART and additional pins.
* After the driver init, the app executes a default configuration.
*
* ## Application Task
* This example displays the Analog Voltage Inputs (IN0-IN6) [mV]
* and Temperature [degree Celsius] data.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "hwmonitor.h"
static hwmonitor_t hwmonitor;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hwmonitor_cfg_t hwmonitor_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.
hwmonitor_cfg_setup( &hwmonitor_cfg );
HWMONITOR_MAP_MIKROBUS( hwmonitor_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == hwmonitor_init( &hwmonitor, &hwmonitor_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( HWMONITOR_ERROR == hwmonitor_default_cfg ( &hwmonitor ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
static float temperature, voltage;
for ( uint8_t in_pos = 0; in_pos < 7; in_pos++ )
{
if ( HWMONITOR_OK == hwmonitor_get_analog_inputs( &hwmonitor, in_pos, &voltage ) )
{
log_printf( &logger, "IN %d: %.1f mV\r\n", ( uint16_t ) in_pos, voltage );
Delay_ms( 100 );
}
}
log_printf( &logger, "- - - - - - - - - - - - - -\r\n" );
if ( HWMONITOR_OK == hwmonitor_get_temperature ( &hwmonitor, &temperature ) )
{
log_printf( &logger, " Temperature: %.3f [deg c]\r\n", temperature );
Delay_ms( 100 );
}
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
