How to Quit GDB While Keeping Your Target Running on STM32H7 Boards

Discover a straightforward solution to debug your STM32H7 while keeping your target device operational. Learn how to detach from GDB and perform resets without interruption.
---
This video is based on the question https://stackoverflow.com/q/73582009/ asked by the user 'Guillaume Petitjean' ( https://stackoverflow.com/u/5836577/ ) and on the answer https://stackoverflow.com/a/73585066/ provided by the user 'Andrew' ( https://stackoverflow.com/u/3228495/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Quit gdb while the target keeps running on STM32H7

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Keep Your STM32H7 Running: Disconnecting GDB Safely

Debugging embedded systems can often feel daunting, especially when you need the flexibility to reset or run multiple targets simultaneously. If you're working with two STM32H7 boards and using GDB for debugging, you might run into the challenge of needing to reset one board while keeping the other operational. In this guide, we’ll explore how you can achieve this without hindering your device's functionality.

The Problem: Remote Debugging Limitations

When debugging remotely using the STLink GDB server for your first STM32H7 board, it may seem counterintuitive to perform a reset or restart the second board. Here are some key points regarding the situation:

Debugging Environment: You are using STMicro Cube IDE and wish to manage two STM32H7 eval boards.

Desired Functionality: You want to reset and run the second board without pressing any physical buttons, as this could complicate your debugging process.

GDB Behavior: The standard command continue blocks GDB and prevents you from exiting successfully.

The Solution: Using the Detach Command

To solve this dilemma, you can conveniently use the detach command in GDB, which allows you to maintain control over your second STM32H7 while disconnecting from the GDB interface. Here’s how to effectively implement this solution step-by-step:

Step-by-Step Instructions

Connect to the Target: Start your GDB session by connecting to your target:

[[See Video to Reveal this Text or Code Snippet]]

Replace xxx with the correct address of your second STM32H7 board.

Run the Target: You can trigger the desired behavior (run the firmware or other commands) using blocking commands. However, to avoid blocking GDB, simply prepare your command utilizing:

[[See Video to Reveal this Text or Code Snippet]]

Keep in mind that this command may block your GDB session.

Detach from the Target: To safely disconnect without terminating the target’s execution, simply run:

[[See Video to Reveal this Text or Code Snippet]]

This command will effectively close the GDB connection while keeping your target running.

Exit GDB: Finally, you can quit GDB using the command:

[[See Video to Reveal this Text or Code Snippet]]

After executing detach, this will not interfere with your live target and will leave it executing normally.

Why This Works

Separation of Responsibility: The detach command effectively tells GDB to abandon its association with the target hardware, allowing the device to continue executing code independently.

Efficiency: This method saves you from repeated manual resets, enhancing efficiency in your debugging workflow and enabling you to handle multiple boards seamlessly.

Conclusion

Successful remote debugging while maintaining board functionality may seem challenging, but with the detach command in GDB, you can easily reset or run an STM32H7 board while keeping your target device operational. This simple yet effective approach can significantly enhance your development process and make your debugging sessions far more productive.

By incorporating these tips into your workflow, you'll be able to manage multiple STM32H7 boards, allowing your projects to thrive without interruption or manual resets. Happy debugging!