Have you ever wondered what it takes to create a small system-on-chip (SoC) based on a Arm Cortex-M processor? In this blog, we explain typically what IP components are required and what other things you might need to put the whole system together.
Since the Cortex-M0 processor was released a few years ago, the number of silicon designs based on Cortex-M processors has increased substantially. By the end of 2016, it was reported that there were over 400 Cortex-M licensees, with most of these licensees using Cortex-M processors in non-MCU products.
In fact, Cortex-M processors are finding their ways into new SoC designs whose previous generations did not include a Cortex-M, let alone a digital processor core. As a result, many SoC design engineers have taken the exciting journey of integrating a Cortex-M processor core for the first time without previous experience or any knowledge of important considerations required.
This white paper seeks to answer some of the frequently asked questions SoC designers face when integrating a Cortex-M processor for the first time. At the end of this white paper you will find a host of links to other resources and information that will be of use.
Since this is a big topic to cover, I am sure there is some information I missed. If you have additional information which can be useful to other chip designers, or if you spot any error in this document, please contact me and I will update this document from time to time.
Download Cortex-M white paper
A big thank you to various people who have been helping me in the preparation of this article:
Good luck with your next Cortex-M based design!
P.S. An older version of this paper is attached in this page below.
Thanks Michael. Document updated.
Oops! You are right. It should be "compliants".
I will update the document.
Hi,Joseph, I find a spelling mistake (maybe I am wrong ):
The CMSDK also included a range of verification components for testing bus protocol complaints, and for bus stimulus generation.
is protocol complaints a spelling mistake?
or should be protocol compliants?
Wonderful, it's not only useful for chip designers to design Cortex-M based SoC or microcontroller, it's also useful for embedded software engineers who develop software for Cortex-M to better understand the inner operation of the Cortex-M based SoC or microcontroller.