Skip to content
SASemiAgoraSemiconductor knowledgeResearch services
Menu
Research services한국어 안내LearnTraceCompareReproducePlanSearch
ExploreKnowledge AtlasDetailed mapSimulationsDomain mapGuided journeysLabs
WorkspacesScenario ComparisonReproducibility RegistryExperiment PlannerResearch Project BuilderClaim-Evidence WorkbenchData Contract
TrustEvidence Knowledge GraphMetric OntologyCitation ProvenanceSource WorkspaceEvidence BrowserPublic Release LedgerSource PolicyCorrections
MoreSearchPracticeCalculatorsResourcesResearch atlasRelease provenanceReading RoomResearch servicesAbout SemiAgora
SASemiAgoraSemiconductor knowledge & engineeringOpen run card

LESSON PACKET / SA-MEM-DRAM-RELIABILITY-003

DRAM reliability is a guardband stack.
Memory / DRAM Reliability

A DRAM reliability note should not split retention, refresh, RowHammer, ECC, scrub, and thermal pressure into isolated slogans. This packet keeps temperature, weak-tail cells, activation pressure, protection policy, residual risk, and next evidence check in one bounded browser replay.

Open simulationOpen replay lab ->
packetSA-MEM-DRAM-RELIABILITY-003runSimulation ObjectlearnEvidence SequencemethodMethodslimitsBoundaries

EVIDENCE SEQUENCE

What the learner should inspect first.

This surface connects the daily-scan source signal to an original SemiAgora simulation object without copying source text, code, figures, PDK files, or process recipes.

01

Start with memory context, retention-tail class, temperature, access pattern, refresh policy, and protection policy before reading a risk number.

Open the run card to inspect the saved rows, methods, limits, and export files behind this step.

Inspect run card ->
02

Compare retention stress, refresh overhead, activation pressure, hammer-risk proxy, ECC coverage, residual uncorrectable-risk proxy, thermal stress, and data-integrity guardband together.

Open the run card to inspect the saved rows, methods, limits, and export files behind this step.

Inspect run card ->
03

Use the decision gate to route the next check to retention-tail, refresh-tax, RowHammer mitigation, ECC/scrub, thermal-system, or bounded-lesson evidence.

Open the run card to inspect the saved rows, methods, limits, and export files behind this step.

Inspect run card ->

METHODS

Precomputed model contract.

The goal is useful study scaffolding and paper-planning discipline, not calibrated production evidence.

method

Original synthetic DRAM reliability table based on public DRAM refresh, RAS, RowHammer, simulator, and ECC vocabulary.

The simulation object keeps the same statement beside downloadable JSON and CSV evidence.

method

No RowHammer exploit, test recipe, memory-controller workflow, standards table, simulator code, vendor row, or product data is copied.

The simulation object keeps the same statement beside downloadable JSON and CSV evidence.

method

The browser filters saved CSV rows and exposes the model card with no-live-simulator and no-qualification boundaries.

The simulation object keeps the same statement beside downloadable JSON and CSV evidence.

LIMITS

Useful, but deliberately bounded.

No account, upload, payment, comment, newsletter, live solver, facility workflow, or product-release surface is enabled.

non-claim

No live DRAMsim3, Ramulator2, RowHammer tester, memory-controller firmware, BIOS setting, DIMM qualification, standards claim, or product recommendation.

Keep this boundary attached when reusing the card for lesson writing, figure planning, or research notes.

non-claim

No exploit workflow, reverse-engineering procedure, proprietary RAS mechanism, internal TRR behavior, ECC implementation, security guarantee, or reliability signoff.

Keep this boundary attached when reusing the card for lesson writing, figure planning, or research notes.

non-claim

Real work needs owned retention distributions, temperature profiles, activation logs, syndrome/scrub evidence, workload traces, thermal maps, and product-owner review.

Keep this boundary attached when reusing the card for lesson writing, figure planning, or research notes.

SOURCE ANCHOR

Link-only public source spine.

SemiAgora uses the source as a signal and citation anchor, then writes original summaries and original toy data with explicit limitations.

Google Security Rowhammer research support

https://blog.google/security/supporting-rowhammer-research-to/

Open source ->