Bao'An Shenzhen China

EFM32 Unlock | Feasibility, Cost & Lead Time

Published · About 8 min read · PCB-Copy

On this page
  1. What Is EFM32 Unlock and When Do You Need It?
  2. How Silicon Labs Protects EFM32 Flash
  3. Which EFM32 Sub-Families Can Be Unlocked?
  4. Our EFM32 Unlock Process — Step by Step
  5. Cost and Lead Time for EFM32 Firmware Recovery
  6. What Can Go Wrong — Realistic Constraints
  7. Authorization and Legal Requirements
  8. Related MCU Unlock Services

What Is EFM32 Unlock and When Do You Need It?

EFM32 unlock is the process of recovering firmware from a Silicon Labs EFM32 Gecko-series microcontroller whose debug access port (DAP) has been locked via the Debug Lock Word (DLW) or AAP lock bits. Authorized recovery is typically needed when original source code is lost, a key engineer has left the company, or a legacy product requires maintenance on a discontinued board. Our engineers perform EFM32 unlock under NDA with proof of ownership, returning a verified binary within 5–15 working days for most Gecko sub-families.

How Silicon Labs Protects EFM32 Flash

efm32 unlock: Silicon Labs EFM32 Giant Gecko MCU on a PCB ready for firmware recovery

Understanding the protection architecture is the first step in assessing whether an EFM32 unlock is feasible for your specific part. Silicon Labs implements several layers across the Gecko platform, and the exact combination determines difficulty.

Debug Lock Word (DLW)

The DLW resides in the User Data page (address 0x0FE00000 region). When all 32 bits of the DLW are cleared to 0x00000000, the Cortex-M DAP is disabled. A standard “device erase” via the AAP can reset the lock—but it wipes all flash contents first, which is exactly what you want to avoid when recovering firmware.

AAP Lock and AAP Window

On newer EFM32 Series 1 parts (Giant Gecko 11, Pearl Gecko, Jade Gecko), the Application Authentication Protocol (AAP) can itself be locked, closing the erase-and-unlock escape path. The AAP window configuration (CLW0) can further restrict the time window during which the AAP responds after reset—sometimes as short as a few microseconds.

Page-Level Lock Bits

Each flash page (typically 2 KB or 4 KB depending on family) has an individual lock bit in the Lock Bits Page. When set, these prevent page-level erase and write operations but do not by themselves block read access if the debug port is open. They become relevant during partial-recovery scenarios.

Protection Feature EFM32 Series 0 EFM32 Series 1 Impact on Unlock
Debug Lock Word (DLW) Yes — User Data page Yes — User Data page Primary barrier; must bypass without triggering mass erase
AAP Lock (CLW0 bit 0) Not available Yes Blocks standard device-erase path; raises difficulty
AAP Window restriction Not available Yes — configurable µs window Narrows timing for glitch-based approaches
Page Lock Bits Yes — per 2 KB/4 KB page Yes — per 2 KB/4 KB page Minor; relevant only for write-back operations
Secure Boot (SE) No EFR32 only (not standard EFM32) If present, significantly harder; assessed case-by-case

Which EFM32 Sub-Families Can Be Unlocked?

Not every Gecko part responds to the same techniques. Our lab maintains a running feasibility matrix based on parts we have physically worked with. Below is a realistic summary—not a guarantee—based on accumulated experience.

Sub-Family Core Typical Flash Unlock Feasibility Notes
EFM32 Zero Gecko (EFM32ZG) Cortex-M0+ 32 KB High Series 0; DLW-only protection
EFM32 Tiny Gecko (EFM32TG) Cortex-M3 32 KB High Series 0; well-documented DLW behavior
EFM32 Gecko (EFM32G) Cortex-M3 128 KB High Original family; mature techniques available
EFM32 Leopard Gecko (EFM32LG) Cortex-M3 256 KB High Larger flash; same Series 0 DLW scheme
EFM32 Giant Gecko (EFM32GG) Cortex-M3 512 KB–1 MB High Series 0; 512 KB readout takes longer but is reliable
EFM32 Wonder Gecko (EFM32WG) Cortex-M4F 256 KB High Series 0; FPU variant, same lock mechanism
EFM32 Happy Gecko (EFM32HG) Cortex-M0+ 64 KB High USB-capable; Series 0
EFM32 Pearl Gecko (EFM32PG1/PG12) Cortex-M4F 256–1024 KB Moderate Series 1; AAP lock may be set
EFM32 Jade Gecko (EFM32JG1/JG12) Cortex-M3 256–512 KB Moderate Series 1; same AAP considerations
EFM32 Giant Gecko 11 (EFM32GG11) Cortex-M4F 2 MB Moderate–Low Series 1; largest flash; 2 MB readout + AAP lock

“High” feasibility means our engineers have a well-established procedure with a success rate above 90 % on Series 0 parts. “Moderate” indicates that the AAP lock configuration must be evaluated on the physical sample before committing. We never quote a guaranteed outcome until the free feasibility assessment is complete.

