From eLinux.org
Jump to: navigation, search


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


R-Car S4 Starter Kit board is on sale.


Type name



[Top view]

Top view

[Bottom view]

Bottom view

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)
  • 3 LEDs/buttons
  • 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.

    Type Name Where to buy
    SMI36-5-V-P6 Click to buy from Digi-Key
    Click to buy from Mouser
    SW4127I Click to buy from here

    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 SHIMAFUJI ELECTRIC INCORPORATED - Japan only - < Available >
    R-Car S4 Starter Kit from SHIMAFUJI ELECTRIC INCORPORATED - World wide - < Available >

    R-Car S4 SoC Documentation

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

    Board documentation

    [Note] A schematic is attached in the board documentation.

    Debug Serial

    Two serial ports are recognized. Please use the younger number.
    Baudrate 921600
    Data 8-bit
    Parity none
    Stop bits 1

    Specification of DIP SW (SW3)

    DIP SW information
    SW Usage When on When off Description Default
    SW3-1 MD1 L H Boot device selection [0] On
    SW3-2 MD2 L H Boot device selection [1] On
    SW3-3 MD3 L H Boot device selection [2] Off
    SW3-4 MD4 L H Boot device selection [3] On
    SW3-5 MD5 L / enabled H / disabled Secure authorization Off
    SW3-6 MD6 L / ICU-MXB H / CR52 Master boot processor On
    SW3-7 -
    SW3-8 -
    MD[4:1] Pins – Selection of Boot Device (SW On = 0 / Off = 1)
    MD4 MD3 MD2 MD1 Selection of Boot Device
    0 1 0 0 Serial flash ROM boot at single read 40MHz using DMA
    1 1 1 1 SCIF Downloading mode
    MD6 Pin – Selection of Master Boot Processor (SW On = 0 / Off = 1)
    MD6 Selection of Master Boot Processor
    0 Booted through ICUMXA (Initial setting)
    1 Booted through Cortex-R52

    How to confirm MAC address

    Check the MAC address of the board using S4_StarterKit_Configurator.exe.
    See R-Car/Boards/S4SK#Tab_of_S4_Starter_Kit

    How to build


    How to flash/update the loader

    Information list of image for S4 Starter Kit (QSPI Flash)

    Write data information
    Filename Program Top Address Qspi Save Address Description
    bootparam_sa0.srec 0xEB200000 0x0000000 ICUMX IPL (boot parameter)
    icumx_loader.srec 0xEB210000 0x0040000 ICUMX IPL
    cert_header_sa9.srec 0xEB230000 0x0240000 ICUMX IPL (certification)
    dummy_fw.srec 0xEB240000 0x0280000 Dummy firmware (Instead of secure firmware)
    dummy_rtos.srec 0xE2100000 0x0500000 Dummy RTOS (Instead of CR main OS)
    dummy_g4mh_case0.srec 0x00000000 0x0900000 Dummy G4MH program image
    dummy_icumh_case1.srec 0x00500000 0x0380000 Dummy ICUMH program image
    bl31-s4sk.srec 0x46400000 0x0E00000 Trusted Firmware-A (BL31)
    tee-s4sk.srec 0x44100000 0x0E80000 OP-TEE OS
    u-boot-elf-s4sk.srec 0x50000000 0x0F80000 U-Boot

    How to get the loader packages


    1. Download ICUMX Loader and Flash writer Package here.
      Decompress ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.16.xx.zip
    2. Build(see R-Car/Boards/S4SK/Yocto-Linux#Building_the_BSP_for_R-Car_S4_Starter_Kit) 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.16.xx folder

    How to flash/update manually

    1. Connect the Windows PC to the S4SK(CN13) with a USB serial cable
    2. baudrate : 921600
    3. SW3 : Set to SCIF Download(DL) mode
    4. SW3
      Default SCIF DL mode
      SW3.1 On Off
      SW3.2 On Off
      SW3.3 Off Off
      SW3.4 On Off
      SW3.5 Off Off
      SW3.6 On On
      SW3.7 Off Off
      SW3.8 Off Off
    5. Power ON (SW5)
    6.  SCIF Download mode (w/o verification) 
       (C) Renesas Electronics Corp. 
      -- Load Program to RT-SRAM ---------------
      please send !
    7. Execute TeraTerm macro "Flash_Bootloader_S4SK.ttl"
    8. Teta Term: Control -> Macro -> ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.16.xx/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 =============
      SAVE SPI-FLASH....... complete!
      ======= Qspi/HyperFlash Save Information  =================
       SpiFlashMemory Stat Address : H'00F80000
       SpiFlashMemory End Address  : H'0101BD2A
    9. Power OFF (SW5)
    10. SW3 : Set to default mode

    How to flash/update by using "Renesas BSP ROM Writer"

    "Renesas BSP ROM Writer" is available as a loader flash tool.

    Windows User

    1. Download
      Go to https://github.com/morimoto/renesas-bsp-rom-writer
      Click "Code" button -> "Download Zip"
    2. Unzip
      Unzip renesas-bsp-rom-writer-master.zip
    3. Download ICUMX loader and copy the built binaries(u-boot-elf-s4sk.srec, tee-s4sk.srec and bl31-s4sk.srec)
      See 1 and 2 of R-Car/Boards/S4SK#How_to_get_the_loader_packages
    4. Execute ttl file
      Tera Term -> Control -> Macro -> renesas-bsp-rom-writer\board\s4_sk\windows\yocto_writer.ttl
      Follow the instructions and flash the loader.
      [Note] If "Select srec binary dir for" is displayed, select the "ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.16.xx" folder.

    Linux(Ubuntu) User

    1. Download
      $ git clone https://github.com/morimoto/renesas-bsp-rom-writer
    2. Install necessary packages (only one time)
      $ ${renesas-bsp-rom-writer}/script/tool_install.ubuntu
    3. Download ICUMX loader and copy the built binaries(u-boot-elf-s4sk.srec, tee-s4sk.srec and bl31-s4sk.srec)
      See 1 and 2 of R-Car/Boards/S4SK#How_to_get_the_loader_packages
    4. Flashing loader
      $ cd ${PATH}/ICUMX_Loader_and_Flashwriter_Package_for_R-Car_S4_Starter_Kit_SDKv3.16.xx/
      $ ${renesas-bsp-rom-writer}/board/s4_sk/linux/sdk_writer

    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.
    3. Execute S4_StarterKit_Configurator.exe
      If above is displayed, use a larger resolution display or check the following disply setting of your Win PC.

    Tab of S4 Starter Kit

    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

    SoC mode configuration

    • This tab allows to set the SoC mode pins.

    Tab of On-board peripheral configuration

    On-board peripheral configuratio

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

    Tab of Power configuration

    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(CN13) and Host PC 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

    If you wanto to use ChB, please enable HSCIF1/SCIF0 of ChB and push "Wite FPGA (non-volatile)"

    Confirmation of ChB(COM28) communication

    1) Boot Linux using ChA(COM27)
    2) Set baudrate for ChB(COM28)
    $ stty -F /dev/ttySC1 speed 115200
    3) Open terminal program(baudrate = 115200) using ChB(COM28)
    4) Output strings to ChB on Linux(ChA)
    $ echo abcdefg > /dev/ttySC1
    abcdefg <--- Output to ChB(COM28)

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

    Debug Interface


    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


    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

    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) -
    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.
    3. [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).

    Q&A site

    If you have any questions, feel free to post them here.

    FAQ site