Skip to content

Releases: Minhyuin/PinyCore-debug-skill

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 13 Oct 15:43

PinyCore-debug-skill 0.3.0

Agent-facing skill package for debugging and profiling a PinyCore board over a SEGGER
J-Link: register access through GDB, CPU-load measurement through SEGGER SystemView.

  • Skills version: 0.3.0 (scripts/piny_debug.py --version)
  • Tests: 213 (python -X utf8 -m unittest discover -s tests -t tests)
  • Python 3.10+ on Windows and Linux; standard library only, no pip install

Changes since v0.2.1

新增 / Features

  • feat(chip): make a second board one profile key

文档 / Documentation

  • doc(status): the stale Codex copy is now the released skill
  • doc(status): record the 0.2.1 release and the re-synced install

Install

git clone https://github.com/Minhyuin/PinyCore-debug-skill.git
Copy-Item -Recurse PinyCore-debug-skill "$env:USERPROFILE\.dsh\skills\PinyCore-debug"
# then, in your PinyCore checkout:
Copy-Item profiles\pinycore.example.json profiles\my-rig.json   # fill it in
python scripts\piny_debug.py doctor --portable                   # what to fix
python scripts\piny_debug.py doctor --write-profile profiles\my-rig.json

The archive attached to this release is the same package; it deliberately does not
contain profiles/pinycore.json, which names one machine and one probe.

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 12 Oct 20:28

PinyCore-debug-skill 0.2.1

Agent-facing skill package for debugging and profiling a PinyCore board over a SEGGER
J-Link: register access through GDB, CPU-load measurement through SEGGER SystemView.

  • Skills version: 0.2.1 (scripts/piny_debug.py --version)
  • Tests: 183 (python -X utf8 -m unittest discover -s tests -t tests)
  • Python 3.10+ on Windows and Linux; standard library only, no pip install

Changes since v0.1.0

新增 / Features

  • feat(platform): support Linux hosts as well as Windows

修复 / Fixes

  • fix(view): take a pushed copy back out of the picture when the caller does
  • fix(view): do not reinstall the proxy over a patched backend lookup
  • fix(view): ask before asserting when no dialog backend exists
  • fix(view): stop wrapping the wrapper on every call
  • fix(view): a replaced lookup has to reach the button search
  • fix(linux): report one install per file, not per path that reaches it
  • fix(platform): describe the platform that is actually running

杂项 / Chores

  • chore(ci): log what the X11 runner actually sees

Install

git clone https://github.com/Minhyuin/PinyCore-debug-skill.git
Copy-Item -Recurse PinyCore-debug-skill "$env:USERPROFILE\.dsh\skills\PinyCore-debug"
# then, in your PinyCore checkout:
Copy-Item profiles\pinycore.example.json profiles\my-rig.json   # fill it in
python scripts\piny_debug.py doctor --portable                   # what to fix
python scripts\piny_debug.py doctor --write-profile profiles\my-rig.json

The archive attached to this release is the same package; it deliberately does not
contain profiles/pinycore.json, which names one machine and one probe.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 18:46

PinyCore-debug-skill 0.1.0

Agent-facing skill package for debugging and profiling a PinyCore board over a SEGGER
J-Link: register access through GDB, CPU-load measurement through SEGGER SystemView.

  • Skills version: 0.1.0 (scripts/piny_debug.py --version)
  • Tests: 130 (python -X utf8 -m unittest discover -s tests -t tests)
  • Python 3.10+ on Windows; standard library only, no pip install

Changes

新增 / Features

  • feat(skill): agent-facing STM32H723 debug and CPU-load skill

测试 / Tests

  • test(ci): keep the suite honest on the platform that runs it

Install

git clone https://github.com/Minhyuin/PinyCore-debug-skill.git
Copy-Item -Recurse PinyCore-debug-skill "$env:USERPROFILE\.dsh\skills\PinyCore-debug"
# then, in your PinyCore checkout:
Copy-Item profiles\pinycore.example.json profiles\my-rig.json   # fill it in
python scripts\piny_debug.py doctor --portable                   # what to fix
python scripts\piny_debug.py doctor --write-profile profiles\my-rig.json

The archive attached to this release is the same package; it deliberately does not
contain profiles/pinycore.json, which names one machine and one probe.