Our EFM32 Unlock Process — Step by Step

  1. Feasibility request: You send us the exact part number (e.g., EFM32WG990F256), a photo of the board or bare chip, and proof of IP ownership or authorization.
  2. Free assessment (1–3 days): We cross-reference the part against our internal matrix, check the Series/revision, and confirm whether the DLW alone is set or if AAP lock is also engaged.
  3. Quotation: You receive a fixed-price quote and estimated lead time. No charge if we determine the part is not recoverable.
  4. Physical recovery (5–15 working days): The chip is de-soldered (if on-board), placed in our test fixture, and subjected to the appropriate bypass technique. Flash contents are read out page by page and reassembled into a complete binary image.
  5. Verification: We compare checksums, validate the vector table (initial SP and reset handler), and optionally re-program a blank EFM32 of the same part number to confirm functional equivalence.
  6. Delivery: You receive the firmware as an Intel HEX or raw .bin file, plus a brief report noting any anomalies (e.g., unused flash regions, bootloader presence). Files are transferred via encrypted channel under NDA.

If your project also involves a different MCU family on the same board—such as a Texas Instruments MSP430 handling a sensor subsystem—we can process both chips in parallel to cut overall turnaround.

Cost and Lead Time for EFM32 Firmware Recovery

De-soldered EFM32 chip placed in a test fixture for debug-lock bypass

Pricing depends on the sub-family, flash size, and protection configuration. The ranges below reflect recent project data and are subject to the free feasibility check.

Category Typical Price Range (USD) Lead Time (Working Days)
Series 0 — DLW only, ≤128 KB flash $400–$800 5–8
Series 0 — DLW only, 256 KB–1 MB flash $600–$1,200 7–12
Series 1 — DLW + AAP lock, ≤256 KB $900–$1,800 10–15
Series 1 — DLW + AAP lock, 512 KB–2 MB $1,200–$2,500 12–18
Rush surcharge (≤5 days) +30–50 % Case-by-case

We charge nothing if the unlock attempt fails. Payment is due only upon confirmed delivery of a verified firmware image.

What Can Go Wrong — Realistic Constraints

Transparency matters. Here are the most common failure or complication scenarios our engineers encounter during EFM32 unlock work:

  • Damaged die: If the chip has been exposed to ESD, overvoltage, or corrosive environments, the flash cells themselves may be corrupted regardless of lock state.
  • Secure Element on EFR32 variants: Some boards labeled “EFM32” actually carry an EFR32 (wireless SoC) with the Secure Element (SE) enabled. The SE adds hardware-rooted key storage that is substantially harder to bypass. We assess this during feasibility and will inform you before any work begins.
  • Partial reads: On rare occasions, a small number of flash pages (typically the last 1–2 pages used for NVM configuration) may return inconsistent data. We flag these pages and, where possible, reconstruct the expected content from surrounding context.
  • Chip revision differences: Silicon Labs has released multiple die revisions within the same part number (e.g., Rev A vs. Rev C of EFM32GG990F1024). Protection behavior can differ between revisions. Providing the full marking from the package top helps us avoid surprises.

Authorization and Legal Requirements

EFM32 unlock is performed exclusively for clients who demonstrate legitimate ownership of the firmware or written authorization from the IP holder. Typical qualifying scenarios include recovering your own production firmware after source-code loss, maintaining legacy equipment you own, or supporting a product redesign where the original developer is unavailable. We require a signed declaration of ownership and work under mutual NDA. For full details on our compliance framework, see our trust and authorization policy.

Related MCU Unlock Services

Many embedded designs pair an EFM32 with a secondary controller. If your board also carries a Nordic Semiconductor BLE chip, our nRF52 unlock service covers the nRF52832 and nRF52840 APPROTECT mechanism. For designs using a Freescale/NXP Kinetis alongside a Gecko for mixed-signal duties, see our Kinetis flash security recovery page. Engineers working with Chinese-market Gecko alternatives such as the APM32 (Geehy) can review feasibility at our APM32 unlock guide.

Can you unlock an EFM32 without erasing the flash?

Yes—that is the entire purpose of the service. A standard “device erase” via the AAP would clear the DLW but also wipe all flash contents. Our techniques bypass the debug lock while preserving the flash image intact. On Series 0 parts this is well-established; on Series 1 parts with AAP lock, additional steps are required but the goal remains non-destructive readout.

How do I know if my EFM32 is Series 0 or Series 1?

Check the part number suffix. Series 0 parts include EFM32G, EFM32GG (original Giant Gecko), EFM32TG, EFM32LG, EFM32WG, EFM32ZG, and EFM32HG. Series 1 parts carry a numeric suffix after the family letter—e.g., EFM32PG1B, EFM32JG12B, EFM32GG11B. If unsure, send us a photo of the chip marking and we will identify it during the free assessment.

Do you need the whole PCB or just the chip?

Either works. If you send the assembled board, our technicians de-solder the EFM32 using a controlled hot-air station, perform the readout, and re-solder it (or a programmed replacement) before returning the board. If you can supply a loose chip, it reduces handling time by roughly one day.

What file format will I receive?

By default we deliver an Intel HEX file covering the full flash address range, plus a raw .bin for direct programming. If you need Simplicity Commander (.s37) format for use with Silicon Labs tools, we can provide that as well. A checksum report accompanies every delivery.

Is the recovered firmware guaranteed to run on a new blank EFM32?

We verify functional equivalence by programming a blank part of the same revision whenever a spare is available. However, if the original firmware reads unique device information (e.g., the 64-bit Unique ID at 0x0FE081F0), behavior on a different physical chip may vary. We document any such dependencies in our delivery report.

Check feasibility for your project

Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.

Request a feasibility review
TURN THE GUIDE INTO A PROJECT QUESTION

What do you need to recover?

Send the full marking or board photos, sample condition and required outcome. Ask for an NDA before sharing confidential files. Scope and sample handling are confirmed individually.

The article title is carried into the contact form. Add your own details and review the enquiry before sending.

WhatsApp Send board details