EK_RA8D1 Hardware connection - renesas/zephyr GitHub Wiki

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

Use Debug On-Board

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

Hardware connection for UART samples

echo_bot (samples/drivers/uart/echo_bot): No additional connection.

zTest (tests/drivers/uart/uart_basic_api): No additional connection.

zTest (tests/drivers/uart/uart_async_api): Loopback for TXD and RXD

Loopback for TXD and RXD

Board	Channel	Pin function	Pin
EK-RA8D1	SCI2	TXD2	PA03
		RXD2	PA02

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>;
	status = "okay";
};

&ioport4 {
	status = "okay";
};
```

zTest (tests/drivers/spi/spi_loopback): Loopback for MISO and MOSI

Loopback for MISO and MOSI

Board	Channel	Pin function	Pin
EK-RA8D1	SPI0	MISO0	P410
		MOSI0	P411

Hardware connection for I2C sample

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

Connections:

GY271	EK-RA8D1
VCC	P3V3
GND	GND
SCL	P512 (SCL1)
SDA	P511 (SDA1)
DDBY	-

Hardware connection for Flash samples

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

Hardware connection for Entropy samples

zTest (tests/drivers/entropy/api): No additional connection.

Hardware connection for can samples

zTest (tests/drivers/can/api): No additional connection.

zTest (tests/drivers/can/timing): No additional connection.

zTest (tests/subsys/canbus/isotp/conformance): No additional connection.

zTest (tests/subsys/canbus/isotp/implementation): No additional connection.

canopennode (samples/modules/canopennode):

Hardware requirements:

Hardware connection:

 Board                 OM13099                                                  PCAN-USB
 CTX P401 (J51:7)  --> CAN0_T (J3:4)                                            ---
 CRX P402 (J52:15) --> CAN0_R (J3:2)                                            ---
 VCC (J18:4)       --> 3V3 (J3:12)                                              ---
 5V  (J18:5)       --> 5V  (J3:14)                                              ---
 GND (J18:6)       --> GND (J3:16)                                              ---
     ---               JP3 close                                                ---
     ---               JP4 close                                                ---
     ---               CAN0 (P3:upper) --> Serial cable D-SUB 9-pin female  --> CAN1

Build guideline:

Update canopenode modules

west config manifest.project-filter +canopennode
west update canopennode

Build:

west build -b ek_ra8d1 samples/modules/canopennode -DCONF_FILE="prj_no_storage.conf" -p

Test guideline:
1. Install software dependencies for PC:
- PCAN driver: PCAN-View: PEAK-System
- python-can and canopen pip packages:
```
pip3 install --user canopen python-can
```
1. Ensure source the Zephyr workspace environment variable before test
```
# Windows (use cmd)
> ./zephyr-env.cmd

# Linux
$ source zephyr-env.sh
```
1. Create a python can connection setting file placed at workspace:
  
  %%HOME%%\zephyrworkspace\zephyr\can.ini
```
[default]
interface = pcan
channel = PCAN_USBBUS1
bitrate = 125000
```
2. Flash and run examples scripts (NMT State Changes, SDO Upload, SDO Download and SDO Mapping) as guideline at canopennode

Hardware connection for ospi samples

spi_flash (samples/drivers/spi_flash): No additional connection.

jesd216 (samples/drivers/jesd216): No additional connection.

Hardware connection for SDHC samples

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

Connections:

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 (tests/drivers/sdhc): Require "--shield pmod_sd" in build command:

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

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

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

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

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

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

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

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

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

Hardware connection for ADC samples

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

zTest (tests/drivers/adc/adc_accuracy_test): loopback 3V3 and AN000 (P004)

ADC_HW_Connection

Hardware connection for PWM (GPT) samples

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

zTest (tests/drivers/pwm/pwm_loopback): Loopback 2 channels (1 PWM output, 1 PMW capture)

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

Hardware connection for Counter (AGT) samples

Counter Alarm (samples/drivers/counter/alarm): No additional connection.

Hardware connection for USB samples

USB Device
- USB-FS as device
  - Connect J11 to a host PC.
  - Configs for jumpers:
    
    Board Jumper Configurations
    
    EK-RA8D1 J12 pins 2-3
    
    J15 Close
- USB-HS as device
  - Connect J31 to a host PC
  - Configs for jumpers
    
    Board Jumper Configurations
    
    EK-RA8D1 J7 pins 2-3
    
    J17 Close
USB Mass Storage (samples/subsys/usb/mass):
```
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):
```
west build -p always -b ek_ra8d1 samples/subsys/usb/cdc_acm -DCONF_FILE=usbd_next_prj.conf
```
ztest (tests/drivers/udc):
```
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
  - Configs for jumpers:
    
    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):
```
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.

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

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

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

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

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 (tests/drivers/display/display_read_write): Require "--shield rtkmipilcdb00000be" in 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:

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:

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

Hardware connection for DAC samples

ztest (tests/drivers/dac/dac_api): No additional connection.

DAC (samples/drivers/dac): No additional connection.