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

Executing software and debugging in the cloud

Making a custom docker image for Gitpod is not much different from the generic dev container. The main difference is the starting point for the image. Instead of starting from Ubuntu, we start from the Gitpod base container, gitpod/workspace-base. The second difference is the username. We created the ubuntu user previously, but with the Gitpod container, the username is already set to gitpod. The final difference is that the package installation requires sudo in front of the commands because everything in the Dockerfile is run by the gitpod user. 

Creating a custom Gitpod image

Take a look at the Dockerfile in the pico-dev-container GitHub repository ( to see the differences in the Dockerfile intended for Gitpod. Gitpod is only available for the x86 architecture, so there is no aarch64 image for Gitpod. Maybe...