Most of the RX130 group lives on 48-pin or 80-pin packages, so the 64-lead version occupies a niche of its own: R5F51306BDFK#10, with 256 KB of code flash, 32 KB of RAM and the group’s standard 8 KB of E2 data flash, in an LQFP that measures 14 x 14 mm on a 0.8 mm pitch. The #10 suffix is packaging metadata, nothing more – the die inside is the same as the #30 tray part. When a client needs us to restore a protected R5F51306BDFK heximal, the wider body is good news twice over: the 0.8 mm pitch tolerates careful probe work, and the package carries the analog extras the small builds omit.
The Analog Extra That Only The 64-Pin Build Has
This is the RX130 variant with digital-to-analog conversion: two 8-bit DAC channels are wired out on the 64-pin package, alongside fourteen channels of 12-bit ADC and two comparators. Applications that generate references – sensor excitation, audio prompts, control voltages – depend on those DACs, and their configuration constants live in flash and data flash just like everything else. Thirty-two capacitive-touch channels and fifty-two general-purpose I/O lines round out the pin budget. A heximal that omits the DAC and touch configuration is a partial image, and we treat the analog blocks as acceptance criteria during retest, not as decoration.
What The 256 KB Array Holds
At this density the application is a real product: protocol stacks, buffered touch processing, fault logging. The code flash is page-programmed with read-while-write support, so field-updated designs show their history in the page map – alignment gaps, stale fragments from superseded builds, occasionally an intact older version of a module the current code no longer calls. Those fragments are documented in our report rather than trimmed away; rebuild teams use them to roll features back or to confirm which constants the production firmware actually shipped with. The E2 data flash keeps its own erase schedule and is imaged independently, block for block.
Protection And The Readout Path
The RX130 group gates external access with the ID code at FFFFFA0h, consulted by both the boot-mode serial programmer and the on-chip debug facility, and every die also carries a 128-bit unique identifier that licensing schemes sometimes reference. The practical consequence is familiar from the rest of the family: configuration bytes and observed bus behaviour decide the entry path, and a die whose ID check is armed will not reward guesswork. We stay inside the 1.8 to 5.5 V operating window throughout, we do not erase, and every delivered read is verified twice against the silicon.
Socket And Rework Reality
The 0.8 mm pitch on this 14 x 14 mm body changes the logistics compared with the group’s finer-pitched builds. Clamshell sockets for 64-lead LQFP at 0.8 mm are commodity items and gentle on leads, so where the client can supply the chip loose, socketed work is the low-risk default. Where the donor must stay on its board – production fixtures, certified assemblies – we work in-circuit, and the wider pitch means flux cleanup and optical inspection after probing are quick and conclusive. Lead damage is not merely cosmetic on this family: several of the analog and touch channels are pin-multiplexed, and a lifted lead can silently remove a DAC output or a touch electrode from the retest matrix. The report records the work mode – socketed or in-circuit – together with a post-probe inspection note, so the client knows exactly what physical condition the donor returned in.
Handover
Deliverables are the full code-flash HEX from address zero to the end of the 256 KB array, the data-flash image, the decoded configuration region, and a handling note for the 0.8 mm pitch – rework stations that behave on finer-pitch parts are usually fine here, but socket selection matters if the donor must stay in service. Family cross-references: the 48-pin 384 KB sibling, the mid-size 128 KB 48-pin part, and the entry 64 KB RX130. One more practical note: because the 64-pin 0.8 mm build is the group’s analog showcase, boards that use the DACs almost always pair them with external reference or filtering circuitry whose behaviour the recovered firmware assumes. A replacement part flashed without the recovered data-flash section can enumerate correctly and still put the wrong voltage on a DAC output – harmless on the bench, expensive at the sensor. Verifying the analog outputs against the donor board before sign-off is part of our standard retest for this variant. Bookings and quotations: the services desk or the contact form.