SOIC Clip Technique

Getting a clean connection with a SOIC clip is a skill. It looks trivial until you've spent 30 minutes chasing a bad read caused by a single pin not making contact. This lesson covers the physical process in the detail it deserves.

Before You Attach Anything

The target board must be powered off. This is not optional. Attaching a SOIC clip to a live board while the SoC is running can: - Corrupt flash contents (SoC and programmer fighting over the bus simultaneously) - Damage the SoC's I/O buffers if you short a pin - Damage the flash chip if you seat the clip with misaligned voltage

Power off, disconnect the power supply, and if the board has a large reservoir capacitor (common in mains-powered devices), wait 30 seconds for it to drain.

Identifying Pin 1

Locate the chip on the board. Use a loupe or phone macro lens if needed — chip markings are small.

Finding pin 1 on the chip body: - A small circular dot molded into the plastic near one corner - A chamfer (beveled edge) on one corner of the chip body - Sometimes a line or notch

Once you see the indicator, orient yourself: pin 1 is at that corner. On SOIC-8, numbering goes counterclockwise from pin 1 when viewed from the top.

Top view (chip marking facing up):

Pin 1 [dot] ---[  chip  ]--- Pin 8
Pin 2       ---[        ]--- Pin 7
Pin 3       ---[        ]--- Pin 6
Pin 4       ---[        ]--- Pin 5

Finding pin 1 on the clip: - Red wire (conventional on Pomona and clones) - Physical marking on the clip housing - Printed label

If your clip has no obvious indicator, use a multimeter in continuity mode: identify which clip contact corresponds to which wire, then build a map against the programmer's pinout.

Attaching the Clip: Physical Procedure

Orient the clip above the chip, not touching it yet. Confirm that pin 1 of the clip (red wire side) is above pin 1 of the chip (dot/chamfer side). If they're inverted, rotate the clip 180 degrees.
Approach at 45 degrees. Hold the clip at an angle — one row of teeth touches first. This lets you visually confirm that row is seated on the correct pins before committing the other row.
Lower the second row. Press straight down until you feel/hear the clip snap. The spring mechanism should provide firm resistance and then seat. All 8 contacts should be touching the 8 chip leads.
Visual inspection. Look at both sides. Every clip tooth should be contacting a pin, not riding between pins or shifted off the end of a lead. The clip body should be approximately parallel to the chip body.
Do not yank the cable. Strain-relief the cable. A tug on the ribbon cable will unseat the clip and can bend chip leads.

Continuity Check Before Powering the Programmer

Before connecting the CH341A to USB, verify connections with a multimeter in continuity mode:

Probe between GND on the clip ribbon and a known GND point on the target board. Should beep.
Probe between VCC on the clip ribbon and the chip's VCC pad. Should beep.
If you have a pinout map, spot-check one or two signal lines.

This catches gross misalignment (clip shifted by one pin) before you apply any voltage.

The Connection Test

Connect the CH341A to USB (board still unpowered, or with board power isolated — see L4 for the details of in-circuit vs. isolated reads).

# Probe only — detects chip, does not read
flashrom -p ch341a_spi -V

Expected good output:

flashrom v1.3.0 on Linux 6.1 (x86_64)
...
Found Winbond flash chip "W25Q128JV" (16384 kB, SPI) on ch341a_spi.

Expected bad output (connection problem):

No EEPROM/flash device found.
Note: flashrom can never write if the flash chip is not found automatically.

Or worse — it detects a nonsense chip ID, or hangs. Both mean a physical connection problem.

If detection fails: 1. Check pin 1 alignment — reseat the clip 2. Check that the clip cable is fully seated into the programmer header 3. Try --spispeed 512 to slow the clock 4. Re-check continuity

Common Failure Modes and How to Diagnose Them

Pin 1 misalignment (off by one): Symptom: flashrom detects a chip with wrong size, or garbage chip ID. The most destructive variant: CS and VCC are swapped — you just applied VCC to CS and CS to VCC. Check pin 1 before powering.

Incomplete contact (one pin not gripping): Symptom: reads that differ between runs, or flashrom detecting the chip inconsistently. Reseat the clip. If the chip leads are oxidized or the clip teeth are worn, clean the leads with IPA and a fine brush.

Clip touching adjacent component: Symptom: flashrom probe hangs, or you smell something burning. SOIC-8 chips often have nearby capacitors or resistors within the clip's footprint. Inspect before seating.

Cable too long / wrong orientation: Symptom: erratic reads that correlate with cable position. Shorter cables mean fewer signal integrity problems. If using jumper wires instead of a ribbon, keep them under 15 cm.

Board capacitance holding clip pins float: Symptom: flashrom detects chip briefly then loses it. Board components on the SPI bus add capacitance that can cause the clip to not make clean contact with the signals. Try slower clock speeds.

The Two-Read Verification Workflow

Never trust a single read.

# First read
flashrom -p ch341a_spi -c "W25Q128JV" -r dump1.bin

# Second read (no changes between these two commands)
flashrom -p ch341a_spi -c "W25Q128JV" -r dump2.bin

# Compare
md5sum dump1.bin dump2.bin

If the hashes are identical: your connection is solid and your dump is trustworthy.

If they differ: you have a noise or contact problem. Reseat the clip, try --spispeed 512, and repeat until you get two matching reads. Do not proceed to analysis with a dump you cannot reproduce.

For extra confidence, do three reads and compare all three:

flashrom -p ch341a_spi -c "W25Q128JV" -r dump3.bin
md5sum dump1.bin dump2.bin dump3.bin

All three should produce the same hash.

Slow Read Mode

When contact is marginal and you cannot improve it (limited physical access, adjacent components preventing a better clip angle), drop the SPI clock:

# 512 kHz — slow but more tolerant of bad connections
flashrom -p ch341a_spi -c "W25Q128JV" --spispeed 512 -r dump1.bin

A 16 MB chip at 512 kHz takes several minutes versus seconds at full speed. Patience is preferable to an unreliable dump.

Available speed options (check flashrom documentation for your programmer): - --spispeed 16384 — default range, fast - --spispeed 2000 — moderate reduction - --spispeed 512 — significant reduction, most compatible - --spispeed 128 — very slow, last resort