Skip to content

EK‐RA8D1 Sample and Demo Hardware configuration

Jump to bottom
Duy Nguyen edited this page Jul 20, 2025 · 1 revision

Followings are hardware connection and test samples for EK-RA8D1, for more detail on 1st setup hardware connection, please visit EK-RA8D1 - Quick Start Guide and EK-RA8D1 v1 - User's Manual

Default HW configuration

Use Debug On-Board mode: EK-RA8D1 board require to configure the jumpers for serial communication with host.

Jumper configuration:

Jumper Configurations
J6 Open
J8 Jumper on pins 1-2
J9 Open
J29 Jumpers on pins 1-2, 3-4, 5-6, 7-8
EK_RA8D1_Debug_connection

Hardware connection for UART samples

  • echo_bot (samples/drivers/uart/echo_bot):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/uart/echo_bot/

  • zTest uart_basic_api (tests/drivers/uart/uart_basic_api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/uart/uart_basic_api/

  • zTest uart_async_api (tests/drivers/uart/uart_async_api):

    • Hardware configuration: Loopback for TXD and RXD

      Board Channel Pin function Pin Connect to
      EK-RA8D1 SCI2 TXD2_C PA03 Loopback to RXD2_C pin
      RXD2_C PA02 Loopback to RXD2_C pin

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/uart/uart_async_api/

Hardware connection for SPI samples

  • spi_bitbang (samples/drivers/spi_bitbang): Loopback for MISO and MOSI

  • Note: The purpose of testing sample spi_bitbang on RA boards is to provide users with an understanding of the RA SPI driver. To test this sample using the SPI hardware IP, you can configure it by adding the overlay and configuration files with the following content:

    samples/drivers/spi_bitbang/boards/ek_ra8d1.conf

    CONFIG_STDOUT_CONSOLE=y
CONFIG_SPI=y
CONFIG_SPI_B_INTERRUPT=y
CONFIG_SPI_B_RA_DTC=y
CONFIG_LOG=y
CONFIG_SPI_BITBANG=n

    • Note: We have to disable the CONFIG_SPI_BITBANG since we use SPI hardware IP to test spi_bitbang.

      samples/drivers/spi_bitbang/boards/ek_ra8d1.overlay

     spibb0: &spi1 {
   		rx-dtc;
   		tx-dtc;
   		pinctrl-0 = <&spi1_default>;
   		pinctrl-names = "default";
   		cs-gpios = <&ioport4 13 GPIO_ACTIVE_LOW>; // dummy config
   		status = "okay";
   	};

 &ioport4 {
   		status = "okay";
 };

    • Hardware configuration:

      Board Channel Pin function Pin Connect to
      EK-RA8D1 SPI1 MISOB_B P410 Loopback to MOSIB_B
      MOSIB_B P411 Loopback to MISOB_B

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/spi_bitbang

  • zTest spi_loopback (tests/drivers/spi/spi_loopback)

    • Hardware configuration: Loopback for MISO and MOSI

      Board Channel Pin function Pin Connect to
      EK-RA8D1 SPI1 MISOB_B P410 Loopback to MOSIB_B
      MOSIB_B P411 Loopback to MISOB_B

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/spi/spi_loopback

Hardware connection for I2C sample

  • zTest i2c_api (tests/drivers/i2c/i2c_api): Require GY-271 QMC5883L module

    • Hardware configuration:

      GY271 EK-RA8D1
      VCC P3V3
      GND GND
      SCL P512 (SCL1_A)
      SDA P511 (SDA1_A)
      DDBY -

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/i2c/i2c_api

Hardware connection for Flash samples

  • zTest flash common (tests/drivers/flash/common):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/flash/common

Hardware connection for Entropy samples

  • zTest entropy api (tests/drivers/entropy/api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/entropy/api

Hardware connection for can samples

  • zTest can api (tests/drivers/can/api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/can/api

  • zTest can timing (tests/drivers/can/timing):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/can/timing

  • zTest canbus conformance (tests/subsys/canbus/isotp/conformance):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/subsys/canbus/isotp/conformance

  • zTest canbus implementation (tests/subsys/canbus/isotp/implementation):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/subsys/canbus/isotp/implementation

Hardware connection for ospi samples

  • zTest spi_flash (samples/drivers/spi_flash):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/spi_flash

  • zTest jesd216 (samples/drivers/jesd216):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/jesd216

Hardware connection for SDHC samples

Require PMOD SD (https://digilent.com/reference/pmod/pmodsd/start)

Hardware configuration:

Board Channel Pin PMOD SD's Pin
EK-RA8D1 SDMMC1 P405 (DAT3) (J51 Pin8) Pin1 (CS)
P401 (CMD) (J51 Pin7) Pin2 (MOSI)
P402 (DAT0) (J52 Pin15) Pin3 (MISO)
P400 (CLK) (J51 Pin10) Pin4 (SCLK)
GND Pin5 (GND)
+3V3 (VCC) Pin6 (VCC)
P403 (DAT1) (J51 Pin9) Pin7 (DAT1)
P404 (DAT2) (J57 Pin1) Pin8 (DAT2)
P406 (CD) (J51 Pin5) Pin9 (CD)
P700 (WP) (J51 Pin6) Pin10 (WP)

Please aware that connect PMOD: use short wiring connections (should be shorter than 10cm).

  • zTest sdhc (tests/drivers/sdhc): Require "--shield pmod_sd" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield pmod_sd tests/drivers/sdhc

  • zTest sdmmc (tests/subsys/sd/sdmmc): Require "--shield pmod_sd" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield pmod_sd tests/subsys/sd/sdmmc

  • zTest disk_access (tests/drivers/disk/disk_access): Require "--shield pmod_sd" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield pmod_sd tests/drivers/disk/disk_access

  • zTest fs ext2 (tests/subsys/fs/ext2): Require "--shield pmod_sd" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield pmod_sd tests/subsys/fs/ext2

  • zTest fs_sample (samples/subsys/fs/fs_sample): Require "--shield pmod_sd" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield pmod_sd samples/subsys/fs/fs_sample

Hardware connection for ADC samples

  • zTest adc_api (tests/drivers/adc/adc_api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/adc/adc_api

  • zTest adc_accuracy_test (tests/drivers/adc/adc_accuracy_test):

    • Hardware configuration: Loopback 3V3 and AN000 (P004).

      ADC_HW_Connection

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/adc/adc_accuracy_test

Hardware connection for PWM (GPT) samples

  • zTest pwm_api (tests/drivers/pwm/pwm_api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/pwm/pwm_api

  • zTest pwm_loopback (tests/drivers/pwm/pwm_loopback):

    • Hardware configuration: Loopback 2 channels (1 PWM output, 1 PMW capture)

      Board Channel Pin Pin function Remark
      EK-RA8D1 PWM7 PA07 GTIOC7A PWM output, loopback to PWM capture pin
      PWM9 P411 GTIOC9A PWM capture, loopback to PWM output pin

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/pwm/pwm_loopback

Hardware connection for Counter (AGT) samples

  • Counter Alarm sample (samples/drivers/counter/alarm):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/counter/alarm`

Hardware connection for USB samples

  • USB Device

    • USB-FS as device: Connect J11 to a host PC.

      • Hardware configuration:

        Board Jumper Configurations
        EK-RA8D1 J12 pins 2-3
        J15 Closed

    • USB-HS as device: Connect J31 to a host PC

      • Hardware configuration:

        Board Jumper Configurations
        EK-RA8D1 J7 pins 2-3
        J17 Closed

    • USB Mass Storage (samples/subsys/usb/mass):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/subsys/usb/mass -DCONF_FILE=usbd_next_prj.conf -DDTC_OVERLAY_FILE=ramdisk.overlay

    • USB CDC-ACM (samples/subsys/usb/cdc_acm):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/subsys/usb/cdc_acm -DCONF_FILE=usbd_next_prj.conf

  • zTest udc (tests/drivers/udc):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/udc

  • USB Host

    • USB-HS as host: Connect J31 to OTG cable (Micro to USB Host (Female)), connect the other end of OTG cable to a USB device

      • Hardware configuration:

        Board Jumper Configurations
        EK-RA8D1 J7 pins 1-2
        J17 Open

      • Set the configuration switches (SW1) on the EK-RA8D1 board as below:

        SW1-1 PMOD1 SW1-2 TRACE SW1-3 CAMERA SW1-4 ETHA SW1-5 ETHB SW1-6 GLCD SW1-7 SDRAM SW1-8 I3C
        OFF OFF OFF OFF OFF OFF OFF OFF

    • USB shell (samples/subsys/usb/shell):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/subsys/usb/shell -DCONF_FILE=device_and_host_prj.conf

    • Known issue of USB-HS as host: The USB-HS host cannot work correctly with USB-HS device due to USB Voltage dropping.

      • Confirmed USB-HS host can work correctly with USB-HS device after remove R83 and R84 resistors. Find R83 & R84 resistors at EK-RA8D1 v1 - Design Package

      • USB-HS host can work correctly with USB Full Speed/Low Speed device.

Hardware connection for MIPI-DSI samples

Connect the MIPI Graphics Expansion Board (included in the kit) to J58 of EK-RA8D1.

  • Set the configuration switches (SW1) on the EK-RA8D1 board as below:
SW1-1 PMOD1 SW1-2 TRACE SW1-3 CAMERA SW1-4 ETHA SW1-5 ETHB SW1-6 GLCD SW1-7 SDRAM SW1-8 I3C
OFF OFF OFF OFF OFF OFF ON OFF

  • ztest display_read_write (tests/drivers/display/display_read_write): Require "--shield rtkmipilcdb00000be" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield rtkmipilcdb00000be tests/drivers/display/display_read_write

  • LVGL basic sample (samples/subsys/display/lvgl): Require "--shield rtkmipilcdb00000be" in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 --shield rtkmipilcdb00000be samples/subsys/display/lvgl

  • LVGL demos (samples/modules/lvgl/demos):Require information of display shield in build command

    • Hardware configuration: No additional connection.

    • Build command:

      west build -b ek_ra8d1 samples/modules/lvgl/demos/ -T sample.modules.lvgl.demos.rtkmipilcdb00000be -p

Hardware connection for DAC samples

  • ztest dac_api (tests/drivers/dac/dac_api):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 tests/drivers/dac/dac_api

  • DAC sample (samples/drivers/dac):

    • Hardware configuration: No additional connection.

    • Build command:

      west build -p always -b ek_ra8d1 samples/drivers/dac

Home

Getting started guide

Supported MCU/MPU family

Samples and Demo Hardware Configuration Reference

RA Sample and Demo Hardware configuration
RX Sample and Demo Hardware configuration
RZ Sample and Demo Hardware configuration
Clone this wiki locally