
Renesas Microcontrollers, Automotive, Power, and Embedded Solutions.
YURUNOX helps engineering and procurement teams connect industrial control, low-power embedded, automotive, connectivity, HMI, and power requirements with suitable Renesas product families, then review the exact ordering code, memory, package, lifecycle, supply condition, evidence, and delivery terms.

Review CPU, memory, real-time behavior, timers, analog, communications, security, software, and package.
Match active current, low-power modes, wake sources, peripherals, voltage, memory, and system duty cycle.
Confirm function, safety and security context, networks, memory, timing, temperature, qualification, and lifecycle.
Review regulation, charging, sensing, drivers, power devices, clocks, interfaces, protection, and thermal design.
Choose the Renesas Product Direction by What the Embedded System Must Control.
The suitable device depends on CPU performance, memory, real-time behavior, analog and timer peripherals, communications, HMI, security, safety context, power target, package, software ecosystem, qualification, and lifecycle.
Need a Scalable 32-Bit MCU for Connected Control?
Review CPU architecture, frequency, flash and RAM, analog, timers, motor-control needs, Ethernet or USB, wireless, security, RTOS, middleware, toolchain, package, and lifecycle.
Need Compact Control With Low Active and Standby Power?
Define duty cycle, active current, standby mode, wake sources, clock, flash, RAM, timers, ADC, display, communications, voltage, pin count, package, and production life.
Need an MCU for Body, Chassis, Powertrain, or Vehicle Networks?
Confirm ECU function, real-time load, memory, timers, CAN or LIN, safety and security context, diagnostic needs, temperature, package, qualification, software, documentation, and lifecycle.
Need a Linux-Capable MPU, Power Stage, Charger, or Connectivity Function?
Review OS and graphics, memory interfaces, networking, startup, security, input and output rails, current, charging profile, driver or switch function, thermal path, package, and protection.
Move From an Embedded Requirement to a Reviewable Renesas Part.
Use the family that matches the control and system requirement, then confirm the exact ordering code, CPU, memory, peripherals, package, temperature range, qualification, lifecycle, software, quantity, and supply condition.
RA Arm Cortex-M MCUs
Scalable 32-bit MCU direction for general embedded, security, connectivity, IoT, motor control, HMI, and intelligent edge applications.
Review an RA RequirementRX 32-Bit MCUs
Renesas-core performance and efficiency direction for industrial control, motor drives, automation, appliances, connectivity, and established production platforms.
View RX ProductsRL78 Low-Power MCUs
Energy-efficient 8- and 16-bit MCU direction for compact controls, appliances, metering, LCD, sensors, lighting, battery, and cost-sensitive designs.
View RL78 ProductRH850 Automotive MCUs
Advanced 32-bit automotive MCU direction for body, chassis, gateway, powertrain, electrification, safety, and vehicle-network control.
View RH850 ProductsRZ 32- and 64-Bit MPUs
Linux and RTOS-capable processing direction for HMI, vision, industrial networking, graphics, gateway, edge intelligence, and connected equipment.
Review an MPU RequirementAnalog and Power
Battery management, regulators, power modules, drivers, amplifiers, data converters, timing, interface, protection, and discrete power directions.
View Power ProductsConnectivity and Timing
Wireless, Ethernet, USB, serial interfaces, clocks, timing, memory-interface, isolation, and system connectivity products selected around the MCU or MPU.
Explore ApplicationsLifecycle and Migration Review
Exact ordering code, memory, package, grade, mask or revision context, lifecycle, software compatibility, documentation, and approved-alternate authority.
Review Supply EvidenceFind the Renesas Family Direction That Matches Your Embedded Function.
Choose the application and primary function first. The result provides a starting family direction and the performance, memory, peripheral, software, package, lifecycle, and purchasing information required for a useful RFQ.
Select the Application and Primary Embedded Function.
Start with what the system must control, process, communicate, display, or power. The exact part can then be narrowed by CPU, memory, peripherals, software, package, temperature, qualification, lifecycle, and supply requirements.
The result is an initial family direction, not a substitute for system architecture, software compatibility, circuit design, prototype validation, safety, cybersecurity, compliance, or engineering approval.
Renesas RX Performance and Efficiency MCU Direction
Begin with real-time workload, frequency, flash, RAM, timers, analog, motor-control peripherals, Ethernet, USB, CAN, security, toolchain, package, temperature, and lifecycle.
Compare Renesas Product Directions Before Reviewing the Exact Ordering Code.
This comparison connects industrial, low-power, automotive, power-management, legacy-control, and ignition needs with the provided Renesas product examples.
| Product | Family / Category | Primary Direction | Package / Status Context | Key Selection Checks | Product Page |
|---|---|---|---|---|---|
| R5F564MLCDFC#V1 | RX64M MCU | High-performance industrial control, communications, and established RX platforms. | 176-lead LFQFP; legacy lifecycle review | CPU load, flash, RAM, Ethernet, USB, CAN, timers, analog, package, software, and migration plan. | View R5F564MLCDFC#V1 |
| R7F7010233AFP#AA2 | RH850 Automotive MCU | Automotive body-control and networked ECU direction within the RH850/F1L context. | Automotive MCU ordering option | Exact RH850 derivative, memory, timers, CAN or LIN, package, temperature, safety context, security, software, and qualification. | View R7F7010233AFP#AA2 |
| R5F100LEAFB#V0 | RL78/G13 MCU | Low-power compact control for appliances, sensors, metering, and general embedded equipment. | 64-lead LQFP ordering option | Flash, RAM, timers, ADC, serial interfaces, voltage, low-power modes, package, software, and lifecycle. | View R5F100LEAFB#V0 |
| ISL6259HRTZ-T | Battery Charger Controller | Notebook, portable, and embedded battery-charging power-path direction. | TQFN tape-and-reel option | Battery configuration, adapter input, charge current and voltage, power-path behavior, external FETs, thermal design, package, and lifecycle. | View ISL6259HRTZ-T |
| R5F5631ECDFM#V0 | RX631 MCU | Industrial real-time control, connectivity, security, and established equipment platforms. | 100-lead LQFP ordering option | Flash, RAM, timers, ADC, communications, security, package, temperature, toolchain, firmware, and lifecycle. | View R5F5631ECDFM#V0 |
| R5F21346CNFP#V0 | R8C/34C MCU | Legacy embedded-control and maintenance direction for released boards. | Legacy LQFP ordering option | Exact suffix, pinout, memory, peripherals, supply, package, firmware, lifecycle, available evidence, and alternate authority. | View R5F21346CNFP#V0 |
| R7F7010033AFP#AA2 | RH850 Automotive MCU | Automotive body, gateway, and vehicle-network control direction. | Automotive MCU ordering option | Exact derivative, real-time load, memory, CAN or LIN, safety and security context, package, temperature, software, and qualification. | View R7F7010033AFP#AA2 |
| ISL9V3040S3ST | Ignition IGBT | Automotive ignition switching and clamped inductive-load direction. | TO-263 power-device option | Clamp voltage, current, energy, gate drive, switching, thermal path, package, qualification, protection, and ECU validation. | View ISL9V3040S3ST |
Use this table for initial direction only. Confirm the complete ordering code, CPU or device attributes, package, grade, qualification, lifecycle, hardware revision, software compatibility, supporting circuit, current Renesas documentation, and prototype results before design or purchasing approval.
Connect Renesas Embedded Platforms to the Control Job Your Product Must Perform.
Renesas MCU, MPU, automotive, analog, power, connectivity, and timing families address different workload, real-time, energy, interface, safety, security, environmental, software, and lifecycle needs. Final selection must be validated against the complete system specification.
Real-Time Control and Factory Connectivity
Coordinate CPU load, deterministic timing, motor and inverter control, analog measurement, industrial Ethernet or fieldbus, HMI, diagnostics, security, software, and lifecycle.
Body, Chassis, Powertrain, and Gateway Control
Match the ECU function to memory, timers, CAN or LIN, diagnostics, safety and security context, temperature, package, qualification, software, documentation, and production life.
Motor Drives, Power Conversion, and Energy Control
Review PWM, timers, ADC timing, position feedback, control algorithms, communications, gate drivers, power stages, sensing, protection, thermal path, and operating environment.
Efficient Control for Connected Everyday Products
Balance low power, display or touch, sensing, motor control, wireless connectivity, safety functions, memory, pin count, package, cost target, and production continuity.
Secure Sensing, Control, and Cloud Connectivity
Define edge workload, low-power behavior, security, wireless or Ethernet, sensors, local control, cloud connection, update strategy, RTOS, memory, interfaces, and lifecycle.
Linux, Graphics, Networking, and Intelligent Processing
Review MPU performance, graphics and display, memory interfaces, networking, camera or audio, AI workload, startup, security, Linux or RTOS support, thermal design, and longevity.
Use a Different Renesas Review Path for Development, Production, Shortages, and Legacy Designs.
A development-board need, released firmware platform, shortage request, and legacy repair carry different risks. Define the exact ordering code, software baseline, approval authority, and evidence requirement before comparing offers.
Prototype, Evaluation, and Platform Choice
Confirm the target application, evaluation board or production device, software package, debugger, quantity, package, development schedule, production forecast, and migration expectations.
Released Hardware and Firmware Supply
Align the complete MPN, memory, package, grade, qualification, mask or revision requirements, firmware baseline, lifecycle, forecast, packing, evidence, terms, and delivery timing.
Hard-to-Find Renesas Part Review
Review the actual offered quantity, source basis, condition, labels, packing, date or lot information, traceability, inspection scope, split delivery, validity, payment, freight, and exceptions.
Legacy Device and Alternate Path
Compare pinout, memory map, peripherals, electrical limits, package, toolchain, firmware, qualification, lifecycle and PCN or PDN context, prototype validation, and customer approval authority.
Connect the Embedded Workload to the Complete Renesas Ordering Specification.
A suitable family is only the start. Before procurement, confirm the complete ordering code, CPU, memory, peripherals, package, grade, temperature, qualification, software compatibility, lifecycle, quantity, source condition, evidence, and delivery timing.
CPU, memory, TrustZone or security needs, analog, timers, connectivity, software package, toolchain, package, and lifecycle.
Real-time load, flash and RAM, motor or timer functions, Ethernet, USB, CAN, analog, toolchain, firmware, package, and production life.
Duty cycle, power modes, wake sources, flash, RAM, timers, ADC, display, voltage, pin count, package, and cost target.
ECU role, memory, timers, CAN or LIN, safety and security context, diagnostics, temperature, package, qualification, and software.
CPU and accelerator workload, graphics, display, memory, Ethernet, camera or audio, Linux or RTOS, startup, security, and thermal path.
Search the Exact Renesas MPN, Then Review the Platform and Supply.
Use the search field for a complete ordering code, family, or application keyword. Product pages support discovery; current availability, suffix, memory, package, condition, quantity, evidence, terms, and lead time must be reconfirmed for each RFQ.

