Files

T

micheleandClaude Sonnet 5 8890b0abc2 fix: ERR-0026 SDRAM tMRD datasheet-unit mismatch at 64MHz

Real Alliance Memory AS4C4M16SA-6TIN datasheet (Rev 5.0, Table 17)
specifies tMRD as a fixed 2-tCK cycle count, not an ns value.
sdram_controller.v modeled it via ns_to_cycles(12), which rounded to
2 cycles by coincidence at every previously-tested frequency
(100/133/166MHz) but rounds to only 1 cycle at the real 64MHz board
target -- an under-provisioned one-time init sequence. Fixed by
hardcoding T_MRD=2, matching how CAS_LATENCY is already modeled.

Verified zero regression: full 9-config legacy sweep + a new
dedicated 64MHz config (461/461 PASS each), N=2/N=4 D-Stress
(identical cycle counts), board-level smoke test (11/11 PASS).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xXuuRUWZScuo1DeYJxs3v

2026-09-06 18:27:36 +02:00

architecture.log

V2.0.0 hardware freeze - single SDRAM

2026-09-06 13:39:55 +02:00

benchmark.log

perf(v2): shared activation cache - further 1.66-2.00x real speedup (DEC-0016)

2026-09-05 20:59:14 +02:00

decisions.log

fix: ERR-0026 SDRAM tMRD datasheet-unit mismatch at 64MHz

2026-09-06 18:27:36 +02:00

development.log

V2.0.0 hardware freeze - single SDRAM

2026-09-06 13:39:55 +02:00

errors.log

fix: ERR-0026 SDRAM tMRD datasheet-unit mismatch at 64MHz

2026-09-06 18:27:36 +02:00

experiments.log

V2.0.0 hardware freeze - single SDRAM

2026-09-06 13:39:55 +02:00

README.md

feat(v2): scaffold hardware/v1 frozen baseline + M1 Neural Processor

2026-09-05 14:06:53 +02:00

simulation.log

perf(v2): shared activation cache - further 1.66-2.00x real speedup (DEC-0016)

2026-09-05 20:59:14 +02:00

synthesis.log

perf(v2): shared activation cache - further 1.66-2.00x real speedup (DEC-0016)

2026-09-05 20:59:14 +02:00

timing.log

perf(v2): shared activation cache - further 1.66-2.00x real speedup (DEC-0016)

2026-09-05 20:59:14 +02:00

README.md

Formato dei log V2

Regola non negoziabile (docs/v2-description.md §25-29): ogni attività significativa (modifica, simulazione, sintesi, benchmark, decisione, errore) deve essere registrata. Nessun log viene mai sovrascritto o troncato — solo append. Nessun ID esperimento (EXP-XXXX) o decisione (DEC-XXXX) viene mai riutilizzato, anche se il risultato è un FAIL.

File

development.log — log principale di sviluppo, un'entry per ogni sessione di lavoro/milestone (creazione file, refactor, avanzamento roadmap).
architecture.log — decisioni e note di architettura a grana fine (non scelte finali — quelle vanno in decisions.log — ma esplorazioni, alternative considerate, vincoli scoperti).
simulation.log — ogni run di simulazione (Icarus/Verilator): test, vettori, cicli, PASS/FAIL, confronto bit-exact con V1, stall/memory-wait.
synthesis.log — ogni run Yosys: LUT/FF/DSP/BRAM, warning, problemi CHECK.
timing.log — ogni run nextpnr-ecp5: Fmax, percorso critico, WNS/TNS se disponibili. Fmax "ufficiale" di una configurazione = solo da qui, mai da simulazione o stima.
benchmark.log — tabelle di confronto per configurazione (Fmax, MAC/cycle, cycles/neuron, utilization, ecc.), sempre con etichetta THEORETICAL/SIMULATED/SYNTHESIZED/POST-P&R.
decisions.log — decisioni architetturali importanti, formato DEC-XXXX (vedi docs/v2-description.md §27).
experiments.log — registro principale, un EXP-XXXX per ogni esperimento end-to-end (config → sim/synth/timing → risultato), rimanda a reports/experiments/EXP-XXXX/.
errors.log — errori/bug/regressioni incontrati durante lo sviluppo V2 stesso (non i bug V1, già chiusi in hardware/v1/docs/validation/bugs.md).

Campi minimi per entry (§26)

timestamp, experiment_id (se applicabile), git_commit, session/agent,
module, configuration, action, reason, command, result, errors, decision,
next_action

Per synthesis/timing aggiungere: LUT, FF, DSP, BRAM, Fmax, critical path, WNS/TNS. Per simulazione: test, vectors, cycles, PASS/FAIL, bit-exact result, stall cycles, memory wait, utilization.