Experience ultra-responsive pulse generation with LTC6993-2 and STM32F091RC
“One-shot” pulse generator
Published Feb 26, 2024
Click board™
One Shot Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Create accurately timed pulses, and ensure synchronized operations in various systems and devices
A
A
Hardware Overview
How does it work?
One Shot Click is based on the LTC6993-2, a monostable multivibrator (also known as a "one-shot" pulse generator) with a programmable pulse width of 1μs to 33.6 seconds from Analog Devices. The LTC6993-2 is part of the TimerBlox® family of versatile silicon timing devices. A single resistor, RSET, programs an internal master oscillator frequency, setting the LTC6993's time base. The output pulse width is determined by this master oscillator and an internal clock divider, NDIV, programmable to eight settings from 1 to 221. The output pulse is initiated by a transition on the trigger input (TRIG). Each part can be configured to generate positive or negative output pulses. The LTC6993-2 has four versions to provide different trigger signal polarity and retrigger capability. Besides that, LTC6993-2 also offers the ability to dynamically adjust the width of the output pulse via a separate control voltage brought to the SET
pin of the IC. A simple trimmer or potentiometer could be used; however, due to reliability reasons, the AD5241 digital potentiometer is used for that purpose on One Shot Click. The word is also about a 256-position digital potentiometer with a low-temperature coefficient (30 ppm/°C) from Analog Devices. The AD5241 communicates with the microcontroller over the standard I2C interface so that the user can easily control and precisely calculate the output pulse width just by simply setting the wiper value in the AD5241 registers. One Shot Click also contains the multi-turn trimmer wired as a resistor divider between V+ and GND and brought to the DIV pin of the LTC6993-2. The DIV pin is the programmable divider and polarity input. The polarity input, which pin voltage is internally converted into a 4-bit result (DIVCODE). The MSB of DIVCODE (POL) determines the polarity of the OUT pins. When
POL = 0, the output produces a positive pulse. When POL = 1, the output produces a negative pulse. That way, the user can easily set the output pulse width range, and polarity by setting the desired voltage on the trimmer mentioned (VR1). This Click also contains test points to ease the user's access to the referent voltage. One can separate the trimmer from the rest of the circuit using the separation switch (SW1), then precisely set and measure the desired voltage and turn the switch back in the ON position. 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 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 One Shot Click driver.
Key functions:
oneshot_get_resistance- This function reads the resistance data from the AD5241 chiponeshot_digital_read_rst- This function reads the digital signal from the RST pinoneshot_digital_write_cs- This function writes the specified digital signal to the CS pin
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
* \brief OneShot Click example
*
* # Description
* This example shows the user how to configure and use the One Shot click. The click has a
* monostable monovibrator which cam generate a pulse of width between 1μs and 33.6 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and click modules. Resistance data,
* acquired from the AD5241, is displayed at the end of the initialization process.
*
* ## Application Task
* This function triggers one shot every 8 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "oneshot.h"
// ------------------------------------------------------------------ VARIABLES
static oneshot_t oneshot;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( )
{
log_cfg_t log_cfg;
oneshot_cfg_t cfg;
/**
* 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.
oneshot_cfg_setup( &cfg );
ONESHOT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
oneshot_init( &oneshot, &cfg );
Delay_100ms( );
oneshot_default_cfg( &oneshot );
Delay_100ms( );
log_printf( &logger, " * Resistance: %.1f Ohm\r\n", oneshot_get_resistance( &oneshot ) );
}
void application_task ( )
{
oneshot_digital_write_cs( &oneshot, 1 );
Delay_ms( 1 );
oneshot_digital_write_cs( &oneshot, 0 );
log_printf( &logger, " * One shot triggered \r\n" );
log_printf( &logger, " --------------------------- \r\n" );
Delay_ms( 8000 );
}
void main ( )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
