thejayman77 547811e89b Z-req FIFO REQ_DEPTH 8192->1024: kill zc_emit EMIF setup path, free 32 M20Ks
The 8K request FIFO was 8x oversized (measured peak ~478; Codex's TB uses 1024).
Its read address routed to 8 spread M20K blocks -> 310MHz EMIF setup miss (-0.103,
MAX_FANOUT can't help: Quartus refuses to duplicate RAM-address regs, Warning 22471).
Shrinking to 1024 (2 blocks): 26.1 fit shows that path GONE, design clk +0.631->+5.693,
RAM 309/358 (86%) -> 277/358 (77%). New worst is a DIFFERENT, skew-dominated EMIF->
texcache-FSM path at -0.074 (TNS -2.032 -> -0.164).

SAFETY GATE before board load: confirm the full zsrt139f52 scene never bursts >1024
Z-requests in flight (peak I have is 478 from a smaller scene). Bump to 2048 if unsure.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 05:43:25 -04:00

retroDE_ps2 Planning Docs

This directory is the working design scaffold for the PS2 core.

Purpose:

  • define the intended repository shape before RTL lands,
  • define subsystem boundaries before implementation choices harden,
  • document what each block owns, what crosses the boundary, and how we will validate it.

Recommended reading order:

  1. repo_layout.md
  2. phase0_checklist.md
  3. contracts/README.md
  4. stub_module_plan.md
  5. wave2_dma_gif_plan.md
  6. wave25_memory_backed_dma_plan.md
  7. wave26_multi_beat_dma_plan.md

Relationship to references/:

  • references/ is the research library.
  • docs/ is the project-definition layer.

Rule of thumb:

  • If a file explains PS2 hardware as it exists, it belongs under references/.
  • If a file explains how retroDE_ps2 intends to model, partition, or validate that hardware, it belongs under docs/.
S
Description
No description provided
Readme 8.2 MiB
Languages
SystemVerilog 75.5%
Verilog 15.4%
Tcl 4.7%
HTML 1.1%
Python 1%
Other 2.3%