EK‐RA4W1 Sample and Demo hardware configuration

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

Default HW configuration

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

Emulator configuration:

Emulator	Channel	Configurations
ESW1	2	On

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_ra4w1 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_ra4w1 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-RA4W1	SCI1	TXD1	P213	Loopback to RXD1 pin
  		RXD1	P212	Loopback to RXD1 pin

  • Build command:

    west build -p always -b ek_ra4w1 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_ra4w1.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_ra4w1.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-RA4W1	SPI1	MISOB	P110	Loopback to MOSIB
    		MOSIB	P109	Loopback to MISOB

  • Build command:

    west build -p always -b ek_ra4w1 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-RA4W1	SPI1	MISOB	P110	Loopback to MOSIB
    		MOSIB	P109	Loopback to MISOB

  • Build command:

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

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_ra4w1 tests/drivers/adc/adc_api
    

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

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

    

  • Build command:

    west build -p always -b ek_ra4w1 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_ra4w1 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-RA4W1	PWM1	P105	GTIOC1A	PWM output, loopback to PWM capture pin
    	PWM4	P205	GTIOC4A	PWM capture, loopback to PWM output pin

  • Build command:

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

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

• DAC sample (samples/drivers/dac):

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

Hardware connection for I2C sample

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

  • Hardware configuration:

    GY271	EK-RA4W1
    VCC	P3V3
    GND	GND
    SCL	P204 (SCL0)
    SDA	P407 (SDA0)
    DDBY	-

  • Build command:

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