Book Image

ARM® Cortex® M4 Cookbook

By : Mark Fisher, Dr. Mark Fisher
Book Image

ARM® Cortex® M4 Cookbook

By: Mark Fisher, Dr. Mark Fisher

Overview of this book

Embedded microcontrollers are at the core of many everyday electronic devices. Electronic automotive systems rely on these devices for engine management, anti-lock brakes, in car entertainment, automatic transmission, active suspension, satellite navigation, etc. The so-called internet of things drives the market for such technology, so much so that embedded cores now represent 90% of all processor’s sold. The ARM Cortex-M4 is one of the most powerful microcontrollers on the market and includes a floating point unit (FPU) which enables it to address applications. The ARM Cortex-M4 Microcontroller Cookbook provides a practical introduction to programming an embedded microcontroller architecture. This book attempts to address this through a series of recipes that develop embedded applications targeting the ARM-Cortex M4 device family. The recipes in this book have all been tested using the Keil MCBSTM32F400 board. This board includes a small graphic LCD touchscreen (320x240 pixels) that can be used to create a variety of 2D gaming applications. These motivate a younger audience and are used throughout the book to illustrate particular hardware peripherals and software concepts. C language is used predominantly throughout but one chapter is devoted to recipes involving assembly language. Programs are mostly written using ARM’s free microcontroller development kit (MDK) but for those looking for open source development environments the book also shows how to configure the ARM-GNU toolchain. Some of the recipes described in the book are the basis for laboratories and assignments undertaken by undergraduates.
Table of Contents (16 chapters)
ARM Cortex M4 Cookbook
About the Author
About the Reviewer


The title of the last chapter included the phrase, "Real Time". The term, Real Time, is used to describe a computing system that must meet deadlines. We did not define this term in Chapter 7, Real-Time Signal Processing because, in the context of handling audio samples, an implicit deadline is the sampling rate. However, you may recall that our ISR illuminated an error LED if the main super loop did not output the previous sample before a new sample arrived.

The audio application is an example of a soft deadline. It wouldn't be a catastrophe if the system missed this deadline once or twice; the audio quality would suffer, but this may go unnoticed. Contrast this with other applications, such as an embedded system used in fly-by-wire avionic applications, medical equipment, or a nuclear reactor. In these cases, missing a deadline could be catastrophic and result in death. Deadlines in these cases are known as hard deadlines and, in order to meet safety standards, designers need...