Search skills.../

Stlink Uart Health | Skills Pool

Skill File

Stlink Uart Health

Use when diagnosing board connectivity, ST-Link access, SWD mailbox reads, nanoff E2001/E2002 errors, /dev/ttyUSB0 instability, transport contention, or deciding whether failures are wiring, host permissions, firmware mode, or tool timing. Keywords: ST-Link, SWD, UART preflight, nanoff listdevices, devicedetails, bringup transport triage.

getpwnam0 starsApr 10, 2026

Occupation
Categories: Debugging

Skill Content

ST-Link and UART Health Triage

Purpose

Run a deterministic, non-destructive transport triage for this board and classify failures quickly.

Primary Targets

software/nanoFramework/toolchain/uart-preflight.sh
software/nanoFramework/tests/swd_read_bringup_status.sh
software/nanoFramework/toolchain/build.sh
software/nanoFramework/docs/BRINGUP_TEST_LOG.md

When To Use

nanoff listdevices/devicedetails intermittently fail.
SWD works but UART does not, or vice versa.
There are E2001/E2002 deployment errors.
You need a clear next action instead of ad hoc probing.

Workflow

Verify basic transport visibility:
- serial device presence

Related Skills

Quick Install

Stlink Uart Health

npx skills add getpwnam/diseqc_cntrl

Download Skill Open repository

Author: getpwnam
stars: 0
Updated: Apr 10, 2026
Occupation

On this page

01ST-Link and UART Health Triage

st-info probe success

Run UART preflight:

classify timeout vs no-device vs partial success

Run SWD mailbox read:

confirm target is responsive independently of UART

If needed, run reset then retry nanoff listdevices/devicedetails once.

Classify into one of these buckets:

Host-side access or permission issue
Cable/orientation or physical UART path issue
Firmware profile not exposing wire protocol
Debugger contention or timing race
Intermittent transport requiring bounded retries

Provide one specific next action for the detected bucket.

Append a concise factual log entry to BRINGUP_TEST_LOG.md when requested.

Output Format

Transport state: PASS, DEGRADED, or FAIL
Evidence lines:
- st-info result
- nanoff listdevices result
- nanoff devicedetails result
- swd mailbox result
Root-cause bucket
Next action (single highest-value step)

Guardrails

Prefer non-destructive commands first.
Avoid long unbounded loops.
Keep retries bounded and explicit.
Separate transport failures from firmware functional failures.

02

Purpose

03Primary Targets

06Output Format

Electronics Engineers, Except Computer

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Electronics Engineers, Except Computer