Upgrade your audio game with SPQ0410HR5H-B and STM32F302VC
Hear the difference. Be heard!
Published Oct 02, 2023
Click board™
Mic Click
Dev Board
UNI-DS v8
Compiler
NECTO Studio
MCU
STM32F302VC
Create crystal-clear audio recordings with your own custom-built microphone system
A
A
Hardware Overview
How does it work?
Mic Click is based on the SPQ0410HRSH-B, a slim ultra-mini SiSonic™ microphone specification with maximum RF protection and ultra-narrow design from Knowles. It is a MEMS microphone and consists of an acoustic sensor, a low noise input buffer, and an output amplifier. It is a very reliable microphone, resistant to mechanical shocks, vibrations, thermal shocks, low and high temperatures, ESD-HBM, and more. It is not resistant to high pressure and vacuum. The
microphone is top-port oriented and has a typical sensitivity of -42dB at 94dB SPL, with a 59dB signal-to-noise ratio. Mic Click uses an analog OUT pin of the mikroBUS™ socket to communicate with the host MCU. The analog output from the microphone to the OUT pin goes through the MCP6022, a rail-to-rail input/output 10MHz Op Amp from Microchip. This operational amplifier has a wide bandwidth, low noise, low input offset voltage, and low distortion and amplifies the
microphone's output with high performance. 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 as a reference for further development.
Features overview
Development board
UNI-DS 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 STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. 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, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the UNI-DS 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. UNI-DS 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.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
100
RAM (Bytes)
40960
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.
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.
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.
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".
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.
Software Support
Library Description
This library contains API for MIC Click driver.
Key functions:
mic_generic_read- This function read ADC data
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 Mic Click example
*
* # Description
* This example showcases the initialization and configuration of the click and logger
* modules and later on reads and displays data recorded by the mic.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes LOG communication, ADC and configures AN pin as input on MIKROBUS1.
*
* ## Application Task
* Reads 12 bit ADC data from AN pin and displays it using the logger module.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mic.h"
// ------------------------------------------------------------------ VARIABLES
static mic_t mic;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mic_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.
mic_cfg_setup( &cfg );
MIC_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mic_init( &mic, &cfg );
}
void application_task ( void )
{
mic_data_t tmp;
// Task implementation.
tmp = mic_generic_read ( &mic );
log_printf( &logger, "** ADC value : [DEC]- %d, [HEX]- 0x%x \r\n", tmp, tmp );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
