/products/devtools/kinetiskl2freedomboard/b/blog/posts/frdm-k64f---pe-tutorial-get-the-maximum-speed-of-120mhz“This tutorial was extracted from Erich Styger blog http://mcuoneclipse.wordpress.com with his agreement.”The ARM Cortex-M4F on the Freescale FRDM-K64F board can run up to 120 MHz. Here is how to get it running with maximum speed: &amp;n...en-USTelligent Community 12https://community.element14.com/products/devtools/kinetiskl2freedomboard/b/blog/posts/frdm-k64f---pe-tutorial-get-the-maximum-speed-of-120mhzTue, 15 Jul 2014 07:56:55 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:854c4825-06e2-4649-8b02-149019cf0eecmichaelkellett1<p>The problem with using these fancy graphic thingies to set up the processor is that you may have no idea what code it has made. You become completely dependent on the continuing existence of the graphical tool and the ability to run it. It&#39;s also very hard to maintain version control. For playing none of this matters but if you want to do any kind of project which needs to be maintained then you will need version control and the ability to rebuild the code years later.</p><p>Frequently the graphical tools don&#39;t even cover all the possibilities.</p><p>How does this tool keep it&#39;s information - is it in a visible file that can be version controlled.</p><p>What code does it make and what are the dependencies of that code ?</p><p>If the data sheet is really not understandable (which I doubt - Freescale&#39;s docs are usually quite good) -&nbsp; it would be better if effort went into sorting that rather than making graphical tools.</p><p>I use ST Cortex processors a lot and it really isn&#39;t that hard to understand how to set up the peripherals directly (the clock systems are of similar complexity).</p><p>&nbsp;</p><p>MK</p><img src="https://community.element14.com/aggbug?PostID=18090&AppID=73&AppType=Weblog&ContentType=0" width="1" height="1">