Introduction

Previously, the MCU+SDK offered limited flexibility in selecting clock sources or frequencies through the sysconfig tool, with most values hardcoded for various modules. These hardcoded values were reflected in the ti_power_clock_config.c file, which is one of the generated sysconfig files. Additionally, the clock values for the PLLs were also hardcoded within the soc_bootloader.c files.

With the introduction of the clock tree, users now have an enhanced view of the entire clock architecture, illustrating how clock sources, multiplexers, dividers, and peripherals are interconnected. This centralizes the configurability of the clocktree, allowing users to adjust these values directly from the ClockTree view, with the changes appearing as read-only values in the Software view. This update significantly reduces the hardcoding of clock values that was prevalent in earlier versions. However, some combinations of muxes and dividers may still produce incompatible input clock frequencies for certain peripherals, and the system includes errors and warnings to address these scenarios.

This new approach also minimizes human errors. For instance, when two modules share the same muxes (such as UART and LIN), any modifications made will automatically reflect on both modules, ensuring consistency that could otherwise be compromised with manual configurations.

Overview

In the ClockTree panel view, components are organized into four categories:

• CLOCKS
• PLLs
• XBARs
• PERIPHERALS

Most configurations will focus on either the PLLs or the PERIPHERALS. The PLL view may appear complex, as it encompasses the entire clocktree architecture. Therefore, it is advisable for users to configure settings from the PERIPHERAL view if they know which peripheral is connected to the PLL they wish to modify.

How a peripheral derives its input clock from Clock source

Since all the components from the clock sources, PLLs, DPLLs etc. are interconnected, any changes made to shared components will be automatically synchronized across all dependent modules.

Modules such as UART, I2C, LIN and a few others previously allowed configuration of clock sources and frequencies from the Software View. Now, all configurations must be made through the ClockTree, with any changes reflected as read-only values in the Software View:

UART Clocktree

UART Clock source and input clock information coming from Clocktree

UART Clock configuration values getting generated

Subsequently, the ti_power_clock_config.c file will be generated with these updated values.

PLL configuration is also possible; however, for changes to take effect, the example must include the Bootloader module added from sysconfig. This will generate two files: ti_clocktree_pll_config.h and ti_clocktree_pll_config.c, with the latter containing the updated PLL configuration.

PLL Files getting generated from Sysconfig

PLL clock frequencies change from Clocktree