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)
Part 1: Get Set Up
Part 2: Sharpen Your Skills

Example software stacks for common use cases

As with selecting hardware, choosing the right software stack depends greatly on your final use case. The functionality required for a low-power IoT sensor and an always-on facial recognition camera is quite different. In Chapter 1, Selecting the Right Hardware, we described six discrete areas to help select the right Cortex-M processor. In contrast, selecting the right software for a given use case, given the number of overlapping options available, has more room to include personal preference.

In this section, we will take the same use cases from the previous chapter and talk through their software requirements. We will then distill the requirements into reasonable selections for each part of the software stack. Note that there are many ways to build a working software stack for these use cases, and other options may be more optimal given previous experience, cost constraints, personal preference, development time versus quality trade...