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

The basics of hello world

Running hello world or Blinky on a microcontroller involves more than just a print statement. The traditional hello world program in C may look as follows:

#include <stdio.h>int main()
    printf("Hello Cortex-M world!\n");

If I compile this program and run it on any of my laptop computers, it will print the following message:

$ gcc -o hello hello.c
$ ./hello
Hello Cortex-M world!

Developers are not typically interested in the details of running a C program on a computer running Windows, Linux, or macOS. It’s clear that the printf function is defined in a C header file, stdio.h, and there is a C library that provides the code. Most developers generally understand that a new process is created, the program is loaded into memory, and the C language defines the standard output file (stdio) to be the terminal and writes the message. The operating system will take care of the details to run the program...