![]() ![]() Then, in the entry field below, enter the following lines: Under Initialization Commands uncheck Reset and Delay (seconds) and Halt. The last tab that requires changing the default configuration is Startup. In field GDB Command, enter xtensa-esp32-elf-gdb to invoke the debugger.Ĭhange the default configuration of the Remote host by entering 3333 under the Port number.Ĭonfiguration entered in points 6 and 7 is shown on the following picture.Ĭonfiguration of GDB Hardware Debugging - Debugger tab Refer to the Eclipse Plugin for instructions.įinally, under Build (if required) before launching click Disable auto build.Ī sample window with settings entered in points 1 - 5 is shown below.Ĭonfiguration of GDB Hardware Debugging - Main tab Ĭlick the Debugger tab. If blink.elf is not there, it is likely that this project has not been built yet. In the next line under C/C++ Application:, press the Browse button and select the blink.elf file. On the Main tab below, under Project:, press the Browse button and select the blink project. In a form that will show up on the right, enter the Name: of this configuration, e.g. In the left pane of the window, double-click GDB Hardware Debugging (or select GDB Hardware Debugging and press the New button) to create a new configuration. In Eclipse, go to Run > Debug Configuration. The source of get-started/blink application is available in examples directory of ESP-IDF repository. If not done already, add this project to Eclipse workspace following Eclipse Plugin. This will be shown below by configuring debugging for “blink” example project. Please note that some configuration parameters are generic, while others are project-specific. To install the GDB Hardware Debugging plugin, open Eclipse and select Help > Install New Software.Īfter installation is complete, follow these steps to configure the debugging session. This approach is recommended only if you are unable to debug using ESP-IDF GDB OpenOCD Debugging for some reason. Therefore, it is recommended to use the ESP-IDF GDB OpenOCD Debugging via the IDF Eclipse plugin. All the required configuration parameters will be pre-filled by the plugin, and you can start debugging with just a click of a button. This functionality supports configuring the OpenOCD server and GDB client from within Eclipse. To make the debugging process easier, the IDF Eclipse plugin has a customized ESP-IDF GDB OpenOCD Debugging functionality. This approach can be time-consuming and error-prone. For ESP-IDF applications, IDF Eclipse plugin provides two ways of debugging:īy default, Eclipse supports OpenOCD Debugging via the GDB Hardware Debugging plugin, which requires starting the OpenOCD server from the command line and configuring the GDB client from Eclipse to start with the debugging. It is recommended to first check if debugger works using idf.py debug targets or from Command Line and then move to using Eclipse.Įclipse is an integrated development environment (IDE) that provides a powerful set of tools for developing and debugging software applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |