![\"TM4C123x](\"http:\/\/embedded-lab.com\/blog\/wp-content\/uploads\/2016\/07\/TM4C123x-Features.png\")
<\/a><\/p>\n<\/h6>\n
<\/p>\n
<\/p>\n
\u00a0Clock System Basics<\/h4>\n
Just as with any modern era micros Tiva C micros have several clock sources. Some of these sources are external while most clock sources are internal.<\/p>\n
<\/p>\n I have taken the liberty to improve the clock tree of Tiva C micros by highlighting special areas of interest. For STM32s micros there is a great tool called STM32CubeMX<\/em><\/strong> that can be used to deduce system and peripheral clocks but for Tiva C we have no such tool. We need to do everything on our own and there we are very much likely to make mistakes if we cannot visualize the clock system well. If you notice the clock tree diagram above, it may look a bit complex but in practice it is simple. The green blocks are selectors or multiplexers that are governed by some bit settings. The red boxes are the clock sources. There are four clock sources and two Phase-Lock-Loop (PLL) designated by the purple boxes. The 480 MHz USB PLL is not a concern for now as we will not be discussing about USB communication here. We will be discussing about the 400 MHz PLL only. The interconnections of these sources and blocks make the clock tree appear like a spider web. To resolve this issue I highlighted these connections with different colours. It should be a relaxing view for the eyes now.<\/p>\n <\/p>\n <\/p>\n All of the aforementioned sources can be system clock source. However peripheral clocks can be different. Most peripherals like SSI<\/em><\/strong>, UART<\/em><\/strong>, ADC<\/em><\/strong>, etc. can clocked by the PIOSC <\/em><\/strong>unless specified otherwise. PIOSC<\/em><\/strong> should never be disabled unless needed and that is because if MOSC<\/em><\/strong> is used and it fails for some reason, PIOSC<\/em><\/strong> will take over the role of providing clock signal.<\/p>\n ARM micros are about speed and power and so most of the times we would want an ARM micro to be as fast as possible. \u00a0To facilitate this speed thrust most ARM microcontrollers are equipped with Phase-Lock-Loops (PLL). Not only it cuts down cost by removing the need for rare, expensive high frequency external crystals but gives users lot of clock frequency options which would have been impossible otherwise. TM4C123x comes with an internal 400 MHz PLL, the internal working mechanism of which is not important here. However unlike the PLLs of other micros like STM32s, instead of multiplying input clock source, it is divided by System Divisor<\/em><\/strong>, Sysdiv<\/em><\/strong> to obtain desired clock speeds. No wonder Americans think differently from the rest of the world. With the internal PLL we can generate clock frequencies from 3.125 MHz to 80 MHz, 80 MHz being the top operating clock speed for the TM4C123x. The PLL can be driven by two sources only:<\/p>\n <\/p>\n The system clock control is provided by a pair of registers called Run-Mode Clock Control<\/em><\/strong>, RCC<\/em><\/strong>. RCC<\/em><\/strong> and RCC2<\/em><\/strong> registers does the following things:<\/p>\n The RCC<\/em><\/strong> register needs to be configured before RCC2<\/em><\/strong> if RCC2<\/em><\/strong> is needed. RCC2 <\/em><\/strong>is basically an extension of the RCC<\/em><\/strong> register and it overrides RCC<\/em><\/strong> settings. In most cases RCC2<\/em><\/strong> will be needed.<\/p>\n Before going further I would like to reintroduce a very useful tool because what will be discussed next is related to this tool and its use. In several of my earlier posts I mentioned the advantage of using MikroC\u2019s project editor. Using this tool we can easily set the required clock settings.<\/p>\n As seen we can see many drop-down menus. However these may look as much ambiguous as the clock tree itself. Thus we need to look at the three tables shown next. Note the 2<\/em><\/strong>s in some menus. These refer to RCC2<\/em><\/strong> while the reset are related to RCC<\/em><\/strong> registers.<\/p>\n <\/p>\n When the BYPASS<\/em><\/strong> bit is 0<\/em><\/strong>, the internal 400 MHz PLL <\/em><\/strong>is used and scaled. It is not bypassed. Likewise when it is 1<\/em><\/strong>, preselected clock source is used and scaled accordingly. These tables demonstrate possible clock frequencies.<\/p>\n When using the MikroC\u2019s Project Editor<\/em><\/strong>, we need to set system clock in a systematic order. Let us consider the 80 MHz max system clock speed setup. First we need to set the RCC<\/em><\/strong> settings as shown.<\/p>\n The first two parameters dictate that we will be using the 16 MHz MOSC<\/em><\/strong> clock. We selected so because the TM4C123GXL Tiva C Launchpad board comes with an external 16 MHz crystal attached to the MOSC<\/em><\/strong>. This clock source is better than the others. We could have used PIOSC<\/em><\/strong> as the main clock source but we are keeping it as a backup oscillator. It is also pointless to keep the 16 MHz external crystal unused when it is already embedded in the board. Next we power up the internal PLL and use it. Note we did not use the System Clock Divisor<\/em><\/strong>, SYSDIV<\/em><\/strong> and that is because we will be using RCC2<\/em><\/strong> also. Though RCC<\/em><\/strong> setting will be overridden by RCC2<\/em><\/strong>, I advise not to use different settings both registers.<\/p>\n As said earlier, RCC2<\/em><\/strong> is more extensive than RCC<\/em><\/strong>. This is reflected by the settings available for RCC2 <\/em><\/strong>in the Project Editor<\/em><\/strong>.\u00a0 In this section we have to enable\/disable the two primary oscillators \u2013 PIOSC<\/em><\/strong> and MOSC<\/em><\/strong>. I am keeping both enabled. PIOSC<\/em><\/strong> is the backup should MOSC<\/em><\/strong> fail. The next two settings dictate what kind of control we are using to set the system clock and if it is required to use the RCC2<\/em><\/strong> fields. If we do not need to use RCC2<\/em><\/strong>, we can simply disable it with the setting available for System Clock Switch<\/em><\/strong>. Here we will need it. Since we did not set the PLL completely in the RCC <\/em><\/strong>field and we will be using RCC2<\/em><\/strong>, we need to set PLL parameters, particularly System Clock Divisor 2<\/em><\/strong>, SYSDIV2<\/em><\/strong>. I recommend readers to set the last to options as per tables shown previously before setting the PLL. Now our TM4C123 micro is ready to run at 80 MHz system clock.<\/p>\n Please note that right after Power-On Reset (POR),<\/em><\/strong> PIOSC<\/em><\/strong> starts up before everything else sets up. It should not be a big deal for us. The final outcome from the Project Editor should look like this:<\/p>\n Note the RCC<\/em><\/strong> and RCC2<\/em><\/strong> register values. If everything is okay they should look like that. Please take care to set the MCU clock frequency to 80 MHz or otherwise time-related functions like delays and other stuffs may work differently than anticipated. Note that the MCU clock frequency is the system clock frequency and that is why it is so critical. Finally the Project Editor<\/em><\/strong> allows us to load and save our favourite system clock schemes \u2013 a very handy feature that saves time by quickly loading such schemes.<\/p>\n We have setup the system clock to 80 MHz but we have no quick way to know for sure if it is really working that fast. Here a debugger becomes a must-have tool. All MikroE compilers come with a built-in software simulator or debugger which can assist in debugging codes. Here we will see how helpful it is.<\/p>\n The Get_Fosc_kHz<\/em><\/strong> built-in function returns the system clock frequency in kHz. If our clock setup is okay, it should be returning 80000, indicating 80 MHz system clock speed.<\/p>\n <\/p>\n Check the video for step-by-step details: https:\/\/www.youtube.com\/watch?v=f7UokGJ7_kI<\/a>.<\/p>\n <\/p>\n Experiment with different clock combinations to build up more confidence on Tiva C clock system. We have yet to do real world experiments and the upcoming post on Tiva C GPIOs will reveal more. We will recheck if this setting of system clock is okay in that post.<\/p>\n <\/p>\n <\/p>\n Happy coding.<\/p>\n \u00a0<\/em><\/p>\n Author: Shawon M. Shahryiar<\/em><\/p>\n https:\/\/www.facebook.com\/groups\/microarena<\/em><\/a><\/p>\n<\/a><\/p>\nMain Oscillator (MOSC)<\/h6>\n
\n
<\/a><\/p>\n<\/a><\/p>\nPrecision Internal Oscillator (PIOSC)<\/h6>\n
\n
Precision Internal Oscillator Divided by 4 (PI4OSC)<\/h6>\n
\n
Low Frequency Internal Oscillator (LFIOSC)<\/h6>\n
\n
Hibernation Module Clock Source<\/h6>\n
\n
<\/h4>\n
<\/h5>\n
400 MHz Phase-Lock-Loop<\/h5>\n
\n
<\/h5>\n
Run-Mode Clock Control<\/h5>\n
\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nSoftware Simulation and Debugging<\/h4>\n
\n
void main() <\/em><\/span><\/pre>\n{<\/em><\/span><\/pre>\n\u00a0\u00a0\u00a0 Get_Fosc_kHz();<\/em><\/span><\/pre>\n}<\/em><\/span><\/pre>\n\n
<\/a><\/p>\n\n
<\/a><\/p>\n\n
<\/a><\/p>\n\n
<\/a><\/p>\n\n