Intermediate
30 min

Process, move, and store information securely thanks to the SEC1210 and STM32F091RC

Elevate access control with smart card reading: Your key to a secure tomorrow

Smart Card 2 Click with Nucleo-64 with STM32F091RC MCU

Published Feb 26, 2024

Click board™

Smart Card 2 Click

Dev Board

Nucleo-64 with STM32F091RC MCU

Compiler

NECTO Studio

MCU

STM32F091RC

Explore the most advanced smart card reader on the market, offering unparalleled protection and ease of use

A

A

Hardware Overview

How does it work?

Smart Card 2 Click is based on the SEC1210, a high-performance single-chip Smart Card controller with a UART interface from Microchip. The SEC1210 is controlled by an enhanced integrated 8051 CPU, with all chip peripherals accessed and managed through the SFR or XDATA register space. Besides, it is fully compliant with the prevailing Smart Card standards (ISO7816, EMV, and PC/SC), keeps up with all requirements for communication bit rate, and includes support for proposed bit rates up to 826Kbps. The SEC1210 power unit is regulated and switched internally, supporting all 5V, 3V, and 1.8V Smart Cards (classes A, B, and C, respectively). The SEC1210 utilizes TrustSpan™ technology, enabling digital systems to communicate securely, process,

move, and store information. A populated onboard card holder supports data processing with 2FF smart cards. An additional connector for external connection also allows the processing of a standard 1FF card, making it ideal for electronic processes such as personal identification, access control (physical and logical access), authentication, and many more. This Click board™ communicates with MCU using the UART interface with commonly used UART RX/TX and operates at 115200 bps by default configuration to transmit and exchange data with the host MCU. The sequence activation/deactivation process itself is possible through software. Still, hardware deactivation is also supported when a card is

pulled out, whereby the required sequence is ensured regardless of software participation. In addition, Smart Card 2 Click also possesses a general Reset feature routed to the RST pin on the mikroBUS™ socket, which puts the module into a Reset state, while a yellow LED indicator labeled SRC represents a Smart Card status indicator. The blinking of this LED indicates that the Smart Card data processing is in progress. This Click board™ can operate with 3.3V and 5V MCUs, while SEC1210 uses only 5V from mikroBUS™ power rail as its primary power supply. However, the Click board™ comes equipped with a library containing functions and example code that can be used as a reference for further development.

Smart Card 2 Click hardware overview image

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.

Nucleo 64 with STM32F091RC MCU double side image

Microcontroller Overview

MCU Card / MCU

default

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.

Click Shield for Nucleo-64 accessories 1 image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Reset
PC12
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
UART TX
PA2
TX
UART RX
PA3
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Smart Card 2 Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-64 front image hardware assembly

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

Click Shield for Nucleo-64 front image hardware assembly
Nucleo 64 with STM32F401RE MCU front image hardware assembly
EEPROM 13 Click front image hardware assembly
Prog-cut hardware assembly
Nucleo-64 with STM32XXX MCU 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 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.

DEBUG_Application_Output

Software Support

Library Description

This library contains API for Smart Card 2 Click driver.

Key functions:

  • smartcard2_send_ccid - This function sends the CCID command message by using UART serial interface

  • smartcard2_read_ccid - This function reads a CCID response or event message by using UART serial interface

  • smartcard2_icc_power_on - This function activates the card by performing an ICC power ON command. The device will respond with a data block containing ICC ATR (Answer to Reset) message

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 Smart Card 2 Click Example.
 *
 * # Description
 * This example demonstrates the use of Smart Card 2 click board by checking
 * the SIM card presence and activating the card on insert. The card should respond
 * with an ATR (Answer to Reset) message.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initializes the driver and enables the device.
 *
 * ## Application Task
 * Reads and parses all CCID messages received from the device. Checks the SIM card presence
 * and activates it if it's inserted. The card should respond with an ATR (Answer to Reset) message.
 * All data is being logged on the USB UART where you can track their changes.
 * 
 * @note
 * This example doesn't parse ATR messages.
 * There are some online ATR parsers which could be used for decoding those messages.
 * For example: https://smartcard-atr.apdu.fr/
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "smartcard2.h"

static smartcard2_t smartcard2;
static log_t logger;
static uint8_t icc_status = SMARTCARD2_ICC_ABSENT;

/**
 * @brief Smart Card 2 display ccid message function.
 * @details This function parses the CCID message and updates the icc_status in the end.
 * The results will be displayed on the USB UART.
 * @param[in] ccid : CCID message to be parsed.
 * See #smartcard2_ccid_t object definition for detailed explanation.
 * @return None.
 * @note None.
 */
