Skip to main content
Be Bitwise

PCB Analysis

Hardware Hacking · Embedded Systems & Firmware track

5 min read

In this module

Reading the Board

A printed circuit board (PCB) is the device's electronic blueprint, exposed in copper. For a hardware security researcher, the trick is reading it: identifying components, tracing signals, and uncovering interfaces the manufacturer never advertised. This lesson covers the techniques for doing all of that without the original design files in hand.

Identifying Components

The first step in PCB analysis is identifying every significant component:

MCU/SoC identification: The main processor usually has the most pins and sits roughly central on the board. Its part number is printed on the package (e.g., STM32F407VET6, BCM2711). Pull the datasheet — that document gives you the memory map, peripheral set, debug interface pinout, and security features.

Flash memory: External flash chips (SPI NOR, NAND) hold the firmware. Common packages: SOIC-8 (SPI NOR), TSOP-48 (parallel NAND). Part numbers like W25Q128 (Winbond SPI flash) or MX25L12835F (Macronix) name the chip.

RAM: External SDRAM or SRAM chips for devices that need more memory than the MCU provides on-die. Usually parked near the MCU with wide data-bus traces.

Communication chips: WiFi modules (ESP8266, RTL8812AU and friends), Bluetooth chips, Ethernet PHYs, cellular modems. Security-relevant because they handle network traffic.

Voltage regulators: These tell you which supply voltages live on the board (3.3V, 1.8V, 1.2V). You'll want that for UART level matching and voltage glitching.

Datasheet Mining

Once you identify a chip's part number, download its datasheet. The datasheet contains the complete pinout, electrical specifications, communication protocol details, and security features. For the main MCU, the reference manual (a more detailed document) describes every register, peripheral, and configuration option. These documents are essential for understanding the device's capabilities and attack surface.

Tracing Signals

PCB traces are the copper paths that connect components. Tracing these signals reveals how components are interconnected:

Visual tracing: On simple two-layer boards, traces are exposed on top and bottom. Follow a trace from the MCU's UART TX pin and see where it ends up — maybe a header pad (handy for tapping), maybe another chip.

Multimeter continuity testing: On multi-layer boards where traces hide in inner layers, switch the multimeter to continuity. Park one probe on a known pin (the MCU's JTAG TDO, say) and walk the other across pads until you get a beep.

X-ray imaging: For genuinely complex multi-layer boards, desktop X-ray systems peel back every internal layer. You see complete trace routing, hidden vias, and components on inner layers. Some security research labs and PCB analysis services rent out X-ray imaging.

Finding Test Points

Test points are small exposed pads or vias placed during PCB design for manufacturing testing. They often connect to important signals:

  • UART TX/RX: Debug console access
  • JTAG/SWD signals: Debug port access
  • SPI bus: Flash memory access
  • Reset line: Ability to reset the device at a controlled moment (useful for fault injection)
  • Power rails: Access points for voltage glitching

Test points are typically unlabelled circular pads, sometimes in a row. They may be marked with silk screen labels like "TP1," "J5," or simply dots. Cross-reference their connections with the MCU datasheet to identify which signals they carry.

Common Chip Families in IoT

Knowing common chip families speeds up analysis:

Routers: Broadcom BCM series, MediaTek MT7621/MT7628, Qualcomm Atheros QCA series, Realtek RTL series. Usually run Linux on MIPS or ARM.

IP cameras: HiSilicon Hi35xx, Ingenic T-series, Ambarella. Often run Linux with custom video pipeline software.

Smart home: ESP8266/ESP32 (WiFi), Nordic nRF52 (BLE), Texas Instruments CC2538 (Zigbee), Silicon Labs EFR32 (multi-protocol).

Industrial: Texas Instruments MSP430 (ultra-low power), NXP LPC series, Renesas RA/RX series.

PCB Photography and Documentation

Good PCB photographs do more work than people expect. Use a macro lens or USB microscope to capture both sides at enough resolution to read every part number. Annotate the images with identified components, traced signals, and discovered test points.

For complex boards, build a signal map documenting every connection you've identified between components. That map becomes the spine of the rest of your analysis — where to tap UART, where to land JTAG probes, which pad to dump flash from, where to inject the next fault.

Board Modification

Advanced hardware hacking sometimes requires modifying the PCB:

  • Soldering wires to test points: For permanent connections to debug interfaces
  • Cutting traces: Isolating a component from the bus (e.g., disconnecting the MCU from SPI flash to read the flash without bus contention)
  • Adding components: Installing pull-up resistors, level shifters, or bypass capacitors
  • Bypassing security: Connecting the MCU's boot mode pin to VCC/GND to force bootloader entry

Document and photograph every modification. Work under a stereo microscope with temperature-controlled soldering equipment — anything else is a slow road to a ruined board.

Safety and Ethics at the Bench

Only open and modify hardware you own or have written permission to test. Anything powered from the mains (routers with internal supplies, smart plugs, appliances) gets unplugged before the case comes off, and stays unplugged: capacitors on the primary side can hold a dangerous charge after disconnection, so work from the low-voltage side or use an isolated bench supply. Wear an ESD strap, since one static discharge can kill the chip you were about to dump. Expect modifications to void the warranty and possibly any certification the device carried, and think twice before a modified mains device goes back into everyday use.

Non-Destructive First

Always exhaust non-destructive analysis techniques before modifying the board. Photograph everything, identify all components, trace accessible signals, and check for accessible debug interfaces. Destructive modifications (desoldering chips, cutting traces) should be the last resort, performed on spare devices when possible. You cannot un-cut a trace on your only sample.