Create a custom voice-activated system with IA611 and STM32G474RE
Say it, and it shall be done!
Published Nov 08, 2024
Click board™
Smart Mic Click
Dev Board
Nucleo 64 with STM32G474RE MCU
Compiler
NECTO Studio
MCU
STM32G474RE
Identify a particular spoken keyword or trigger phrase within a larger sentence or command to wake up any embedded system
A
A
Hardware Overview
How does it work?
Smart Mic Click is based on the IA611, a flexible, low-power, highly integrated voice and audio processor system from Knowles Electronics. The IA611 includes an advanced Knowles audio-optimized DSP sub-system designed to calculate intensive audio-processing algorithms with low power consumption. It also comprises a System Control Unit (SCU) that handles power management states such as sleep mode and generates internal clock signals. The IA611, “Always-On” Acoustic Processor, features a voice wake and voice ID keyword detector, a three-second buffer, and Knowles’ proven high-performance acoustic SiSonicTM MEMS technology in a single package. The IA611 can be in one of the following operating modes. The Bootloader is a mode where, after Power-Up, the IA611 waits for firmware download or use case setup. In Instruction mode, the IA611 waits for use case setup after firmware download, while in Open DSP Mode, the IA611 enables third-party algorithms. In Normal operational mode, the IA611 can be in software or hardware pass-through mode, which acts as a mic to the host.
The Voice Wake Mode allows low-power voice wake-up based on the detection of either a built-in keyword (OEM keyword), a user-trained keyword (user keyword), or a user-conditioned OEM keyword (Voice ID). In this mode, the IA611 monitors the microphone stream for acoustic activity. When acoustic activity is detected, the IA611 automatically enters a slightly higher power mode to analyze the speech utterance for the presence of the wake-up keyword. When a valid keyword is detected, the IA611 asserts an interrupt routed to the INT pin of the mikroBUS™ socket to trigger a complete system wake-up. If a keyword is not detected, the device returns to the ultra-low-power mode until the acoustic activity is detected again. The IA611 implements various control interfaces, including UART, SPI, and an I2C slave interface with a control interface and audio interface port. Depending on the desired interface, the user must populate the selected jumper to activate that interface (SPI, I2C, or UART). Using an I2C interface, the user is given the option of additional activation of 4.7kΩ pull-up resistors on I2C lines,
populating jumpers marked with PULL-UP. The IA611 does not require a specific Power-Up sequence but requires a voltage of 1.8V for its supply and logic part to work correctly. Therefore, a small regulating LDO is used, the TC1015, providing a 1.8V out of 3.3V mikroBUS™ power rail, alongside Enable feature through the EN pin routed to the RST pin of the mikroBUS™ socket offering a switch operation to turn ON/OFF power delivery to the TC1015. Since the sensor for operation requires a power supply of 1.8V, this Click board™ also features the TXS0108E voltage-level translator. The interface lines are routed to the voltage-level translator allowing this Click board™ to work with 3.3V MCUs properly. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32G474R 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-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
128k
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 STM32G474RE 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 Smart Mic Click driver.
Key functions:
smartmic_wait_keywordThis function waits for a keyword event, reads it, and returns the keyword ID number.smartmic_download_keywordThis function downloads keyword models to the module.smartmic_voice_makeThis function performs the voice-make feature. It stops the route, then sets the digital gain to 20db, sample rate to 16K, frame size to 16 ms, and finally, it selects route 6 and configures algorithm parameters.
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 SmartMic Click example
*
* # Description
* This example demonstrates the use of Smart Mic click board by programming
* it with 4 different keywords, and then waiting for a keyword event,
* parsing it and displaying on the USB UART.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration
* which programs the device with system config, firmware, and 4 keywords
* ("Hello VoiceQ","Switch The Light","Next Song","Baidu Yixia") binaries.
*
* ## Application Task
* Waits for a keyword event, parses it and displays on the USB UART
* an appropriate message for the detected keyword.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "smartmic.h"
static smartmic_t smartmic;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
smartmic_cfg_t smartmic_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.
smartmic_cfg_setup( &smartmic_cfg );
SMARTMIC_MAP_MIKROBUS( smartmic_cfg, MIKROBUS_1 );
if ( SMARTMIC_OK != smartmic_init( &smartmic, &smartmic_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, " Configuring device... \r\n" );
if ( SMARTMIC_OK != smartmic_default_cfg ( &smartmic ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
switch ( smartmic_wait_keyword ( &smartmic ) )
{
case SMARTMIC_OEM1_KWD_DETECTED:
{
log_printf ( &logger, " Hello VoiceQ keyword detected!\r\n" );
break;
}
case SMARTMIC_OEM2_KWD_DETECTED:
{
log_printf ( &logger, " Switch The Light keyword detected!\r\n" );
break;
}
case SMARTMIC_OEM3_KWD_DETECTED:
{
log_printf ( &logger, " Next Song keyword detected!\r\n" );
break;
}
case SMARTMIC_OEM4_KWD_DETECTED:
{
log_printf ( &logger, " Baidu YiXia keyword detected!\r\n" );
break;
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