R5F564MLCDFC#V1
RX64M 32-bit MCU direction for established industrial control and connected equipment. Confirm the 176-lead LFQFP code, firmware baseline, lifecycle, and approved migration path.
View R5F564MLCDFC#V1
R7F7010233AFP#AA2
RH850 automotive-control direction for body electronics and networked ECUs. Confirm the exact derivative, memory, peripherals, package, qualification, software, and safety context.
View R7F7010233AFP#AA2
R5F100LEAFB#V0
RL78/G13 low-power MCU direction for compact industrial, appliance, metering, sensor, and general embedded control. Confirm memory, peripherals, voltage, package, and software.
View R5F100LEAFB#V0
ISL6259HRTZ-T
Battery-charging and power-path control direction for portable and embedded equipment. Confirm battery configuration, adapter range, charge targets, external power stage, thermal design, and package.
View ISL6259HRTZ-T
R5F5631ECDFM#V0
RX631 real-time control direction for industrial equipment and established connected platforms. Confirm flash, RAM, timers, analog, communications, security, package, toolchain, and firmware.
View R5F5631ECDFM#V0
R5F21346CNFP#V0
R8C legacy-control direction for maintenance of released embedded boards. Confirm the exact suffix, pinout, memory, peripherals, firmware, lifecycle, supply evidence, and alternate authority.
View R5F21346CNFP#V0
R7F7010033AFP#AA2
RH850 automotive embedded-control direction for body, gateway, and vehicle-network functions. Validate the exact derivative, memory, peripherals, qualification, package, and software baseline.
View R7F7010033AFP#AA2
ISL9V3040S3ST
Automotive ignition-switching power-device direction. Confirm clamp behavior, current and energy requirements, gate drive, switching, thermal path, package, qualification, and ECU validation.
View ISL9V3040S3STCannot find the Renesas part number? Send the complete MPN or family, required function, memory, package or grade, quantity, application, firmware or software context, target date, destination, approved alternatives, and required evidence.

