Files
FPGA-Neural/hardware/v2/logs/simulation.log
T
micheleandClaude Sonnet 5 3cdaeaee35 test(v2): final benchmark campaign - real end-to-end characterization (EXP-0014)
Post-M10, user-requested final benchmark campaign: 6 realistic
workloads (16-256 independent neurons in a shared-input dense-layer
shape, a random-seeded 2-layer network with real cross-node PSRAM
forwarding, and a 6-node 2-hop dependency diamond) x 4 concurrency
levels (N_SLOTS=1/2/4/8) through the real, full neural_multiprocessor
system (real V1 PSRAM chain, real slot_mem_arbiter). 24/24 runs PASS
bit-exact against a software golden model (11,520 individual neuron/
node checks, zero mismatches).

Three real bugs found and fixed during the campaign itself (ERR-0009):
1. neural_director.v (M5) had a real RTL bug at N_SLOTS=1
   ($clog2(1)=0 makes a replication expression illegal) - never
   caught because M5-M10 only ever tested N_SLOTS=2/4/8. Fixed with
   a width-agnostic '0 literal; M5's own testbench re-verified
   unaffected.
2/3. Two testbench sizing bugs in tb_benchmark_suite.v itself
   (psram_model DEPTH too small for the Large workload's address
   range; N_NODES too small for the Stress workload's node-id range,
   causing a real deadlock via node-id wraparound colliding with an
   already-DISPATCHED node - a real, honest consequence of DEC-0008's
   own "no node-slot reclamation" design choice).

Headline finding: real parallel scaling is essentially flat beyond
N_SLOTS=2 - the single shared PSRAM port saturates at ~91%
utilization regardless of slot count, so memory-bound workloads gain
only 1.05-1.06x real speedup from N=1 to N=8. Once real POST-P&R Fmax
degradation is also factored in, N_SLOTS=4 is measurably 21% SLOWER
in real wall-clock time than N_SLOTS=1 for the largest workload
tested. N_SLOTS=2 is recommended as the default (DEC-0014,
superseding DEC-0012's resource-only "N_SLOTS=8 ceiling" framing for
general use).

Full 21-section report (every number classified THEORETICAL/
SIMULATED/POST-P&R MEASURED/DERIVED, per the user's own
methodology requirements): hardware/v2/docs/benchmarks/
final-benchmark.md

Logged: simulation/synthesis/timing/benchmark/decisions (DEC-0014)/
experiments (EXP-0014)/errors (ERR-0009)/development.log,
ROADMAP.md updated.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xXuuRUWZScuo1DeYJxs3v
2026-09-05 19:58:30 +02:00

137 lines
7.3 KiB
Plaintext

