EK‐RA6M2 Sample and demo Hardware configuration - renesas/zephyr GitHub Wiki

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

Default HW configuration:

Zephyr UART Console setting: EK-RA6M2 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 B
EK-RA6M2 SCI7 TXD7 P401 (PMOD B) USB UART RXD pin
RXD7 P402 (PMOD B) USB UART TXD pin

image

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_ra6m2 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_ra6m2 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-RA6M2 SCI9 TXD9 P203 Loopback to RXD9 pin
      RXD9 P202 Loopback to RXD9 pin

    • Build command:

      west build -p always -b ek_ra6m2 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_ra6m2.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_ra6m2.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-RA6M2 SPI0 MISO0 P410 Loopback to MOSI0
      MOSI0 P411 Loopback to MISO0

    • Build command:

      west build -p always -b ek_ra6m2 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-RA6M2 SPI0 MISO0 P410 Loopback to MOSI0
      MOSI0 P411 Loopback to MISO0

    • Build command:

      west build -p always -b ek_ra6m2 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-RA6M2 RIIC2 SCL2 P512 SCL
      SDA2 P511 SDA
      P3V3 P3V3 VCC
      GND GND GND
      - - DDBY

    • Build command:

      west build -p always -b ek_ra6m2 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_ra6m2 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_ra6m2 tests/drivers/adc/adc_api

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

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

      ADC_HW_Connection

    • Build command:

      west build -p always -b ek_ra6m2 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_ra6m2 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-RA6M2 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_ra6m2 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_ra6m2 samples/drivers/counter/alarm`

Hardware connection for USB samples

  • USB FS Device:

    • Hardware configuration: Connect USB FS Port (J9) to a host PC.
    • Build command

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

        west build -p always -b ek_ra6m2 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_ra6m2 samples/subsys/usb/cdc_acm -DCONF_FILE=usbd_next_prj.conf

      • ztest udc (tests/drivers/udc):

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

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

  • DAC sample (samples/drivers/dac):

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