fix(v2): resolve ERR-0025 Part B - SRAM read timing bug in weight/activation memory
Root-causes and fixes the real, disclosed defect left open at the end of the previous STEP20 commit: the board-level SPI host interface produced wrong compute results when jobs were dispatched with realistic (widely time-separated) pacing, even though job registration itself was already confirmed correct at the dependency_manager handshake. Root cause: nms_weight_packed.v and nms_activation_replicated.v both used a REGISTERED SRAM read (rd_data_reg <= mem[addr], one full clock of latency), but nms_memory_manager_stream_wide.v's own read-ahead pipeline (its `rd_pending` bit) is designed around a COMBINATIONAL read -- a request issued this cycle produces data already valid to capture the very next cycle. A busy, multi-tile job (e.g. the STEP19 D-Stress regression, 16 tiles/neuron) never exposes the mismatch, since its own weight/activation prefetch always runs far enough ahead that any given tile has been sitting stable in the SRAM for many cycles by the time it's actually consumed. An uncontested single-tile job has zero such margin: its one tile's read fires on the exact edge the data nominally becomes ready, landing squarely on the missing cycle and permanently latching stale/zero data. Fixed by making both SRAMs' reads combinational, with an explicit same-cycle fill/read address-match bypass for the one hazard a plain combinational read alone would still miss. No FSM, arbiter, or SDRAM controller logic was touched. Verified (Verilator, per this project's own standing DEC-0004 protocol): - tb_fpga_neural_v2_top_smoke.v: 11/11 PASS -- single job, back-to-back jobs, a realistic ~85us-gap job pair, and a parametric sweep of inter-job gaps (100ns/5000ns/50000ns). - STEP19 D-Stress N=2: 49788 cycles, 256/256 bit-exact -- identical cycle count to before this fix (zero regression). - STEP19 D-Stress N=4: 49771 cycles, 256/256 bit-exact -- identical cycle count to before this fix (zero regression). - tb_sdram_unified_backend.v (40/40) and tb_spi_host_bridge.v (18/18) reconfirmed unaffected. The physical SPI host interface is now verified correct end-to-end. Real synthesis/P&R of the board-level top (fpga_neural_v2_top.v) is the deliberate next step, not yet performed this round. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013xXuuRUWZScuo1DeYJxs3v
This commit is contained in:
@@ -22,10 +22,15 @@ masked.
|
||||
(39 signals) REALLY assigned from the official
|
||||
Lattice CSV and P&R-confirmed; host bus (110
|
||||
signals) deliberately unassigned (see below)
|
||||
[ ] clock defined -- oscillator-vs-PLL decision NOT made
|
||||
[ ] clock defined -- real EHXPLLL RTL now exists (STEP20,
|
||||
ecp5_pll_sys_clk.v, 16MHz->64MHz), NOT yet
|
||||
confirmed by synthesis/P&R of the board top
|
||||
[ ] power defined -- rail voltages known; regulators NOT selected
|
||||
[ ] FPGA configuration defined -- standard pins identified; flash NOT chosen
|
||||
[ ] host interface defined -- BLOCKER: 110-pin raw bus, no real protocol
|
||||
[x] host interface defined -- STEP20: real SPI protocol engine
|
||||
(spi_host_bridge.v), verified correct
|
||||
end-to-end (11/11, board-level smoke test),
|
||||
zero regression to the STEP19 baseline
|
||||
[x] schematic requirements complete -- SCHEMATIC_READINESS.md's own block diagram
|
||||
and interconnection list are complete
|
||||
[x] first-power-on test defined -- FIRST_POWER_ON.md's own 12-step procedure
|
||||
@@ -37,17 +42,20 @@ masked.
|
||||
real board-programmable artifact
|
||||
```
|
||||
|
||||
**7 of 14 items checked. HARDWARE READY = NO.**
|
||||
**8 of 14 items checked. HARDWARE READY = NO.**
|
||||
|
||||
**STEP20 update:** a real SPI host interface RTL now exists
|
||||
(`spi_host_bridge.v` + `fpga_neural_v2_top.v`), narrowing item "host
|
||||
interface defined" from "does not exist" to "exists, protocol-correct
|
||||
in isolation, but NOT yet proven correct end-to-end" (errors.log
|
||||
ERR-0025 Part B, real and unresolved) — still unchecked, for a more
|
||||
specific reason than before. The STEP19 core (raw `reg_*` interface)
|
||||
remains bit-exact verified and was reconfirmed fresh this session via
|
||||
Verilator after an unrelated Icarus Verilog v13.0 toolchain regression
|
||||
was found and ruled out (ERR-0024).
|
||||
**STEP20 update:** a real SPI host interface (`spi_host_bridge.v` +
|
||||
`fpga_neural_v2_top.v`) now exists AND is verified correct end-to-end
|
||||
(errors.log's "ERR-0025 Part B — RESOLUTION": a registered- vs
|
||||
combinational-read SRAM timing bug, found via the board-level smoke
|
||||
test, root-caused, fixed with zero regression to the STEP19 baseline)
|
||||
— "host interface defined" is now checked. A real EHXPLLL clock
|
||||
wrapper also now exists (`ecp5_pll_sys_clk.v`) but has not yet been
|
||||
through synthesis/P&R of the board-level top, so "clock defined"
|
||||
remains unchecked for that specific, narrower reason. The STEP19 core
|
||||
(raw `reg_*` interface) remains bit-exact verified and was reconfirmed
|
||||
fresh this session via Verilator after an unrelated Icarus Verilog
|
||||
v13.0 toolchain regression was found and ruled out (ERR-0024).
|
||||
|
||||
## Why each unchecked item is unchecked (no vague language)
|
||||
|
||||
@@ -56,10 +64,9 @@ was found and ruled out (ERR-0024).
|
||||
| N4 timing ≥80MHz | 8 real P&R seeds measured; only 1 (81.84MHz) clears 80MHz. This is a real MARGINAL result, not a PASS, per the governing spec's own explicit classification rule (some seeds pass, most do not). |
|
||||
| Constraints complete | `v2_unified.lpf` real and P&R-verified for 39/149 signals (clock frequency + clk/rst + the full 37-signal SDRAM bus, sourced from the real Lattice pinout CSV found at `~/Downloads/` during this step's own pre-commit review). The 110-signal host bus is deliberately left unassigned. |
|
||||
| Pinout complete | Signal inventory is complete (149, exactly matching real P&R); SDRAM+clk/rst (39 signals, 26%) are now really assigned and P&R-confirmed; the 110-signal host bus is unassigned, not because pin data is missing, but because that bus is not yet a real physical protocol (see below) — assigning it balls now would be premature. |
|
||||
| Clock defined | No PLL exists in the RTL (confirmed: 0/4 EHXPLLL in every synthesis run); the board's real oscillator frequency (16MHz per prior project memory) does not match the RTL's own 80MHz requirement, and neither "new oscillator" nor "add a PLL" has been decided. |
|
||||
| Clock defined | A real EHXPLLL wrapper now exists (`ecp5_pll_sys_clk.v`, STEP20, real Project Trellis `ecppll`-generated parameters, 16MHz->64MHz) and is instantiated in the board-level top, but has NOT yet been confirmed by synthesis/P&R of that top — deliberately deferred until ERR-0025 Part B was resolved (decisions.log DEC-0037). |
|
||||
| Power defined | Rail VOLTAGES are known from real datasheets; regulator SELECTION, CURRENT budget, and decoupling are not — no real power-estimation tool was run, and the previously-referenced board power-tree design is not accessible this session to confirm as a concrete plan. |
|
||||
| FPGA configuration defined | Standard ECP5 config pins (TDI/TDO/TCK/TMS/PROGRAMN/INITN/DONE/CCLK) are correctly identified as existing and standard, but no configuration-flash part number or SPI-vs-JTAG-only bring-up approach has been chosen for V2 specifically. |
|
||||
| Host interface defined | The RTL's own "host" ports are a 110-pin raw parallel test-harness bus (`reg_valid`/`reg_node_id`/etc.), not a real board protocol. No serializing bridge RTL exists. This is the single largest real gap between "simulated/synthesized" and "physically buildable." |
|
||||
| Bitstream reproducible | Every P&R run this project has performed used free (unconstrained) I/O placement — a real, valid way to prove the design FITS the package, but not a way to produce a bitstream a real board's own fixed wiring could actually use. |
|
||||
|
||||
## What this means, precisely
|
||||
|
||||
Reference in New Issue
Block a user