# V2 simulation log -- solo append, mai troncato/sovrascritto (vedi README.md)
# Nessuna entry ancora -- popolato incrementalmente man mano che avanza lo sviluppo V2.
[2026-09-05] EXP-0001/EXP-0002 -- hardware/v2/sim/tb_neural_processor.v
test: 7 cases (16/32/8/8/8/8/64-input jobs; ACT_NONE + ACT_RELU;
extreme INT8 saturation; back-to-back zero-idle-gap tiles)
vectors: regular positive, mixed-sign cancellation, extreme INT8
(-128,-127,-1,0,1,126,127,127 in one 8-lane tile), back-to-back
jobs, 8-tile (64-input) job
simulator: Verilator 5.050 (--binary --timing) -- see decisions.log
DEC-0004 for why Icarus v13.0 is not trusted for this testbench
cycles: not separately profiled at this milestone (throughput/stall
cycle counting deferred to M9 per §22)
PASS/FAIL: 7/7 PASS (ACC_WIDTH=32); 7/7 PASS (ACC_WIDTH=24, EXP-0002)
bit-exact result: V1.y === V2.result_data for every case, both widths
stall cycles / memory wait / utilization: N/A (no Memory Manager yet,
M1 operands fed directly by testbench per the roadmap)
[2026-09-05] EXP-0003 -- hardware/v2/sim/tb_neural_processor_array.v
(N_PROCESSORS=4)
test: 7 cases (single-processor sanity; 4-way same-cycle concurrent
launch with different tile counts; staggered-start 2-processor test)
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 7/7 PASS
bit-exact result: N/A at this milestone (hand-computed expected
values, arithmetic itself already bit-exact-certified vs V1 at M1)
concurrency: confirmed genuine -- in the staggered test, the
later-launched, shorter job (processor 1) completes BEFORE the
earlier-launched, longer job (processor 0), proving independent
progress rather than serialization.
[2026-09-05] EXP-0004 -- hardware/v2/sim/tb_buffers.v
test: 10 cases across activation_buffer/weight_buffer/result_buffer
vectors: extreme INT8 (-128, 127, -100, 100), regular values, full
64-bit tile round-trip (weight_buffer), re-reads confirming earlier
writes undisturbed
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 10/10 PASS
[2026-09-05] EXP-0005 -- hardware/v2/sim/tb_memory_manager.v
test: 3 end-to-end jobs (3-tile/saturating, 1-tile/non-saturating,
5-tile/steady-state-swap), real V1 PSRAM backend chain (unmodified),
real M1 neural_processor
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 3/3 PASS
bit-exact result: PSRAM-read-back result byte matches hand-computed
expectation in every case (independent oracle, not derived from the
RTL under test)
cycles: 446 (3 tiles), 166 (1 tile), 728 (5 tiles) -- real PSRAM
latency dominates, not memory_manager's own control overhead
[2026-09-05] EXP-0006 -- hardware/v2/sim/tb_neural_director.v
test: 4 cases (3-jobs-2-slots first-free dispatch + queueing,
backpressure fill/recover)
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 4/4 PASS
[2026-09-05] EXP-0007 -- hardware/v2/sim/tb_dependency_manager.v
test: 4 cases on a 4-node DAG (2 independent + 1 dual-dependency +
1 single-dependency-shared-producer)
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 4/4 PASS
[2026-09-05] EXP-0008 -- hardware/v2/sim/tb_dataflow_core.v
test: full end-to-end M1-M6 integration through dataflow_core.v (M7),
a 3-node DAG (node0/node1 independent, node2 depends on BOTH) run
through the REAL dependency_manager -> neural_director -> N_SLOTS x
(memory_manager + neural_processor) chain for the first time, each
slot backed by its own independent behavioral byte memory
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 4/4 PASS -- node0=48, node1=8 (both real neural_processor
computations via the full stack), node2=40 dispatched only after
BOTH node0 and node1 genuinely completed (continuously polled every
cycle up to completion, not just checked at the end) -- the
dependency-manager-to-director wake-up loop closes correctly
end-to-end with real hardware in between, not just in isolation
(M6's own testbench already proved the wake-up logic alone)
[2026-09-05] EXP-0009 -- hardware/v2/sim/tb_neural_multiprocessor.v
test: same 3-node DAG as EXP-0008 (node0/node1 independent, node2
depends on both), routed through neural_multiprocessor.v (M8): the
REAL, UNMODIFIED V1 PSRAM backend chain (int8_memory_access ->
memory_interface -> psram_controller -> psram_model) shared across
N_SLOTS=2 genuinely concurrent memory_manager instances via the new
slot_mem_arbiter.v -- node0 and node1 are registered back-to-back
with no dependencies, so both dispatch to their slots essentially
simultaneously and genuinely contend for the one real PSRAM port.
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 4/4 PASS after fixing a real dropped-request bug in the
first arbiter draft (errors.log ERR-0008) -- node0=48, node1=8
(concurrent, real PSRAM, real arbitration), node2=40 dispatched only
after both genuinely completed. 444 cycles end-to-end (vs 20000-cycle
watchdog timeout with the buggy first draft, where node1's request
was silently dropped and its slot hung forever).
regression: hardware/v2/sim/tb_memory_manager.v (M4) re-run unchanged
(no M4 file touched) -- still 3/3 PASS, identical cycle counts
(446/166/728), confirming slot_mem_arbiter.v is purely additive.
[2026-09-05] EXP-0013 -- hardware/v2/sim/tb_neural_multiprocessor.v,
M10 cycle-accounting instrumentation (closes decisions.log DEC-0011's
deferred stall %/utilization gap with real data, testbench-only
addition, no RTL touched)
test: same EXP-0009 scenario (3-node DAG, N_SLOTS=2, real V1 PSRAM
chain, real slot_mem_arbiter contention), instrumented with cycle
counters (shared PSRAM port busy cycles via
u_nmp.u_arbiter.owner!=0, each slot's memory_manager busy cycles via
its own state!=MM_IDLE), measured from the first node registration
to test completion.
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 4/4 PASS (unchanged from EXP-0009), plus real measured
data: 684 total cycles measured; shared PSRAM port busy 559/684
(81.7% utilization, 18.3% idle); slot 0 (memory_manager) busy
651/684 (95.2%); slot 1 (memory_manager) busy 446/684 (65.2%).
note: slot 0's higher utilization is at least partly explained by it
serving TWO sequential jobs in this run (node0, then whichever slot
frees first serves node2 -- likely slot 0, first-free/lowest-index)
while slot 1 only ever serves node1 -- NOT conclusive evidence of
harmful priority starvation on its own; see decisions.log DEC-0010's
original fairness deferral, now informed by this real (if small)
data point.
[2026-09-05] EXP-0014 -- hardware/v2/sim/tb_benchmark_suite.v (final
benchmark campaign, post-M10)
test: 6 workloads (16/64/128/256 independent neurons + 10-node
multilayer with random data + 6-node 2-hop DAG), each bit-exact
verified against a software golden model, at N_SLOTS=1/2/4/8 (24
total runs) through the real full neural_multiprocessor.v (real V1
PSRAM chain, real slot_mem_arbiter)
simulator: Verilator 5.050 (--binary --timing)
PASS/FAIL: 24/24 PASS bit-exact (11,520 individual neuron/node
comparisons, zero mismatches) after fixing 3 real issues found
during this campaign (errors.log ERR-0009: 1 real RTL bug in
neural_director.v at N_SLOTS=1, never exercised before; 2 testbench
sizing bugs -- psram_model DEPTH too small, N_NODES too small
causing a real node-id wraparound deadlock)
full data/analysis: hardware/v2/docs/benchmarks/final-benchmark.md