Services Products Company Journal Contact
English Türkçe Deutsch

ECHO / JOURNAL · NOTE 08

Why Chip Code Tables Can Be Wrong

People who sort memory chips desoldered from scrap boards rely on tables that map a chip’s code to its capacity. These tables speed the work up, but not every row is right. We compared a 1,185-row chip code table, row by row, with the manufacturers’ own documents. This note shows what we found and what BoardVision does with those rows.

ECHO ·

A stack of blank cream index cards with a silver pen and three small black BGA memory chips on a travertine desk
A table is a shortcut. The manufacturer’s document is the reference.

Rows that contradict the documents

In some rows, the capacity in the table did not match the value in the manufacturer’s document:

CodeIn the tableIn the manufacturer’s document
D9TXF1 GB3 GB (Micron MT52L768M32D3PU: 768M × 32 bit)
D9PNQ512 MB768 MB (Micron)
H9TKNNNAADAPLR-NGH1 GB1.5 GB (SK hynix, 12 Gb)
W978H6KBV256 MB32 MB (Winbond, 256 Mb)

Where these errors may come from

We do not know the cause of every row; we only report what the documents show.

  • Bits and bytes mixed up. In Winbond’s catalogue, W978H6KBV sits in the 256 megabit (Mb) section, which is 32 megabytes. The table’s “256 MB” most likely comes from misreading the unit.
  • Unusual sizes. Two of the correct values, 768 MB and 1.5 GB, are not the familiar “round” sizes. Values like these are easy to get wrong in a table.
  • Differences we cannot explain. For D9TXF the table says 1 GB; Micron’s part number shows 768M × 32 bit, which is 24 gigabit, which is 3 GB. We do not know why.

Rows without a document

For roughly half of the table we found no manufacturer document at all. That does not mean those rows are wrong. It only means they could not be verified.

What BoardVision does with these rows

  • Rows that contradict a document are locked: BoardVision shows no capacity for those codes. In the current version that applies to 9 rows covering 7 codes.
  • Rows backed by a manufacturer document are shown as confirmed. Rows resolved only through the manufacturer’s numbering rule carry a separate label, because that is weaker evidence.
  • Brands with no supporting document, for example Toshiba-Kioxia, SanDisk, CXMT, YMTC and Foresee, are shown as “unverified”.

When you use a table

  • Where possible, check a code’s capacity against the manufacturer’s own document.
  • Look at the unit: Gb or GB?
  • Treat a row with no source as a clue, not as a fact.

How a five-character code leads to a capacity in the first place is explained in D9XPZ: Why a Memory Chip Doesn’t Show Its Capacity.

Limits

  • Reading accuracy with a real camera has not been measured yet, so we give no rate.
  • BoardVision does not test a chip electrically and does not prove that a chip is genuine. The marking tells you what the chip claims to be.
  • The iOS and Android versions are in development and not in the app stores yet. The version we use today is an internal macOS prototype.

Get in touch→