STM32U5 Unlock — What You Need to Know First
The STM32U5 series (STM32U575, STM32U585, STM32U595, STM32U5A5, STM32U5A9, and others) is ST Microelectronics’ ultra-low-power Cortex-M33 line featuring Arm TrustZone hardware isolation, AES-256 crypto acceleration, and a three-tier Read-Out Protection (RDP) scheme. An STM32U5 unlock means recovering firmware from a device where these protections have been engaged — typically for authorized purposes such as legacy product maintenance, prototype recovery, or IP you own but have lost the source for.
Our engineers evaluate every STM32U5 unlock request on a per-device basis because the combination of TrustZone, TZEN bit state, and RDP level creates a protection matrix that varies significantly between part numbers and revision IDs. Below we break down exactly what determines feasibility, what it costs, and how long it takes.
How Does STM32U5 Protection Work?
Understanding the protection architecture is essential before any unlock attempt. The STM32U5 family layers multiple security mechanisms:
RDP Levels (Read-Out Protection)
- RDP Level 0 (0xAA): No protection. Flash is fully readable via SWD/JTAG. No unlock needed.
- RDP Level 0.5: Debug port open but flash access blocked — unique to STM32U5. Partial access possible with specific tooling.
- RDP Level 1 (0xBB): Debug access disabled for flash readout; SRAM remains accessible. Regression to Level 0 triggers a full flash erase, but certain side-channel and glitch-based techniques may recover content before erase completes on some silicon revisions.
- RDP Level 2 (0xCC): Permanent lockout — debug port physically disabled, boot from RAM/system memory blocked. This is the hardest tier and success is never guaranteed.
TrustZone (TZEN Bit)
When TZEN = 1, the Cortex-M33 core partitions memory into Secure and Non-Secure worlds. Secure firmware runs behind a hardware boundary that Non-Secure code cannot cross. Even if RDP is at Level 1, the Secure flash region has an independent access gate. Unlocking a TrustZone-enabled STM32U5 effectively requires defeating two layers — RDP and the Secure Attribution Unit (SAU) / IDAU configuration.
Additional Hardening
- Secure Boot (RSS / Root Secure Services): Validates firmware integrity before execution.
- Write Protection (WRP): Sector-level write locks that complicate in-situ modification approaches.
- Proprietary Code Readout Protection (PCROP) equivalent: Execute-only regions that block even privileged read access.
- Anti-tamper pins: External tamper detection can trigger key/data erasure.
| Protection Feature | STM32U5 Implementation | Impact on Unlock |
|---|---|---|
| RDP Level 0.5 | Debug open, flash blocked | Moderate — firmware not directly readable but attack surface exists |
| RDP Level 1 | Debug port locked; regression erases flash | High — requires glitch/fault injection; success varies by revision |
| RDP Level 2 | Debug permanently fused off | Very high — invasive techniques only; success rate under 50% |
| TrustZone (TZEN=1) | Secure/Non-Secure partition | Adds a second isolation layer on top of RDP |
| Tamper detection | Active pins + backup register erase | Can destroy keys/data if triggered during physical probing |
Is STM32U5 Unlock Feasible for Your Device?
Feasibility depends on three variables we assess during a no-cost evaluation:
- Exact part number and silicon revision. Early revisions of the STM32U575/U585 (Rev A, Rev B) have known errata that can widen the attack surface. Later revisions (Rev Z and beyond) patch many of these vectors.
- RDP level currently set. Level 0.5 and Level 1 devices have meaningfully higher success rates than Level 2. We verify the RDP state non-destructively before quoting.
- TrustZone activation state. TZEN = 0 simplifies the task considerably. When TZEN = 1, the Secure flash region adds 3–7 working days to the timeline and may require a second sample chip.
We are transparent about limits: RDP Level 2 on a late-revision STM32U585 with TrustZone enabled is the most difficult configuration in the current STM32 portfolio. We will not accept a project we assess as unviable. If the protection configuration on your chip is similar to what we encounter on the STM32L5 series (also Cortex-M33 with TrustZone), some techniques overlap — but the STM32U5 adds hardened RSS and updated glitch countermeasures.
STM32U5 Unlock Process — Step by Step
1. Feasibility Request
Submit your part number (e.g., STM32U585AIIxQ), current RDP state if known, and proof of ownership or authorization. We sign a mutual NDA before any device ships.
2. Non-Destructive Assessment (1–2 Days)
Our lab reads option bytes via SWD (if accessible) or power-analysis profiling to confirm RDP level, TZEN state, and boot configuration without altering the chip. You receive a written feasibility report with a success probability estimate and a firm quote.
3. Unlock Attempt (5–15 Working Days)
Depending on protection tier, our engineers apply one or more techniques:
- Voltage fault injection (VFI): Precisely timed supply glitches during the RDP check sequence — effective on certain RDP Level 1 configurations.
- Electromagnetic fault injection (EMFI): Localized EM pulses targeting the flash controller — used when VFI alone is insufficient.
- Laser fault injection (LFI): For RDP Level 2 on decapped die — highest precision, highest cost.
- Cold-boot / SRAM dump: Capturing volatile data from SRAM immediately after power-on when bootloader briefly exposes it.
4. Firmware Delivery
Recovered firmware is delivered as a raw binary (.bin) or Intel HEX file, verified against a CRC/checksum where possible. If only partial recovery is achieved, we deliver what was extracted with a detailed map of which flash sectors were readable.
Cost and Lead Time
| Protection Configuration | Typical Cost (USD) | Lead Time (Working Days) | Estimated Success Rate |
|---|---|---|---|
| RDP 0.5, TZEN = 0 | $500 – $900 | 5 – 7 | High (>85%) |
| RDP 1, TZEN = 0 | $800 – $1,500 | 7 – 10 | Moderate-High (60–80%) |
| RDP 1, TZEN = 1 | $1,200 – $2,500 | 10 – 15 | Moderate (50–70%) |
| RDP 2, TZEN = 0 | $2,000 – $4,000 | 12 – 18 | Low-Moderate (30–50%) |
| RDP 2, TZEN = 1 | $3,000 – $6,000+ | 15 – 25+ | Low (<40%) |
Pricing follows a “no-success, reduced-fee” model: if we cannot extract usable firmware, you pay only a bench-time fee (typically 20–30% of the quoted price) to cover lab consumables and engineering hours. We require 1–3 sample chips; invasive techniques (decapping for LFI) destroy the device.
Authorization and Legal Requirements
Every STM32U5 unlock engagement requires documented proof of ownership or written authorization from the IP holder. Acceptable documentation includes original purchase records, a signed letter from the rights holder, or a statutory declaration. We operate under NDA and will not proceed without this step — protecting both parties. For more on our compliance framework, see our trust and authorization policy.
Related STM32 and Arm Cortex-M33 Unlocks
If your project involves other STM32 families with similar TrustZone-based protection, our lab handles those as well. The STM32L5 unlock process shares the Cortex-M33 / TrustZone architecture but uses an older flash controller with different glitch timing windows. For wireless-enabled STM32 variants, we also support STM32WL LoRa-capable MCUs and STM32WB Bluetooth-enabled devices, both of which add radio coprocessor firmware to the recovery scope.
Working with non-STM32 Arm parts? Our Microchip/Atmel capabilities cover devices like the ATSAM4 series, which uses a different but comparably layered protection scheme.
What Can Go Wrong
Transparency matters. Here are realistic failure modes our engineers encounter:
- Flash erase on regression: An improperly timed glitch during RDP Level 1 regression can trigger the mass-erase routine before data is captured. This is why we request spare samples.
- Tamper-triggered key wipe: If anti-tamper pins are configured and the board is removed from its enclosure without disabling them, AES keys stored in backup registers are erased instantly.
- Die damage during decapping: Chemical or laser decapping can damage bond wires or the flash array on the 40 nm process node used in STM32U5. Success requires precise acid exposure timing (typically 45–90 seconds with fuming nitric acid at 80 °C).
- Partial reads: Fault injection may yield 90–95% of flash content with corrupted sectors. We can often reconstruct the missing sections from context (vector tables, known library code), but full recovery is not always possible.
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 reviewCan STM32U5 RDP Level 2 be unlocked?
It is technically possible using invasive methods such as laser fault injection on a decapped die, but success rates are below 50% on late silicon revisions. We assess each device individually and provide an honest feasibility estimate before you commit. The process destroys the chip, so at least two samples are recommended.
How does TrustZone affect the STM32U5 unlock difficulty?
When the TZEN bit is set to 1, flash memory is split into Secure and Non-Secure regions with independent access controls enforced by hardware. This means bypassing RDP alone is insufficient — the Secure Attribution Unit must also be circumvented. Expect 3–7 additional working days and a 10–20% increase in cost compared to a TZEN = 0 device at the same RDP level.
Do I need to send the entire PCB or just the chip?
For most STM32U5 unlock projects, the bare chip (desoldered) is preferred because it gives our equipment direct probe access. However, if anti-tamper circuits are board-level and you need us to safely disable them first, send the complete assembly. We can desolder BGA and QFP packages in-house using IR reflow.
What file format will I receive after a successful STM32U5 firmware extraction?
We deliver a raw .bin file mapped to the flash base address (0x0800 0000) and, optionally, an Intel HEX (.hex) or Motorola S-Record (.srec). A flash sector map and CRC verification report are included. If partial recovery occurs, we annotate which sectors are verified and which are reconstructed.
Is STM32U5 firmware recovery legal?
Firmware recovery is legal when performed on devices you own or when you have written authorization from the IP holder. Common lawful scenarios include recovering lost source code from your own prototypes, maintaining legacy equipment, and failure analysis. We require proof of authorization and work under NDA on every engagement.
Working on a board like this?
Send the chip marking or two photos. You get feasibility, lead time and price within 24 hours, and the check costs nothing.
Get a free quote