skills.rest
Sonder4
Sonder4COMMUNITY
Explore all skills by this author →
GitHub

bfd-ozone

Generate canonical SEGGER Ozone .jdebug files and bind J-Link probes to STM32 profiles.

27|1|Updated Mar 9, 2026
Search Tags:#automation#debugging#stm32#project-generation#jlink#ozone#probe-binding
One-click install
npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-ozone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bfd-ozone
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-ozone
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-ozone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates canonical SEGGER Ozone project preparation and binding of J-Link probes to STM32 bootstrap profiles, ensuring Ozone sessions start from a clean, current project configuration.

Core Features & Use Cases

  • Canonical Ozone generation: render a standardized .jdebug/.jdebug.user from the active STM32 bootstrap profile.
  • Probe binding and environment consistency: manage USB binding, device/OSPlugin settings, ELF/SVD paths, and open-document/watched-variable state for debugging sessions.
  • Quick-start oriented workflows: recover from stale or misconfigured Ozone exports and launch ready-to-debug sessions from the current project.

Quick Start

Render a canonical Ozone project from the active STM32 bootstrap profile using python3 scripts/prepare_ozone_project.py, then launch Ozone with scripts/launch_ozone.sh.

Frequently Asked Questions about bfd-ozone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a canonical Ozone .jdebug file for my STM32 project?▼

You generate a canonical Ozone .jdebug file for STM32 by running prepare_ozone_project.py, which renders standardized debugging configurations from the active project bootstrap profile.

Why does my SEGGER Ozone session launch with stale ELF and SVD paths?▼

Ozone sessions launch with stale ELF and SVD paths when project exports are misconfigured; running project preparation scripts refreshes these paths to match the active STM32 bootstrap.

How do I bind a J-Link probe to an STM32 debug session in Ozone?▼

You bind a J-Link probe to an STM32 debug session in Ozone by using the project generation script to configure USB binding and device settings within the canonical .jdebug file.

Can I configure OSPlugin settings and watched variables for Ozone automatically?▼

Yes, you can configure OSPlugin settings and watched variables automatically by generating a canonical .jdebug.user file that manages Open Documents and watch state for debugging sessions.

What is the best way to recover from a misconfigured Ozone export?▼

The best way to recover from a misconfigured Ozone export is to regenerate the .jdebug and .jdebug.user files from the active STM32 bootstrap profile and relaunch Ozone.

Do I need a specific J-Link setup to open a controlled Ozone profile for STM32?▼

You need a J-Link probe connected via USB to open a controlled Ozone profile for STM32, as the generation scripts specifically handle probe binding and environment consistency.

Related Skills

Explore More Software Engineering Skills→
Sonder4Sonder4
27

bfd-project-init

Generate canonical STM32 runtime profiles from IOC, startup, linker, SVD, and CFG artifacts.

Community
Advanced
Sonder4Sonder4
27

bfd-debug-executor

Execute J-Link command sequences for STM32 debugging workflows.

Community
Intermediate
Sonder4Sonder4
27

bfd-stlink-interface

Flash, read, and write STM32 memory via ST-Link CLI tools.

Community
Intermediate
Sonder4Sonder4
27

bfd-debug-orchestrator

Orchestrate multi-tool STM32 debugging campaigns with flashing, RTT logging, and fault evidence archival.

Community
Advanced