Renesas R-Car H3ULCB


  • The H3 Starter Kit board is designed for evaluating the features and performance of the R-CAR H3 device from Renesas Electronics and it is also used for developing and evaluating application software for these R-CAR H3.

  • The H3 Starter Kit, based on the R-CAR H3 SIP, comes with LPDDR4 @4GB in 2-channel, each 64-bit wide+Hyperflash @64MB, CSI2 interfaces and several communication interfaces like USB, Ethernet, HDMI and can work standalone or can be adapted to other boards, via 440pin connector on bottom side.

It is possible to order 2 different types of H3 Starter Kit Boards, one with Ethernet connection onboard and one with Ethernet connection on ComExpress.

R-Car starter kit


The H3ULCB board can be plugged on a Renesas Kingfisher Infotainment daughter board through COM Express connector in order to physically access more I/O. CAUTION : In this case, power supply is managed by the daughter board.

More information about the board can be found at Renesas R-Car Starter Kit website.


Hardware capabilities for the H3ULCB for can be found on the eLinux H3SK page of the board.

R-Car starter kit features


Zephyr will be booted on the CR7 processor provided for RTOS purpose.

More information about the SoC that equips the board can be found here :

Supported Features

Here is the current supported features when running Zephyr Project on the R-Car ULCB CR7:








GIC 400 interrupt controller

It’s also currently possible to write on the ram console.

More features will be supported soon.

Connections and IOs

H3ULCB Board :

Here are official IOs figures from eLinux for H3ULCB board :

H3SK top view

H3SK bottom view

Kingfisher Infotainment daughter board :

When connected to Kingfisher Infotainment board through COMExpress connector, the board is exposing much more IOs.

Here are official IOs figures from eLinux for Kingfisher Infotainment board :

Kingfisher top view

Kingfisher bottom view

Programming and Debugging

The Cortex®-R7 of rcar_h3ulcb board needs to be started by the Cortex®-A cores. Cortex®-A cores are responsible to load the Cortex®-R7 binary application into the RAM, and get the Cortex®-R7 out of reset. The Cortex®-A can currently perform these steps at bootloader level.


Applications for the rcar_h3ulcb_cr7 board configuration can be built in the usual way (see Building an Application for more details).

# From the root of the zephyr repository
west build -b rcar_h3ulcb_cr7 samples/hello_world


You can debug an application using OpenOCD and GDB. The Solution proposed below is using a OpenOCD custom version that support R-Car ULCB boards Cortex®-R7.

Get Renesas ready OpenOCD version

git clone --branch renesas
cd openocd
sudo make install

Start OpenOCD

cd openocd
sudo openocd -f tcl/interface/ftdi/olimex-arm-usb-ocd-h.cfg -f tcl/board/renesas_h3ulcb.cfg

In a new terminal session

telnet 4444
r8a77950.r7 arp_examine

Start Debugging

In a new terminal session

{ZEPHYR_SDK}/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb {APP_BUILD_DIR}/zephyr/zephyr.elf