The downside of the ease of programming is that debugging without the right tools is harder: figuring out a bug that is caused by two threads, running even simultaneously on two different CPU cores, can take a long time when all you have are printf() statements. The FreeRTOS OS that comes with ESP-IDF is capable of multi-core preemptive scheduling, allowing for an intuitive way of writing software. The ESP32 has two powerful Xtensa cores, allowing for a great deal of variety of program architectures. This section provides collection of tips and quirks related to JTAG debugging of ESP32 with OpenOCD and GDB. Procedure to build OpenOCD from sources for Windows, Linux and macOS operating systems. If you are not familiar with GDB, check this section for debugging examples provided from Eclipse as well as from Command Line. Steps to start up a debug session with GDB from Eclipse and from Command Line. Configuring ESP32 TargetĬonfiguration of OpenOCD software and setting up of JTAG adapter hardware, which together make up the debugging target. Procedure to install OpenOCD and verify that it is installed. What are the criteria and options to select JTAG adapter hardware. How it Works?ĭescription how ESP32, JTAG interface, OpenOCD and GDB are interconnected and working together to enable debugging of ESP32. Introduction to the purpose of this guide.
The document is structured as follows: Introduction This document provides a guide to installing OpenOCD for ESP32 and debugging using GDB.
0 kommentar(er)
