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

Debugging your code using print statements

This section deals with debugging. Errors fall into two classes, compilation errors and run-time errors. Compilation errors arise when we compile our programs, and the compiler parses each of the statements to produce executable code. Syntactic errors such as a missing semi-colon or forgetting to declare a variable before assigning it will produce a compilation error. Luckily, uVision5 highlights and checks the syntax of our programs as we type. So, many problems that would have gone undetected in the past are now brought to our attention before compilation. When errors do occur, they are printed in the output window together with details of the file and the line number where the error occurred. In addition to errors, the compiler will also issue warnings relating to unusual conditions in the code that might be indicative of a problem. It's a good plan to treat warnings as errors, and track down their source. Further information about compiler diagnostic...