Memory learning path
Concept sequence and review gate.
Open route ->DOMAIN LANE / MEMORY
How does memory preserve, sense, move, disturb, retain, protect, and place data across SRAM, DRAM, HBM, NAND, MRAM, FeFET, SCM, CIM, and hybrid memory systems?
ROUTE STACK
This lane collects the learning packets, replay labs, simulation objects, and evidence routes that belong together. It is a filter, not a new workflow engine.
Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->SIMULATION FILTER
Paper-writing users can enter from this page and open the relevant run cards, exports, methods, limits, and evidence without first watching a lecture.
Replay SKY130 6T read cases across bitline load, 100 mV sense delay, and internal-node disturb.
Compare hold and read butterfly curves, maximum-square SNM, and read-access margin loss.
Replay the 24-case SKY130 shmoo that maps dynamic write success versus wordline level and write-VDD assist.
Replay a lumped-bitline model that connects cell current, bitline capacitance, and sense-enable timing.
Replay bitline differential, offset sigma, attenuation loss, positive margin, and decision-time interpretation before claiming a sense amplifier can resolve.
Replay how normalized cell ratio and wordline pulse width change read-disturb peak, read-SNM proxy, and a retained/not-retained budget.
Classify baseline write, cell-VDD collapse, wordline boost, negative bitline, and read wordline-underdrive as tradeoff cards instead of recipe settings.
Replay blocked, sequential, strided, random, and conflict-thrashing access patterns with AMAT so SRAM timing stays connected to system-visible latency.
Replay the verified transaction trace that turns read/write requests into one-cycle checked responses.
Replay 80-access March C- traces for no-fault, stuck-at-0, and stuck-at-1 SRAM scenarios.
Replay exhaustive one- and two-bit codeword fault injection for an 8-bit SECDED memory word.
Replay row-hit rate and bank count to see why locality and bank-level parallelism shape DRAM/HBM latency and throughput before raw bandwidth matters.
Replay STT/SOT-style write probability, pulse width, retention barrier, and write energy as a compact MRAM tradeoff card.
Replay endurance, temperature, variability, and normalized read margin across RRAM, PCM, and FeFET style memory labels.
Replay array size, ADC bits, conductance variation, accuracy proxy, and energy index for compute-in-memory crossbar intuition.
Replay cell capacitance, bitline capacitance, and stored voltage to see the small differential a DRAM sense amplifier must resolve.
Replay leakage class, temperature, and refresh interval to see why weak-cell tails drive refresh policy.
Replay activation count, victim distance, and temperature to frame RowHammer as a pattern, margin, mitigation, and ECC-evidence problem.
Replay SLC/MLC/TLC/QLC threshold crowding, P/E cycles, retention time, and ECC margin proxy.
Replay cycle count, temperature, and program pulse to see how ferroelectric memory window can wake up, fatigue, and shift.
Replay stack height, target bandwidth, and cooling class to see usable bandwidth, energy per bit, and throttle risk together.
Replay SRAM, DRAM, HBM, SCM, NAND, and MRAM across workload weights to choose the right evidence question.
Replay STT/SOT labels, thermal barrier, and pulse width to compare write energy, switch probability, read margin, retention, and disturb risk.
Replay SET/RESET pulse proxies, retention time, drift coefficient, and read margin so PCM is taught as a window-and-drift problem, not one ideal resistance ratio.
Replay compliance, cycling, temperature, selector on/off ratio, and LRS/HRS spread to see why ReRAM is a variability and array-read problem.
Replay layer group, program/erase cycles, retention time, and read-retry steps to connect 3D NAND stack variation with threshold overlap and ECC margin.
A browser CSV replay of 864 verified PDK-free ngspice cases connecting mux ratio, pass-device scale, shared sense/I/O load, write-path off-state, transfer efficiency, and output latency.
A browser CSV lab for memory-system partitioning: compare workload traffic, HBM stack class, base-die controller/PHY/RAS placement, interposer budget, thermal class, capacity, bandwidth, energy, and yield risk before calling an HBM plan feasible.
A browser CSV replay that keeps temperature, retention-tail cells, refresh policy, activation pressure, RowHammer disturbance risk, ECC coverage, thermal stress, and next evidence check in one table.
A browser CSV replay that compares SRAM, DRAM, HBM, NAND, MRAM, FeFET, ReRAM, PCM, SCM, embedded NVM, and CIM-style memory across placement, reliability, integration, and evidence maturity.
Trace declared device tiers and oxide-semiconductor access transport through contacts, inter-tier connectivity, WL/BL loading, thermal budget, extraction maturity, cell/subarray sensitivities, contradictions, and owned replacement evidence without copying a topology or issuing a node, architecture, or signoff claim.
Follow bounded process variation families through device characterization, circuit margin, reliability and yield observations, three exact ledgers, four accountable role views, upstream packet postures, and a human-reviewed public-atlas gate without claiming physical causality, signoff, qualification, or production fitness.
DEEPENING PLAN
Memory depth now spans SRAM cell/peripheral/I/O, DRAM/HBM locality, HBM/base-die partitioning, DRAM 1T1C sensing, retention, refresh, RowHammer, ECC/scrub guardbands, NAND threshold margin, MRAM switching/read/retention, FeFET/FeRAM, PCM, ReRAM, CIM, SCM, eDRAM/MIMCAP, 3D memory, and hierarchy placement while keeping device, cell, peripheral, controller, package, system, reliability, and evidence layers separate.
A memory evidence packet now travels from SRAM cell/peripheral/I/O evidence into DRAM/HBM locality, MRAM switching, RRAM/PCM/FeFET margin, CIM crossbar tradeoffs, controller traces, BIST, and ECC without blurring abstraction layers.
Open all-domain roadmap ->EVIDENCE BACKLOG
The backlog keeps future additions useful rather than noisy. New pages should enter through a domain tag, public source anchor, model boundary, and precomputed evidence package.
BOUNDARIES
Every domain can grow as education, simulation replay, and evidence planning. The page must not become a job board, tool controller, recipe workflow, upload service, or signoff surface.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
SOURCE SPINE
These source links help name the domain. They do not convert teaching replays into certified measurements, process recipes, facility procedures, or product signoff results.
Public thesis used for offset, attenuation, control-timing, and sense-amplifier vocabulary.
Open source ->Public paper used for read-stability, write-ability, SNM, and N-curve vocabulary.
Open source ->Public paper used to anchor assist, reverse assist, VMIN, guardband, and canary vocabulary.
Open source ->Public course note used for hit time, miss rate, miss penalty, and AMAT vocabulary.
Open source ->External MIT-licensed DRAM/HBM memory-system simulator reference; SemiAgora page uses original precomputed teaching data.
Open source ->External MIT-licensed DRAM timing and thermal-capable simulator reference.
Open source ->External compute-in-memory accelerator reference; link-only until license and model boundaries are reviewed.
Open source ->External memristor PIM behavior-level simulator reference; link-only until manual rights review.
Open source ->NEIGHBOR DOMAINS
Semiconductor work is coupled. These links keep the site navigable when one claim crosses process, device, circuit, memory, equipment, metrology, or reliability boundaries.
What changed on the wafer, and what evidence proves it?
Open domain ->How do charge, potential, materials, thermal path, and carriers become I-V, C-V, RF, or power-device evidence?
Open domain ->How does a device-level curve become gain, delay, and oscillation?
Open domain ->What cycle-level contract was actually checked?
Open domain ->How do layout markers, connectivity reports, parasitics, and timing evidence become a public-safe verification claim?
Open domain ->What tool or facility condition supports the process, and what is still not an operating instruction?
Open domain ->Is the measurement fit for the claim?
Open domain ->What evidence remains after the die is fabricated, bonded, packaged, screened, and stressed?
Open domain ->