Shape your audio landscape with CS3310 and MK64FN1M0VDC12
A symphony of sound awaits: Unleash your inner audiophile
Published Oct 22, 2023
Click board™
Volume Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Our stereo digital volume control device is designed to give you unparalleled control over your audio, allowing you to fine-tune your sound to perfection
A
A
Hardware Overview
How does it work?
Volume Click is based on the CS3310, a complete stereo digital volume control designed specifically for audio systems from Cirrus Logic. It features a 16-bit serial interface that controls two independent, low-distortion audio channels. The left and right levels of the analog input channels are set by a 16-bit serial data word (the first 8 bits address the right while the remaining 8 bits address the left channel). The CS3310 includes an array of well-matched resistors and a low-noise active output stage capable of driving a 600Ω load. A total adjustable range of 127dB, in 0.5dB steps, is achieved through 95.5dB of attenuation and 31.5dB of gain. The digital section power supply of the Volume Click is achieved through a 5V pin from a mikroBUS™ socket while the device itself is powered by ±5V from the LT3032, a dual 150mA positive and negative low noise low dropout linear
regulator with micropower quiescent current from Analog Devices. Volume Click communicates with MCU using the standard SPI serial interface with two additional GPIO pins that accept 16-bit data and enable users to read the current volume setting. Those two GPIO pins brought with this Click board™ are used for Zero Crossing Enable and Hardware MUTE functions. Once in operation, the CS3310 can be brought to a muted state with the MUTE pin labeled as SEN routed on the PWM pin of the mikroBUS™ socket or by writing zeros to the volume control registers. A volume control change occurs after the CS pin latches the data in the volume control data register, and two zero crossings are detected. The zero-crossing enable pin, labeled as ZCE routed on the AN pin of the mikroBUS™ socket, turns on or off the zero-crossing detection function and the 18ms
time-out circuit. If two zero crossings are not detected within 18ms of the change in the CS pin, the new volume setting is implemented. Upon initial application of power, the SEN pin of the CS3310 should be set to LOW to initiate a Power-Up sequence. This sequence sets the serial shift register and the volume control register to zero and performs an offset calibration. The device should remain muted until the supply voltages have settled to ensure accurate calibration. This Click board™ can be operated only with a 5V 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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 Clicker 2 for Kinetis 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 Volume Click driver.
Key functions:
volume_set_vol_gain- Set volume gain functionvolume_power_up- Power Up functionvolume_hw_mute- Hardware MUTE function
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 main.c
* @brief Volume Click example
*
* # Description
* This example sets up the device and performs volume turn up and down.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes drivers and powers up the device.
*
* ## Application Task
* Circles the volume from -40 [dB] to 10 [dB] back and forth.
*
* @author Stefan Nikolic
*
*/
#include "board.h"
#include "log.h"
#include "volume.h"
float left_speaker_gain;
float right_speaker_gain;
uint8_t one_circle;
static volume_t volume;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
volume_cfg_t volume_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.
volume_cfg_setup( &volume_cfg );
VOLUME_MAP_MIKROBUS( volume_cfg, MIKROBUS_1 );
err_t init_flag = volume_init( &volume, &volume_cfg );
if ( init_flag == SPI_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
volume_default_cfg ( &volume );
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
left_speaker_gain = -40;
right_speaker_gain = -40;
one_circle = 0;
log_printf( &logger, " Turning volume up.\r\n" );
while ( one_circle < 2 ) {
if ( one_circle == 0 ) {
if ( left_speaker_gain <= 10 || right_speaker_gain <= 10 ) {
volume_set_vol_gain( &volume, left_speaker_gain, right_speaker_gain );
left_speaker_gain += 0.5;
right_speaker_gain += 0.5;
Delay_ms( 50 );
} else {
one_circle++;
log_printf( &logger, " Turning volume down.\r\n" );
}
} else if ( left_speaker_gain >= -40 || right_speaker_gain >= -40 ) {
volume_set_vol_gain( &volume, left_speaker_gain, right_speaker_gain );
left_speaker_gain -= 0.5;
right_speaker_gain -= 0.5;
Delay_ms( 50 );
} else one_circle++;
}
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
