PostHeaderIcon Retrieve Secured STM32G030F6P6 Flash: TSSOP20 32 KB Read

Some of the hardest-looking recoveries are physically the easiest to open, and the STM32G030F6P6 is the clearest example. This is the G0 value line in a 20-lead TSSOP body just 6.5 mm long, an Arm Cortex-M0+ at 64 MHz with 32 KB of flash and 8 KB of SRAM, and it is the part you find soldered onto single-function appliance and sensor boards. Those boards carry no second storage chip, so when the firmware was never archived the MCU is the only copy. To retrieve secured STM32G030F6P6 flash you work the package, not the pins, and the tiny body is on your side.

A small die that is easy to reach

The TSSOP20 is a generous shape for decapsulation even though the part is small. The silicon die sits centred and roomy inside the moulding compound, with bonding wires fanned out to the leads. That geometry means the chemical etch can expose the full die face without risking the bond pads, and the STM32G030F6P6 stays electrically live after the cap comes off. Our silicon package decapsulation work covers this body routinely, and the same handling applies to the larger STM32G030C6T6 in LQFP48.

Why these boards lose their only copy

The STM32G030F6P6 is chosen for cost and pin count, flashed once on the line, and then the project file disappears into an archive that is never opened again. Years later a single failed unit is the whole source of truth. Because the board has no SPI flash or EEPROM holding a second copy, there is nothing to read except the MCU itself. The program restoration steps we document assume exactly this situation: the device is the archive.

Where the security actually sits

On the STM32G030F6P6 the read protection lives in the option bytes, in a security-protection level that the flash controller samples out of reset. Level 1 is what a locked unit carries and it stays recoverable, while level 2 is permanent. The part has no USB, so there is no DFU door, and the ROM bootloader over USART obeys the same level. The design parallels the AVR fuse-and-lock model described in our lock-bit primer, with the same warning: dropping level 1 to level 0 erases the flash you came to read.

Reading the die after the etch

With the die exposed, a timed optical fault at the boot security check can let the verification fall through, holding the debug port open long enough to stream the 32 KB array out. Microprobing is the fallback when a fault window is awkward here. Either way the STM32G030F6P6 is a quick capture once the port holds, because the array is small and the bus is simple. The flash recovery path is the same one we use on the STM32G030C8T6 when its image is needed.

With twenty leads at 0.65 mm pitch there is room to work around the package without fouling a neighbour. The part is kept soldered and powered through the whole procedure, so the fault lands on a live boot sequence rather than on a device that only answers a debugger. On this part the security decision is taken very early, before the application touches its peripherals, which is exactly the moment a timed pulse needs.

Where the optical route is not the right fit, a supply or clock perturbation can widen the same comparison window without opening the package. Our power glitch notes and clock glitch material describe those attempts. They cost little and carry no risk to the image, since a failed attempt simply leaves the part locked, so they are tried before the package is opened.

What is readable at each level

Level Debug read USART boot Outcome on this part
0 – open yes yes no recovery needed
1 – read lock no no decap then read alive die
2 – sealed no no probing only, no erase

What the recovered flash contains

You receive the complete 32 KB binary, the option bytes recording the original lock state, and a verification report that confirms both read passes checksummed equal. The array is read twice and the passes compared cell by cell, so a capture that closed mid-transfer is caught rather than handed over as a short file. The write-protection settings are mapped as well, which tells the customer whether a region can be reprogrammed on the recovered part or whether the original vendor sealed it against updates.

Where the aim is a replacement appliance board, the same verified image is what goes onto a blank part through our firmware cloning process, with the option bytes programmed first so the replacement starts in the same state as the original. The neighbouring STM32G030K6T6 decode follows the same recovery discipline in a 32-lead body.

Comments are closed.

Categories