Skip to content

analog M3f phase 2a: the comparator device evaluation as a clocked unit with its table ROMs, bit for bit, placed and routed on the AX7203 part (part of #11380) #11425

Closed

Description

@gHashTag

Part of #11380 (the comparator step on the AX7203), phase 2a. Phase 1 was #11386 (PR #11387).

Requirements

  • FR-001: the device evaluation of sar_comparator_qi.t27 (one PSP103 device: current, charges, the 20 stamp words) is a clocked unit in .t27 with the tables in block-RAM ROMs, and it is bit for bit equal to the spec at every device and step tested.
  • FR-002: one unit with its ROM is placed and routed on xc7a200tfbg484-2 (the openXC7 flow). The resources after routing, the post-route Fmax and the clocks per evaluation are measured and recorded, with the ROM BRAM kept apart from the logic.
  • FR-003: a negative control is refused: a flipped table word makes the unit differ from the spec.

Boundary

  • specs/fpga/
  • docs/analog/

Success Criteria

  • t27c test-report FAIL 0 and vacuous 0 on each new spec; t27b test --check exit 0 with no MISMATCH
  • the resources table and the rerun steps in docs/analog/board-sar-cmp-unit-2026-10-20.md

🤖 Generated with Claude Code

User Scenarios

  • Given the sar_comparator_qi.t27 specification exists, when the device evaluation is implemented as a clocked unit with its table ROMs in block-RAM, then the implementation produces bit-for-bit identical results to the specification at every device and step tested.
  • Given the clocked comparator unit with its ROMs, when it is placed and routed on the xc7a200tfbg484-2 (AX7203) using the openXC7 flow, then the post-route resources, Fmax, and clocks-per-evaluation are measured and recorded with the ROM BRAM resources reported separately from logic resources.
  • Given a flipped table word in the comparator's ROM, when the unit is evaluated against the specification, then the negative control is refused because the unit output differs from the spec.

Activity

  1. added a commit that references this issue on Oct 20, 2026
    a626f0f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions