Generate highly stable and coherent high-frequency signals for applications requiring tight synchronization and minimal phase noise
A
A
Hardware Overview
How does it work?
PLL Click is based on the ICS501, a LOCO™ PLL clock multiplier, from Integrated Device Technology. This IC uses the Phase-Locked Loop to provide a high-frequency clock output, deriving input from a much cheaper, standard fundamental frequency crystal oscillator. Besides the onboard crystal oscillator fixed at 12MHz, it is possible to select the signal from the mikroBUS™ PWM pin as the clock input source. To select the desired multiplication factor, the states of the two input pins, S0 and S1, are routed to the mikroBUS™ pins RST and AN, respectively. These pins can be set to a HIGH or LOW logic state or disconnected (by tri-stating the MCU pins). The combination of these pins states will set the PLL
Click to a specific multiplier. The Output Enable (OE) pin of the ICS501 is used to turn off the output clock by setting it to a LOW logic level. It will additionally set the clock output pin in high impedance (Hi-Z) mode, allowing complete disconnection and no influence on the rest of the circuit, which is useful for experimenting and prototyping purposes. This pin is internally pulled to a HIGH logic level. The OE pin is routed to the CS pin of the mikroBUS™. PLL Click is equipped with two onboard SMD jumpers. The SMD jumper labeled as the VCC SEL is used to select the operating voltage level, consequently limiting the amplitude of the clock output signal with respect to the selected voltage. The other SMD jumper
labeled as the OSC SEL chooses the clock input source between the onboard 12MHz crystal oscillator or the external clock signal. The output signal is routed through the onboard SMA connector, which provides a secure connection and good signal shielding. PLL Click has a library containing functions for all the MIKROE compilers (mikroBASIC, mikroPASCAL, and mikroC). Although relatively easy to control, the library offers comprehensive functions that make the code readable and easy to use. The included example application demonstrates the use of these functions, and it can be used as a reference for custom projects.
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
Schematic
Step by step
Project assembly
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 PLL Click driver.
Key functions:
pll_set_clock_output
- This function settings clock outputpll_set_pll_4x
- This function settings PLL x4pll_set_pll_6x
- This function settings PLL x6
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 PLL Click example
*
* # Description
* This app sets PLL signals.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes device.
*
* ## Application Task
* Every 2 seconds, the PLL increases the input clock from min (x2) to max (x8) level.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pll.h"
// ------------------------------------------------------------------ VARIABLES
static pll_t pll;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
pll_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.
pll_cfg_setup( &cfg );
PLL_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pll_init( &pll, &cfg );
pll_set_clock_output( &pll, PLL_CLOCK_ENABLE );
}
void application_task ( void )
{
log_printf( &logger, " PLL level: x2\r\n\n" );
pll_set_pll_2x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x3\r\n\n" );
pll_set_pll_3x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x3.125\r\n\n" );
pll_set_pll_3_125x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x4\r\n\n" );
pll_set_pll_4x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x5\r\n\n" );
pll_set_pll_5x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x5.3125\r\n\n" );
pll_set_pll_5_3125x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x6\r\n\n" );
pll_set_pll_6x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x6.25\r\n\n" );
pll_set_pll_6_25x( &pll );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " PLL level: x8\r\n\n" );
pll_set_pll_8x( &pll );
Delay_ms ( 1000 );
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