chsh-sk-ncs-3-dev-debug

Diagnose boot failures, WiFi issues, crashes, and hangs on Nordic nRF firmware.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-3-dev-debug-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-3-dev-debug
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-3-dev-debug
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-3-dev-debug-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Debugging firmware on Nordic nRF devices involves juggling UART logs, crash dumps, board configuration quirks, and intermittent failures. This Skill provides a systematic workflow that routes any firmware reliability symptom to the right diagnostic mode and tool. ## Core Features & Use Cases - Guided debug modes: Routes symptoms to dedicated workflows — serial capture and reset (Mode A), WiFi debugging (Mode B), crash/hardfault analysis with addr2line and GDB (Mode C), co-processor barrier debugging (Mode D), and loop stability testing (Mode F). - Baseline and safety checks: Enforces board/port confirmation, nRF54LM20DK Board Configurator verification, serial port availability checks, and live session logging before any hardware operation. - External tool integration: Covers Saleae logic analyzer, JLink probe, router control, PPK2, GitHub Actions CI debugging, and EEDP hardware-in-the-loop automation via MCP. - Use Case: A device silently reboots during WiFi reconnect. The Skill identifies the hidden fault dump pattern, enables immediate log mode, decodes PC/LR with the Zephyr SDK addr2line, and pinpoints a sysworkq stack overflow fixed by raising CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE. ## Quick Start Ask the agent to debug why your nRF54LM20DK board shows no UART output after flashing, and it will check the Board Configurator, capture the boot log, and diagnose the failure.

Frequently Asked Questions about chsh-sk-ncs-3-dev-debug

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

FAQPage Schema
How do I debug a boot failure on an nRF54LM20DK board?

Start with serial capture and reset to read the boot log, after verifying Board Configurator settings in nRF Connect for Desktop. External memory is disabled by default, which causes JEDEC ID read failures that look like firmware bugs but are hardware configuration issues.

How to decode a Zephyr hardfault dump with addr2line?

Use the Zephyr SDK arm-zephyr-eabi-addr2line, not arm-none-eabi-addr2line, against the per-app zephyr.elf in the sysbuild sub-directory. Decode both the PC (faulting instruction) and LR (calling function) addresses from the fault dump.

Why does my nRF device reboot silently during WiFi reconnect?

Silent reboots during reconnect typically indicate a system workqueue stack overflow, since the reconnect path uses about 4488 bytes of stack. Enable CONFIG_LOG_MODE_IMMEDIATE to surface the hidden fault dump, then set CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=6144.

Can I use a logic analyzer or JLink probe with this debugging workflow?

Yes, the workflow integrates Saleae logic analyzers and JLink probes through MCP servers for SPI/I2C bus capture, memory inspection, and CPU halt/resume. These are used when UART logs alone cannot reveal protocol timing or memory-state issues.

How many loop test iterations confirm a firmware fix is stable?

Run 10 iterations as the minimum acceptance gate and 20 iterations for a release claim. The loop test resets the board, connects WiFi, and verifies status each cycle, logging per-iteration pass/fail results.

What should I check before starting serial debugging on Nordic boards?

Confirm the exact board and VCOM port, verify the port is not held by another process using lsof, and create a session log file for live monitoring. Wrong port selection produces silently misleading output.