Intermediate
30 min

Experience ultra-responsive pulse generation with LTC6993-2 and TM4C129XNCZAD

“One-shot” pulse generator

One Shot Click with Fusion for Tiva v8

Published Aug 09, 2023

Click board™

One Shot Click

Dev Board

Fusion for Tiva v8

Compiler

NECTO Studio

MCU

TM4C129XNCZAD

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.

One Shot Click hardware overview image

Features overview

Development board

Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access

anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.

Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 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.

Fusion for Tiva v8 horizontal image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

ARM Cortex-M4

MCU Memory (KB)

1024

Silicon Vendor

Texas Instruments

Pin count

212

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Output Signal
PB6
RST
Trigger Input
PE7
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB2
SCL
I2C Data
PB3
SDA
Power supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

One Shot Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Fusion for Tiva v8 as your development board.

Fusion for PIC v8 front image hardware assembly
Buck 22 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
v8 SiBRAIN MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

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 chip

  • oneshot_digital_read_rst - This function reads the digital signal from the RST pin

  • oneshot_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

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.