PCBA and EMS

PCB Reverse Engineering in China

Rebuilding a schematic, netlist and BOM from a physical board. The technical work is routine; the legal position is not, and it decides whether the job can be done at all.

What this service covers

Reverse engineering takes a physical board and produces a design package: layer images, a netlist, a schematic, a bill of materials and, for simple boards, a set of Gerbers.

The technique is not exotic. Layers are scanned, delaminated or X-rayed, the copper is digitised, connectivity is extracted and the result is checked against the physical board. What makes these jobs fail is rarely the extraction. It is either a board that cannot be read without destroying it, or a legal position that was never settled.

This is not a disclaimer, it is the first technical constraint on the job.

  • You need the right to the design. Owning a physical board is not the same as owning the design. If the product is your own, or you commissioned it, that is a clean basis. If it is a competitor’s product, it is not.
  • Patents expire, copyright does not. A circuit topology that was patented may be free to use after the term. The artwork, the firmware and the documentation remain protected works regardless of patent status.
  • Firmware is a separate question from hardware. Reading a microcontroller’s code out of a device is legally different from tracing copper, and in many jurisdictions it is not permitted at all. A supplier that offers both without asking why should worry you.
  • The output is a new design, not a copy. Reproducing a board exactly, including silkscreen marks and the original manufacturer’s identifiers, creates a counterfeit rather than a redesign.

A factory that will start the job before asking these questions is telling you it has not thought about them, which is a quality signal as much as a legal one.

What the technical work actually involves

  • Layer count and stack-up recovery. Delamination destroys the board; X-ray and controlled milling preserve it. Which method is used decides whether the sample survives.
  • Netlist extraction and verification. Every net is checked against the physical board by continuity, because digitisation errors are silent and appear later as a design fault.
  • Component identification. Marking codes, package sizes and measured values. Parts with obscured or proprietary markings become the schedule risk.
  • BOM reconstruction with alternatives. Obsolete parts need a documented substitute, which is a design decision, not a purchasing one.
  • Documentation of what could not be recovered. Internal layers on a board that cannot be delaminated, embedded components, and calibrated analog sections. Stating the gap is part of the deliverable.

What drives the price

  • Layer count and board area, because scanning and digitising scale with both.
  • Whether the board can be delaminated, and whether a sacrificial sample is available.
  • Component count and marking legibility, since identification is manual work.
  • Firmware scope, if it is in scope at all.
  • Verification depth: continuity check only, or a functional comparison against a known-good unit.

What we check before listing a factory here

  • The factory asks for the legal basis before quoting, and documents the answer.
  • The deliverable set is defined in writing: layers, netlist, schematic, BOM, Gerbers, and which of these are native files.
  • A verification method is stated, because an unverified netlist is a guess with a file extension.
  • The factory states what it cannot recover on your specific board rather than claiming full recovery.
  • Firmware is either explicitly out of scope or handled under a separate, documented agreement.
  • The factory will not reproduce third-party brand marks, which is the line between reverse engineering and counterfeiting.

Where it goes wrong

  • A netlist that was never checked. The design builds, and the fault appears as an intermittent connection three revisions later.
  • Marking codes read as part numbers. A package code is mistaken for a device type, and the BOM is wrong from the start.
  • The sample is destroyed before a backup is made. No second attempt is possible without another unit.
  • Obsolete parts replaced without documentation. The board works, and no one can explain why the replacement was chosen.
  • The legal question is answered after the work is done. By then the deliverable exists and cannot be unused.

How it differs from neighbouring services

PCB design starts from a specification; this service starts from an object. Fabrication and assembly are downstream and are quoted separately. A supplier that offers all three may be convenient, and the reverse-engineering scope still needs its own written definition.

What to send in an RFQ

The board or a photograph of both sides, layer count if known, the intended use of the output, the legal basis on which you hold the design rights, whether firmware is in scope, and the deliverable format you need. The reverse engineering quote specification lists the fields that change the answer.

If you own the design and only need updated manufacturing data, PCB design services is the correct route and avoids the legal question entirely.