Two files for the same board code can disagree: a resistor value changes, a capacitor disappears, a MOSFET moves to the other side of the board. The reason is almost always the revision. Understanding what changes between revisions tells you when a mismatched file is a minor nuisance and when it will mislead you.
Where revisions come from
A laptop board goes through several builds before mass production. The schematic and the PCB are updated at each stage, and each update gets a new revision number. The exact naming varies between ODMs, but the pattern is usually:
- Rev 0.1, 0.2, 0.3… — engineering and validation builds. The design is still changing; boards of these revisions rarely reach customers, but their schematics often leak.
- Rev 1.0 — the design released for mass production.
- Rev 1.1, 2.0, 3.0… — later changes during production: component substitutions, fixes for field problems, cost reductions, new processor or memory support.
On top of the board revision, some brands add a build stage. Dell boards built by Compal carry codes such as X00, A00, A01 and A02, printed next to the revision. Quanta encodes the revision as a letter inside the part number (…MB6D0 is revision D), Inventec as a -MB-A0x suffix, and Asus as REV 2.0 after the model name.
What usually changes between revisions
| Change | Typical example | Does it affect repair? |
|---|---|---|
| Component values | A feedback resistor changes, shifting a rail voltage slightly | Yes, if you replace that part or compare voltages |
| Populated options | A part marked "not fitted" in Rev 0.3 becomes fitted in Rev 1.0 | Yes, the empty footprint may be correct on your board |
| Second-source parts | A different MOSFET or charger IC with the same function | Sometimes — pin-outs or values can differ |
| Layout | Parts moved or rotated to fix interference | Yes for boardviews, rarely for schematics |
| Circuit fixes | An added capacitor, a changed enable path, a new protection part | Yes — this is where old schematics mislead you |
| Page order and numbering | Pages split or merged | Only for navigation |
Early 0.x schematics are the riskiest. They may show circuits that were later redesigned, parts that were removed and debug connectors that never made it to production boards.
How to find the revision of your board
- Silkscreen — next to the board code:
REV 1.0,REV:2.0,R1.1. - Quanta part number — the letter near the end:
DA0R63MB6F1is revision F. - Inventec suffix —
6050A2412601-MB-A02is revision A02. - Asus main board label —
X540MB REV 2.0printed on the board, often near the memory or the CPU. - Dell build stage —
(A00),(A02)printed near the Compal code.
Our guide to finding the right schematic shows where to look on the board.
Reading the change history page
Most ODM schematics end with a revision history page — sometimes titled "Change List", "History" or "Revision History". It lists each change with the page number, the parts involved and a short reason. Read it whenever your board revision differs from the schematic you have:
- Find the entries between your revision and the schematic's revision.
- Note each page and part mentioned.
- When your diagnosis touches one of those parts, measure or check the boardview rather than trusting the drawing.
If your schematic is newer than your board, the history tells you what your older board does not have yet. If it is older, the history is missing — another reason to prefer the newest schematic available.
When a close revision is good enough
In practice you will often work with a schematic one revision away from your board. That is fine when:
- you are tracing power paths and sequence logic, which rarely change between production revisions;
- you are checking which signal enables which rail;
- the history page shows no changes in the area you are working on.
It is not fine when you need exact component values to replace a part, when the change history mentions the circuit you are diagnosing, or when you are using a boardview to find a part's position. Positions are where revisions differ most — see How to Match a Boardview to Your Board Revision.
A practical example
You are chasing a missing always-on 3.3 V rail on a board printed Rev 2.0, and the only schematic available is Rev 1.0. The schematic shows the regulator, its enable resistor divider and a single output capacitor. On the board you find the regulator and the divider exactly where the boardview says — but the output has two capacitors, and one footprint near the enable pin that the schematic marks as unfitted carries a part on your board.
The change history at the end of the schematic does not cover Rev 2.0, because the document predates it. So you treat the drawing as a guide: the enable logic and the regulator are the same design, which is enough to diagnose the fault. For the extra parts, you measure instead of trusting the drawing — the added capacitor turns out to be the shorted one. Had you replaced only the parts shown in the Rev 1.0 schematic, the rail would still be dead.
That is the typical pattern: a close revision explains how the circuit works, and the board itself tells you what is actually fitted.
Populated or not: options across revisions
A related trap is the option system. Each schematic covers several variants of the board, and parts belonging to other variants are marked with codes like @, NC or DNI. Between revisions, a part can move from one group to another. If you see an empty footprint where your schematic shows a part, check the option marking and the history before assuming the part is missing. Option markers are explained in Unpopulated Components (NC, DNI, @) in Laptop Schematics.
Revisions and BIOS files
Revisions matter for firmware too. A BIOS dump from a later board revision may expect hardware that an earlier revision lacks, and EC firmware is sometimes tied to a specific board revision. When the catalog shows several BIOS files for a board, pick the one whose revision matches yours, and always keep a backup of your original chip before flashing.
FAQ
Is Rev 1.0 always the version sold in shops?
Usually it is the first mass-production revision, but many boards sold to customers are later revisions. Read the revision on your board rather than assuming.
Why would anyone share a Rev 0.3 schematic?
Because that is what leaked. Engineering documents from early builds circulate as often as production ones. They are still very useful for understanding the circuit; just verify details against your board.
Can a different revision of the boardview damage anything?
Not directly — it is just a file. The risk is measuring or replacing the wrong part because it moved between revisions. Compare part positions with the real board before you heat anything up.
What do A00 and X00 mean on Dell boards?
They are build stages added by Dell and its ODMs: X stages are pre-production, A stages production. They sit alongside the board revision and help match a board to the right documents.
Should I keep files for several revisions of the same board?
Yes. Two revisions side by side often answer questions neither answers alone — one may have a clearer power sequence page, the other a change history that explains a part you found on your board. Keep them together in one folder named after the board code.
Bottom line
Always read the board revision from the PCB and pick the closest schematic and boardview. Use the change history to see what differs, trust power-path logic across revisions, and verify values and part positions on the board whenever your work depends on them.