Beginner
10 min

Implement iButton™ technology into your projects with CZ-0-PIN and STM32L073RZ

Secure and reliable data transfer with a simple touch

iButton Click with Nucleo-64 with STM32L073RZ MCU

Published Mar 15, 2024

Click board™

iButton Click

Dev Board

Nucleo-64 with STM32L073RZ MCU

Compiler

NECTO Studio

MCU

STM32L073RZ

Create systems that require secure, physical touchpoints for data transfer or user identification

A

A

Hardware Overview

How does it work?

iButton Click is based on the CZ-0-PIN, a high-quality iButton probe from Demiurge. The metal probe ensures resistance to dirt, dust, moisture, shock, and other environmental hazards while ensuring good alignment with the iButton device. The manufacturer guarantees compatibility with Analog iButton devices, but the probe can read any other device compatible with the maxim iButton. The iButton device can power itself up through the data line by employing the so-called parasite power supply. This Click board™ is equipped with the pull-up resistor to the 3.3V mikroBUS™ rail, providing power for the iButton. The so-called parasite PSU of the iButton contains an internal capacitor, which

provides enough current for the proper operation once the data line has charged. To allow proper functioning of the parasitic PSU, the idle state of the data line is HIGH, while the data line of the iButton device is in an open-drain configuration, pulling the data line to a LOW logic level when asserted. The 1-Wire communication line is routed to the SMD jumper, which allows routing of the 1-Wire communication either to the PWM pin or to the AN pin of the mikroBUS™. These pins are labeled GP0 and GP1, respectively, the same as the SMD jumper positions, making the selection of the desired pin simple and straightforward. The green LED labeled as ST1 is routed to the RST pin of the

mikroBUS™, while the red LED is labeled as ST2 and is routed to the CS pin of the mikroBUS™. These two pins allow visual feedback from the software; for example, if the serial number of the docked iButton matches the authorization criteria, the green LED can signal it. These LEDs can be used for any signalization and are not directly connected to the iButton device. 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 for further development.

iButton? Click hardware overview image

Features overview

Development board

Nucleo-64 with STM32L073RZ 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.

Nucleo 64 with STM32L073RZ MCU double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M0

MCU Memory (KB)

192

Silicon Vendor

STMicroelectronics

Pin count

64

RAM (Bytes)

20480

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.

Click Shield for Nucleo-64 accessories 1 image

The DS1990A is a unique serial number identification iButton™. The iButton is a technology based on the one-wire communication protocol and a chip packed in a robust stainless steel casing. This button-shaped device has two contacts - the lid and the base. These contacts carry the necessary connections down to a sensitive silicone chip embedded inside the metal button. When the iButton touches the reader probe, it establishes the communication with the host MCU via the one-wire interface. The communication is almost instant, so pressing the iButton lightly to the probe contacts is enough.

iButton Click accessories 1 image

Used MCU Pins

mikroBUS™ mapper

1-Wire Data IN/OUT
PC0
AN
Status 2 Indicator
PC12
RST
Status 1 Indicator
PB12
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
1-Wire Data IN/OUT
PC8
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
NC
NC
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

iButton? Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-64 accessories 1 image hardware assembly

Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32L073RZ MCU as your development board.

Click Shield for Nucleo-64 accessories 1 image hardware assembly
Nucleo 64 with STM32F401RE MCU front image hardware assembly
LTE IoT 5 Click front image hardware assembly
Prog-cut hardware assembly
LTE IoT 5 Click complete accessories setup image hardware assembly
Nucleo-64 with STM32XXX MCU Access MB 1 Mini B Conn - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Clicker 4 for STM32F4 HA MCU Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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 iButton Click driver.

Key functions:

  • ibutton_add_key - This function reads the ROM address from a DS1990A Serial Number iButton and stores it in the ctx->key_rom buffer

  • ibutton_remove_keys - This function removes all stored keys by clearing the ctx->key_rom buffer

  • ibutton_check_key - This function reads the ROM address from a DS1990A Serial Number iButton and checks if it is already stored in the ctx->key_rom buffer

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 iButton Click Example.
 *
 * # Description
 * This example demonstrates the use of the iButton click boards by registering a DS1990A Serial Number iButton
 * key and then waiting until a key is detected on the reader and identifying if the key matches one of
 * those stored in RAM.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes the driver and registers a new DS1990A Serial Number iButton key and stores it in RAM.
 * 
 * ## Application Task  
 * Waits until a key is detected on the reader, and checks if there's a key found in the library that matches
 * the one it has just read. All data is being logged on the USB UART where you can track the program flow.
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "ibutton.h"

#define NUMBER_OF_KEYS  1   // Number of keys to register.

static ibutton_t ibutton;
static log_t logger;

