the signals and their derived score are provisional and subject to change.
validate manually before sharing.
b796a16843390e548dd70d5d1a8eae83505a18b6e98343476fd03 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdk14cac5e9aba43 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdk4e44429c10c53 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdk846666f8e3be3 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdk5d529a91b49a3 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdkf2d8b417758c3 weeks agoClaude-Session: https://claude.ai/code/session_015wddLpJLCZcURH5D5TbNdk---
name: capture-samd51-logic-analyzer
description: "Capture and analyze SAMD51 board signals with sigrok-cli; use when a task requires the repository's fx2lafw logic-analyzer setup, reset timing, or capture validation workflow."
---
# Capture and Analyze the Logic Analyzer
Use this skill when you need to capture board activity with the USB logic analyzer and inspect the recorded data.
## Device And Channel Map
- Analyzer driver: `fx2lafw`
- Channels used for the board reset check:
- `D0` -> `PA01`
---
name: debug-pvdxos-hardware
description: Debug the PVDXos firmware (SAMD51P20A, FreeRTOS) on real hardware via J-Link, GDB and RTT logs. Use for hard faults, resets, hangs, task or stack problems, or inspecting registers, memory and backtraces on the running board. For building and flashing, use build-and-flash-pvdxos.
---
# Debugging PVDXos on hardware
Use only the wrappers in `tools/`. Never run these directly; they are interactive or never
terminate and will hang the session: `make connect`, `make ---
name: build-and-flash-pvdxos
description: "Build, flash, and verify the PVDXos SAMD51 firmware with SEGGER J-Link; use when a task requires the repository's hardware build or standalone flashing workflow."
---
# Build and Flash PVDXos
Use this skill when a future agent needs the standard build and flash flow for this repository.
## Build
Run the build from the repository root:
```bash
make clean all
```
This builds the bootloader, builds the main firmware, and runs `scripts/create_flash_segment.py# Copilot compatibility
Follow the canonical repository-wide instructions in [`AGENTS.md`](../AGENTS.md).
Use the shared skills in `.agents/skills/` when their descriptions match the
task. This file intentionally contains no duplicate project or skill
procedures.
# PVDXos Repository Instructions
PVDXos is the real-time operating system for Brown Space Engineering's PVDX
satellite, running on an ATSAMD51P20A/SAMD51 Cortex-M4. The firmware is built
with the Arm GNU toolchain (`arm-none-eabi-*`) and runs on hardware such as the
Adafruit Grand Central development board.
## Architecture and hardware
- `bootloader/` contains three independently linked `0x3000`-byte bootloader
images at flash offsets `0x00000000`, `0x00003000`, and `0x00006000`.
`startup.c` validate# PVDXos Repository Instructions
PVDXos is the real-time operating system for Brown Space Engineering's PVDX
satellite, running on an ATSAMD51P20A/SAMD51 Cortex-M4. The firmware is built
with the Arm GNU toolchain (`arm-none-eabi-*`) and runs on hardware such as the
Adafruit Grand Central development board.
## Architecture and hardware
- `bootloader/` contains three independently linked `0x3000`-byte bootloader
images at flash offsets `0x00000000`, `0x00003000`, and `0x00006000`.
`startup.c` validate@AGENTS.md
none