A board built around the GD32F330C8T6 carries a Cortex-M4 @84 MHz, no FPU with 64 KB program block and 8 KB of working RAM inside a LQFP48. The recovery service reads the GD32F330C8T6 physically and preserves its protection state.
Bench Routine
We read 64 KB program block first, then the option bytes bytes, then a live RAM snapshot if the assembly boots, followed by a confirming second pass. The bench order for a GD32F330C8T6 is fixed: flash, then option region, then any live RAM, then two full reads for a checksum.
Flash And Working Memory
With 64 KB program block the GD32F330C8T6 executes in place, so the reset vector and interrupt table sit at the bottom of the user region. The 8 KB of working RAM on the GD32F330C8T6 sits below the peripheral bus and often caches a calibration table a cold dump misses. The RX563 extraction case shows a larger RX part with the same debug-ID convention.
Where The Read Protection Lives
The GD32F330C8T6 stores its readout-protection level in the flash option bytes, managed by the FMC peripheral rather than a one-time fuse. On the GD32F330C8T6 the protection state lives in the option bytes region and is handled through the FMC block, so it stays reversible. A bypass overview explains holding a steady rail and reading twice on 5 V silicon.
Peripheral Set
The LQFP48 body also exposes two CAN controllers and a USB OTG interface on the F3xx line, details that matter for a clone. A GD32F330C8T6 design leans on the Cortex-M4 @84 MHz, no FPU FPU for motor maths, with CAN and USB handling the off-board traffic. A PIC clone note shows the timing source is reconstructed from evidence, not the hex alone.
Reporting And Hand-Off
Customers receive an Intel HEX sized to the full map, one binary per region, and a report listing the RDP level and oscillator. Delivery is one Intel HEX at the true addresses, separate binaries, and a short report for the LQFP48 with the protection state. A sibling page on the related GD32F303RCT6 covers the same group from a different package angle.
We archive a checksum per region so a future read of the GD32F330C8T6 can be compared byte for byte.
The Cortex-M4 @84 MHz, no FPU clock source is noted for the GD32F330C8T6, because a rebuild with the wrong PLL will not start.
The GD32F330C8T6 is photographed next to a scale so the package size is unambiguous in the archive.
The 64 KB program block on the GD32F330C8T6 is read at the true addresses, not a relocated image a tool might invent.
A GD32F330C8T6 recovered for a warranty claim ships with the evidence package the LQFP48 board provides.
Where the GD32F330C8T6 arrived with corroded pins, we clean the LQFP48 before the first bench attempt.
We note the batch code on the LQFP48 GD32F330C8T6, which sometimes explains a quirk in the silicon revision.
The LQFP48 outline of the GD32F330C8T6 matches other group members, so the marking confirms the exact die fitted.
Where a bootloader stage exists that region is captured in full for the GD32F330C8T6, the usual third-party omission.
A LQFP48 GD32F330C8T6 that locked mid-project is common; the array is intact, only the debug path is closed.
Our report flags any external memory the LQFP48 board carried, since the GD32F330C8T6 image may span parts.
We store the LQFP48 board in anti-static foam until the read is done and the files are handed over.
For field units the GD32F330C8T6 usually has no source; the extracted image is the only copy that survives.
The Cortex-M4 @84 MHz, no FPU on the GD32F330C8T6 runs the extracted code in place, so our report notes the boot setup for a spare LQFP48.
Photographs of the 48-pin board are filed with our report so the GD32F330C8T6 package can be audited later.
Most GD32F330C8T6 jobs arrive with no compiler project, only the physical part and a failed recovery attempt.
Our turnaround notes record the socket used, because the LQFP48 GD32F330C8T6 rarely sits in a standard adapter.
The Cortex-M4 @84 MHz, no FPU on the GD32F330C8T6 is documented in our report so a replacement part boots identically.
The 8 KB of working RAM on the GD32F330C8T6 is captured live only when the assembly still comes up on power.
We record the supply rail used on the LQFP48, because the GD32F330C8T6 flash timing is sensitive to voltage.