Ozone
Debugger and performance analyzer
SEGGER's multi-platform debugger and performance analyzer for Arm- and RISC-V-based applications
1. Key Features
2. How Ozone Works
3. Efficient Debugging
4. Target Control and Communication
5. RTOS and Middleware Support
6. System and Performance Analysis
7. Setup and Test Automation
8. Debug - and - Trace Prob Support
9. System requirements
10. Licensing
Overview
Ozone is a full-featured graphical stand-alone debugger for embedded applications. With Ozone, it is possible to debug any Arm- or RISC-V-based embedded application on the C, C++, and Rust source and assembly levels.
Ozone can load applications built with almost any toolchain or integrated development environment (IDE), or debug a target's resident application with no source. It includes all well-known debug controls and information windows. While Ozone performs best with J-Link and J-Trace debug and trace probes, it is also available for use with third-party probes and simulators.
More than just a debugger, Ozone provide comprehensive performance analysis tools, including instruction tracing , code profiling, and code coverage. This allows users to measure execution time, detect bottlenecks, track down inefficiencies and bugs, and analyze system behavior in the event of crashes or other technical issues.
Key Features
Advanced Debugging
Ozone is an intuitive full-featured graphical debugger. It provides all common debug tools, such as a source window, memory and register windows, execution control, and more. In addition, it also adds numerous tools for validation, advanced debugging, and performance analysis
Performance Analysis
Ozone turns raw trace data into actionable insights. Visual timelines, code profiling, and coverage reports helps identify bottlenecks, optimize execution paths, and validate test completeness - ensuring highly reliable systems
Maximum
Flexibility
Ozone supports any toolchain, including Embedded Studio, GCC-based IDEs, Clang/LLVM, IAR, the ARM Compiler, and others. This ensures maximum flexibility, as applications can be loaded from a user's preferred build environment or debugged directly on a device with no need to rebuild
Testing and Automation
Automation interface grants full access to the console window, allowing a user to issue commands and monitor output. Anything that can be done in a manual debug session can also be done via the automation interface in an automated environment
How Ozone Works
Using Ozone stars with creating firmware with a toolchain of the user's choice. Once Ozone is started, the user selects a firmware image and a target microcontroller or microprocessor in order to start debugging immediately. Ozone establishes a connection with a debug probe and provides full control over the target system. When changes are made to the firmware image, a running Ozone instance detects the update and suggests using the modified image.
Users who want to quickly verify a simple code change can also use the built-in source editor to apply an immediate bug fix or perform a quick test.
Efficient Debugging
Ozone provides developers with all of the features commonly found in modern debuggers. These include a full-fledged source-code window, syntax highlighting, symbol and data windows, and register and memory displays. Ozone goes beyond typical debugging use cases to enable efficient and extensive debugging within a fully integrated user interface.
Target Control and Communication
Ozone provides full control over the target via the debug interface, which means users can step through code, utilize breakpoints, and more. Additionally, Ozone enables device communication and logging of firmware output.
RTOS and Middleware Support
Ozone offers debug tools designed to address the growing complexity of modern embedded systems. To enable users to gain improved insight into the behavior of an RTOS or middleware, Ozone includes RTOS plug-ins and a SmartView interface for middleware.
System and Performance Analysis
Ozone helps developers understand how their embedded systems perform. It collects a wide range of valuable information, such as data on instruction traces, power consumption, and more. Its performance analysis features make it easier to understand and optimize a system.
Setup and Test Automation
Automation tasks, Ozone users can add scripts to a project or run them directly in the console. By utilizing scripts, users can create consistent and comprehensive verification and debug setups, as well as automated tests that do not require user interaction.
These scripts can perform almost all actions available through Ozone's graphical user interface. They can be used to configure the GUI and automate the debug work flow. Users also have access to event handlers, so they can create triggering events for specific actions within a script. Events include downloads, resets, halts, gos, and breakpoints. Users can set triggers to occur before, after, or at the time of an event.
Debug-and Trace-Probe Support
J-Trace
- Source view with syntax highlighting
- Debug information windows
- Terminal communication
- Full target control
- ROTS awareness
- SmartView for middleware
- Data sampling
- Real Time Transfer (RTT)
- Instruction tracing
- Unlimited Flash Breakpoints
- Ozone license
- Power profiling
J-Link
- Source view with syntax highlighting
- Debug information windows
- Terminal communication
- Full target control
- RTOS awareness
- SmartView for middleware
- Data sampling
- Real Time Transfer (RTT)
- No Instruction tracking
- Unlimited Flash Breakpoints (Depends on Probe)
- Ozone license (Depends on Probe)
- Power profiling (Depends on Probe)
GDB-Server Interface
- Source view with syntax highlighting
- Debug information windows
- Terminal communication
- Full target control
- RTOS awarness
- SmartView for middleware
- Data sampling
- No Real Time Transfer (RTT)
- Instruction tracing (Depends on Probe)
- No Unlimited Flash Breakpoints
- No Ozone License
- No Power profiling
System Requirements
| Operating System | Version |
|---|---|
| Windows | Microsoft Windows (Arm/Intel) |
| macOS | macOS (Apple/Intel) |
| Linux | Linux |
| Hardware component | Item |
|---|---|
| CPU | 1GHz or better |
| Memory | 1GB RAM |
| Disk space | 1GB |
| Debug probe | J-Link, J-Trace or GDB Server |
Licensing
For commercial use, SEGGER’s Commercial-use License is required. Licenses for Ozone are perpetual, meaning the tool can be used indefinitely and no annual subscription is required.
J-Link PLUS, J-Link Ultra, J-Link Pro, and J-Trace PRO include a free Ozone license. When using other debug probes, Ozone can be licensed separately for commercial use.