Bao'An Shenzhen China

CH32V307 Unlock | Feasibility, Cost & Turnaround

Sep 26, 2026  /  PCB COPY

ch32v307 unlock: WCH CH32V307 microcontroller on PCB with probe needle during firmware recovery

CH32V307 Unlock — What You Need to Know

The CH32V307 is a 32-bit RISC-V microcontroller from WCH (Nanjing Qinheng Microelectronics) built on the RISC-V3A core running at up to 144 MHz. It integrates 256 KB of flash and 64 KB of SRAM, along with USB HS OTG, Ethernet MAC, CAN, and a rich set of peripherals. CH32V307 unlock — authorized firmware readout from a read-protected device — is feasible in many configurations, but success depends on the specific protection bits set during production and the physical condition of the target IC.

How Does the CH32V307 Protect Its Firmware?

ch32v307 unlock: WCH CH32V307 microcontroller on PCB with probe needle during firmware recovery

WCH’s CH32V307 implements a layered protection scheme that differs from the ARM Cortex-M read-out protection (RDP) model most engineers are familiar with. Understanding these layers is essential before requesting any unlock service.

Read Protection (RDPR)

The option bytes include a Read Protection field. When activated, external debug access via the single-wire debug (SWD-like) interface or the WCH-Link tool is blocked. The flash contents cannot be read through standard JTAG/SWD operations. This is the most commonly encountered protection level on production CH32V307 devices.

Write Protection (WRPR)

Independent write-protect bits can lock individual 4 KB flash sectors against erase or reprogram operations. Write protection alone does not prevent readout, but when combined with RDPR it complicates recovery because the option-byte area itself may be write-locked.

User Configuration Byte Lockout

Certain CH32V307 revisions allow the user configuration word to disable the bootloader ROM entry entirely. If the UART/USB ISP bootloader path is closed, the only remaining electrical interface to the flash is the debug port — which RDPR has already blocked.

Protection Layer What It Blocks Bypass Difficulty
RDPR active Debug-port flash readout Moderate — well-understood attack surfaces
WRPR active Sector erase/write via ISP Low additional barrier to readout
Bootloader disabled UART/USB ISP entry Eliminates one recovery path; debug glitching still viable
RDPR + Bootloader disabled All standard external access Requires invasive or semi-invasive techniques

Is CH32V307 Unlock Realistic?

Yes — for the majority of production-locked CH32V307 devices our engineers have evaluated, firmware recovery is achievable. WCH’s RISC-V protection implementation is newer and less battle-tested than, for example, STM32 RDP Level 2. The CH32V307’s option-byte structure and debug-port handshake expose timing and voltage-glitch vectors that have been validated in our lab on multiple silicon revisions (V307 rev B and rev C confirmed). Success rate across recent projects sits above 85 % for RDPR-only protection.

Where feasibility drops is the rare case of a CH32V307 with a custom-masked ROM bootloader or physically damaged bond pads. In those scenarios we perform a free feasibility assessment before quoting, so you never pay for a failed attempt.

Techniques Our Lab Uses

  • Voltage-glitch fault injection: Precisely timed VCC transients during the RDPR-check window can force the debug controller to serve flash contents. Non-destructive to the die.
  • Debug-protocol exploitation: Proprietary WCH-Link protocol weaknesses in certain bootloader ROM versions allow partial or full readout under specific timing conditions.
  • Semi-invasive optical/laser probing: Reserved for high-value cases where non-invasive methods fail. Adds cost and turnaround but preserves the original firmware bit-for-bit.

All work is performed under NDA with proof of device ownership or authorized-agent documentation required before we begin. Our authorization and legal compliance policy details the documentation we accept.

CH32V307 Unlock Cost and Turnaround

Pricing depends on the protection configuration and the technique required. The table below reflects typical ranges — your actual quote may differ after feasibility review.

Scenario Estimated Cost (USD) Typical Turnaround
RDPR only, standard revision $400 – $700 5 – 7 working days
RDPR + bootloader disabled $600 – $1,000 7 – 10 working days
RDPR + WRPR + bootloader disabled $800 – $1,400 8 – 12 working days
Semi-invasive / laser probing required $1,200 – $2,500 10 – 18 working days

Feasibility evaluation is free. If we determine the device cannot be unlocked, you owe nothing. Expedited service (3–5 day rush) is available at a 40 % surcharge for RDPR-only cases.

Deliverables After a Successful CH32V307 Unlock

