Apply to Test the Arduino Nano R4!

View table of contents ...  

In this RoadTest, testers will explore the Arduino Nano R4, a compact development board featuring the Renesas RA4M1 Arm® Cortex‑M4 microcontroller, USB‑C connectivity, CAN bus support, and expanded analog capabilities including 14-bit ADC and 12-bit DAC. Testers will be able to experiment with the board’s I²C/Qwiic, SPI, UART, and CAN interfaces, as well as its real-time clock for time-based applications.

What’s the Nano R4?

The Arduino Nano R4 is a compact, production-ready board built around the Renesas RA4M1 microcontroller,  a 48 MHz Arm® Cortex‑M4 core with 256 kB Flash, 32 kB SRAM and 8 kB EEPROM. It retains the familiar Nano form factor (≈ 18 mm × 45 mm) and the same pinout as previous Nanos, while adding modern features such as a USB‑C programming port, CAN bus support, and a Qwiic I²C connector.

Why This May be Interesting To You:

  • From prototype to production: Its castellated‑pin, single‑sided design makes it ideal for tight board layouts or embedding into custom carrier boards.

  • Flexible connectivity: Built‑in Qwiic connector supports easy connection to sensors and modules; it also supports I²C, SPI, UART, CAN.

  • Analogue capabilities: Features a 14‑bit ADC, 12‑bit DAC, and built-in operational amplifier for signal conditioning.

  • Real‑time applications: Onboard real‑time clock (RTC) to support timekeeping and alarm events.

  • 5 V compatibility: The board operates at 5 V, making it compatible with legacy Nano shields and hardware.

  • Compact & robust form: Excellent for space-constrained embedded projects or industrial use.

Key Specifications

Parameter Value
Microcontroller Renesas RA4M1 (Arm Cortex‑M4)
CPU Speed 48 MHz 
Flash 256 kB
SRAM 32 kB
EEPROM 8 kB
GPIO / I/O 21 exposed digital I/O, 8 analog inputs, 6 PWM
USB USB-C for programming & power
Power input 6–21 V via VIN, 5 V via USB-C
Operating Voltage 5 V
Real‑Time Clock Yes, with external crystal
ADC 14-bit (8 channels)
DAC 12-bit (1 channel) 
OpAmp Yes, built-in
Communications I²C (including Qwiic), SPI, UART, CAN (requires external transceiver) 
Dimensions 18 mm × 45 mm
Operating Temp –40 °C to +85 °C
Certifications CE, FCC, UKCA, RoHS, REACH, etc.

Possible Applications

Here are some scenarios where the Nano R4 could shine, and which would be compelling to test:

  • Industrial automation: Use the board to control sensors, actuators or monitor systems in an industrial environment, leveraging CAN communication for networked devices.

  • Compact robotics: Its small form factor and real-time clock make it suitable for micro-robots, drones, or automation where size and timing matter.

  • IoT edge devices: Combine its low power footprint with I²C connectability (via Qwiic) to build connected sensor nodes.

  • Prototyping to production: Use the same firmware and board architecture when scaling your prototype to a product by embedding the Nano R4 into custom hardware.

  • Audio / signal processing: With its DAC and op‑amp, it's a good fit for simple audio generation or analog signal processing tasks.

  • Time-based systems: The built-in RTC is useful for applications that need scheduling, logging, or timed triggering.

What You’d Need to Try It

To fully evaluate the Nano R4, you might want to bring:

  • A USB‑C cable and power supply

  • External CAN transceiver if testing CAN

  • Qwiic-compatible sensors/modules for I²C experimentation

  • A carrier board or perf‑board if embedding into a custom design

  • Tools for debugging (e.g. logic analyser, multimeter)

  • Software: Arduino IDE or relevant toolchain compatible with RA4M1

If you don't have these parts available, but you're considering applying, let us know in your application and we may be able to supply them if they're available on the Farnell, element14 or Newark stores.

What You Will Be Testing with Suggested RoadTester Tasks and Instructions

