Book Image

The Insider's Guide to Arm Cortex-M Development

By : Zachary Lasiuk, Pareena Verma, Jason Andrews
Book Image

The Insider's Guide to Arm Cortex-M Development

By: Zachary Lasiuk, Pareena Verma, Jason Andrews

Overview of this book

Cortex-M has been around since 2004, so why a new book now? With new microcontrollers based on the Cortex-M55 and Cortex-M85 being introduced this year, Cortex-M continues to expand. New software concepts, such as standardized software reuse, have emerged alongside new topics including security and machine learning. Development methodologies have also significantly advanced, with more embedded development taking place in the cloud and increased levels of automation. Due to these advances, a single engineer can no longer understand an entire project and requires new skills to be successful. This book provides a unique view of how to navigate and apply the latest concepts in microcontroller development. The book is split into two parts. First, you’ll be guided through how to select the ideal set of hardware, software, and tools for your specific project. Next, you’ll explore how to implement essential topics for modern embedded developers. Throughout the book, there are examples for you to learn by working with real Cortex-M devices with all software available on GitHub. You will gain experience with the small Cortex-M0+, the powerful Cortex-M55, and more Cortex-M processors. By the end of this book, you’ll be able to practically apply modern Cortex-M software development concepts.
Table of Contents (15 chapters)
1
Part 1: Get Set Up
5
Part 2: Sharpen Your Skills

Navigating IDEs

Arm Cortex-M processors are supported by all the major IDE vendors. Some of the IDEs are Eclipse-based, some are based on a proprietary graphical user interface (GUI), and some are open source. They are available at a variety of price points and licensing business models, ranging from free to low-cost based on open source to higher-priced proprietary IDEs.

As we introduced earlier, IDEs are a complete solution for code development and debugging. The distinction between SDKs and IDEs is subtle, but differentiating between them is helpful in thinking about different groups of tools. Some (but not all) SDKs include IDEs, such as the NXP MCUXpresso SDK, which includes software libraries for your particular NXP board and also an IDE to develop on. Some SDKs do not include IDEs—for example, the Raspberry Pi Pico SDK. One definition of an IDE is a tool with a GUI that is used for editing, compiling, and debugging. The user interface (UI) takes care of calling the...