static void smartcard2_display_ccid_message ( smartcard2_ccid_t ccid );

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    smartcard2_cfg_t smartcard2_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.
    smartcard2_cfg_setup( &smartcard2_cfg );
    SMARTCARD2_MAP_MIKROBUS( smartcard2_cfg, MIKROBUS_1 );
    if ( UART_ERROR == smartcard2_init( &smartcard2, &smartcard2_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    smartcard2_ccid_t ccid = { 0 };
    if ( SMARTCARD2_OK == smartcard2_read_ccid ( &smartcard2, &ccid ) )
    {
        smartcard2_display_ccid_message ( ccid );
    }
    if ( SMARTCARD2_ICC_PRESENT == icc_status )
    {
        log_printf( &logger, " Activating card... \r\n" );
        smartcard2_icc_power_on ( &smartcard2, SMARTCARD2_POWER_SEL_3V );
        Delay_ms ( 100 );
    }
}

void main ( void ) 
{
    application_init( );

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

static void smartcard2_display_ccid_message ( smartcard2_ccid_t ccid )
{
    log_printf( &logger, "---------------------------------\r\n" );
    switch ( ccid.type )
    {
        case SMARTCARD2_EVT_NOTIFY_SLOT_CHANGE:
        {
            log_printf( &logger, " Message type: Slot change\r\n" );
            if ( SMARTCARD2_CARD_ABSENT == ccid.payload[ 0 ] )
            {
                icc_status = SMARTCARD2_ICC_ABSENT;
            }
            else if ( SMARTCARD2_CARD_PRESENT == ccid.payload[ 0 ] )
            {
                icc_status = SMARTCARD2_ICC_PRESENT;
            }
            break;
        }
        case SMARTCARD2_CTRL_NACK:
        {
            log_printf( &logger, " Message type: NACK\r\n" );
            log_printf( &logger, " Command not acknowledged\r\n" );
            break;
        }
        case SMARTCARD2_RSP_SLOT_STATUS:
        {
            log_printf( &logger, " Message type: Slot status\r\n" );
            log_printf( &logger, " Slot number: 0x%.2X\r\n", ( uint16_t ) ccid.slot_num );
            log_printf( &logger, " Seq number: 0x%.2X\r\n", ( uint16_t ) ccid.seq_num );
            log_printf( &logger, " Status: 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 0 ] );
            icc_status = ccid.spec_bytes[ 0 ] & SMARTCARD2_ICC_STATUS_MASK;
            log_printf( &logger, " Error: 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 1 ] );
            log_printf( &logger, " Clock status: " );
            switch ( ccid.spec_bytes[ 2 ] )
            {
                case SMARTCARD2_CLK_STATUS_RUNNING:
                {
                    log_printf( &logger, "Running\r\n" );
                    break;
                }
                case SMARTCARD2_CLK_STATUS_STATE_L:
                {
                    log_printf( &logger, "Stoped in state L\r\n" );
                    break;
                }
                case SMARTCARD2_CLK_STATUS_STATE_H:
                {
                    log_printf( &logger, "Stoped in state H\r\n" );
                    break;
                }
                default:
                {
                    log_printf( &logger, "Unknown\r\n" );
                    break;
                }
            }
            break;
        }
        case SMARTCARD2_RSP_DATA_BLOCK:
        {
            log_printf( &logger, " Message type: Data Block\r\n" );
            log_printf( &logger, " Payload size: %lu\r\n", ccid.payload_size );
            log_printf( &logger, " Slot number: 0x%.2X\r\n", ( uint16_t ) ccid.slot_num );
            log_printf( &logger, " Seq number: 0x%.2X\r\n", ( uint16_t ) ccid.seq_num );
            log_printf( &logger, " Status: 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 0 ] );
            icc_status = ccid.spec_bytes[ 0 ] & SMARTCARD2_ICC_STATUS_MASK;
            log_printf( &logger, " Error: 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 1 ] );
            log_printf( &logger, " Chain parameter: 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 2 ] );
            if ( ccid.payload_size )
            {
                log_printf( &logger, " Payload (ATR data as response to power on):\r\n" );
                for ( uint32_t cnt = 0; cnt < ccid.payload_size; cnt++ )
                {
                    log_printf( &logger, " %.2X", ( uint16_t ) ccid.payload[ cnt ] );
                }
                log_printf( &logger, "\r\n" );
            }
            break;
        }
        default:
        {
            log_printf( &logger, " Message type: 0x%.2X\r\n", ( uint16_t ) ccid.type );
            log_printf( &logger, " Payload size: %lu\r\n", ccid.payload_size );
            log_printf( &logger, " Slot number: 0x%.2X\r\n", ( uint16_t ) ccid.slot_num );
            log_printf( &logger, " Seq number: 0x%.2X\r\n", ( uint16_t ) ccid.seq_num );
            log_printf( &logger, " Spec bytes: 0x%.2X, 0x%.2X, 0x%.2X\r\n", ( uint16_t ) ccid.spec_bytes[ 0 ], 
                                                                            ( uint16_t ) ccid.spec_bytes[ 1 ], 
                                                                            ( uint16_t ) ccid.spec_bytes[ 2 ] );
            if ( ccid.payload_size )
            {
                log_printf( &logger, " Payload:\r\n" );
                for ( uint32_t cnt = 0; cnt < ccid.payload_size; cnt++ )
                {
                    log_printf( &logger, " 0x%.2X", ( uint16_t ) ccid.payload[ cnt ] );
                    if ( 7 == cnt % 8 )
                    {
                        log_printf( &logger, "\r\n" );
                    }
                }
                log_printf( &logger, "\r\n" );
            }
            break;
        }
    }
    if ( SMARTCARD2_ICC_ABSENT == icc_status )
    {
        log_printf( &logger, " ICC status: ABSENT\r\n" );
    }
    else if ( SMARTCARD2_ICC_PRESENT == icc_status )
    {
        log_printf( &logger, " ICC status: PRESENT\r\n" );
    }
    else if ( SMARTCARD2_ICC_ACTIVE == icc_status )
    {
        log_printf( &logger, " ICC status: ACTIVE\r\n" );
    }
    log_printf( &logger, "---------------------------------\r\n\n" );
}

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