You may want to do any of the below to inspire you on how to put this hardware through its paces:

  • Unbox and verify: Power the Nano R4, confirm USB-C programming connectivity, and upload a basic blink example. Record firmware upload steps and any driver/tool issues.

  • Power & thermal test: Measure current draw at idle and under a sustained workload (e.g., ADC sampling + UART logging). Note voltages, temperatures, and any stability issues.

  • Analog tests: Capture ADC readings with known input voltages to assess resolution and noise. Output test waveforms with the DAC and measure with an oscilloscope. Document results.

  • Connectivity checks:

    • Connect Qwiic/I²C sensors and confirm detection and data reads.

    • Test SPI and UART communication with a peripheral device.

    • Validate CAN communication using an external CAN transceiver and another CAN node; log message throughput and error behavior.

  • RTC & scheduling: Use the RTC for scheduled data sampling and verify timekeeping over a multi-hour period. Log drift if observed.

  • Integration test: Solder or mount the Nano R4 onto a simple carrier or perf-board, demonstrate how it fits and interfaces with external power and sensors. Note mechanical and soldering considerations.

  • Toolchain & libraries: Note which libraries required changes (if any), any compilation issues, and the overall user experience in Arduino IDE or alternative toolchain. Provide commands, screenshots, or steps that reproduce issues.

  • Create a project example: Build a small project (suggested: sensor logger with timestamped entries sent over UART or logged to an SD module) and provide source code, wiring diagram, and a short walkthrough.

  • The 'out of the box' experience, from setup to running your first example

  • Using the Arduino Development Environments to program and code for the controller

  • Your experience integrating it with sensors, circuitry and peripheral components and devices and protocols

  • Report: Submit a RoadTest Review covering setup steps, measured data, code examples, photos of the test setup, and clear recommendations for prospective users

When Applying

When live, click the button to enrol, you'll be expected to include:

  1. A brief description of your background and experience (especially with embedded systems / Arduino / Arm MCUs and programming)

  2. What specific project or test you plan to build using the Nano R4

  3. What you want to evaluate: performance, form‑factor integration, communication features (e.g. CAN), power consumption, or development workflow

Important Dates

Begin enrollment

November 28 2025

End enrollment

January 11 2026

Select RoadTesters

Within two weeks of enrollment end

Ship unit

Week during/after RoadTester selection

Begin RoadTesting

On Receipt of Kit

element14 followup

6 weeks after Selection

Post reviews by

2 to 3 month after Kit Receipt

About the Sponsor

Arduino is a company that develops open-source hardware and software designed to make embedded electronics accessible for engineers, educators, and makers, offering a wide range of microcontroller boards, development tools, and a global ecosystem that supports rapid prototyping and product development. For more information click here.

RoadTest Reviews
Comment List
Anonymous
  • Deadline for entering was extended, so selection is also delayed.

  • guys anyone here,the term and condition says that final roadtesters may be announced today but this web says that its uptill 11 jan for enrolment

  • thanks for verifying - on the image above there is a resonator and current schematics seem to include one, but things happen and UNO R4 Minima has one crossed out (as mentioned)

  • Just checked my Nano R4: the crystal is on the board.

  • I check it further. Maybe their intention is to use it for trimming. It seems that they want to clock RTC by LOCO (which is the 15% tolerance as mentioned on Arduino Forums), but when measured by main faster clock and user trimming is in place. I checked MCU datasheet and reference manual. MCU supports it. It is likely going to shift tolerance to acceptable range, despite it will be still far from about 30ppm of typical 32.768kHz crystals, but at least somehow usable.

  • I think they screw up once more. While they claim that they added external 16MHz crystal for RTC, I think they did it incorrectly. Also note that they mark added crystal as DNP in schematics, so I am still not sure if it is even present on board but at least there should be space for it. But even if they assemble it actually, I still think they did it incorrectly, because for RTC you need low speed 32.678kHz crystal, not high speed crystal. From Arduino schematics:

    image

    I think they should connect crystal to pins 6, 7, not to 9, 10 and it should be 32.768kHz, not 16 MHz.

    I am curious if they somehow hacked it in software using alternate or soft timers (SW patch for HW problem) or how is it intended to work, because according to RA4M1 datasheet (Figure 8.1 Clock generation circuit block diagram), there is no way from high speed (XTAL/EXTAL) to the RTC clock. Only from XCIN/XCOUT.

    It is one point I want to focus as part of "low power evaluation" which I promissed in my RoadTest application. If selected, of course.

  • The teams that advertise the RoadTest may look at those kind of ratios or metrics, I personally look through the applicants and decide if we've found someone suitable (and has the time) to do the RoadTest.

    We've had RoadTests where there have only been 3 applicants before, but they happened to be suitable.

    A high number of applicants usually suggests that spam bots may have gotten hold of it.

  • Thanks for pointing that out. I didnt notice that specific point.  Since Nano R4 features a real time clock, the accuracy is important. 

  • Out of curiosity, in general, is there a target for the ratio of road tester units to applicants, or total # of applicants ?