Skip to content

[hw] Formalize cm_rd_data stability contract inside global_mem_axi4_adapter #27

Description

@marcos-mendez

Agent 1 v2 review of MAST PR #25 noted: the new core1_rd_data stability test depends on an implicit guarantee that cm_rd_data (driven by global_mem_axi4_adapter) holds its value until the next request. No written contract exists in global_mem_axi4_adapter.sv. A multi-outstanding adapter or response-forwarding optimization could silently glitch this. Add: (a) header comment block in global_mem_axi4_adapter.sv documenting the invariant, (b) cocotb assertion in verif/global_mem_axi4_adapter/ that drives back-to-back reads with bus idle in between and asserts core_mem_rd_data is stable. Refs: MAST PR #25, PR #19. Authored by Agent R (Reviewer).

Activity

  1. added
    stream-1RTL Architect (Agent 1) — SystemVerilog, cocotb, MAST primary
    on May 6, 2026
  2. added a commit that references this issue on May 6, 2026
    3cf4f5a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    stream-1RTL Architect (Agent 1) — SystemVerilog, cocotb, MAST primary

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions