Control the flow of power to connected loads (resistive, inductive, and capacitive) with with BV2HD070EFU-C and ATmega324P
AEC-Q100 qualified (Grade 1) two-channel high-side switch for controlling various loads
Published Dec 12, 2024
Click board™
IPD 2 Click
Dev. board
EasyAVR v7
Compiler
NECTO Studio
MCU
ATmega324P
High-side switching with advanced protection and diagnostics perfect for automotive lighting, motor control, and solenoid applications
A
A
Hardware Overview
How does it work?
IPD 2 Click is based on the BV2HD070EFU-C, an automotive-grade two-channel high-side switch from ROHM Semiconductor, designed to handle resistive, inductive, and capacitive loads in automotive applications. The BV2HD070EFU-C features a 70mΩ on-resistance high-side switch and incorporates advanced protection and diagnostic functionalities to ensure reliable operation in demanding environments. This Click board™ is particularly suitable for automotive applications, supporting various types of loads such as lights, solenoids, and motors. It provides an efficient, reliable, and compact solution for high-side switching requirements, ensuring stable performance and enhanced safety in automotive systems. The BV2HD070EFU-C is AEC-Q100 qualified (Grade 1) and operates across a wide input voltage range of 6V to 28V, supplied via the VDD terminal. Its comprehensive protection suite includes overcurrent detection (OCD) with a
configurable mask function, ensuring precise fault management and preventing unintended load disconnection. Additional safety features include thermal shutdown protection, which halts operation under excessive temperature conditions, and undervoltage lockout (UVLO) to safeguard against unstable power supply conditions. Moreover, the switch includes an open load detection function, providing feedback when the load is disconnected or the circuit is incomplete. This Click board™ uses several pins of the mikroBUS™ socket for control and diagnostics. The IN1 and IN2 pins serve as control signals, enabling activation of the respective outputs marked as 1 and 2 on the output OUT terminal. For monitoring and fault detection, the board includes a diagnostic output function accessible via the ST1 and ST2 pins of the mikroBUS™ socket, providing real-time feedback on abnormalities. In addition to these control and diagnostic pins, the board features two
configuration jumpers. The first, SET SEL, allows users to configure the overcurrent limit between 1A and the default value of 2.3A. While the BV2HD070EFU-C supports overcurrent limits of up to approximately 10A, users can achieve this by replacing the selected resistance as specified in the datasheet recommendations. The second jumper, VOC SEL, activates a functionality that optimizes the time required to achieve precise overcurrent protection for the connected load. This feature is enabled by default, ensuring enhanced load safety and performance without additional configuration. 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. It also comes equipped with a library containing functions and example code that can be used as a reference for further development.
Features overview
Development board
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 EasyAVR v7 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 IPD 2 Click driver.
Key functions:
ipd2_enable_out1- This function enables OUT1 by setting the IN1 pin to high logic state.ipd2_disable_out1- This function disables OUT1 by setting the IN1 pin to low logic state.ipd2_get_st1_pin- This function returns the ST1 pin logic state.
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 IPD 2 Click Example.
*
* # Description
* This example demonstrates the use of IPD 2 Click by toggling the output state.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Toggles OUT1 and OUT2 state every 3 seconds and displays both outputs state and
* status diagnostics pin state. If the status pin is HIGH it indicates that the fault
* condition on this output has occurred and the output is disabled.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "ipd2.h"
static ipd2_t ipd2; /**< IPD 2 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
ipd2_cfg_t ipd2_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.
ipd2_cfg_setup( &ipd2_cfg );
IPD2_MAP_MIKROBUS( ipd2_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == ipd2_init( &ipd2, &ipd2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
ipd2_enable_out1 ( &ipd2 );
ipd2_disable_out2 ( &ipd2 );
Delay_ms ( 100 );
log_printf( &logger, " OUT1: enabled\r\n" );
log_printf( &logger, " OUT2: disabled\r\n" );
log_printf( &logger, " ST1: %s\r\n", ( char * ) ( ipd2_get_st1_pin ( &ipd2 ) ? "high" : "low" ) );
log_printf( &logger, " ST2: %s\r\n\n", ( char * ) ( ipd2_get_st2_pin ( &ipd2 ) ? "high" : "low" ) );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
ipd2_disable_out1 ( &ipd2 );
ipd2_enable_out2 ( &ipd2 );
Delay_ms ( 100 );
log_printf( &logger, " OUT1: disabled\r\n" );
log_printf( &logger, " OUT2: enabled\r\n" );
log_printf( &logger, " ST1: %s\r\n", ( char * ) ( ipd2_get_st1_pin ( &ipd2 ) ? "high" : "low" ) );
log_printf( &logger, " ST2: %s\r\n\n", ( char * ) ( ipd2_get_st2_pin ( &ipd2 ) ? "high" : "low" ) );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
