Modules / M4

FieldEmbedded systemsWritten material

Board reverse engineering

The topic

Board-level reverse engineering starts from a populated printed circuit board with no schematic. Students identify the parts, write a bill of materials, and draw a block diagram.

Where it belongs

Course: Embedded systems.
Teach this after: microcontroller interfacing, serial protocols, power distribution, and reading a datasheet. The lab is written and has not been assigned yet. The bench needs a multimeter.

Files and how to use them

There is no slide deck. The lab specification is the handout. Read the safety notes before students power the board. The required work fits one lab period.

  • Lab specification. Give this to students at the start of the period. It states the required identification work, the optional measurement work, the deliverables, and the evaluation.
  • Students need a populated board with no schematic, and a digital multimeter. A logic analyzer is optional and is used only if the course already has one.

Video lectures

These are links, not files stored with the module. Play one in class, or send the link to students.

Further reading

Optional papers for the instructor, or for a student who wants to read past the assignment.

  • Kleber, Nölscher, and Kargl, “Automated PCB Reverse Engineering,” USENIX Workshop on Offensive Technologies (WOOT), 2017.
  • Tehranipoor, Guin, and Bhunia, “Invasion of the Hardware Snatchers,” IEEE Spectrum, vol. 54, no. 5, pp. 36–41, 2017. Why a cloned or altered board is a supply-chain problem. This lab stops at identification.

The exercise

The student receives a populated board and no schematic. The required work is identification: a bill of materials and a functional hypothesis for each region of the board. Optional work moves from identification to measurement of the power rails and the serial links.

Outcome

A bill of materials with part numbers, a high-level block diagram, and a functional hypothesis for each section of the board. The lab specifies no defensive deliverable.

Required

  1. Identify components from the ICs down to passives and test points. Capacitor markings can be skipped when the marking is not recoverable.
  2. Build a bill of materials: description, part number, and value, with datasheets for the ICs.
  3. Hypothesize what each region does, and write the reason.
  4. Draw a high-level block diagram once the parts are known.

If the board is dense, restrict the required work to one or two chips. The lab period is the constraint the design rule is written for.

Optional, if the period or a second sitting allows it

  • Continuity-map one non-trivial part, such as a sensor or a memory, back to the microcontroller, and redraw that cone in KiCad or a similar tool.
  • Power the board and measure rails and regulators. Record what buttons, switches, or sensors do when the board is on.
  • Identify a UART, SPI, or I²C link. Confirm it with a logic analyzer when one is on the bench.

What is graded

Accuracy of the identification, quality of the reconstruction, and whether the reasoning connects a datasheet application circuit to the region of the board in front of the student. Safety notes in the lab specification cover powered measurement. Read them before the section.

Support

This work was supported in part by the U.S. National Science Foundation (NSF) Secure and Trustworthy Cyberspace (SaTC) program under Award No. 2114157.

Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the U.S. National Science Foundation.

The project is a collaboration of the University of Kansas, the University of Florida, and Florida International University.