Beginner
10 min

Experience a revolution in temperature monitoring thanks to TSYS03 and TM4C129ENCPDT

ThermoSense: Smart. Simple. Precise.

Thermo 20 Click with Fusion for Tiva v8

Published Nov 11, 2023

Click board™

Thermo 20 Click

Dev.Board

Fusion for Tiva v8

Compiler

NECTO Studio

MCU

TM4C129ENCPDT

Measuring heat with ease has never been simpler, thanks to our innovative temperature monitoring solution.

A

A

Hardware Overview

How does it work?

Thermo 20 Click is based on the TSYS03, an ultra-compact digital temperature sensor with precise digital output and low power consumption from TE Connectivity. The TSYS03 is factory-calibrated and provides accurate temperature measurements through several I2C configurable addresses. Operating from a supply voltage between 2.4V and 5.5V and drawing just 5µA Thermo 20 Click board™ is well suited for battery-powered and automotive applications. With an extended operating range from -40°C to +125°C, the TSYS03 provides digital temperature measurements that offer an accuracy of ±0.5°C when operating at ambient temperatures between 0°C and 60°C. The TSYS03 consists of a semiconductor

diode as a measuring element, which was integrated into an ASIC. The temperature is obtained from the voltage that drops across the diode and through an A/D converter with a 16-bit resolution. The output is obtained as a digital value via a configurable I2C interface. The TSYS03 impresses with its high accuracy, current consumption lower than 5 µA, and low self-heating of max. 0.1 °C. Thermo 20 Click communicates with MCU using the standard I2C 2-Wire interface with a maximum clock frequency of 1MHz. The standard I2C address is 0x40, but the sensor can also react to a second, alternative I2C address. It is possible to do one-time subsequent writing of an alternative static I2C address.

This leads to a wrong memory CRC, but the sensor is still functional. It is also possible to write an alternative I2C address to the sensor during operation. This address is temporary and is overwritten during a software reset or a hardware restart function. 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.

Thermo 20 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

128

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
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
PD2
SCL
I2C Data
PD3
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Thermo 20 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 Thermo 20 Click driver.

Key functions:

  • thermo20_set_cmd - Send command function.

  • thermo20_start_conversion - Start conversion function.

  • thermo20_get_temperature - Get temperature data 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 Thermo20 Click example
 *
 * # Description
 * This example showcases the ability of Thermo 20 Click board to
 * read it's serial number. It can read themperature and measure from -40degC to
 * 120degC.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization communication modules(I2C, UART). Resets device and read Serial Number.
 *
 * ## Application Task
 * In span of ~ 1000ms it sends command for adc conversion of temperature, reads ADC value,
 * and calculates temperature in degrees C.
 * 
 * @note For this driver to work on 18bit PIC MCU-s you need to additionally pull up communication lines.
 *
 * @author Mikroe Team
 *
 */

#include "board.h"
#include "log.h"
#include "thermo20.h"

static thermo20_t thermo20;
static log_t logger;

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    thermo20_cfg_t thermo20_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.
    thermo20_cfg_setup( &thermo20_cfg );
    THERMO20_MAP_MIKROBUS( thermo20_cfg, MIKROBUS_1 );
    err_t init_flag = thermo20_init( &thermo20, &thermo20_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) 
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    thermo20_default_cfg ( &thermo20 );
    
    uint32_t ser_numb = thermo20_get_serial_number( &thermo20 );
    log_printf( &logger, " > Serial Number: %lu\r\n", ser_numb );
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    thermo20_start_conversion( &thermo20 );
    
    float temperature = thermo20_get_temperature( &thermo20 );
    
    log_printf( &logger, " > Temperature[deg C]: %.2f\r\n", temperature );
    
    Delay_ms( 1000 );
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) 
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources