agentsclimarketplace

Segger rtt integration

Skill easyzoom/aix-skills/skills/segger-rtt-integration

Reusable Agent Skills for embedded systems, MCU debugging, firmware workflows, and AI automation. （嵌入式、MCU 调试、固件流程与 AI 自动化的可复用 Agent Skills 集合）。

Install
npx -y skills add easyzoom/aix-skills --skill segger-rtt-integration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when integrating, configuring, or debugging SEGGER RTT logs, J-Link real-time terminal I/O, RTT control blocks, buffers, blocking modes, or embedded debug output

SKILL.md

2.6 KB, 553 tokens by cl100k_base, as published. Nobody here has run it

SEGGER RTT Integration

Overview

Use this skill to integrate SEGGER RTT as a low-intrusion debug channel. Prove the RTT control block, buffer configuration, J-Link connection, and blocking policy before relying on RTT logs in timing-sensitive firmware.

When To Use

Use this skill when:

  • The user wants SEGGER RTT logs or terminal input on an MCU.
  • RTT Viewer/J-Link cannot find the control block, logs are missing, output blocks, or input commands fail.
  • The task involves RTT buffers, up/down channels, blocking modes, J-Link, SystemView, or debug builds.

Do not use this skill when the debug probe cannot connect. Use architecture or flashing debug skills first.

First Questions

Ask for:

  • MCU/core, debug probe, J-Link software version, and IDE/toolchain.
  • RTT source files/config and whether SEGGER_RTT_Init() is called.
  • Output mode: blocking, no-block-skip, or no-block-trim.
  • Buffer sizes and channels used.
  • Whether caches, MPU, low power, or secure/non-secure memory are involved.

Integration Checklist

  1. Include RTT sources once. Avoid duplicate control blocks from multiple copies of RTT source.

  2. Place control block in accessible RAM. J-Link must be able to locate and read the RTT control block.

  3. Configure buffer policy. Blocking output can disturb real-time behavior; choose mode intentionally.

  4. Verify host tooling. RTT Viewer, J-Link console, IDE plugin, or SystemView must attach to the correct target.

  5. Handle cache and low power. Cacheable memory and deep sleep can hide or disrupt RTT buffers.

Common Failures

  • Control block optimized out or duplicated.
  • RTT logs block because host is disconnected and blocking mode is used.
  • Buffers too small for burst logs.
  • J-Link scans wrong RAM region.
  • Cache prevents host from seeing updated data on some cores.

Verification

Before claiming RTT works:

  • State probe, RTT source/config, buffer sizes, and blocking mode.
  • Confirm host tool sees the control block.
  • Confirm one output channel and one input channel if input is needed.
  • Confirm behavior with host disconnected if product timing matters.

Example

User:

SEGGER RTT Viewer 连上了但没有日志。

Agent:

  1. Asks for RTT config, init path, J-Link target, and map/control block placement.
  2. Checks duplicate RTT sources and buffer mode.
  3. Verifies a minimal early boot RTT print.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.