Skip to content

[EPIC] v002 correctness, bring-up, and hardware closure tracking #43

Description

@hkimw

Goal

Track all v002 correctness, bring-up, verification, software, and hardware-closure issues in one parent issue.

Scope

This parent issue groups the full v002 bring-up plan:

  • P0: spec, preprocess, GEMM/GEMV correctness, and minimal NPU_top integration
  • P1: dispatcher, STAT, result writeback, GEMV/CVO verification, and synthesis baseline
  • P2: software pipeline, golden model, memory, scheduler, implementation, docs, and admin tasks

Management Policy

  • Sub-issues represent actual implementation or verification tasks.
  • Dependencies should be used only for real blocked-by relationships.
  • Development branches should be created only when work starts.
  • Large model artifacts, safetensors, generated blobs, and restricted files must not be committed.

Expected Completion

This EPIC is complete when:

  • All P0 blockers are resolved.
  • M01 bring-up issues pass simulation or have documented blockers.
  • M02 software/model/hardware closure issues have either working outputs or clear follow-up reports.
  • README/docs reflect the final v002 architecture and artifact policy.

Today's progress - 2026-05-07

Evidence note: at update time, gh pr view #80-#98 reports these PRs as OPEN, so they are tracked here as session PRs queued for maintainer review/landing rather than merged into the base branch.

Open gating items:

  • Clarify the KVFPGA environment before claiming hardware reproducibility.
  • Run the Vivado bitstream flow and attach/report concrete outputs.
  • Resolve PR docs(spec): resolve v002 quantization, K-drain, and DSP baseline #80 CONFIRM checklist: 6 items remain before it can be treated as accepted evidence.
  • Work through the user-tracked 65-PR review/merge queue; current repo check showed 20 open PRs at update time, and this EPIC remains open until review evidence is landed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:adminExternal application, license, access, funding, or artifact policy.area:specArchitecture, ISA, scale policy, or data format.priority:P1Next milestone blockerstatus:in-progressActively being workedtype:docsDocumentation-only change

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions