R-Car/Boards/S4SK

Introduction
This page is for the R-Car S4 Starter Kit board. Refer to the R-Car page for information about Renesas' R-Car SoC family. The official product page is here

Type name
Y-ASK-RCAR-S4-1000BASE-T#WS12

Hardware feature
 Equipped with R-Car S4(ws1.2)  Power connector for 5V input (incl. protection circuit) The actually consumed current or power depends on the usage configured by software and may vary. When using the power connector on the R-Car S4 Starter Kit, the input is protected against overvoltage, undervoltage and reverse polarity. The pass-through voltage range is 3.5V to 5.5V. The FPGA on this board is powered at all times, so that the board current will never drop to zero. The board will consume approx. 25mA (125mW) in the off-state. In RESET, the board will consume around 640mA (3.2W). Directly after booting the consumption.  LPDDR4X (4 GiB)  Boot device: QSPI (64 MiB)  UFS memory (128GB(SanDisk/SDINFDO4-128G))  Micro SD card slot x1  Ethernet TSN via RSwitch2: two PHYs(88E2110) for 1000BASE-T  Ethernet AVB (ETNB): 100 Mbps at G4MH  PCIe interfaces available on two OCuLink connectors (2 channels x 2 lanes) CH0(CN30) : Root Complex, CH1(CN31) : Endpoint  Debug port DBG0 and DBG1  two CAN transceivers (6-pin headers)  one LIN transceiver (4-pin headers) <li> 3 LEDs/buttons <li> Dimensions : 110 x 127 mm

AC Adapter
AC adapter may not be bundled with the board. In that case, please provide your own. Here is the AC adapter information that has been confirmed.

Where to buy
<Inquiry Model No> Y-ASK-RCAR-S4-1000BASE-T#WS12 (With AC Adapter) Y-ASK-RCAR-S4-1000BASE-WS12-JP (Without AC Adapter) R-Car S4 Starter Kit from Farnell - World wide - < Not Available > R-Car S4 Starter Kit from SHIMAFUJI ELECTRIC INCORPORATED - Japan only - < Available >

R-Car S4 SoC Documentation
https://www.renesas.com/us/en/document/mah/r-car-s4-users-manual-overview (Overview)

Board documentation
https://www.renesas.com/us/en/document/mat/r-car-s4-starter-kit-hardware-manual [Note] A schematic is attached in the board documentation.

Debug Serial

 * CN13
 * Two serial ports are recognized. Please use the younger number.

How to confirm MAC address
Check the MAC address of the board using S4_StarterKit_Configurator.exe. See R-Car/Boards/S4SK

How to build
Yocto(Linux) Xen(Hypervisor)

How to get the loader packages
Preparation
 * 1) Download ICUMX Loader and Flash writer Package here.
 * Decompress ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.xx.0.zip
 * 1) Build(see R-Car/Boards/S4SK/Yocto-Linux) U-boot, OP-TEE OS and Trusted Firmware and prepare their binaries(u-boot-elf-s4sk.srec, tee-s4sk.srec and bl31-s4sk.srec).
 * Copy binaries(u-boot-elf-s4sk.srec, tee-s4sk.srec and bl31-s4sk.srec) to ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.xx.0 folder

Windows user
 <li> Connect the Windows PC to the S4SK(CN13) with a USB serial cable </li> baudrate : 921600 <li> SW3 : Set to SCIF Download(DL) mode </li> <li> Power ON (SW5) </li> SCIF Download mode (w/o verification) (C) Renesas Electronics Corp. -- Load Program to SystemRAM --- please send ! <li> Execute TeraTerm macro "Flash_Bootloader_S4SK.ttl" </li> Teta Term: Control -> Macro ->  ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.xx.0/Flash_Bootloader_S4SK.ttl The following log is output: Flash writer for R-Car S4 Series Rev.0.13.0 Jan.16,2023 > xls2 ===== Qspi/HyperFlash writing Command =============

(snip)

SAVE SPI-FLASH....... complete!

= Qspi/HyperFlash Save Information
=========== SpiFlashMemory Stat Address : H'00F80000 SpiFlashMemory End Address : H'0101BD2A

=
==============================================

> <li> Power OFF (SW5) </li> <li> SW3 : Set to default mode </li> </ol>

R-Car S4 Starter Kit Configuration Tool (S4_StarterKit_Configurator.exe)
You can download here Please download the latest Configuration Tool. See board manual for details.

How to use

 * 1) Connect the Windows PC to the S4SK(CN13) with a USB serial cable.
 * 2) Close the terminal program
 * If COM port Channel B(large COM port number) is blocked, e.g. by a terminal program, the configuration tool cannot communicate with the hardware.
 * 1) Execute S4_StarterKit_Configurator.exe
 * Tips
 * S4SK_tools_err.jpg
 * If above is displayed, use a larger resolution display or check the following disply setting of your Win PC.
 * Ex)
 * S4SK_disp_ok.jpg

Tab of S4 Starter Kit

 * The information shown will include the PCB version, the SoC version, the FPGA version, the PCB serial number, COM port number(ChA and ChB) and MAC address.

Tab of SoC mode configuration

 * This tab allows to set the SoC mode pins.

Tab of On-board peripheral configuration

 * This tab allows to enable or disable features of the R-Car S4 Starter Kit.

Tab of Power configuration

 * This tab allows to make power and reset configurations of the R-Car S4 Starter Kit.

Tab of DIPSW

 * This tab shows the current DIPSW settings of the R-Car S4 Starter Kit.

How to write FPGA

 * If changed, press either "Write FPGA(volatile)" or "Write FPGA(non-volatile)".
 * If "Write FPGA(non-volatile)" is pressed, the setting remains even if the power is turned off.
 * To return to the initial state, press "Set defaults".

How to use two COM ports
When S4SK and CN13 are connected with a USB cable, two COM ports appear(Ex COM27 and COM28). You can confirm them using S4_StarterKit_Configurator.exe ChB(COM27) is disabled by default Enable HSCIF1/SCIF0 of ChB and push "Wite FPGA (non-volatile)" Confirmation of ChB(COM28) communication

Note: Use HSCIF0 and HSCIF1 since the SDK v3.16.0/v3.16.1 doesn't support HSCIF2 and HSCIF3

Debug0(CN10)

 * Following parts are required in order to connect the E2 Emulator to Debug 0 of the R-Car S4 Starter Kit:
 * [A] SICA20I2P
 * [B] RTE0T00020KCA10000R
 * Debug0.jpg

Debug1(CN2)

 * The signal DCU1_RDY# is not connected by default, therefore the cores ICUMH and G4MH CANNOT be debugged.
 * If you want to use Debug1, add a 0Ω resistor to R309 at your own risk.

Debug case

 * {| class="wikitable"

! !! Debug0 [ Target CPU core ] !! Debug1 [ Target CPU core ] !! Debug0 [ Connection type ] !! Debug1 [ Connection type ] ! Case1 !! ICUMX !! - !! JTAG/LPD !! - ! Case2 !! CoreSight !! - !! JTAG !! - ! Case3 !! ICUMX !! CoreSight !! JTAG/LPD !! JTAG(*1) ! Case4 !! G4MH(ICUMH) !! - !! JTAG/LPD(*2) !! - ! Case5 !! ICUMX !! G4MH(ICUMH) !! JTAG/LPD !! JTAG/LPD(*3) ! Case6 !! G4MH(ICUMH) !! CoreSight !! JTAG/LPD(*2) !! JTAG(*1)
 * }
 * (*1)：Debugging from Debug1 supports only hot plug-in connection
 * (*2)： If the Boot Processor is ICUMX, a hot plug-in connection is recommended. (Normal connection may conflict with IPL execution on ICUMX)
 * (*3)： The signal DCU1_RDY# is not connected by default, therefore the cores ICUMH and G4MH cannot be debugged.

Known issues & Restrictions

 * 1) [Affected PCB version : v2.10] Simultaneous usage of Debug 0 and Debug 1 is not available.
 * 2) [Affected PCB version : v2.10] Connector CN2, “Debug 1” is intended to debug Arm CoreSight. By specification ICU-MH and G4MH cores are not supported.
 * The signal RDY# is not connected by default, therefore the cores ICUMH and G4MH cannot be debugged.
 * To be able to debug these cores, the resistor R309 needs to be assembled at your own risk.
 * 1) [Affected PCB version : v2.10] External tracing is not available.
 * Internal tracing is available. The amount of traced data depends on the size of the internal trace memory (G4MH: 64 KiB, ARM: 32 KiB).