Intermediate
30 min

Generate high-frequency clock output with ICS501 and MK22FN512VLH12

Phase-Locked Loop (PLL) mechanism

PLL Click with Kinetis Clicker

Published Aug 09, 2023

Click board™

PLL Click

Dev Board

Kinetis Clicker

Compiler

NECTO Studio

MCU

MK22FN512VLH12

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.

PLL click hardware overview image

Features overview

Development board

Kinetis Clicker 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-M4 microcontroller, the MK22FN512VLH12 from NXP Semiconductor, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access

anywhere and under any circumstances. Each part of the Kinetis Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Kinetis Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for Kinetis programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB-MiniAB connection provides up to 500mA of current, which is more than enough to operate all

onboard and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. Kinetis Clicker 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.

Kinetis Clicker double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M4

MCU Memory (KB)

512

Silicon Vendor

NXP

Pin count

64

RAM (Bytes)

131072

Used MCU Pins

mikroBUS™ mapper

Multiplier Adjustment
PTB2
AN
Multiplier Adjustment
PTB3
RST
Output Enable
PTC4
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
External Clock Source
PTC1
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

PLL click Schematic schematic

Step by step

Project assembly

Kinetis Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Kinetis Clicker as your development board.

Kinetis Clicker front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Kinetis Mini B Connector Clicker Access - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Kinetis Clicker HA MCU/Select Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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.

Application Output Step 1

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™.

Application Output Step 3

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.

Application Output Step 4

Software Support

Library Description

This library contains API for PLL Click driver.

Key functions:

  • pll_set_clock_output - This function settings clock output

  • pll_set_pll_4x - This function settings PLL x4

  • pll_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

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.