Enhance your electrical control with TPS22918 and STM32F091RC combo
Revolutionize your electrical control with solid-state relays
Published Feb 26, 2024
Click board™
SolidSwitch Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Experience a new era of electrical control with our solid-state relay innovations, designed to meet the demands of modern technology
A
A
Hardware Overview
How does it work?
SolidSwitch Click is based on the TPS22918, a 5.5V 2A load switch from Texas Instruments. To reduce voltage drop for low voltage and high current rails, every TPS22918 implements a low resistance N-channel MOSFET, reducing the drop-out voltage across the device. An ON/OFF input on the ON pin of the TPS22918 controls the switches. The ON pin is compatible with the standard GPIO logic threshold and can be used with any MCU with 1V or higher GPIO voltage. That’s why the control of all switches is established via the port expander, the MAX7323. This Click board™ is designed to operate from an external supply voltage range from 1V to 5.5V. The TPS22918 works regardless of power sequencing order. The order in which
voltages are applied to the VIN terminal and ON pin of the load switch will not damage the device as long as the voltages stay within the absolute maximum operating conditions. SolidSwitch Click communicates with MCU through the MAX7323 port expander using the standard I2C 2-Wire interface with a frequency of up to 400kHz. It also has two address pins (A0 and A1) programmed by the user to determine the value of the last two LSBs of the slave address, selected by onboard SMD jumpers labeled as ADDR SEL to an appropriate position marked as 0 and 1, allowing selection of the slave address LSBs. Also, this Click board™ has a Reset pin, routed to the RST pin on the mikroBUS™ socket, which clears the serial
interface in case of a bus lockup, terminating any serial transaction to or from the MAX7323. Also, it uses an additional pin, the INT pin of the mikroBUS™ socket, which automatically flags data changes on any of the I/O ports of the MAX7323 used as inputs. The interrupt output INT and all transition flags are de-asserted when the MAX7323 is accessed through the serial interface. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing 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
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 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 SolidSwitch Click driver.
Key functions:
solidswitch_write_single- SolidSwitch I2C writing logic state function.solidswitch_read_single- SolidSwitch I2C reading logic state function.solidswitch_reset- Click Default Configuration function.
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 main.c
* @brief SolidSwitch Click example
*
* # Description
* This example demonstrates the use of SolidSwitch click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger and enables the click board.
*
* ## Application Task
* Enables different outputs every 3 seconds and displays all enabled
* outputs on USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "solidswitch.h"
static solidswitch_t solidswitch;
static log_t logger;
/**
* @brief Displays all enabled channels on USB UART.
* @details This function reads logic state of outputs and
* displays all enabled channels on USB UART.
*
* @return None.
* @note None.
*/
static void solidswitch_display_enabled_channels ( void );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
solidswitch_cfg_t solidswitch_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.
solidswitch_cfg_setup( &solidswitch_cfg );
SOLIDSWITCH_MAP_MIKROBUS( solidswitch_cfg, MIKROBUS_1 );
err_t init_flag = solidswitch_init( &solidswitch, &solidswitch_cfg );
if ( init_flag == I2C_MASTER_ERROR )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
solidswitch_default_cfg ( &solidswitch );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
solidswitch_write_single ( &solidswitch, SOLIDSWITCH_ENABLE_OUT0 | SOLIDSWITCH_ENABLE_OUT1 );
solidswitch_display_enabled_channels( );
Delay_ms ( 3000 );
solidswitch_write_single ( &solidswitch, SOLIDSWITCH_ENABLE_OUT6 | SOLIDSWITCH_ENABLE_OUT7 );
solidswitch_display_enabled_channels( );
Delay_ms ( 3000 );
solidswitch_write_single ( &solidswitch, SOLIDSWITCH_ENABLE_ALL_OUTPUTS );
solidswitch_display_enabled_channels( );
Delay_ms ( 3000 );
solidswitch_write_single ( &solidswitch, SOLIDSWITCH_DISABLE_ALL_OUTPUTS );
solidswitch_display_enabled_channels( );
Delay_ms ( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void solidswitch_display_enabled_channels ( void )
{
uint8_t logic_state;
uint8_t enabled_flag = 0;
solidswitch_read_single ( &solidswitch, &logic_state );
log_printf( &logger, " Outputs enabled: " );
for ( uint8_t cnt = 0; cnt < 8; cnt++ )
{
if ( logic_state & 1 )
{
if ( enabled_flag == 1 )
{
log_printf( &logger, ", %u", ( uint16_t ) cnt );
}
else
{
log_printf( &logger, " %u", ( uint16_t ) cnt );
}
enabled_flag = 1;
}
logic_state >>= 1;
}
if ( enabled_flag == 0 )
{
log_printf( &logger, " none" );
}
log_printf( &logger, "\r\n-----------------------\r\n" );
}
// ------------------------------------------------------------------------ END
