EK‐RA6M5 Sample and Demo Hardware configuration

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

Default HW configuration:

Zephyr UART Console setting: EK-RA6M5 board require to connect with a USB UART board to communicate with PC console

e.g. PMOD USB UART

Pin configuration:

Board	Channel	Board Pin function	Board Pin	Connect to PMOD 2
EK-RA6M5	SCI0	TXD0	P411 (PMOD 2-2)	USB UART RXD pin
		RXD0	P410 (PMOD 2-3)	USB UART TXD pin
		GND	GND	USB UART GND pin
		P3.3V	VCC	USB UART VCC pin

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_ra6m5 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_ra6m5 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-RA6M5	SCI7	TXD7	P613	Loopback to RXD9 pin
    		RXD7	P614	Loopback to RXD9 pin

  • Build command:

    west build -p always -b ek_ra6m5 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_ra6m5.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_ra6m5.overlay

   spibb0: &spi0 {
     		rx-dtc;
     		tx-dtc;
     		pinctrl-0 = <&spi0_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-RA6M5	SPI0	MISO0	P202	Loopback to MOSI0
    		MOSI0	P203	Loopback to MISO0

  • Build command:

    west build -p always -b ek_ra6m5 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-RA6M5	SPI0	MISO0	P202	Loopback to MOSI0
    		MOSI0	P203	Loopback to MISO0

  • Build command:

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

Hardware connection for I2C sample

• zTest i2c_api (tests/drivers/i2c/i2c_api):

  • Hardware configuration: Require GY-271 QMC5883L module

    Board	Channel	Pin function	Pin	Connect to GY-271 QMC5883L module
    EK-RA6M5	RIIC1	SCL1	P512	SCL
    		SDA1	P511	SDA
    		P3V3	P3V3	VCC
    		GND	GND	GND
    		-	-	DDBY

  • Build command:

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

Hardware connection for Flash samples

• zTest flash common (tests/drivers/flash/common): No additional connection.

  • Hardware configuration: No additional connection.

  • Build command:

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

Hardware connection for ADC samples

• zTest adc_api (tests/drivers/adc/adc_api): No additional connection.

  • Hardware configuration: No additional connection.

  • Build command:

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

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

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

  • Build command:

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

Hardware connection for PWM (GPT) samples

• zTest pwm_api (tests/drivers/pwm/pwm_api): No additional connection.

  • Hardware configuration: No additional connection.

  • Build command:

    west build -p always -b ek_ra6m5 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-RA6M5	PWM1	P405	GTIOC1A	PWM output, loopback to PWM capture pin
    	PWM4	P302	GTIOC4A	PWM capture, loopback to PWM output pin

  • Build command:

    west build -p always -b ek_ra6m5 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_ra6m5 samples/drivers/counter/alarm`
    

Hardware connection for USB samples

• USB HS Device:

  • Hardware configuration: For a USB Device configuration, set Jumper J7 to pins 2-3, install a jumper on J17 pins 1-2, connect USB HS Port (J31) to a host PC.
  • Build command

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

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

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

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

    • ztest udc (tests/drivers/udc):

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

• USB FS Device:

  • Hardware configuration: For a USB Device configuration, set jumper J12 to pins 2-3, install a jumper on J15 pins 1-2, connect USB FS Port (J11) to a host PC.
  • Build command

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

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

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

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

    • ztest udc (tests/drivers/udc):

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

Note: You need to replace the the USB HS node in zephyr/boards/renesas/ek_ra6m5/ek_ra6m5.dts with below define for USB FS

&usbfs {
	pinctrl-0 = <&usbfs_default>;
	pinctrl-names = "default";
	maximum-speed = "full-speed";
	status = "okay";
	zephyr_udc0: udc {
		compatible = "renesas,ra-udc";
		status = "okay";
		cdc_acm_uart0 {
			compatible = "zephyr,cdc-acm-uart";
		};
	};
};

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_ra6m5 tests/drivers/dac/dac_api

• DAC sample (samples/drivers/dac):

  • Hardware configuration: No additional connection.
  • Build command: west build -p always -b ek_ra6m5 samples/drivers/dac

Hardware connection for DHCPv4 client samples

• Note: In RA6M5, Ethernet buffers do have to be allocated in a non-secure region. It requires reconfiguring Trustzone memory boundary during flash process for ethernet normal working. Renesas Flash partition (RFP) tool will be used for this reconfigure. Please refer to Renesas Flash Programmer Download to download and install RFP tool before flash image.

• Ethernet with RFP tool support is in PR: https://github.com/zephyrproject-rtos/zephyr/pull/88568

• DHCPv4 client (samples/net/dhcpv4_client)

  • Hardware configuration: Connect ethernet port (J5) to DHCPv4 server (ex. Linux host machine)

  • Build command:

    west build -b ek_ra6m5 samples/net/dhcpv4_client -p
    

  • Flash command with RFP:

    west flash -r rfp