Summary
This chapter presented the development-tools that we’ll use throughout the book. The IDE we’ll be using is the STM32CubeIDE, including its source-code editor, the build system, the system libraries, and the code generator.
Three SEGGER debugging tools are also used. A J-Link debug-probe is used, and it is made available by installing J-Link firmware on the ST-Link part of the dev-board. Ozone is used to load firmware on the MCU, and it provides source-code debugging. SystemView provides real-time monitoring of the firmware, and a means for viewing the application’s debug-messages.
The book’s example-programs were also presented, including how to install them for use in the IDE.
Appendix A provides a quick-reference for using the tools (i.e., a “cheat-sheet”). It summarizes the tool-use instructions from the present chapter.
In the next two chapters, we’ll see how a super-loop program works, and how it can be...
