Technical specifications
- Manufacturer
- Arduino
- MCU / Part
- Renesas RA4M1
- Architecture
- Arm Cortex-M4
- Logic voltage
- 5 V
- Recommended input
- 6–24 V VIN / 5 V USB
- GPIO limits
- 5 V logic; observe per-pin and total current limits
- Flash
- 256 KB
- RAM
- 32 KB
- Clock
- 48 MHz
- ADC
- 6 inputs, up to 14-bit
- DAC
- 1 × 12-bit
- PWM / timers
- 6 PWM outputs
- Connectivity / buses
- UART, I²C, SPI, CAN
- Programmer
- USB bootloader / SWD tools
- Debugger
- SWD-compatible debugger
Pin reference
| Pin | Type | Main functions | Electrical note |
|---|
| D0/RX | Digital/UART | UART receive, GPIO | 5 V logic |
| D1/TX | Digital/UART | UART transmit, GPIO | 5 V logic |
| D3,D5,D6,D9,D10,D11 | Digital/PWM | PWM-capable GPIO | Observe current limits |
| A0–A5 | Analog | ADC inputs / GPIO | Up to 5 V board domain |
| DAC/A0 | Analog output | 12-bit DAC | Check configured range |
| SDA/SCL | I²C | Two-wire bus | External device voltage compatibility required |
| CANRX/CANTX | CAN logic | CAN peripheral pins | External transceiver required |
| 5V/3.3V/GND | Power | Supply rails and ground | Do not short rails |
Features and compatibility
RTC, HID, CAN, DAC, 5 V GPIO
Verify the exact board revision and manufacturer documentation before wiring. Never apply 5 V to a 3.3 V-only GPIO.
Open official datasheet/documentation ↗Deep reference
Architecture, electrical limits and engineering guidance
- Exact MCU / SoC
- Renesas RA4M1
- Maximum GPIO current
- 5 V logic; observe per-pin and total current limits
- EEPROM / NVM
- On-chip EEPROM is available; endurance and page-write limits apply.
- Interrupts / DMA
- GPIO/peripheral interrupts are available. DMA capability is device-specific; confirm channels, request mapping and memory-access restrictions in the reference manual.
- Sleep and power
- Use the light/deep/standby modes offered by the device. Measure board current because regulators, LEDs and USB interfaces can dominate MCU sleep current.
- Boot and programming
- Confirm boot-mode pins before reset. Use the official bootloader/programmer and retain a recoverable debug/programming header.
Special and restricted pins
Reset, clock, debug, USB, crystal and analogue-reference pins have special electrical or boot functions. Avoid loading them until the boot sequence is understood.
Boot-strapping warnings
Check BOOT/RESET/programming pin truth tables before assigning peripherals; keep required pull resistors fitted.
I/O voltage warnings
5 V domain. Never exceed VDD + permitted injection limits; level-shift incompatible modules and share ground only where safe.
Memory map and registers
Start with the memory map: code flash, SRAM, peripheral registers and system/control space. Use vendor headers instead of hard-coded addresses, then study GPIO direction/output/input, clock-enable, interrupt and timer registers.
Board-selection guidance
Choose this device only after checking logic voltage, required interfaces, memory margin, timers/ADC resolution, debugging access, package availability and long-term tool support.
Common faults and troubleshooting
Not detected: verify data USB cable, driver, boot mode and target power. Upload failure: select the exact target and programmer. Unstable operation: inspect supply ripple, reset, clock and watchdog cause. Wrong readings: check reference voltage, grounding, pin multiplexing and calibration.
Interview and viva questions
What is the difference between an absolute maximum and an operating limit?
Absolute maximum prevents damage; reliable design stays within recommended operating conditions.
Why must peripheral clocks be enabled?
Many MCUs gate clocks to save power; registers may not operate until the peripheral clock is enabled.
Why preserve a debug interface?
It enables programming, breakpoints, fault inspection and production recovery.
What causes GPIO damage?
Over-voltage, excess source/sink current, negative injection, ESD or driving against another output.
