• SPI
  • Intermediate
  • 5 min
  • Serial CLI

Recipe · Intermediate · SPI

How to analyze a SPI flash chip from the CLI

The browser flash programmer is best for clean backups. The CLI flash shell is useful when you want to inspect, search or analyze the chip from the device.

SPI flash chip with analysis markers.
Probe first, then use analyze/search/strings before deciding what to dump or modify.

Wiring View

SPI flash BP CSSPI CSCLKSPI CLKMISOSPI MISOMOSISPI MOSIVCC3.3VGNDBP GND
Generated from the wiring summary: SPI flash to BP.
Step 1

Commands

Run the typed commands first. If the command opens an interactive shell, select the named action from the shell menu instead of treating it as another CLI command.

Result

What success looks like

A stable JEDEC probe is the minimum signal that wiring is probably correct. Repeat it before trusting reads.

Troubleshooting

  • Leaving WP# or HOLD# floating on a bare flash chip.
  • Letting the target board drive the flash at the same time.
  • Trusting one read without a repeated probe or hash.
  • Using long clip wires at high speed.

Next steps

  • Run Probe Flash first.
  • Use Extract strings or Search string for quick reconnaissance.
  • Use the browser SPI flash programmer for a clean full backup.

SPI flash CLI analysis FAQ

When should I use the CLI shell instead of the browser programmer?

Use the CLI shell for quick probing, reading small ranges, searching strings and understanding what is on the chip. Use the browser programmer when you need a full backup file or a guided dump workflow.

Is a stable JEDEC probe enough before analysis?

It is the minimum sanity check, not the whole proof. Repeat the probe, keep wires short, confirm the expected capacity and avoid write or erase actions until you have a verified backup.

Can CLI analysis modify flash contents?

Probe, read, search and string extraction are read-oriented actions. Write or erase menu actions can modify contents, so keep them for lab chips or only after a backup is verified.

Go deeper