Tick runtime deploy (ZCU102 + AD9081)

The Tick classes deploy the axi_timed_command_scheduler IP onto a board that already booted its pre-baked Kuiper SD image, at runtime over SSH.

Components

  • TickArtifacts (resource) – paths to the bitstream, prebuilt .dtbo overlay, and kernel module, plus target-side naming.

  • TickFpgaManagerDriver – programs the FPGA via the fpga_manager sysfs.

  • TickOverlayDriver – applies/removes the DT overlay via configfs.

  • TickModuleDriver – insmods the module and (optionally) restarts iiod so the IIO device is network-discoverable.

  • BootTickFPGASSH – subclasses BootFPGASoCSSH; boots to a shell, then runs the three deploy steps. States: tick_fpga_loaded -> tick_overlay_applied -> tick_module_loaded; tick_off reverses the deploy and powers down.

Example environment

imports:
  - adi_lg_plugins
targets:
  main:
    resources:
      - RemotePlace: {name: mini2}
      - TickArtifacts:
          bitstream_path: /run/tick/ad9081_fmca_ebz_zcu102.bit
          overlay_dtbo_path: /run/tick/tick.dtbo
          module_ko_path: /run/tick/axi_timed_command_scheduler.ko
    drivers:
      - VesyncPowerDriver: {}
      - SSHDriver: {keyfile: ""}
      - TickFpgaManagerDriver: {}
      - TickOverlayDriver: {}
      - TickModuleDriver: {}
      - BootTickFPGASSH: {}

Note

The Tick drivers bind the CommandProtocol + FileTransferProtocol pair. When the env also defines a console-based shell that satisfies those protocols, name the intended SSH driver explicitly so binding is unambiguous.