Upgrade your audio game with SPQ0410HR5H-B and PIC18F4455
Hear the difference. Be heard!
Published Nov 01, 2023
Click board™
Mic Click
Dev Board
Curiosity HPC
Compiler
NECTO Studio
MCU
PIC18F4455
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
Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All
these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware
quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
24
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 Curiosity HPC as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
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
