Renesas MCU Suffix and Package Guide

The answer in one minute

A Renesas MCU identifier can describe several different things. The orderable part number selects a shippable configuration. A short field inside that number may point to a package option. Renesas also maintains a longer package code for mechanical construction. The factory label adds quantity, lot, date, origin, and trace information. The device top mark may be shortened because the package has limited space.

Verified against current Renesas RA4M1, RX65N/RX651, and RL78/G23 documents and product pages. Review date: 28 August 2026.

A five-step method that works across Renesas families

1. Copy the complete string exactly.Preserve the prefix, every letter and digit, the #, and the characters after it. Normalize only visual spacing or case for searching; never silently edit the approved BOM.
2. Identify the MCU family and group.Start from a current Renesas product page or parametric search. The family tells you which datasheet’s “ordering information” or “product lineup” table is authoritative.
3. Decode position by position in that family document.Mark memory, feature, temperature/application, package, and packing fields only where the table defines them. Leave a field “unconfirmed” rather than borrowing a meaning from another family.
4. Cross-check mechanical and environmental facts.Verify package type, lead count, body dimensions, height, pitch, MSL, lead-free status, and temperature range on the exact part page and package drawing.
5. Close the commercial loop.Confirm lifecycle, packing carrier, MOQ, factory label expectations, compliance record, date/lot requirement, and approved substitution conditions before purchase.

Use a source hierarchy when documents disagree

Why RA, RX, and RL78 need separate lookups

The following examples are documented manufacturer records, not invented YURUNOX transactions. Their purpose is to show how the same buyer question—“what does the suffix mean?”—leads to different tables and different checkpoints.

On narrow screens, scroll tables horizontally. A code meaning is safe only inside the cited family and document revision.

Package names still need dimensions

LQFP, LFQFP, HWQFN, and WFLGA describe package families. They do not by themselves lock pin count, pitch, height, or body outline. For PCB compatibility, use the exact Renesas package drawing and land-pattern guidance, then verify the approved assembly process.

A short package field is a route to that mechanical record. It is not a universal mechanical specification.

Documented RA4M1 case: package and packing change independently

RA4M1 provides a clean way to see two layers of the orderable number. The core string R7FA4M1AB3C remains the same in the examples below while the short package field and post-hash packing code change.

The exact R7FA4M1AB3CFM#HA0 product page lists active status, LQFP-64, 10 × 10 × 1.7 mm, 0.5 mm pitch, MSL 3, Pb-free status, and tape-and-reel carrier. Renesas’s orderable-part RoHS record also uses the complete MPN—including #HA0—as the compliance identifier.

Primary sources: RA4M1 Group Datasheet; exact 48-pin tray, 64-pin tray, 64-pin reel, and 100-pin tray pages; RoHS record for R7FA4M1AB3CFM#HA0.

Documented RX65N case: a packing suffix can carry lifecycle consequences

The RX65N datasheet decodes R5F565NEDDFP#30 by position. In that example, E represents 2 MB code flash with 640 KB RAM and 32 KB data flash; the following D selects the documented feature combination; the next D is the −40 to +85°C temperature/application field; and FP selects a 100-pin LFQFP measuring 14 × 14 × 1.7 mm at 0.5 mm pitch.

This case answers a practical question. If an older AVL, drawing, or quote shows #30 while the current manufacturer record shows #10, do not delete both suffixes and approve only R5F565NEDDFP. Link the manufacturer change record to the alternate approval, confirm tray/carton quantity and label expectations, update purchasing data deliberately, and keep the old and new trace records distinct.

Primary sources: RX65N/RX651 Group Datasheet; current R5F565NEDDFP#10 product page; and Renesas’s List of Changed PLP Products.

Worked RL78/G23 example: R7F100GSK2DFB#HA0

The RL78/G23 ordering table gives its own positional key. In the documented example, S represents 128 pins, K represents 384 KB of code flash, 2 represents the −40 to +85°C range, D is the listed consumer-application field, and FB selects a 128-pin LFQFP with 0.5 mm pitch. The #HA0 field selects embossed-tape packing for the applicable package group.

Primary source: RL78/G23 Datasheet, Rev. 1.40. A current exact-part page also exists for R7F100GSK2DFB#UA0; do not infer another carrier from it without the family packing table.

How to read a full Renesas package code

Renesas’s package-code system answers a different question from the MCU ordering table. Its example PLQP0176KB-A describes a physical package through a sequence of mechanical fields.

The last two characters deserve restraint. Renesas says the appearance-identification and auxiliary-appearance fields are sequential and have no general common rules. Do not invent a universal meaning for B or A. Open the exact package page or drawing.

What a 0.5 mm pitch changes

Pin pitch affects the land pattern, solder-paste design, placement accuracy, bridging risk, AOI settings, rework method, and inspection magnification. Body size and pin count remain separate variables. A buyer’s “same LQFP” note is therefore insufficient for engineering substitution.

For PLQP0176KB-A, Renesas lists LFQFP-176, 24 × 24 × 1.7 mm, and 0.5 mm pitch. Those dimensions—not the family nickname alone—belong in the package-compatibility review.

Primary sources: Renesas package-code structure, PLQP0176KB-A package page, and package search.

Document selector: choose the next verification step

This aid does not decode an unlisted part automatically. It tells an engineer or buyer which primary record should resolve the current uncertainty.

RFQ, substitution, and incoming-inspection controls

YURUNOX is an independent electronic-component sourcing partner, not the manufacturer of Renesas MCUs. Renesas datasheets, package drawings, lifecycle notices, and compliance records remain the technical authority. A sourcing review should connect that authority to the quote, supplier evidence, and received material.

Minimum RFQ record

• Complete manufacturer part number.Include every character and the # suffix; prohibit substitution by shortened base name.
• Functional configuration.State required code/data flash, RAM, security/peripheral set, temperature/application grade, and any automotive or quality qualification.
• Mechanical package.State type, lead count, body dimensions, height, pitch, and—where controlled—the full Renesas package code or drawing.
• Packing and quantity.State tray, embossed tape/reel, tube/magazine, full carton, MOQ, reel quantity, and acceptable split-lot policy.
• Lifecycle and change status.Request current manufacturer status and any PCN/PDN/PLP notice that changes the orderable code or packing.
• Traceability and condition.Request manufacturer label photographs, lot/date code, country information where required, sealed moisture barrier packaging, humidity indicator/desiccant condition, and storage history for opened or legacy material.
• Compliance and quality evidence.Match RoHS/material declarations and quality records to the exact orderable part, not only the device family.

Incoming inspection is a reconciliation task

Compare purchase order, outer label, inner label, reel or tray, device marking, quantity, lot/date rules, and package geometry as one chain. Photograph discrepancies before opening moisture-sensitive packaging. Confirm seal and indicator condition, then follow the approved bake/handling plan where exposure limits are exceeded.

A top mark can support identification, but it should be reconciled with Renesas marking guidance and trace documents. It should not be expanded into a full MPN by guesswork.

Learn more about YURUNOX’s quality-assurance approach, purchasing process, and Renesas sourcing page.