USB2.0 OTG PHY supporting UTMI+ level 3 interface - 28HK/55LL
Basics of the Cortex MCU Software Interface Standard: Part 1 - CMSIS Specification
Trevor Martin, Hitex UK
embedded.com (February 17, 2015)
The widespread adoption of the Cortex-M processor into general purpose microcontrollers has led to two rising trends within the electronics industry. First of all the same processor is available from a wide range of vendors each with their own family of microcontrollers. In most cases, each vendor creates a range of microcontrollers that span a range of requirements for embedded systems developers.
This proliferation of devices means that as a developer you can select a suitable microcontroller from many hundreds of devices while still using the same tools and skills regardless of the silicon vendor. This explosive growth in Cortex-M-based microcontrollers has made the Cortex-M processor the de facto industry standard for 32-bit microcontrollers and there are currently no real challengers.
The flip side of the coin is differentiation. It would be possible for a microcontroller vendor to design their own proprietary 32-bit processor. However, this is expensive to do and also requires an ecosystem of affordable tools and software to achieve mass adoption. It is more cost effective to license the Cortex-M processor from ARM and then use their own expertise to create a microcontroller with innovative peripherals.
There are now more than 10 silicon vendors shipping Cortex-M-based microcontrollers. While in each device the Cortex-M processor is the same, each silicon manufacturer seeks to offer a unique set of user peripherals for a given range of applications.
E-mail This Article | Printer-Friendly Page |
Related Articles
- Dealing with automotive software complexity with virtual prototyping - Part 1: Virtual HIL development basics
- Defining standard Debug Interface Socket requirements for OCP-Compliant multicore SoCs: Part 1
- Understanding layers in the JESD204B specification: A high speed ADC perspective, Part 1
- Optimizing embedded software for power efficiency: Part 1 - measuring power
- Automotive System & Software Development Challenges - Part 1