Ozone GDB server support

A GDB Server enables communication between the debugger and a target device. While GDB runs on the host machine, it cannot directly access external hardware. The GDB Server manages this connection by receiving commands from GDB, executing them on the target, and returning the results.

This setup allows remote debugging of embedded systems. Features such as breakpoints, single-step execution, and memory inspection are supported using standard debugging tools.

All functionality defined by the GDB remote protocol is available in Ozone when connected through a GDB server, including:

• Starting and stopping debug sessions
• Controlling target execution (run, halt, reset)
• Stepping into, over, and out of code in source and disassembly windows
• Setting instruction and data breakpoints
• Reading and writing registers and memory
• Downloading firmware images to the target

These capabilities cover the vast majority of everyday debugging tasks, supported by Ozone’s comprehensive debug windows such as source viewer, disassembly, call stack, memory, registers, breakpoints, watched variables, call graph, and memory usage. RTOS and SmartView windows can also be used.

Ozone offers flexible scripting options to integrate with external GDB servers. 

• A GDB server can be launched with a single click via a custom button in Ozone’s button bar.
• In many cases, it can also be started automatically when initiating a debug session.

This setup simplifies the debugging process and ensures compatibility with both SEGGER probes and third-party hardware.