Voltage-glitch fault injection lab setup used for MCU flash readout
  • Binary firmware image (.bin / .hex) — full flash dump, verified with checksum.
  • Option-byte dump — complete configuration register state including RDPR, WRPR, and user bytes.
  • Disassembly listing (optional add-on) — RISC-V disassembly with symbol annotation where identifiable.
  • Reprogramming guidance — notes on re-flashing the firmware to a blank CH32V307 using WCH-LinkE or OpenOCD, including option-byte restoration sequence.

Files are delivered encrypted via our secure portal. Physical return shipping of the original IC is included.

CH32V307 vs. Other Common Unlock Targets

Engineers often ask how the CH32V307 compares to other MCUs they may need recovered. The WCH RISC-V family sits in a middle difficulty tier — harder than basic serial EEPROMs like the 24C256, but generally more accessible than dual-core ARM parts such as the STM32WB55 with its RDP Level 2 and Secure Element co-processor.

MCU / IC Architecture Top Protection Relative Difficulty
CH32V307 RISC-V RDPR + bootloader disable Medium
STM32WB55 ARM Cortex-M4 + M0+ RDP Level 2 + SE High
24C256 I²C EEPROM Write-protect pin only Low
MSP430F2xx MSP430 JTAG fuse Medium-Low
PIC18FK PIC Code-protect bits Medium

If your project involves multiple device types — say a CH32V307 main controller alongside an SST25VF SPI flash for data logging — we handle both in a single engagement, which can reduce total cost by 10–15 %.

When Do Engineers Need CH32V307 Unlock?

The most common scenarios we see are not adversarial. They are practical engineering problems:

  • Lost source code: A development team’s repository was corrupted or a contractor departed without delivering source. The only surviving copy of the firmware is on a production-locked CH32V307.
  • Legacy product maintenance: An older product revision used the CH32V307 and the original programming files were never version-controlled. A hardware fault requires re-flashing replacement ICs.
  • Failure analysis: Comparing the firmware on a field-failed unit against a known-good binary to identify corruption or tampering.
  • Authorized second-source production: An OEM with full IP rights needs to migrate firmware to a new production line but lacks the hex file.

In every case, we require written proof of ownership or a signed authorization letter before work begins.

How to Get Started

Submit your CH32V307 for a no-cost feasibility check. Our typical workflow:

  1. Inquiry: Send the part number, quantity, and a brief description of the protection state (if known) via our quote form.
  2. Feasibility report: We evaluate the device and confirm whether unlock is viable, the expected technique, cost, and turnaround — usually within 2 working days.
  3. Authorization & NDA: You provide proof of ownership; we countersign an NDA.
  4. Extraction: Firmware is recovered, verified, and delivered via secure portal.
  5. Support: 30-day post-delivery support for reprogramming questions.

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
Can a CH32V307 be unlocked without destroying the chip?

In most cases, yes. Our primary techniques — voltage-glitch fault injection and debug-protocol exploitation — are non-destructive. The original IC is returned fully functional. Semi-invasive methods (used in under 15 % of cases) carry a small risk of bond-wire damage, which we disclose before proceeding.

What documentation do I need to authorize a CH32V307 unlock?

We accept a signed declaration of IP ownership, a purchase order showing you procured the devices, or a letter of authorization from the IP holder. Government or institutional clients can provide an official request on letterhead. Details are on our trust and compliance page.

Does unlocking the CH32V307 also recover the bootloader ROM contents?

The mask ROM bootloader is WCH factory code and is identical across all CH32V307 units of the same revision. We do not extract it as part of a standard unlock because it is not user-specific firmware. If you need it for analysis, ask during the feasibility stage — it can be included at no extra charge.

How does CH32V307 protection compare to CH32F103 or CH32V003?

The CH32F103 (ARM Cortex-M3 based) uses a similar RDPR scheme and is roughly equivalent in difficulty. The CH32V003, a smaller RISC-V part with 16 KB flash, has a simpler protection model and is generally easier and cheaper to unlock. If you have multiple WCH parts, we can bundle them into one project for cost efficiency.

What if the CH32V307 flash is partially corrupted?

We perform a full binary dump and a CRC-32 verification pass. If sectors are corrupted, we flag them in the deliverable report and provide the raw dump alongside a corrected image where bit-flip patterns are recoverable. Corruption does not prevent extraction — it only affects the usability of the recovered data.

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

Related reading

WhatsApp Send board details