Upgrade your audio game with SPQ0410HR5H-B and ATmega324P
Hear the difference. Be heard!
Published Oct 02, 2023
Click board™
Mic Click
Dev. board
EasyAVR v7
Compiler
NECTO Studio
MCU
ATmega324P
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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 EasyAVR v7 as your development board.
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 MIC Click driver.
Key functions:
mic_generic_read- This function read ADC data
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
* \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 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
