Smart Lock EEPROM Memory
A smart lock forgets everything the moment the batteries die — unless the credential, configuration, and audit data live in a non-volatile memory chip that survives power loss. That memory is most often an EEPROM (Electrically Erasable Programmable Read-Only Memory), sometimes a companion flash page inside the lock controller, and the buyer-side discipline is to ask which one it is, what it stores, and how the supplier proves it. For every model in the catalogue, the per-model memory spec (chip family / storage envelope in users, cards, fingerprints, PINs, audit events / write-cycle envelope / data-retention posture) is a "check the model’s published specification" cell the buyer signs, not a brochure sentence the salesperson repeats. This article reads EEPROM literacy the way the engineering tearoff at smart lock materials buyer guide reads housing-material literacy: vocabulary first, then per-environment row of type-built the supplier fills in.
EEPROM literacy is one of the seven engineering sub-systems the buyer verifies before signing the procurement order; the data-retention sibling at smart lock data retention reads the same sub-system through the time lens (how long the bits survive without power), and the engineering tearoff at smart lock engineering procurement checklist is where the memory row drops in as a new EC-row. The whole memory discipline stands or falls on one habit: every per-SKU figure routes to the dated product page, and the only sanctionable anchor is the SLK-9936S "audit/event records up to 1,000" line, scoped strictly to that SKU.
What EEPROM actually is — and what it is not
EEPROM is a non-volatile memory technology that can be erased and rewritten one byte (or one small page) at a time, electrically, without removing the chip from the circuit board. On a smart lock, EEPROM is typically the place where the lock stores the things the lock must remember even when the batteries are dead: the master credential, the list of enrolled users, the list of issued cards, the list of enrolled fingerprints, the list of PINs, the configuration string (auto-lock delay, backlight behaviour, alarm thresholds, language, time zone), and the rolling audit log. Without EEPROM — or some equivalent non-volatile store — a smart lock becomes a blank-slate device the moment the batteries go flat.
EEPROM is not the only non-volatile memory option a smart lock might use. Three alternatives appear in the wider industry:
- Flash memory — cheaper per byte, faster in bulk, but typically written in larger blocks (4 KB to 64 KB or more). Flash is common in connected locks that store larger credential databases and software-update history.
- Battery-backed SRAM — fast, byte-addressable, but requires a coin-cell or supercapacitor to retain data through battery swaps; if the backup fails, the data is lost.
- One-Time Programmable (OTP) memory — can be written once, never erased; used for permanent identifiers (factory serial, default keys) rather than user-editable data.
The buyer's question is not "does it use EEPROM" — the buyer's question is "which memory family, what capacity in what unit (bytes / cards / users / events / fingerprints / PINs), and what is the supplier's evidence." The answer varies by SKU and lives on the dated product page; it is never ported across SKUs.
What EEPROM stores on a smart lock — the six storage buckets
Across the 79-model catalogue, EEPROM (or its functional equivalent — flash page / battery-backed SRAM / OTP for permanent IDs) carries six storage buckets. Per-bucket capacity is a per-model figure; the bucket itself is universal.
| Storage bucket | Typical contents | KEEP / EDIT | LOS example |
|---|---|---|---|
| Master credential | Default manager PIN / default manager card / engineering key | Write-once at factory, read-many after | Many keys overwrite risk |
| Enrolled credentials | User list (PINs / cards / fingerprints / app-bound IDs) | Frequent rewrite during onboarding, occasional rewrite after | Service-life cycle envelope |
| Configuration | Auto-lock delay / backlight / alarm threshold / language / time zone | Folded at commissioning, rewritten on reconfiguration | Re-write cycle during commissioning |
| Time / clock state | Real-time clock (RTC) values, daylight-savings markers | RTC writes each minute / each hour | Drift after long power loss |
| Audit / event log | Open events, fail events, low-battery events, tamper events, admin events | Append-only | Roll-over or wrap behavior |
| Factory identifiers | Serial number, MAC, model string, hardware revision | Write-once at factory | One-time programmable |
The single PDP-cited anchor in this article is the SLK-9936S line "audit/event records up to 1,000" — a figure that places the SLK-9936S audit bucket at the 1,000-event order of magnitude for the hotel-class reader. That figure is scoped strictly to the SLK-9936S SKU and is never ported to siblings SLK-9936G, SLK-9905A, SLK-9951TH, SLK-9962S, SLK-G200, SLK-8831, SLK-1104-class, SLK-3108, cylindrical Tuya, 3D-face, B09, cabinet 6-model, outdoor D11-D12-D15-ODS-DQ, stainless-keypad 019-022-309, RFTC-RF card-and-code 118-760, face 9L5-R-Q7-Future 1, 516 cat-eye, Q7 intercom, 4G, grip-to-open. Every other per-model audit capacity, every user count, every card count, every fingerprint count, every PIN count routes to "check the model’s published specification."
The four memory families and where they sit on a smart lock
The catalog-wide vocabulary for memory on a smart lock resolves to four families. The buyer's job is to read the supplier's named document and identify which family (or which combination) the SKU uses; the answer is never assumed from the catalogue category.
| Memory family | Where it sits | Strength the buyer cares about | Watch-out the buyer cares about |
|---|---|---|---|
| EEPROM (standalone or controller-integrated) | Inside the lock controller or as a separate serial chip on the PCB | Byte-level rewrite, no battery backup needed, decades of retention claim on datasheet | Page-write time, write-cycle ceiling per page, brown-out during write |
| Flash (NOR or NAND) | Inside the lock controller or as a separate chip on the PCB | Bulk-rewrite, larger capacity, cheaper per byte | Block-erase granularity (cannot rewrite one byte), wear-distribution discipline |
| Battery-backed SRAM | Inside the controller with coin-cell or supercapacitor | Fast, byte-addressable, low write latency | Backup-battery age, coin-cell replacement schedule, backup-fail behavior |
| OTP / fuse memory | Factory-programmed identifiers (serial, MAC, model) | Cannot be silently rewritten, permanent record | One-time write means no field service for re-identification |
EEPROM is the most common family on the credential-bearing SKUs because credentials are written and re-written one user at a time; flash dominates the firmware-update path and the larger credential-database SKUs; battery-backed SRAM appears in watch-bearing SKUs where the buyer needs millisecond RTC writes; OTP is universal in the factory-identifier bucket but never used for user data. The per-SKU choice is the supplier's engineering decision, not the buyer's — but the buyer signs the per-SKU choice against the supplier's named document.
EEPROM literacy — what each spec line on the datasheet means
A smart lock memory datasheet line does not stand alone; each line has to be read against the unit it is published in, the test condition it was generated under, and the SKU it was generated for. The buyer-side reading discipline is a vocabulary of seven line-reading habits.
| Spec line as written on the datasheet | What it actually means to the buyer | What the buyer must demand | What is a bluff |
|---|---|---|---|
| "Stores up to N users" | Maximum users credential capacity, written against the SKU's enrolled-credentials bucket | The SKU name, the firmware version the figure was measured on, the definition of "user" (one PIN / one card / one fingerprint / one app-bound ID) | A catalog-wide number that is never pinned to the dated product page |
| "Stores up to N cards" | Maximum RFID card capacity | The SKU name, the firmware version, whether guest cards and staff cards share the bucket | A category-wide number carried across SKUs |
| "Stores up to N fingerprints" | Maximum fingerprint template capacity (not raw images — templates only) | The SKU name, whether the figure assumes one template per user or two (enrol + back-up) | A figure sourced from a fingerprint sensor datasheet, not the lock's memory map |
| "Stores up to N audit events" | Maximum rolling audit-log capacity, before wrap or roll-over | The SKU name, the firmware version, the wrap behavior (oldest overwritten vs lockout) | A figure copied from one SKU onto another without re-verification |
| "Data retention N years" | Retention claim after power loss at a stated temperature | The test condition (temperature / humidity / number of write cycles before retention test), the SKU name | A bare "N years" with no test condition named |
| "Write cycles N per page" | Endurance claim per memory page | The page size in bytes, the test condition (temperature / write voltage), the SKU name | A figure sourced from a memory-vendor datasheet, not the lock's qualification report |
| "Brown-out protected" | Behavior during voltage drop mid-write | The protection mechanism (voltage supervisor / write latch / ECC), the SKU name | A bare adjective, no mechanism named |
Every line on this table is a per-SKU figure. The buyer signs the line against the dated product page, not against the category brochure.
The buyer-side engineering vocabulary — 18 items the RFQ must carry
The procurement engineer's first move on memory is to file an 18-vocabulary-item row group into the engineering tearoff. Each item is a question whose default answer route is "check the model’s published specification."
| Vocabulary item | What is documented |
|---|---|
| V1 memory family | Question the buyer asks: Is the credential storage EEPROM / flash / battery-backed SRAM / combination? |
| V2 memory capacity in bytes | Question the buyer asks: What is the total addressable memory in bytes (or kilobytes)? |
| V3 user-record size | Question the buyer asks: How many bytes per enrolled user (PIN / card / fingerprint / app-bound ID)? |
| V4 maximum enrolled users | Question the buyer asks: How many enrolled users (PIN / card / fingerprint / app-bound ID) does the lock hold? |
| V5 maximum cards | Question the buyer asks: How many RFID cards does the lock hold (guest + staff shared or segregated)? |
| V6 maximum fingerprints | Question the buyer asks: How many fingerprint templates does the lock hold (one or two per user)? |
| V7 maximum PINs | Question the buyer asks: How many PIN codes does the lock hold (one-time + time-bound + permanent)? |
| V8 maximum audit events | Question the buyer asks: How many audit events does the lock hold before wrap or roll-over? |
| V9 audit wrap behavior | Question the buyer asks: Does the audit log overwrite the oldest event, or does the lock stop recording at capacity? |
| V10 write-cycle endurance | Question the buyer asks: What is the write-cycle endurance per memory page (per-page, in cycles)? |
| V11 page size | Question the buyer asks: What is the page-write size in bytes (1 byte / 4 bytes / 16 bytes / 64 bytes / larger)? |
| V12 data-retention envelope | Question the buyer asks: What is the data-retention figure, and under what test condition (temperature / prior write cycles)? |
| V13 brown-out protection | Question the buyer asks: What is the brown-out protection mechanism (voltage supervisor / write latch / ECC)? |
| V14 RTC backup | Question the buyer asks: If the LTRA clock is battery-backed, what is the backup source (coin cell / supercapacitor) and expected service life? |
| V15 factory-identifier storage | Question the buyer asks: Are the serial number, MAC, and model string stored in OTP, EEPROM, or flash? |
| V16 firmware-update storage | Question the buyer asks: Is firmware-update space in flash separate from the credential space? |
| V17 memory-write logging | Question the buyer asks: Are memory writes logged into the audit bucket or a separate diagnostic bucket? |
| V18 memory-test routine | Question the buyer asks: Does the lock run a power-on self-test of the memory subsystem, and what does it report on failure? |
The product-page-documented SLK-9936S audit-records-up-to-1,000 figure is invoked ONCE in this article as the documentation-granularity yardstick — never extended across the catalogue.
The documentation loop — memory's standing rule
Every memory figure a salesperson quotes must be verified against three artefacts on the dated product page. The discipline is a habit the buyer runs once per shortlisted SKU before the RFQ is written.
| Step | What the buyer does | What the buyer writes | Where the answer lives |
|---|---|---|---|
| Step 1 — open the dated product page for the SKU | Pull up the supplier's dated product page for the specific SKU (not the catalogue category page) | SKU name + firmware revision + page date | Supplier product page |
| Step 2 — locate the memory section | Find the memory section in the datasheet, the controller datasheet, or the OEM memory-declaration form | Memory family chip family + page-write size + retention figure + endurance figure + audit-event ceiling | Supplier memory datasheet |
| Step 3 — cross-check the figure | Confirm the per-SKU figure against the supplier's evidence (sample power-loss test report / OEM memory-declaration form / controller-datasheet excerpt) | Three-way cross-check signed by engineering | Buyer-side memory row of the engineering tearoff |
A bare figure without a named document is a brochure sentence, not an engineering specification. The buyer's standing rule: any memory figure that cannot be traced to the dated product page is treated as unverified and is escalated to request a quote with the residual-question line.
What EEPROM does NOT do — five memory misconceptions to retire
EEPROM literacy collapses without the negative vocabulary. Five misconceptions appear on the buyer's desk with enough regularity to retire them one by one.
| Misconception | Why it is wrong | What the buyer does instead |
|---|---|---|
| "EEPROM lasts forever" | EEPROM has a write-cycle endurance per page (a finite number of writes per memory cell) and a data-retention envelope that depends on temperature and prior write cycles | Ask V10 write-cycle endurance and V12 data-retention envelope, both per-SKU |
| "More EEPROM means always better." | Larger memory does not always help; it can mean slower page-write time, larger brown-out window, and higher cost | Ask V2 capacity and V11 page size together, per-SKU |
| "Audit log never gets full." | Every audit-log implementation either overwrites oldest events or stops recording at capacity; both behaviors have operational consequences | Ask V8 audit capacity and V9 wrap behavior, per-SKU |
| "Battery swap loses all data." | Battery swap does not lose data if the data lives in EEPROM or flash; battery swap can lose data if the data lives in battery-backed SRAM and the backup is dead | Ask V14 RTC backup and confirm credential storage is non-volatile, per-SKU |
| "Memory figures are universal across the catalogue." | Memory figures vary by SKU and firmware revision; porting a figure from one SKU to another is a substitution | — |
Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.
These five misconceptions are the buyer's first filter at the quotation stage; each one rephrases into a row of the engineering tearoff at smart lock engineering procurement checklist.
Power-loss scenarios — what survives and what does not
EEPROM literacy is most often tested at the moment of a power-loss event. Three scenarios are the realistic stress tests the buyer runs in the engineering judgment.
| Scenario | What happens to the memory | What the buyer demands |
|---|---|---|
| Battery dies during normal use | EEPROM and flash retain data indefinitely; battery-backed SRAM retains data if backup is healthy | Confirm credential storage is non-volatile, per-SKU |
| Battery is removed during a memory write | EEPROM write may be incomplete; flash write is block-level so partial block can be inconsistent; battery-backed SRAM is intact | Ask V13 brown-out protection and the supplier's behavior on incomplete write |
| Battery removed for weeks or months | EEPROM and flash retain data; battery-backed SRAM may lose data if the backup battery is at end of life | Ask V14 RTC backup source and expected service life |
| Power restored after a long outage | Lock returns to the same credential list, configuration, and audit log (subject to last-known byte-write completion) | Check the model’s published specification with the supplier's retention-envelope test report |
The buyer never asks "does it survive a power loss" — the buyer asks "which memory family, what retention envelope, what brown-out protection, and what is the supplier's evidence." The four questions are answered against the dated product page, never ported across SKUs.
Firmware updates and the memory-discipline companion
Firmware updates are the second operational pressure on the memory subsystem. The firmware-update routine erases the firmware-update space (typically a flash page separate from the credential space) and writes the new image; if the firmware update fails mid-write, the lock must roll back to the prior firmware image without losing the credential list. The buyer-side literacy is six items:
| Firmware-update literacy item | What is documented |
|---|---|
| FU1 firmware-update space | Question the buyer asks: Is the firmware-update space separate from the credential space? |
| FU2 rollback behavior | Question the buyer asks: Does a failed firmware update roll back to the prior image without credential loss? |
| FU3 firmware version logging | Question the buyer asks: Is the firmware version logged into the audit bucket or a separate diagnostic bucket? |
| FU4 firmware-update authentication | Question the buyer asks: Is the firmware image authenticated (key / signature) before flash? |
| FU5 firmware-update logging | Question the buyer asks: Is the firmware-update event logged in the audit bucket with timestamp? |
| FU6 firmware-update evidence | Question the buyer asks: Is there a named document that confirms the firmware-update process is non-destructive to credentials? |
The firmware-update discipline is the companion to the memory discipline; both are tracked in the firmware-security sibling at smart lock firmware security and the audit-log sibling at smart lock audit logs.
Where the EEPROM vocabulary does not belong
ROM literacy separates the buyer from the paper-flow when vocabulary is misused. Seven vocabulary items travel with EEPROM but belong elsewhere.
| Vocabulary item | Where it belongs | Why it does not belong in the EEPROM RFQ |
|---|---|---|
| Memory chip vendor brand name (Atmel / Microchip / STMicro / NXP / Winbond / Macronix / Gigadevice / Espressif / etc.) | Engineering tearoff / BOM (Bill of Materials) row | The brand of the memory chip is the supplier's engineering decision; the buyer signs the per-SKU performance figure, not the brand |
| Memory capacity in raw bits vs bytes | Engineering tearoff / controller datasheet | Raw bit count is a marketing figure; the buyer-relevant figure is the per-bucket count (users / cards / fingerprints / PINs / events) |
| Endurance in cycles per bit cell | Memory-vendor datasheet | Cycle-per-bit is the memory-vendor specification; the buyer-relevant figure is the cycle-per-page of the SKU |
| ECC (Error-Correcting Code) implementation | Engineering tearoff | ECC is the supplier's engineering decision; the buyer signs the per-SKU error-rate, not the ECC scheme |
| Wear-levelling algorithm | Engineering tearoff | Wear-levelling is the supplier's engineering decision; the buyer signs the per-SKU endurance, not the algorithm |
| Power-on self-test routine | Engineering tearoff | POST is the supplier's engineering decision; the buyer signs the per-SKU behavior on POST failure |
| Memory-write encryption | Firmware-security RFQ | Encryption-of-memory-at-rest is a firmware-security topic; it consumes V13 brown-out protection but is not the memory-feasibility question |
Each of these seven items is a vocabulary swap. The buyer's job is to keep the swap visible — write the EEPROM row, and route the swaps to the right sibling.
Illustrative scenario — a 280-room mixed-use property reading the EEPROM chain across five SKUs
Consider a 280-room mixed-use property being rolled out across two adjacent buildings: a 180-room mid-tier city hotel and a 100-unit serviced-apartment building. Five SKUs are shortlisted to cover the door populations:
- Hotel guest-room door (180 rooms) — hotel-class RFID keypad lock in the SLK-9936S family
- Serviced-apartment guest door (100 units) — keypad / card / multi-credential lock in an alternate hotel-class family
- Back-of-house staff door (24 doors) — keypad-only or RFID-only lock in a narrower-feature class
- Glass-partition conference door (12 doors) — glass-door smart lock in the SLK-G200 family
- Outdoor perimeter gate (8 gates) — outdoor-class smart lock with broader temperature envelope
The buyer runs the 18-vocabulary-item table (V1-V18) against each shortlisted SKU. The SLK-9936S row carries the product-page-documented "audit/event records up to 1,000" line under explicit no-porting-across-models firewall. Every other memory figure — V1 memory family, V2 capacity, V4 maximum enrolled users, V5 maximum cards, V6 maximum fingerprints, V7 maximum PINs, V8 maximum audit events, V10 write-cycle endurance, V11 page size, V12 data-retention envelope, V13 brown-out protection, V14 RTC backup, V17 memory-write logging, V18 memory-test routine — defaults to "check the model’s published specification" for each of the five SKUs.
The buyer writes 18 × 5 = 90 memory cells into the engineering tearoff. The supplier returns the tearoff with 90 cells filled (or 90 cells blank, which is itself a signal). The buyer then runs the seven-item firmware-update literacy (FU1-FU6) against each SKU, the five-item power-loss-scenario table against each SKU, and the five-item misconception filter against each SKU. The total cells filed and signed for this property is approximately 90 + 30 + 25 + 25 = 170 memory-related cells, every one routed to the dated product page, every one signed against the supplier's named document.
This scenario is illustrative, not a customer story. The SKU pairings, the door counts, and the property class are intentionally generic. The buyer runs this discipline on the property the buyer is actually procuring; the discipline scales linearly with the number of shortlisted SKUs.
What to demand from the supplier before the order is written
Five demands sit at the buyer's head for procurement sign-off. None is negotiable; none is asserted as a held certification; none is a price / MOQ / lead-time / warranty claim.
| Demand | What the supplier provides | Where the answer lives |
|---|---|---|
| Memory datasheet excerpt | Per-SKU memory family chip, capacity, page size, endurance, retention | Supplier memory datasheet |
| Controller datasheet excerpt | Per-SKU controller family, integrated memory map, write-cycle budget | Supplier controller datasheet |
| Sample power-loss test report | Per-SKU behavior on battery removal during write, on long-term power loss, on RTC backup failure | Supplier test report or sample-test report |
| OEM memory-declaration form | Per-SKU signed statement of memory family, audit-event ceiling, wrap behavior, firmware-update non-destructive posture | Supplier OEM declaration form |
| Brown-out behavior note | Per-SKU behavior on voltage drop mid-write, including the protection mechanism | Supplier engineering note |
Each demand routes to a named document. A supplier who cannot produce a named document for any one of the five demands is a supplier whose memory row is escalated to request a quote before the order is written.
Decision matrix — when memory becomes a buying gate
Memory is a buying gate under five trigger patterns. The buyer-side discipline is to recognize the trigger and run the corresponding row of the memory vocabulary table.
| Trigger | Why memory becomes a gate | Primary vocabulary row | Secondary vocabulary row |
|---|---|---|---|
| Hotel-class deployment >100 rooms | Audit log retention and wrap behavior become operationally critical | V8 + V9 | V10 + V12 |
| Multi-tenant residential | Per-user credential list grows, wrap behavior on user records becomes critical | V4 + V9 | V11 + V18 |
| Outdoor perimeter gate | Temperature envelope stresses data-retention; brown-out becomes critical | V12 + V13 | V14 |
| Glass-partition door with limited fingerprint access | Smaller memory footprint; per-user record size becomes critical | V3 + V4 | V6 + V11 |
| Property with mixed firmware-update history | Firmware-update non-destructive posture becomes critical | FU2 + FU3 | V15 + V16 |
The trigger table is the buyer's quick filter at the RFQ stage. A trigger that matches the buyer's property profile moves memory from a brochure line to a procurement gate.
EEPROM, flash, and battery-backed SRAM — the comparative posture
A short comparative table closes the family vocabulary. The buyer's job is to read the table as engineering posture, not as a substitute for the per-SKU datasheet.
| Memory family | Strength | Watch-out | Where it is most common in the catalog |
|---|---|---|---|
| EEPROM | Byte-level rewrite, no battery backup needed for retention, long retention claim | Page-write time, write-cycle ceiling per page, brown-out during write | Hotel-class credential buckets, configuration buckets |
| Flash | Bulk-rewrite, larger capacity, cheaper per byte | Block-erase granularity, wear-distribution discipline | Firmware-update space, large credential databases |
| Battery-backed SRAM | Fast, byte-addressable, low write latency | Backup battery age, replacement schedule, backup-fail behavior | RTC clock, fast-cycle counters |
| OTP / fuse | Cannot be silently rewritten, permanent record | One-time write means no field service | Factory identifiers (serial, MAC, model) |
The table is posture, not specification. Every cell of the table is overridden by the per-SKU figure on the dated product page.
Memory literacy hand-off — the closing loop
EEPROM literacy on a smart lock resolves to a per-SKU memory row the buyer signs against the dated product page. The discipline scales linearly with the number of shortlisted SKUs, the number of door populations, and the number of property profiles. The closing hand-off is six steps:
| Step | What the buyer does | Where the answer lives |
|---|---|---|
| 1 — open the engineering tearoff | Pull up smart lock engineering procurement checklist | Buyer-side engineering tearoff |
| 2 — file 18 vocabulary rows per shortlisted SKU | V1-V18 cells filed against each SKU | Buyer-side memory row of the tearoff |
| 3 — file 6 firmware-update vocabulary rows per SKU | FU1-FU6 cells filed against each SKU | Buyer-side firmware-update row of the tearoff |
| 4 — request the five supplier documents | Memory datasheet + controller datasheet + power-loss test report + OEM declaration form + brown-out note | Supplier document pack |
| 5 — escalate residuals to the quote desk | Any cell that cannot be traced to the named document is escalated | Request a quote |
| 6 — order physical samples for memory-test acceptance | Physical chip reference + sample-test battery-swap test + sample-test long-power-loss test | Order samples |
The discipline is the same discipline the smart lock materials buyer guide runs for housing materials, the same discipline the smart lock data retention sibling runs for the time lens, and the same discipline the smart lock audit logs sibling runs for the audit-bucket lens. Every sub-system gets the same habit: per-SKU check the model’s published specification, named document, engineering signature.
EEPROM literacy is not a chip-vendor conversation; it is a buyer-side engineering habit. The chip on the lock controller board is the supplier's choice; the per-SKU performance figure is the buyer's signed cell. The whole discipline stands or falls on whether the buyer writes the cell against the named document, or whether the buyer accepts the brochure sentence.
The next move is the engineering tearoff at smart lock engineering procurement checklist where the 18 memory vocabulary rows drop in as new EC-rows, the supplier-side evidence pack comes back through request a quote, the physical chip reference comes back through order samples, and the catalog brochure comes back through request catalog. Memory literacy is a written programme, not a brochure line.

