pyadi-dt
pyadi-dt
  • Developer Guides
pyadi-dt

User Guide

  • Quick Start
  • XSA to Device Tree
  • PetaLinux Integration
  • Visualization and Diagnostics
  • Examples
    • XSA Flow Tutorials
    • XSA + adijif Tutorial
    • XSA → Device Tree: AD9081 on ZCU102
    • Board Model: Unified Device Tree Generation
  • Live Update Access Models
  • Utilities

Developer Guide

  • Developer Guides
    • Authoring a new device class
    • Hardware CI
    • Labgrid exporter systemd service
  • XSA Pipeline — Developer Guide

Reference

  • Command Line Interface
  • MCP Server
  • API Reference
    • Core Module
    • Declarative Devices
    • Board Model
    • XSA Pipeline Module

    Developer Guides

    Guides aimed at contributors extending pyadi-dt — new device classes, eval-board composites, FPGA-platform definitions, and XSA board builders.

    • Authoring a new device class
      • 1. Overview & scope
      • 2. Class hierarchy at a glance
      • 3. End-to-end call flow
      • 4. Anatomy of a Device
      • 5. Port & clock-output plumbing
      • 6. Converter patterns
      • 7. Cookbook 1 — Adding a new clock device
      • 8. Cookbook 2 — Adding a new converter / transceiver
      • 9. Cookbook 3 — Adding an eval board or an FPGA board
      • 10. Bridging to the XSA pipeline
      • 11. Testing your new device
    • Hardware CI
      • How it works
      • Boot reliability
      • Board power-off on teardown
      • Node manifest
      • Adding a new hardware node
      • Self-hosted runner registration
      • Exporter systemd service
      • Fork-PR approval gate
      • Private-repo dependency access
      • Debug artifacts
      • Local DT-emission parity test
      • Troubleshooting
    • Labgrid exporter systemd service
      • Convention
      • Installation
      • Installer options
      • Day-to-day operation
      • Migrating from the older templated scheme
      Utilities Authoring a new device class
    ©2024-2026, Analog Devices, Inc. | Made with Sphinx & Doctools