/**
 * @brief iButton led indication function.
 * @details This function indicates the selected state over LEDs indication.
 * @param[in] ctx : Click context object.
 * See #ibutton_t object definition for detailed explanation.
 * @param[in] state : @li @c 0 - Disable LEDs.
 *                    @li @c 1 - Wait for a key.
 *                    @li @c 2 - Operation successfull.
 *                    @li @c 3 - Wrong key found.
 * @return None.
 * @note None.
 */
static void ibutton_led_indication ( ibutton_t *ctx, ibutton_led_state_t state );

/**
 * @brief iButton register keys function.
 * @details This function registers a desired number of keys.
 * Each step will be logged on the USB UART where you can track the function flow.
 * @param[in] ctx : Click context object.
 * See #ibutton_t object definition for detailed explanation.
 * @param[in] num_keys : Number of keys to register.
 * @return None.
 * @note None.
 */
static void ibutton_register_keys ( ibutton_t *ctx, uint8_t num_keys );

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    ibutton_cfg_t ibutton_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.
    ibutton_cfg_setup( &ibutton_cfg );
    IBUTTON_MAP_MIKROBUS( ibutton_cfg, MIKROBUS_1 );
    if ( ONE_WIRE_ERROR == ibutton_init( &ibutton, &ibutton_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    ibutton_register_keys ( &ibutton, NUMBER_OF_KEYS );
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    err_t error_flag = IBUTTON_OK;
    ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
    log_printf( &logger, " >>> Waiting for a key <<<\r\n" );
    do
    {
        ibutton_led_indication ( &ibutton, IBUTTON_LED_WAIT_KEY );
        error_flag = ibutton_check_key ( &ibutton );
    }
    while ( IBUTTON_ERROR == error_flag );

    ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
    if ( IBUTTON_OK == error_flag )
    {
        log_printf( &logger, " MATCH, access allowed!\r\n" );
        ibutton_led_indication ( &ibutton, IBUTTON_LED_SUCCESS );
    }
    else if ( IBUTTON_KEY_NO_MATCH == error_flag )
    {
        log_printf( &logger, " NO MATCH, access denied!\r\n" );
        ibutton_led_indication ( &ibutton, IBUTTON_LED_WRONG_KEY );
    }
    ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
    log_printf( &logger, "--------------------------------\r\n\n" );
    Delay_ms ( 500 );
}

int main ( void ) 
{
    application_init( );
    
    for ( ; ; ) 
    {
        application_task( );
    }

    return 0;
}

static void ibutton_led_indication ( ibutton_t *ctx, ibutton_led_state_t state )
{
    switch ( state )
    {
        case IBUTTON_LED_DISABLE:
        {
            ibutton_disable_green_led ( ctx );
            ibutton_disable_red_led ( ctx );
            break;
        }
        case IBUTTON_LED_WAIT_KEY:
        {
            ibutton_enable_green_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_green_led ( &ibutton );
            ibutton_enable_red_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_red_led ( &ibutton );
            break;
        }
        case IBUTTON_LED_SUCCESS:
        {
            ibutton_enable_green_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_green_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_enable_green_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_green_led ( &ibutton );
            Delay_ms ( 250 );
            break;
        }
        case IBUTTON_LED_WRONG_KEY:
        {
            ibutton_enable_red_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_red_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_enable_red_led ( &ibutton );
            Delay_ms ( 250 );
            ibutton_disable_red_led ( &ibutton );
            Delay_ms ( 250 );
            break;
        }
        default:
        {
            break;
        }
    }
}

static void ibutton_register_keys ( ibutton_t *ctx, uint8_t num_keys )
{
    err_t error_flag = IBUTTON_OK;
    uint8_t key_cnt = 1;
    while ( key_cnt <= num_keys )
    {
        ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
        log_printf( &logger, " >>> Registering key %u of %u <<<\r\n", ( uint16_t ) key_cnt, ( uint16_t ) num_keys );
        log_printf( &logger, " Insert a DS1990A Serial Number iButton to click board reader plate\r\n" );
        do
        {
            ibutton_led_indication ( &ibutton, IBUTTON_LED_WAIT_KEY );
            error_flag = ibutton_add_key ( &ibutton );
        }
        while ( IBUTTON_ERROR == error_flag );

        ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
        if ( IBUTTON_KEY_ALREADY_EXIST == error_flag )
        {
            log_printf( &logger, " This key is already registered!\r\n" );
            log_printf( &logger, " Use another key or decrease the number of keys\r\n" );
            ibutton_led_indication ( &ibutton, IBUTTON_LED_WRONG_KEY );
        }
        else if ( IBUTTON_OK == error_flag )
        {
            log_printf( &logger, " The key is registered successfully!\r\n" );
            ibutton_led_indication ( &ibutton, IBUTTON_LED_SUCCESS );
            key_cnt++;
        }
        ibutton_led_indication ( &ibutton, IBUTTON_LED_DISABLE );
        log_printf( &logger, "--------------------------------\r\n\n" );
        Delay_ms ( 500 );
    }
}

// ------------------------------------------------------------------------ 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.