Confirm the Exact Renesas Ordering Code, Platform Fit, and Evidence Before Shipment.
Selecting an MCU, MPU, or power family does not confirm the condition of an actual offer. YURUNOX aligns the quoted Renesas part with the complete code, memory and package context, lifecycle, source basis, quantity, commercial terms, and agreed evidence.
Manufacturer, complete MPN, suffix, memory, package, temperature or qualification context, quantity, labels, packing, and available traceability.
Current lifecycle information, datasheet and hardware context, available PCN or PDN records, toolchain or firmware compatibility, and customer alternate authority.
Packaging and label photos, visual or microscopic condition, marking review, X-ray, electrical or other suitable checks when available and agreed.
Offered quantity, price basis, validity, lead time, payment, freight, date or lot information, exceptions, destination, and receiving requirements.
Turn a Part-Number Request Into a Reviewable Purchase Decision.
A complete RFQ makes technical, quality, commercial, and delivery expectations visible before the order moves forward.
Released Industrial Controller Requires R5F564MLCDFC#V1
The buyer needs the exact 176-lead LFQFP ordering code for a released RX64M platform. Because lifecycle and firmware compatibility matter, another device cannot be accepted without engineering review and validation.
Align the Released Platform
Confirm application, exact MPN, memory and package, hardware revision, firmware and toolchain, qualification, lifecycle, quantity, required date, and alternate authority.
Review the Offered Supply
Record source basis, offered quantity, condition, packing, available date or lot information, lead time, price basis, validity, and exceptions.
Agree the Evidence
Define label, packaging, visual, microscopic, marking, X-ray, electrical, documentation, or other requirements when suitable and agreed.
Approve Release and Delivery
Review evidence, exceptions, commercial terms, shipping documents, protective packaging, carrier handoff, destination, and tracking.
Renesas Component Sourcing FAQ.
Use these answers to prepare a clearer Renesas ordering-code search, MCU or MPU selection review, shortage request, legacy-device review, or BOM quotation.
Can YURUNOX source an exact Renesas ordering code?
Send the complete MPN including every suffix, required quantity, target date, destination, memory and package requirements, temperature or qualification context, packing preference, and any date-code, lot, traceability, inspection, or documentation requirements. Availability and terms are confirmed for the actual RFQ.
What information is needed for a Renesas MCU or MPU selection review?
Provide the application, workload, real-time behavior, CPU architecture, flash and RAM, timers, analog, communications, graphics, security, safety context, power target, software environment, package, temperature, qualification, lifecycle, and production quantity.
How do RA, RX, RL78, RH850, and RZ directions differ?
RA provides an Arm Cortex-M MCU direction, RX targets efficient high-performance embedded control, RL78 emphasizes compact low-power control, RH850 addresses automotive MCU functions, and RZ supports higher-level MPU, Linux, HMI, networking, and edge-processing needs. The exact family and device depend on the complete system.
How do I avoid ordering the wrong suffix or package?
Use the complete ordering code from the approved BOM or current manufacturer documentation. Confirm package, packing method, temperature or performance grade, lead finish, qualification, revision, and lifecycle rather than matching only the base family name.
What happens if the requested Renesas component is unavailable or obsolete?
The review can separate split quantity, revised timing, another packing option, available legacy supply, an approved migration device, or a technical alternate path. No replacement is treated as approved until the customer completes the required hardware, firmware, prototype, compliance, and purchasing review.
Can I submit a BOM containing R5, R7, ISL, and other Renesas codes?
Yes. Include the manufacturer, complete MPN, quantity, target date, destination, approved alternatives, application and software notes, package or qualification context, and required evidence for each line. The quotation can then show line-specific availability, exceptions, and terms.
What quality evidence can be requested before shipment?
Depending on the part, supply condition, quantity, risk, samples, equipment, available records, and agreed scope, evidence may include packaging and label photos, visual or microscopic inspection, marking review, X-ray, electrical checks, and supporting documents.
Are price and inventory shown on this page current?
No fixed inventory or price is represented by this page. Current quantity, price basis, validity, lead time, source condition, packing, date or lot information, evidence, freight, payment, and exceptions are confirmed for each quotation.
Have a Renesas Part Number, BOM, or Embedded-Control Requirement?
Send the system function, technical limits, preferred MPN or BOM, memory, package or qualification context, software baseline, quantity, target date, destination, approved alternatives, and evidence requirements for an order-specific review.
